Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
censorship-analysis
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Jobs
  • 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.

  • The Tor Project
  • Anti-censorship
  • censorship-analysis
  • Issues
  • #40001

Closed
Open
Opened Sep 08, 2020 by Philipp Winter@phwOwner

Investigate what our default bridge statistics can teach us

Our default bridges publish the approximate number of IP addresses per country that requested the network status. One can find these numbers in the dirreq-v3-ips field of the bridge's extra-info document. As far as I know, nobody studied how these numbers change over time. I would love to learn the following:

  • Can we use these numbers to infer where a default bridge is blocked?
  • Can we see censorship events in these numbers? For example the recent network interference that happened in Belarus?
  • How do these numbers correlate with other data sets? Like BridgeDB's metrics?
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/anti-censorship/censorship-analysis#40001