Changes between Version 255 and Version 256 of doc/meek


Ignore:
Timestamp:
Aug 24, 2017, 3:57:54 AM (4 weeks ago)
Author:
dcf
Comment:

Remove log of user events, which has been imported to MetricsTimeline.

Legend:

Unmodified
Added
Removed
Modified
  • doc/meek

    v255 v256  
    394394[https://metrics.torproject.org/userstats-bridge-transport.html?graph=userstats-bridge-transport&transport=meek Link to metrics.]
    395395
    396 History of events that might have affected the number of users:
    397  * ca. 2014-02 Installed meek-server on bridge already hosting websocket-server for flash proxy.
    398  * 2014-05-08 Migrated and reinstalled bridge, still running both flash proxy and meek.
    399  * ca. 2014-07-28 Enabled meek-amazon.
    400  * 2014-09-15 [https://www.torservers.net/wiki/setup/server#multiple_tor_processes Split flash proxy and meek] into separate processes in order to avoid [https://lists.torproject.org/pipermail/tor-dev/2014-September/007483.html user counting confusion]. Everything before that is baloney.
    401  * 2014-09-16 Switched meek-amazon to HTTPS (#13174).
    402  * 2014-09-29 Changed the bridge backing meek-amazon.
    403  * 2014-10-14 Enabled PublishServerDescriptor on the meek-amazon bridge. Between 09-29 and 10-14, meek-amazon users were not being counted; [https://lists.torproject.org/pipermail/tor-dev/2014-October/007611.html see here].
    404  * 2014-10-15 [https://blog.torproject.org/blog/tor-browser-40-released Tor Browser 4.0 released] with support for meek built in and adding meek-azure.
    405  * 2014-10-25 Changed the bridge backing meek-google. Upgraded the meek-google App Engine instance to [https://cloud.google.com/appengine/docs/adminconsole/performancesettings#Setting_the_Frontend_Instance_Class F2] class.
    406  * 2014-10-27 Changed meek-google back to [https://cloud.google.com/appengine/docs/adminconsole/performancesettings#Setting_the_Frontend_Instance_Class F1] class because the costs got close to the daily limit I set.
    407  * 2014-10-31 Changed meek-google to [https://cloud.google.com/appengine/docs/adminconsole/performancesettings#Setting_the_Frontend_Instance_Class F2] again.
    408  * 2014-11-08 Changed meek-google back to [https://cloud.google.com/appengine/docs/adminconsole/performancesettings#Setting_the_Frontend_Instance_Class F1].
    409  * 2014-11-15 Moved meek-google bridge to better hardware.
    410  * 2015-02-28 Altered [https://cloud.google.com/appengine/docs/adminconsole/performancesettings#Setting_the_Number_of_Idle_Instances performance settings] on App Engine in an effort to reduce instance hours. Set max idle instances to 4 and min pending latency to 500 ms.
    411  * 2015-04-08 Implemented [https://lists.torproject.org/pipermail/tor-dev/2015-April/008637.html persistent connections] for meek-azure, increasing performance.
    412  * 2015-04-15 Tor Weekly News [https://blog.torproject.org/blog/tor-weekly-news-%E2%80%94-april-15th-2015 covers the meek-azure performance improvement].
    413  * 2015-05-22 Rate-limited the meek-google bridge to 1.5 MB/s.
    414  * 2015-06-02 Further rate-limited meek-google to 1.1 MB/s.
    415  * 2015-06-08 Rate-limited the meek-amazon bridge to 1.1 MB/s.
    416  * 2015-07-20 [https://lists.torproject.org/pipermail/tor-talk/2015-July/038487.html Outage of meek-azure.]
    417  * 2015-07-22 Published [https://lists.torproject.org/pipermail/tor-talk/2015-July/038496.html workaround for meek-azure outage].
    418  * 2015-08-14 [https://lists.torproject.org/pipermail/tor-talk/2015-August/038780.html End of meek-azure outage.]
    419  * 2015-09-23 Upgraded meek-azure bridge [https://blog.linode.com/2015/06/16/linode-turns-12-heres-some-kvm/ from KVM to Xen].
    420  * 2015-09-30 [https://lists.torproject.org/pipermail/tor-talk/2015-October/039231.html Outage of meek-amazon] caused by an expired certificate.
    421  * 2015-10-02 Rate-limited the meek-azure bridge to 1.1 MB/s. (Azure grant expired.)
    422  * 2015-10-09 [https://lists.torproject.org/pipermail/tor-talk/2015-October/039234.html End of meek-amazon outage.]
    423  * 2015-10-30 Altered [https://cloud.google.com/appengine/docs/go/modules/#Go_Configuration performance settings] on App Engine. Set max idle instances to 2 and min pending latency to 1000 ms. This used to be configured through the web interface but is now configured in an application file. Some time ago, I don't know when, this change caused my settings from 2015-02-28 to be forgotten.
    424  * 2015-10-30 Further rate-limited the meek-azure bridge to 0.8 MB/s.
    425  * 2015-12-14 Enabled client IP statistics (comment:7:ticket:13171) on the meek-azure bridge.
    426  * 2015-12-20 Enabled client IP statistics (ticket:13171) on meek-google.
    427  * 2015-12-25 Established an [https://atlas.torproject.org/#details/C20658946DD706A7A2181159A1A04CD838570D04 unthrottled bridge] for people who set up their own CDN.
    428  * 2016-01-11 Enabled client IP statistics (ticket:13171) on meek-amazon.
    429  * 2016-01-14 Increased meek-azure rate limit to 3 MB/s.
    430  * 2016-01-15 Increased meek-google rate limit to 3 MB/s.
    431  * 2016-01-16 Increased meek-amazon rate limit to 3 MB/s.
    432  * 2016-01-29 [https://lists.torproject.org/pipermail/tor-talk/2016-February/040199.html Azure edge server blocked in China.]
    433  * 2016-02-02 [https://lists.torproject.org/pipermail/tor-talk/2016-February/040199.html Azure edge server no longer blocked in China.]
    434  * 2016-03-27 18:30–20:30 meek-azure TLS certificate was expired.
    435  * 2016-03-27 21:28 Began running Karsten's [https://gitweb.torproject.org/karsten/tor.git/log/?h=task-18460-2&id=b79d859 task-18460-2 branch] for IPv6 counting on meek-azure.
    436  * 2016-03-31 17:20 Switched back to running the standard Debian tor on meek-azure.
    437  * 2016-05-13 [https://lists.torproject.org/pipermail/tor-talk/2016-June/041057.html meek-reflect.appspot.com suspended]; meek-google stops working.
    438  * 2016-08-18 Changed meek-amazon [https://aws.amazon.com/cloudfront/pricing/ price class] from "All" to "Use Only US, Canada and Europe."
    439  * 2016-10-28 Reset meek-amazon rate limit to 1 MB/s (it had apparently been at 3 MB/s since about 2016-09-28).
    440  * 2016-10-30 Increased meek-amazon rate limit back to 3 MB/s.
    441  * 2016-11-22 Decreased meek-amazon rate limit to 2 MB/s.
    442  * 2017-01-09 Decreased meek-azure rate limit from 3 MB/s to 2 MB/s.
    443  * 2017-03-03 17:32 [https://lists.torproject.org/pipermail/tor-project/2017-March/000981.html Stopped CDN endpoint az668014.vo.msecnd.net (meek-azure).]
    444  * 2017-03-03 17:34 [https://lists.torproject.org/pipermail/tor-project/2017-March/000981.html Stopped CDN endpoint az786092.vo.msecnd.net (meek-azure).]
    445  * 2017-03-03 17:36 [https://lists.torproject.org/pipermail/tor-project/2017-March/000981.html Stopped CDN endpoint meek-reflect.azureedge.net (wasn't being used).]
    446  * 2017-03-07 [https://blog.torproject.org/blog/tor-browser-651-released Tor Browser 6.5.1 released], with a new working meek-azure configuration.
    447  * 2017-03-22 [https://lists.mayfirst.org/pipermail/guardian-dev/2017-March/005220.html Orbot 15.4.0 beta-2 multi released], with a new working meek-azure configuration.
    448  * 2017-04-30 meek-amazon bridge upgrades to [https://gitweb.torproject.org/pluggable-transports/meek.git/log/?id=0.27 0.27].
     396For a log of events that might have affected the number of users, see the entries with "meek" in the "protocols" column at [[MetricsTimeline]].
    449397
    450398== Costs ==