Opened 9 years ago

Closed 8 years ago

Last modified 8 years ago

#5867 closed task (fixed)

Devise methodology taxonomy.

Reported by: phobos Owned by: hellais
Priority: Medium Milestone:
Component: Archived/Ooni Version:
Severity: Keywords: SponsorH201206
Cc: ioerror, isis Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description


Child Tickets

Change History (7)

comment:1 Changed 9 years ago by phobos

Original goal is to:

"research various surveillance and censorship methodologies in order to understand what are their false positive/false negative rates. We will produce high level descriptions of how the tests will work as well as in-depth technical descriptions. In describing the methodology we will focus on explaining the meaning and predicted accuracy of returned results."

comment:3 Changed 9 years ago by hellais

Cc: ioerror isis added

comment:4 Changed 8 years ago by hellais

I believe the description of this deliverable was a bit ambiguous. What I think we really meant is that we should devise a "Testing Methodology" as in a way to describe, implement and perform tests.

We should then also specify what is the taxonomy for people that are interested in deploying censorship and surveillance. This second point does not necessarily impact directly censorship detection measurements, but rather censorship circumvention technology.

For this reason I think we should focus on the first point.

comment:5 Changed 8 years ago by hellais

Status: newneeds_review

The methodology section should now be complete: https://trac.torproject.org/projects/tor/wiki/doc/OONI/Methodology.

I concluded that it was not possible to distill the risk level in a number from 1 to 5 since this is very country specific and such metric would lead the user to be tricked into believing that such an absolute truth exists. I think it's best to formalize the description of a test the risk analysis contextual to the countries should be delegated to other people.

For the time being the "Censorship Taxonomy" has not been removed. I think that is somewhat out of scope and should probably removed.

ioerror, isis: what do you think?

comment:6 Changed 8 years ago by isis

Resolution: fixed
Status: needs_reviewclosed

Good work, hellais!

I apologise, I had assumed this was finished and wondered why you hadn't closed it. I re-reviewed and made a few changes to fix typos, and to improve clarity and lexicographic variety. Overall it looks great, and I'm going to mark it done.

I'm also unsure if we should keep the Censorship Taxonomy section, so I shortened it a bit. We may want to keep and revise it so that we can potentially write a followup paper to Leberknight et al. If either ioerror or hellais is against keeping this, we can delete it later.

comment:7 Changed 8 years ago by karsten

Keywords: SponsorH201206 added
Milestone: Sponsor H: June 2012

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

Note: See TracTickets for help on using tickets.