Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #31661

Closed (moved)
Open
Opened Sep 06, 2019 by cypherpunks@cypherpunks

Run multiple snowflake bridges and optimize for least latency most throughput by GeoIP based route selection

After the publication of this article hundreds of Japanese people started installing the Snowflake WebExt (yay!), but despite having an Internet service that's orders of magnitudes better than the average American household, the distance between then and the nl snowflake bridge seriously impacts the throughput, so much that some snowflake proxies from Japan - despite having more than 20MB/s upload/download - can't offer a download speed bigger than 150KiB/s. What if there were for instance 5 snowflake bridges in different geographical locations in the world and the broker associated with each snowflake proxy the nearest snowflake bridge and sent this information to the user (based on GeoIP, of course, not perfect but better than the status quo)?

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: legacy/trac#31661