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 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • 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
  • #40022
Closed
Open
Created Aug 26, 2019 by Philipp Winter@phwReporter

Recruit potential default bridges from set of long-running bridges

We would like to set up more default bridges. One way to recruit more is to look for non-default bridges that have 1) high capacity, 2) have been around for a long time, and 3) have a stable uptime. Ideally, we should also know the person who runs the bridge, as stated in our list of criteria for setting up a new default bridges.

Let's have a look at archived bridge data and extract a list of default bridge candidates.

Assignee
Assign to
Time tracking