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
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

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
  • #21389

Closed (moved)
Open
Opened Feb 03, 2017 by cypherpunks@cypherpunks

Support searches for effective family (strict and non strict maching)

I maintain a list of top exit/guard/middle/cw effective families [1]. Every entry is uniquely defined by the sorted list of effective family members (effective_family).

I'd like to make every entry clickable (link to atlas), which would list all relays that make up that entry. To be able to use atlas for this, onionoo needs to support it first unless atlas emulates this by making multiple fingerprint= onionoo backend requests.

onionoo currently offers the 'family' [2] parameter which will give you all effective family members for a given relay fingerprint (which is not what I'm looking for).

[1] example for top eff. families by CW: https://raw.githubusercontent.com/ornetstats/stats/master/o/main_families_by_cw.txt

[2]

family Return only the relay whose fingerprint matches the parameter value and all relays that this relay has listed in its family by fingerprint and that in turn have listed this relay in their family by fingerprint. If relays have listed other relays in their family by nickname, those family relationships will not be considered, regardless of whether they have the Named flag or not. The provided relay fingerprint must consist of 40 hex characters where case does not matter, and it must not be hashed using SHA-1. Bridges are not contained in the result, regardless of whether they define a family.

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