Skip to content

GitLab

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

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
  • Metrics
  • Analysis
  • Issues
  • #28555

Closed
Open
Opened Nov 21, 2018 by Roger Dingledine@armaReporter

Assess methodology for modern privcount Tor user counts

With our traditional user count methods, based on extrapolating from consensus fetch counts -- and assuming each client is online all day -- we see approximately 2 million daily users.

The IMC 2018 paper estimates closer to 8 million daily users: https://www.ohmygodel.com/publications/tor-usage-imc18.pdf

Understanding how many users we have is a critical building block for Isabela's "user retention" cycle. It also turns out to really impact how other large organizations view us: from Mozilla's perspective, 8 million daily users is wildly more attractive than 2 million daily users, and similarly with larger numbers we're in a position to negotiate funding for a spot in the search box. And third, understanding our user base helps us understand the capacity of the Tor network, by making us better able to predict how Tor would handle an influx of n million new users (from Brave, from Firefox private browsing mode, or from other apps that integrate Tor and then become popular).

We should figure out what we think about this paper's counting methodology, and either (1) identify follow-up research questions that we need to investigate to convince ourselves that this newer number is more right, or (2) decide that the methodology is solid, in which case we should (a) tell the world about it in a blog post or similar, (b) update our various documentation and metrics graphs, and (c) figure out a way to deploy ongoing user count measurements with this new approach.

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: tpo/metrics/analysis#28555