Re: [tor-relays] OrNetStats: Operator Level Graphs added
On 1/9/21 2:42 PM, nusenu wrote: > Toralf Förster: >> cool idea, >> >> canthose graphs being linked from eg >> https://yui.cat/relay/63BF46A63F9C21FD315CD061B3EAA3EB05283A0A.html ? > > Yes, that should be easy. > The best way to get that done is to either submit a patch or feature > request here: > https://github.com/tempname1024/allium/issues > > kind regards, > nusenu > Sweet graphs, thanks Nusenu! I opened an issue[1] to address support for the ContactInfo-Information-Sharing-Specification which includes outbound links to graphs of verified operators/domains at OrNetStats, and rendering of provided attributes on per-relay pages. [1] https://github.com/tempname1024/allium/issues/9 -- Jordan https://yui.cat/ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] OrNetStats: Operator Level Graphs added
On 1/9/21 9:38 PM, nusenu wrote: - change the scale on the y axis (vertical drag and drop) Maybe nitpicking but IMO It is irritating, that the 0% value (zero) of the left y-axis doesn't match the 0 GBit/s at the right y-axis (per default). -- Toralf OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
[tor-relays] My relay software gets hung up on OVH
Hi, so my relay running on OVH at https://metrics.torproject.org/rs.html#details/79E3B585803DE805CCBC00C1EF36B1E74372861D Sometimes gets hung up. About every two weeks or so, the relay software gets hung up, causing the relay to go offline. I notice when this happens, the tor log file becomes unreadable, making it difficult to tell what was happening with the tor process when this occurs. It is only when the relay is restarted by running “killall tor” in terminal and then restarting the relay. I am wondering if any other relay operators on OVH are getting this issue? It seems to sporadically happen once every two weeks or so. Thank you. --Keifer ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] OrNetStats: Operator Level Graphs added
Hi Am 10.01.2021 um 19:08 schrieb li...@for-privacy.net: On 09.01.2021 21:38, nusenu wrote: - Shall we also add the fingerprints from the bridges in 'proof'? https://gitlab.torproject.org/tpo/core/torspec/-/blob/master/proposals/326-tor-relay-well-known-uri-rfc8615.md /.well-known/tor-relay/rsa-fingerprint.txt - The file contains one or more Tor relay RSA SHA1 fingerprints operated by the entity in control of this website. - Each line contains one fingerprint. - The file may contain comments (starting with #). - Non-comment lines must be exactly 40 characters long and consist of the following characters [a-fA-F0-9]. - Fingerprints are not case-sensitive. - Each fingerprint MUST appear at most once. - The file MUST not be larger than one MByte. - The file MUST NOT contain fingerprints of Tor bridges (or hashes of bridge fingerprints). - The content MUST be a media type of "text/plain". :: No bridge fingerprints :: -- Cheers, Felix ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] OrNetStats: Operator Level Graphs added
On 1/10/21 7:08 PM, li...@for-privacy.net wrote: I don't want to expect the average user to fish something obfuscated out of the string. Yes, I am old and conservative ;-) /me too - therefore I tend to not add detailed technical information about the relays. (BTW that doesn't work at all with the current ciissversion if relays are hosted at different hoster at all, or?) -- Toralf OpenPGP_signature Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] OrNetStats: Operator Level Graphs added
On 09.01.2021 21:38, nusenu wrote: I've added new operator level pages with an interactive graph showing the aggregated guard/exit probability and advertised bandwidth over time across all relays for a given operator. This should allow you to see whether your bandwidth and fractions are growing or decreasing. Nice, thanks. I entered the DNS TXT records for my relays. 2 questions: - Shall we also add the fingerprints from the bridges in 'proof'? - Can I leave my email address as it is for "foo bar", see below? I don't want to expect the average user to fish something obfuscated out of the string. Yes, I am old and conservative ;-) https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/ An example ContactInfo string as defined by this specification could look like this: foo bar email:tor[]example.com url:https://example.com proof:uri-rsa ciissversion:2 ^^^ ab...@for-privacy.net email:admin[]for-privacy.net url:for-privacy.net proof:dns-rsa keybase:boldsuck ciissversion:2 ^^^ General question: Is it possible to introduce a new option in the configuration file for the ContactInfo string? (ContactInfo + ContactInfoString)? Maybe when the IPv6 development is done. Because of contact info. There are a couple of relays that have given these lists addresses: https://metrics.torproject.org/rs.html#search/contact:tor-relays@lists.torproject.org%20 -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
