Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #3223

Closed
Open
Created May 18, 2011 by Roger Dingledine@armaDeveloper

bridgedb's reserved bridge emails should annotate bridges by stability

Right now in the emails that bridgedb sends out for its reserved bridges, the order of bridges seems pretty arbitrary. My guess is that it's based on whatever order they appear in the db.

Once we've sent out 10 days worth of bridges though, some of these bridges have been in the "Bridges still RUNNING since the last email I sent you:" list for all 10 of those days. We should make it clearer which ones are stable.

One approach would be to annotate the address like

128.31.0.34:9101    (8 days at this address)

and then sort the bridges by stability in the email we send.

Assignee
Assign to
Time tracking