CHchris-dickson·Jan 20, 2016
Thanks for this! I opened an issue for it.
https://github.com/unchartedsoftware/torflow/issues/4
In TorFlowunchartedsoftware
torflow
JavaScript2016–2016
unchartedsoftware / torflow · Archived
torflow
Data flow in the Tor network
3Distinct people
4Mentions
0Explicit recommenders
539GitHub stars
What to know before exploring
What it is
Data flow in the Tor network
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by hour4 dated mentions
Observed mentions: 2016-01-20 14:42:05 UTC to 2016-01-20 19:34:57 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jan 20, 14:00 | 2016-01-20 14:00:00 UTC | 2016-01-20 15:00:00 UTC | 1 | 0 | 1 |
| Jan 20, 15:00 | 2016-01-20 15:00:00 UTC | 2016-01-20 16:00:00 UTC | 0 | 0 | 0 |
| Jan 20, 16:00 | 2016-01-20 16:00:00 UTC | 2016-01-20 17:00:00 UTC | 0 | 0 | 0 |
| Jan 20, 17:00 | 2016-01-20 17:00:00 UTC | 2016-01-20 18:00:00 UTC | 1 | 0 | 1 |
| Jan 20, 18:00 | 2016-01-20 18:00:00 UTC | 2016-01-20 19:00:00 UTC | 1 | 0 | 1 |
| Jan 20, 19:00 | 2016-01-20 19:00:00 UTC | 2016-01-20 20:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
4 sourcesVery classy visualization! Have a look at the code that determines the visual flow of data between relays: https://github.com/unchartedsoftware/torflow/blob/master/pub...
I think it doesn't exactly reflect how paths are chosen based on relay bandwidth scores, if we compare to the actual path selection algorithm: http://tor.stackexchange.com/a/114
I might be missing something, but it seems that relay same-family and same-/16-subnet exclusions are ignored. This might bias the visualization to increase the apparent traffic between popular nodes, while in reality, the traffic should be slightly more evened out with less popular nodes. Hard to tell if this effect makes any visible difference without analyzing the data, though. Either way, because of the way the code is structured, it shouldn't be too hard to fix: just simulate full paths inste
Read the rest
ad of single connections between nodes.
Because the nodes in a path are determined randomly, with weighting based on publicly available scores, you can simply estimate the amount of traffic between any two given nodes. Here's a summary of how routes are chosen:
http://tor.stackexchange.com/a/114
And here's the code that does the traffic estimation based on node bandwidth scores (edit: hmm, seems that code might be slightly inaccurate, added a top level comment to point this out...):
https://github.com/unchartedsoftware/torflow/blob/master/pub...
In TorFlowAnd the source: https://github.com/unchartedsoftware/torflow
In TorFlow