Opened 8 years ago

Closed 8 years ago

#6067 closed task (fixed)

Create a mailing list for automatic censorship-detection system reports

Reported by: asn Owned by: phobos
Priority: Medium Milestone:
Component: Internal Services/Tor Sysadmin Team Version:
Severity: Keywords:
Cc: karsten, weasel, runa Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

We've been running George Danezis' anomaly-based automatic censorship-detection system in yatei, but it's classified as BETA and its results are not shown in metrics.

I tweaked its code a bit [0], and now it's capable of spitting out small daily reports of potential censorship. We can create a mailing list, and start putting those reports there, so that people interested in these things can keep an eye on them (without looking at a hundred metrics graphs every day).

I think that the mailing list should function like tor-consensus-health does. That is, it should accept mails from yatei periodically, and people will be able to subscribe and receive the reports as mails. Web archive support would also be nice.

I'm not sure if we should allow members to post, but I guess it doesn't make too much sense (although it might turn into a censorship-discussion hub where people can verify/deny or dig further into the automatic reports).

WRT the name it could be [tor-automatic-censorship-reports] but I'm fine with anything. A disclaimer in the front page, saying that the data and reports are created automatically and might not represent real censorship events, could also be useful.

Oh yeah, is there a reason on not doing this at all?

Anything else I forgot?

[0]: https://gitorious.org/metrics-tasks/metrics-tasks/commits/anomaly_detection_reports

Child Tickets

TicketStatusOwnerSummaryComponent
#6163closedAdd graph links to the posts in tor-censorship-eventsMetrics Utilities

Change History (5)

comment:1 Changed 8 years ago by runa

I think creating this list with the idea that it will turn into a censorship-discussion hub is a good idea, but I'm worried that it will turn into yet-another-support-list. We could encourage members to take the discussion to tor-talk or tor-dev if they see/find anything useful. As for a list name, how about censorship-reports, censorship-detection, or censorship-events?

comment:2 Changed 8 years ago by karsten

I like the idea.

For the name, I have a slight preference to start the name with tor- and to pick up how we refer to detector results on the metrics website, e.g., "Show possible censorship events if available." How about tor-censorship-events?

I can rather imagine how this list only contains automatically generated reports and no further discussion between humans. We shouldn't force people who'd like to discuss interesting Tor censorship aspects to receive automatically generated reports. They can take the discussion to tor-dev and link to posts on the automatic report mailing list.

comment:3 Changed 8 years ago by phobos

Component: CompanyTor Sysadmin Team

comment:4 Changed 8 years ago by karsten

What's the status here?

comment:5 Changed 8 years ago by weasel

Resolution: fixed
Status: newclosed

tor-censorship-events - automatic censorship-detection system reports

Note: See TracTickets for help on using tickets.