Relay Search issueshttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues2022-01-29T11:43:28Zhttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/33493Encourage operators to ignore bridge flags on relay search2022-01-29T11:43:28ZteorEncourage operators to ignore bridge flags on relay searchThe bridge flags on relay search confuse some bridge operators:
https://lists.torproject.org/pipermail/tor-relays/2020-February/018188.html
Can we grey them out, or otherwise indicate that they're not used by clients?
Can we change the...The bridge flags on relay search confuse some bridge operators:
https://lists.torproject.org/pipermail/tor-relays/2020-February/018188.html
Can we grey them out, or otherwise indicate that they're not used by clients?
Can we change the mouseover help message on the "flags" heading for bridges?
Can we also change the definition of Flags, and the Bridge Descriptors definition, so they talk about bridge flags?https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/28304Please deliver png when svg is filtered2021-06-30T15:33:15ZtraumschulePlease deliver png when svg is filteredHi metrics team!
With legacy/trac#19654 the relay search shows
> Graphs cannot be shown as your browser does not support Scalable Vector Graphics (SVG). This is the case when Tor Browser is in High Security mode.
This is very useful. Ho...Hi metrics team!
With legacy/trac#19654 the relay search shows
> Graphs cannot be shown as your browser does not support Scalable Vector Graphics (SVG). This is the case when Tor Browser is in High Security mode.
This is very useful. However i'd like to download a png of the graph, or just csv/xml/json in that case.
On a sidenote the graph shows "No data available" while data is loading which can be confusing, ie. it's not clear with a slow connection if the graph will show up later or not - would "data is loading .." make sense? Hesitating to open another ticket about this because it looks like legacy/trac#25264.
Thought it could help to show captions (or similar) to indicate what kind of data isn't available.
Let me know if you prefer a separate issue for the latter. Thanks for your work!https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/27154Do not display "AS0" in results or details pages2021-06-30T15:32:58ZnusenuDo not display "AS0" in results or details pagesRS uses "AS0" as a placeholder for "unknown AS number",
but "AS0" has a special meaning in BGP (https://tools.ietf.org/html/rfc7607 ), lets use something else?
maybe "ASXY"?RS uses "AS0" as a placeholder for "unknown AS number",
but "AS0" has a special meaning in BGP (https://tools.ietf.org/html/rfc7607 ), lets use something else?
maybe "ASXY"?https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/26964support custom column selection for search result overview2021-06-30T15:32:58Znusenusupport custom column selection for search result overviewthe current set of shown information for search results is fixed and can not be customized by the user, but for different people different information is relevant.
onionoo provides a lot of information, would be great if search results ...the current set of shown information for search results is fixed and can not be customized by the user, but for different people different information is relevant.
onionoo provides a lot of information, would be great if search results were more customizable via the URL
examples:
* first_seen
* last_restarted
* tor version / os
* hostnames
* as_name
* *_bandwidth
* *_probability
* hide specific currently shown columns
torstatus allows for custom column selection, see:
http://torstatus.blutmagie.de/column_set.phphttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/26767add consensus weight line/graph2021-06-30T15:32:58Znusenuadd consensus weight line/graphRelay Search has two graphs showing bw history data and relative values (fraction and probabilities):
* consensus weight fraction
* middle probability
* guard probability
* exit probability
* written bytes per second
* read bytes per se...Relay Search has two graphs showing bw history data and relative values (fraction and probabilities):
* consensus weight fraction
* middle probability
* guard probability
* exit probability
* written bytes per second
* read bytes per second
One of the most relevant question for a relay operator is:
How is my relay doing?
Is it doing better or worse than usually?
A good data point to answer this is to look at the cw value over time (not cw fraction) since the probabilities and fraction values are relative and not directly controllable by the operator (i.e. other operators add relays).
This will allow relay operators to answer questions like:
"My cw fraction decreased, was it because my cw decreased or did my cw remain stable and someone else added more resources?"
a graph showing the ratio between cw fraction to cw would also be nice since it answers above question more directly without having to compare the cw and cw fraction lines manually
onionoo data:
https://metrics.torproject.org/onionoo.html#weights_relay_consensus_weight
the onion box displays a cw graph:
https://raw.githubusercontent.com/ralphwetzel/theonionbox/master/docs/images/weights.pnghttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/26090show tor exit DNS resolver data on RS2023-01-23T14:11:47Zcypherpunksshow tor exit DNS resolver data on RScontext:
https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca
"
5. Add DNS related information to Relay Search (a long term item)
It would be nice and probably effective to have information about DNS resolvers show up ...context:
https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca
"
5. Add DNS related information to Relay Search (a long term item)
It would be nice and probably effective to have information about DNS resolvers show up on Relay Search, because it is a popular tool for relay operators to check on their relay state. Operators could easily see if they use any less desirable DNS resolvers if that information is shown on Relay Search. That way we could even reach operators who have no or invalid ContactInfo data, but multiple steps are required before this could happen:
The currently unavailable data needs to be
collected and regularly updated
added to onionoo
shown on Relay Search <<<<
"https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/25673allow users to set the show ___ entries value directly in the url2021-06-30T15:32:59Zcypherpunksallow users to set the show ___ entries value directly in the urlThis would allow for convenient linkingThis would allow for convenient linkinghttps://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/24834Map consensus weight vs bandwidth for each bandwidth authority's votes2021-06-30T15:32:58ZteorMap consensus weight vs bandwidth for each bandwidth authority's votesThe new map on Relay Search is great!
The consensus weight versus bandwidth map has been really helpful for analysing bandwidth authority behaviour.
We now know that the measurements are biased towards the north of the northern hemispher...The new map on Relay Search is great!
The consensus weight versus bandwidth map has been really helpful for analysing bandwidth authority behaviour.
We now know that the measurements are biased towards the north of the northern hemisphere. (We don't know why yet: maybe the Internet is better, maybe the relays are all there, or maybe the bandwidth authorities are all there.)
I can look at the bias for the Guard and Exit flags by doing an aggregate search, then mapping it.
But I'd also like to see the bias for each bandwidth authority, using the bandwidth figures in their votes.
Is this possible in Relay Search?
Having this map on a country level would help us when we start experimenting with moving the servers around, or pooling them, or using a CDN.https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/24463Advanced search: Add a client auto-completion filter to AS field2021-06-30T15:32:59ZcypherpunksAdvanced search: Add a client auto-completion filter to AS fieldAdd something like compass has on the Country field (that is different from what atlas has on the country field) to atlas' AS field. Typing should start filtering in the AS name and number.Add something like compass has on the Country field (that is different from what atlas has on the country field) to atlas' AS field. Typing should start filtering in the AS name and number.https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/23941Determine if a relay is eligible for a t-shirt and display on details page2021-06-30T15:32:58ZirlDetermine if a relay is eligible for a t-shirt and display on details pageA script was written for legacy/trac#9889 to determine if a relay is eligible for a t-shirt or not.
We've talked about having this in Atlas and having seen another mail on tor-relays today asking about eligibility, I think it's a useful...A script was written for legacy/trac#9889 to determine if a relay is eligible for a t-shirt or not.
We've talked about having this in Atlas and having seen another mail on tor-relays today asking about eligibility, I think it's a useful feature to have.
Input from the t-shirts team would be appreciated to make sure we have the criteria correct, and to know where to send those that are eligible. Ideally we could link to a web page that explains any caveats to the process (e.g. you can't get 500 t-shirts for 500 relays) and how to apply for your t-shirt.https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/23509Implement family-level pages showing aggregated graphs2021-06-30T15:33:15ZcypherpunksImplement family-level pages showing aggregated graphsCurrently atlas is about single relays, many operators run more than a single relay and would like to see the aggregated data of all their relays on a single page with the graphs showing all relays in stacked way.
This allows them to see...Currently atlas is about single relays, many operators run more than a single relay and would like to see the aggregated data of all their relays on a single page with the graphs showing all relays in stacked way.
This allows them to see how they are doing across all their relays.
example graphs:
https://nos-oignons.net/Services/index.en.html
To avoid discussing how to identify MyFamilies lets just use onionoo lookup:
https://atlas.torproject.org/#search/family:<fingerprint of an arbitrary relay>
This would also create an incentive for properly configuring MyFamily since incorrect set MyFamily would result
relay operators find this useful (counted ~11)
https://lists.torproject.org/pipermail/tor-relays/2017-September/012942.html
https://twitter.com/nusenu_/status/907366138149044224https://gitlab.torproject.org/tpo/network-health/metrics/relay-search/-/issues/8667Distinguish between permanent and temporary Onionoo errors2021-06-30T15:33:15ZKarsten LoesingDistinguish between permanent and temporary Onionoo errorsAs of now, Onionoo has a "maintenance mode" that I'm planning to use very rarely. But sometimes it's necessary to shut down Onionoo to support new features or fix bugs. During this time, Onionoo responds to all requests with a 503 Serv...As of now, Onionoo has a "maintenance mode" that I'm planning to use very rarely. But sometimes it's necessary to shut down Onionoo to support new features or fix bugs. During this time, Onionoo responds to all requests with a 503 Service Unavailable status code. Atlas should respect this code and display a different warning than:
"Backend error! The backend server replied with an error to your query. This probably means that you did not properly format your query. If your query was properly formatted it may mean that there is an issue with your browser/add-ons. Please report which browser/addons/etc. you're using to the bug tracker."
How about this warning?
"Backend temporarily unavailable! The backend server is temporarily unavailable. If this issue persists for more than a few hours, please report it using the <a href="https://trac.torproject.org/projects/tor/newticket?component=Atlas">bug tracker</a>."