-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the analysis methodology for detecting throttling #1406
Comments
- outline the current methodology; - explain its theoretical assumptions; - describe limitations; - mention possible future directions. Part of ooni/ooni.org#1406.
I have documented the theory used by the probe to collect data useful to detect throttling (see above). |
- outline the current methodology; - explain its theoretical assumptions; - describe limitations; - mention possible future directions. Part of ooni/ooni.org#1406. Closes #684 because we've now gone full circle and we have infrastructure to setup a comparable experiment via richer input without the need of *implementing* a new experiment. --------- Co-authored-by: DecFox <33030671+DecFox@users.noreply.github.com>
I merged ooni/probe-cli#1546, that explains the methodology and the theory we use on the probe side of things. I am not sure whether we also want a backend-side documentation of this. I'll remove myself as an assignee from this issue and assign to @jbonisteel such that she can evaluate this topic and coordinate with other team members. |
Will close this epic for now since it focuses on the engine side of things. |
No description provided.
The text was updated successfully, but these errors were encountered: