[tor-bugs] #22329 [Metrics/Onionoo]: add support for relays-only / bridges-only onionoo instances

[Tor Bug Tracker & Wiki]

#22329: add support for relays-only / bridges-only onionoo instances
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 The goal is to allow the instance operator to only enable needed
 functionality for more specific onionoo instances to avoid processing (and
 downloading) data that the operator does not need.
 (or run them separately on dedicated system)

 I would envision two new cli parameters:
 {{{
 --relays-only: ignores bridge related documents (does not download or
 process them)

 --bridges-only: ignores relay related documents (does not download or
 process them)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22329 [Metrics/Onionoo]: add support for relays-only / bridges-only onionoo instances

[Tor Bug Tracker & Wiki]

#22329: add support for relays-only / bridges-only onionoo instances
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I'd think that this will be quite confusion for users of such a mirror who
 don't expect it to leave out relay or bridge details.  It also adds
 overhead to operators going through existing options and to developers
 maintaining yet some more code.  I'd say that if somebody decides to set
 up an Onionoo instance, they should plan for providing enough resources
 for processing both relays and bridges.  Thanks for the suggestion, but
 I'll close this as won't fix.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #22329 [Metrics/Onionoo]: add support for relays-only / bridges-only onionoo instances

[Tor Bug Tracker & Wiki]

#22329: add support for relays-only / bridges-only onionoo instances
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 Replying to [comment:1 karsten]:
 > I'd think that this will be quite confusion for users of such a mirror

 Since the user is the operator this would not be an issue.

 > It also adds overhead [...] to developers maintaining yet some more
 code.

 Point taken.

 > I'd say that if somebody decides to set up an Onionoo instance, they
 should plan for providing enough resources for processing both relays and
 bridges.

 The point was more that all that BW and CPU cycles to process bridge data
 is wasted since the instance would _neve_ get a request for bridges.

 > Thanks for the suggestion, but I'll close this as won't fix.

 Thanks for your answer.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs