Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #10968

Closed (moved)
Open
Opened Feb 20, 2014 by George Kadianakis@asn

Authorities should use past consensuses to decide how to vote on relay flags

At the moment, each authority decides what flags to assign to each node based on its own memory. This means that authorities that have been started recently have a different impression -- compared to more long-lived authorities -- about some relays .

Something that might make more sense is if authorities used past consensuses to get a better idea about the stability and speed of relays.

Since authorities don't keep past consensuses around, a way to do the above might be to create a script that each authority runs, downloads the past consensuses, calculates statistics about all nodes, and then it creates a file with those statistics. Then the authority loads that file, and uses it to update its knowledge base.

There might be better approaches.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#10968