Re: [tor-relays] TorWeather replacement features
Would greatly appreciate relay monitoring. On Thu, 10 Feb 2022 at 01:09, nusenu wrote: > which implies it is public. How important are private (non-public) ways to > subscribe > to notifications for you? (non-public email address) 3 > TorWeather used to have an option where the operator was able to specify after > what amount of downtime they would get a notification. > I would simply go with a single static value: "2 consensus are missing your > relays" (2 hours) -> notify. > How important are configurable downtime periods to you and what timeframe > would you choose? 2 > I'm primarily focusing on notifications about "changed to the worse" (i.e. up > -> down; ok -> eol). > How important are recovery notifications (i.e. down -> up) to you? 1 > What would be the next most useful/important notification use-case for you > after - relay is running a vulnerable/end-of-life tor release > The first notification method will be email. > How important would be matrix as a second notification method to you? 3 > Would you use one or multiple notification methods at the same time? No -tom ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] TorWeather replacement features
On Thursday, February 10, 2022 2:09:07 AM CET nusenu wrote: > Hi, > > I'm currently working on a TorWeather replacement (mainly using a byproduct > of another project) that should be helpful for relay operators to get > notifications about their relay downtimes and other issues. > I believe such a service will contribute to a more healthy tor network > and better informed operators leading to less relays running on > old vulnerable and end-of-life tor versions. > ?? Torweather works. ;-) I only got an email 2 weeks ago because a relay was down. -- Forwarded Message -- Subject: [Tor Weather] Node Down! Date: Freitag, 21. Januar 2022, 12:19:09 CET From: Tor Weather To: ad...@for-privacy.net It appears that the Tor node ForPrivacyNET (fingerprint: 376DC7CAD597D3A4CBB651999CFAD0E77DC9AE8C) has been uncontactable through the Tor network for at least 48 hours. You may wish to look at it to see why. You can find more information about the Tor node at: https://metrics.torproject.org/rs.html#details/ 376DC7CAD597D3A4CBB651999CFAD0E77DC9AE8C You can unsubscribe from these reports at any time by visiting the following url: https://www.torweather.org/unsubscribe? hmac=xxxtralalaxx=376DC7CAD597D3A4CBB651999CFAD0E77DC9AE8C The original Tor Weather was decommissioned by the Tor project and this replacement is now maintained independently. You can learn more here: https://github.com/thingless/torweather/blob/master/README.md - -- ╰_╯ Ciao Marco! Debian GNU/Linux It's free software and it gives you freedom! signature.asc Description: This is a digitally signed message part. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] TorWeather replacement features
How important are private (non-public) ways to subscribe to notifications for you? 1 How important are configurable downtime periods to you and what timeframe would you choose? 3 How important are recovery notifications (i.e. down -> up) to you? 2 How important would be matrix as a second notification method to you? 3 Would you use one or multiple notification methods at the same time? Just email for me. Thanks, John C. On 2022-02-09 08:09 PM, nusenu wrote: Hi, I'm currently working on a TorWeather replacement (mainly using a byproduct of another project) that should be helpful for relay operators to get notifications about their relay downtimes and other issues. I believe such a service will contribute to a more healthy tor network and better informed operators leading to less relays running on old vulnerable and end-of-life tor versions. For those that did not have the chance to use TorWeather in the past before it died due to lack of a maintainer: It was a simple software as a service for relay operators that allowed them to subscribe for email notifications in case their relay dropped out of consensus (and a few more use-cases). The service will be for the operator of the relay(s). Subscribing and notifications will be aggregated by operators, meaning if multiple relays from a single operator go down at the same time, it will produce a single notification only (instead of one per relay). If a new relay gets added by an operator no additional steps are required to get notification for the newly added relays. You can rate the items below with these levels: (off-list replies are fine as well) 1 = must have 2 = should have 3 = nice to have The system will use the email address in your CIISS email field, which implies it is public. How important are private (non-public) ways to subscribe to notifications for you? (non-public email address) TorWeather used to have an option where the operator was able to specify after what amount of downtime they would get a notification. I would simply go with a single static value: "2 consensus are missing your relays" (2 hours) -> notify. How important are configurable downtime periods to you and what timeframe would you choose? I'm primarily focusing on notifications about "changed to the worse" (i.e. up -> down; ok -> eol). How important are recovery notifications (i.e. down -> up) to you? What would be the next most useful/important notification use-case for you after - relay dropped out of consensus - relay is running a vulnerable/end-of-life tor release - relay lost guard/exit flag The first notification method will be email. How important would be matrix as a second notification method to you? Would you use one or multiple notification methods at the same time? kind regards, nusenu 0xB77A70C2.asc Description: application/pgp-keys signature.asc 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] TorWeather replacement features
nusenu: Hi, I'm currently working on a TorWeather replacement (mainly using a byproduct of another project) that should be helpful for relay operators to get notifications about their relay downtimes and other issues. I believe such a service will contribute to a more healthy tor network and better informed operators leading to less relays running on old vulnerable and end-of-life tor versions. Right. That's a good idea. We have been proposing a Tor Weather replacement for a number of times now as a Google Summer of Code project but alas it did not get picked up and we don't have the time to rewrite it ourselves. However, I'd suggest that we as the Tor Project would host such a Tor Weather instance powered by your code as I think many more relay operators would trust such a service if it were hosted by us and thus the effect on the health of the network would be vastly superior. There is a ticket open in our bug tracker[1] you filed a while back where we could coordinate. Let us know what you think, but the overall idea sounds exciting. Georg [1] https://gitlab.torproject.org/tpo/network-health/team/-/issues/107 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] TorWeather replacement features
Hi, I'm currently working on a TorWeather replacement (mainly using a byproduct of another project) that should be helpful for relay operators to get notifications about their relay downtimes and other issues. I believe such a service will contribute to a more healthy tor network and better informed operators leading to less relays running on old vulnerable and end-of-life tor versions. For those that did not have the chance to use TorWeather in the past before it died due to lack of a maintainer: It was a simple software as a service for relay operators that allowed them to subscribe for email notifications in case their relay dropped out of consensus (and a few more use-cases). The service will be for the operator of the relay(s). Subscribing and notifications will be aggregated by operators, meaning if multiple relays from a single operator go down at the same time, it will produce a single notification only (instead of one per relay). If a new relay gets added by an operator no additional steps are required to get notification for the newly added relays. You can rate the items below with these levels: (off-list replies are fine as well) 1 = must have 2 = should have 3 = nice to have The system will use the email address in your CIISS email field, which implies it is public. How important are private (non-public) ways to subscribe to notifications for you? (non-public email address) TorWeather used to have an option where the operator was able to specify after what amount of downtime they would get a notification. I would simply go with a single static value: "2 consensus are missing your relays" (2 hours) -> notify. How important are configurable downtime periods to you and what timeframe would you choose? I'm primarily focusing on notifications about "changed to the worse" (i.e. up -> down; ok -> eol). How important are recovery notifications (i.e. down -> up) to you? What would be the next most useful/important notification use-case for you after - relay dropped out of consensus - relay is running a vulnerable/end-of-life tor release - relay lost guard/exit flag The first notification method will be email. How important would be matrix as a second notification method to you? Would you use one or multiple notification methods at the same time? kind regards, nusenu -- https://nusenu.github.io ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
