[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #32690 [Core Tor/Tor]: Create new directive HiddenServiceExportStats.
#32690: Create new directive HiddenServiceExportStats.
--------------------------+-----------------------------------
Reporter: moonsikpark | Owner: moonsikpark
Type: enhancement | Status: needs_information
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: tor-hs | Actual Points:
Parent ID: #32511 | Points:
Reviewer: | Sponsor:
--------------------------+-----------------------------------
Changes (by teor):
* status: assigned => needs_information
Comment:
Here's some context for this question:
https://trac.torproject.org/projects/tor/ticket/32604#comment:22
How do you expect people to use this feature? It's hard for me to decide
between these options, when I don't know how they will be used.
Unless there is some compelling use case for per-service or per-field
options, I'd prefer this design:
4. Only one directrive HiddenServiceExportStats, global, exports all
fields, for all hidden services.
I also don't think it's helpful to call this data "Stats", because Tor
already has a statistics system, on relays, that works via extra-info
descriptors.
Let's say "HIddenServiceExportCircuitInfo" ir something similar.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32690#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs