Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #6067

Closed (moved)
Open
Opened Jun 05, 2012 by George Kadianakis@asn

Create a mailing list for automatic censorship-detection system reports

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?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#6067