Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
Depictor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Network Health
  • Depictor
  • Issues
  • #3

Closed
Open
Created Oct 19, 2016 by teor@teor

Make it easier for relay operators to find their observed bandwidth

Hi tom, thanks for legacy/trac#20372 (moved), makes a big difference to relay operators.

I was answering another relay operator question today, and realised I needed the observed bandwidth. Because they were measured high, but then limited by the observed bandwidth.

Is that the sort of thing we can put on consensus health? Under the fingerprint? (Because it's set by the relay, not an authority.) Or another row? Also, should we show the consensus weight?

Or is that just too confusing, and I should direct them to use Atlas, and hover over the bandwidth heading? (If it works, which it doesn't on high security tor browser.)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None