webconnectivity 0.6: flag server side blocking #2269
Labels
enhancement
improving existing code or new feature
methodology
issues related to the testing methodology
needs investigation
This issue needs extra data and investigation
ooni/probe-engine
priority/medium
As part of the upcoming OONI Probe CLI v3.16.0 release, we're introducing incremental improvements to our web measurement methodology ("Web Connectivity"). We labelled these improvements "Web Connectivity v0.5" in #2237.
For v3.16.0, Web Connectivity v0.5 will only be available to
miniooni
users. We need additional research to confirm the improved experiment is working as intended. If everything is smooth, we expected v0.5 to be available toooniprobe
users as part of the v3.17.0 release cycle.While v0.5 lands and stabilizes, it is worth starting to aim at subsequent changes. Drawing from our "websteps" research implementation (https://github.com/bassosimone/websteps-illustrated/), I would argue that one of the most important low hanging fruits to the Web Connectivity lineage is the possibility of flagging server side blocking. We should be able to flag possible server side blocking as an anomaly inside the probe and we should also support pipeline side flagging.
The text was updated successfully, but these errors were encountered: