Closed
Milestone
Jun 1, 2020–Mar 31, 2023
Sponsor 30 - Objective 2.3
Objective O2: Ensure users in target countries have access to the best Tor bridge options for circumventing censorship.
O2.3 - Develop new and/or improve existing bridge selection and distribution strategies.
- A1 - Develop new and/or improve existing bridge selection and distribution strategies based on data collected about successful, effective methods per evaluation during O1.1.
- A2 - Develop methods to present bridges to users based on their location, potentially incorporating relevant censorship data published by OONI.
- A3 - Improve ability for bridgedb/authority to test bridges that only expose a pluggable transport.
- A4 - Update bridgeDB/gettor to give region-specific recommendations for PT and bridges.
Unstarted Issues (open and unassigned)
0
Ongoing Issues (open and assigned)
0
Completed Issues (closed)
59
- TPA team · Debugging domain fronting access to conjure station
- Tor Browser · Designing the User Interface of Conjure in Tor Browser
- Tor Browser · Integrate the Conjure PT into alpha versions of Tor Browser
- conjure · Implement conjure as a pluggable transport
- rdsys · run tests in the gitlab CI
- bridgestrap · review CollecTor metrics
- rdsys · document what gettor does and how is implemented
- bridgestrap · CollecTor metris reports all bridges as non-functional
- BridgeDB · Go through process of distributing private bridges
- BridgeDB · change email distributor to provide obfs4 transport by default
- Tor · Remove distribution methods from BridgeDistribution option
- conjure · Create a local test environment for Conjure client, relay station, and bridge
- conjure · Create a Tor PT server for Conjure
- conjure · Create a Tor PT client for conjure
- Team · Implement conjure as a pluggable transport
- BridgeDB · run the tests on the gitlab CI
- BridgeDB · "Just give me bridges!" should use the default transport of the Advanced Options
- BridgeDB · Attach the QR code of bridges in the email sent by bridges.torproject.org
- bridgestrap · Bridgestrap should export bulk sanitized state for Collector
- rdsys · Create a dummy distributor for educational purposes
- rdsys · Integrate GetTor into rdsys
- rdsys · Document how rdsys tests bridges
- bridgestrap · Create a Prometheus dashboard for bridgestrap metrics
- bridgestrap · Tor's dormant mode breaks bridgestrap
- rdsys · Where is rdsys's memory leak?
- bridgestrap · Follow Prometheus's suggestions on metrics and label naming
- rdsys · Make supported resources configurable
- Tor · Make it possible to forget bridge descriptors before SETCONF
- rdsys · Allow resource status lookup by hashed fingerprint
- rdsys · Take into account bridge-distribution-request field
- bridgestrap · Make cache timeout configurable
- rdsys · Make type parameter of resource status optional
- bridgestrap · Add field to test result that reveals when a bridge was last tested
- rdsys · Pool bridgestrap test requests for increased efficiency
- bridgestrap · Deploy bridgestrap on polyanthum
- rdsys · Refactor rdsys's domain logic
- bridgestrap · Make bridgestrap export metrics
- rdsys · Collapse Salmon's social graph into root nodes to preserve privacy
- rdsys · Devise a user ID for Salmon
- rdsys · Implement persistence mechanism for resources
- rdsys · Build API that lets resources register themselves
- rdsys · Reimplement and generalise BridgeDB?
- rdsys · Implement the Salmon bridge distribution mechanism
- wolpertinger · Make wolpertinger fetch OONI's test results from raw data cans
- wolpertinger · Set up a domain-fronted end point for wolpertinger
- wolpertinger · Make wolpertinger create usage metrics
- trac · Go through process of distributing private bridges
- trac · Automatically test the PTs of bridges
- trac · Evaluation of bridge statistics
- pluggable transports · Look into alternatives for distributing bridge info to clients
- pluggable transports · Look into getting default Tor bridges scanned by external reachability tests
- pluggable transports · Get default bridges checked for reachability by OONI
- lyrebird · Reachability tests for new obfs4 bridges
- censorship-analysis · Create a shim that hooks up wolpertinger with bridgestrap
- BridgeDB · Make BridgeDB take into account its BlockedBridges table
- BridgeDB · Reimplement and generalise BridgeDB?
- BridgeDB · Implement a feedback loop between BridgeDB and OONI
- BridgeDB · Implement the Salmon bridge distribution mechanism
- BridgeDB · O2.3 - Develop new and/or improve existing bridge selection and distribution strategies.
Loading
Loading
Loading