Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • rdsys rdsys
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • rdsysrdsys
  • Issues
  • #63
Closed
Open
Issue created Sep 24, 2021 by Gus@gus🍕Reporter

Moat bucket shouldn't have non-obfs4/vanilla bridges

While doing some data visualization for tpo/network-health/team#115 (comment 2750865), I noticed that we have more than 200 bridges without any pluggable transport enabled on Moat bucket. Talking with Richard, it looks like Tor Browser only requests obfs4 bridges using Moat. So, these bridges aren't being used at all.

We could reallocate these vanilla bridges on another bucket and move more obfs4 bridges from other buckets to Moat, as this is the most popular way to fetch Tor bridges.

bridgedb-buckets

moat-bucket-non-obfs4-bridges_2021-09-23T21_50_49.71273-03_00.csv

Assignee
Assign to
Time tracking