Opened 4 years ago

Closed 3 years ago

#16818 closed defect (fixed)

Publishing Download Stats

Reported by: mrphs Owned by: Sebastian
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Normal Keywords: stats, UX, metrics
Cc: isabela, mikeperry, karsten, brade, mcs, pde Actual Points:
Parent ID: Points:
Reviewer: Sponsor:



It has come up a couple of times that having and publishing the number of downloads from Tor website would be very useful in many ways.

The most recent case is a proposal Isabela and some of us are working on. This numbers are super useful for usability related projects.

Some of the things I find useful to have:

  • Total number of downloads for the latest version of Tor Browser (Bonus point if we can break this into 'dist' and 'download page')
  • Total number of successful updates, to the latest Tor Browser
  • Total number of failed updates
  • Total number of downloads for Tor source and packages (Bonus point if we can break this into 'dist', 'download page' and 'official *nix' repos)

Child Tickets

Change History (9)

comment:1 Changed 4 years ago by mrphs

I wasn't sure whether it should be under website or sysadmin component. Please change it to whatever is more accurate.

comment:2 Changed 4 years ago by mrphs

Keywords: metrics added; removed

comment:3 Changed 4 years ago by Sebastian

Cc: karsten added

Adding Karsten who has worked on stats before iirc

comment:4 Changed 4 years ago by arma

Cc: karsten removed

Sounds great.

In the distant past, we did some webalyzer style stats on our apache logs. Runa probably knows best what we did back then.

For those observers on the ticket, I should remind us all that our apache logs don't include IP address, and round timestamps to midnight. The goal is to avoid having anything that some external attacker might find useful:

comment:5 Changed 4 years ago by arma

Cc: karsten added

(Wow. Apparently trac tries to merge multiple comments at once, and has bugs in its merge. Awesome. Adding Karsten back.)

comment:6 Changed 4 years ago by mcs

Cc: brade mcs added

comment:7 Changed 4 years ago by mikeperry

Cc: pde added

For downloads, we can use something like, which hashes IPs with an ephemeral salt/key that rotates every so often. Unfortunately, it uses MD5, which is less than ideal. I think the EFF uses something like this. Perhaps they updated it to SHA?

Updates are trickier, because they always come through the Tor network, so we'll have many people using the same exit IP to check for and download updates, so it will be harder to filter out repeat downloads/failures/etc. The updates themselves are also (sometimes, depending on network conditions) downloaded in HTTP range requests (partial chunks), so there are often (but not always) a variable number of requests from the same user.

Last edited 4 years ago by mikeperry (previous) (diff)

comment:8 Changed 4 years ago by mrphs

Keywords: UX added; usability removed
Severity: Normal

comment:9 Changed 3 years ago by Sebastian

Resolution: fixed
Status: newclosed is a thing.

Note: See TracTickets for help on using tickets.