aboutsummaryrefslogtreecommitdiff
path: root/proposals/201-bridge-v3-reqs-stats.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2012-05-10 15:33:59 -0400
committerRoger Dingledine <arma@torproject.org>2012-05-10 15:33:59 -0400
commitb1be41c7337d3d642ed646b47970843ffffc7771 (patch)
tree39856249b08e150c88fc82c143413c3d29fb5e52 /proposals/201-bridge-v3-reqs-stats.txt
parent00e515a56bb9cb67d37a05f3697436abacd1daad (diff)
downloadtorspec-b1be41c7337d3d642ed646b47970843ffffc7771.tar.gz
torspec-b1be41c7337d3d642ed646b47970843ffffc7771.zip
add key missing word
Diffstat (limited to 'proposals/201-bridge-v3-reqs-stats.txt')
-rw-r--r--proposals/201-bridge-v3-reqs-stats.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/201-bridge-v3-reqs-stats.txt b/proposals/201-bridge-v3-reqs-stats.txt
index 7ac6e56..67d8c00 100644
--- a/proposals/201-bridge-v3-reqs-stats.txt
+++ b/proposals/201-bridge-v3-reqs-stats.txt
@@ -9,7 +9,7 @@ Overview:
Our current approach [0] to estimate daily bridge users is based on
unique IP addresses reported by bridges, and it is very likely broken.
- A bridge can connect to two or more bridges, so that unique IP address
+ A bridge user can connect to two or more bridges, so that unique IP address
sets overlap to an unknown extent. We should instead count requests for
v3 network statuses, sum them up for all bridges, and divide by the
average number of requests that a bridge client makes per day. This