-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
I have played quite a bit with onionoo and wrote a wrapper in Go for it.
I am willing to rewrite Tor Weather using Go (or python if you like).
I'll go over the old code and this email again to make sure I understand the full scope of the project.
As an operator I have relied on the Tor Weather alerts to know if one if my nodes were down and while it's wasn't quick enough in sending alerts it was a good tool.
I have some ideas about the t-shirts alerts so that we won't miss sending to those that need it and wouldnt send to those that don't need it.
Eran
On Mon, Apr 4, 2016, 17:49 Karsten Loesing karsten@torproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= =LVj8 -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
So, I was also thinking about basing a new system off of onionoo. It should be fairly easy to handle that.
Basic flow would be the same:
- Register with fingerprint + email + select notifications (down, low bandwidth etc). - Get confirmation email - Confirm
We can discuss what notifications are needed (the same or others as before).
Regarding T-Shirts, I think automatically sending emails might be a bit too much. Perhaps it should collect that data and send an email to the people responsible sending out the t-shirts 1-2 a month. They can review some data (when the node first appeared, how stable it is, etc - or we can determine new parameters for getting a t-shirt) and authorize sending out an email.
I would be interested to know what other notifications are worth while.
Regarding operational details, I have a few questions:
- How are emails being sent today? - Is there a main torproject.org email server that was used? Obviously we would all rather have these emails reach their destination and not fall into SPAM folders. - How open are every one to run the new Weather system on a PaaS like Google AppEngine? We can probably get free credits to run it and it will save us a server to run. We can use AppEngine's cron feature to do the scheduling and check if things are up and running. That should be much more efficient as this system won't really be taking 100% CPU from a server (and its one less server to maintain).
Eran
On Mon, Apr 4, 2016 at 5:58 PM Eran Sandler eran@sandler.co.il wrote:
I have played quite a bit with onionoo and wrote a wrapper in Go for it.
I am willing to rewrite Tor Weather using Go (or python if you like).
I'll go over the old code and this email again to make sure I understand the full scope of the project.
As an operator I have relied on the Tor Weather alerts to know if one if my nodes were down and while it's wasn't quick enough in sending alerts it was a good tool.
I have some ideas about the t-shirts alerts so that we won't miss sending to those that need it and wouldnt send to those that don't need it.
Eran
On Mon, Apr 4, 2016, 17:49 Karsten Loesing karsten@torproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= =LVj8 -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Eran,
On 04/04/16 17:31, Eran Sandler wrote:
So, I was also thinking about basing a new system off of onionoo.
Sounds great. I'm happy to help with this effort by implementing any missing Onionoo features that are needed to build a Weather-like service.
It should be fairly easy to handle that.
Basic flow would be the same:
- Register with fingerprint + email + select notifications (down,
low bandwidth etc). - Get confirmation email - Confirm
We can discuss what notifications are needed (the same or others as before).
This is a fine question for people on this list who are likely your main user base. But to give you a rough idea how Tor Weather is currently used, here are the subscription numbers by type:
- 3808 node down subscriptions, - 3535 t-shirt subscriptions, - 3518 outdated version subscriptions, and - 2043 low bandwidth subscriptions.
Regarding T-Shirts, I think automatically sending emails might be a bit too much. Perhaps it should collect that data and send an email to the people responsible sending out the t-shirts 1-2 a month. They can review some data (when the node first appeared, how stable it is, etc - or we can determine new parameters for getting a t-shirt) and authorize sending out an email.
I hope that Juris has feedback on this one. I'm copying him on this message.
I would be interested to know what other notifications are worth while.
Regarding operational details, I have a few questions:
- How are emails being sent today? - Is there a main torproject.org
email server that was used? Obviously we would all rather have these emails reach their destination and not fall into SPAM folders.
So, the current Weather sends two kinds of emails: welcome messages to operators whose relays have first become stable, and notifications based on subscriptions as outlined above. I think the rewrite should leave out welcome messages entirely, because those can easily be considered as spam. It was very controversial years ago whether Weather should be sending these welcome messages, and I'm not convinced that we'd make the same decision again. I'd say it's better to advertise the existence of your service on this list and in documentation for prospective relay operators, including the Tor website. Note that it doesn't have to run on a .torproject.org subdomain for that.
As for notification messages, I don't expect there to be too many of those over the day. Given the subscription numbers above, I'd say there are no more than a hundred notifications per day. But that's just a guess, I don't have exact numbers.
I'm aware that this doesn't fully answer your questions. But maybe it helps you make better plans for picking a mail server for this purpose.
- How open are every one to run the new Weather system on a PaaS
like Google AppEngine? We can probably get free credits to run it and it will save us a server to run. We can use AppEngine's cron feature to do the scheduling and check if things are up and running. That should be much more efficient as this system won't really be taking 100% CPU from a server (and its one less server to maintain).
That's also a question for others on this list, but I'm not worried. Onionoo data is public anyway, so the only thing you're giving to Google (or to whichever provider you choose) is the mapping between subscriber email address and relay fingerprint they're interested in.
I would start with whatever hosting place is most convenient, and if this turns out to be a problem later, move the service elsewhere. Unless there are major concerns on this list, of course. Good thinking to ask in advance though.
All the best, Karsten
Any chance I could *buy* some t-shirts? I am running 4 tor middles nodes atm and 2 exit nodes coming soon and I would kill for some t-shirts.
2016-04-04 16:48 GMT+02:00 Karsten Loesing karsten@torproject.org:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= =LVj8 -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/04/16 06:00, Markus Koch wrote:
Any chance I could *buy* some t-shirts? I am running 4 tor middles nodes atm and 2 exit nodes coming soon and I would kill for some t-shirts.
Just in case nobody reached out to you yet, please get in touch with folks at tshirt@torproject.org.
All the best, Karsten
Thanks. I'll ping them.
On Mon, Apr 11, 2016 at 12:12 PM Karsten Loesing karsten@torproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/04/16 06:00, Markus Koch wrote:
Any chance I could *buy* some t-shirts? I am running 4 tor middles nodes atm and 2 exit nodes coming soon and I would kill for some t-shirts.
Just in case nobody reached out to you yet, please get in touch with folks at tshirt@torproject.org.
All the best, Karsten -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXC2pWAAoJEC3ESO/4X7XBsLAIAITQDGczE3sjhroEoj/fYvT/ UWeNrksvNtgePAg5kLy+GqIM4mFNVpWpjjuBRwouelFE5d85oe7o0NVLlQRjy6hS cl5IO6zd1lqsf+Vj/1To+MzWyVWq4GhB3NUHmx4ppaHrPGeX+nnr2W/phfI6vyrE UhBQmhFBDV25WqRuU6xKpQngREFgzIemc/XEgT7qbqsxOC93c2THEtFd+4zBazmS +uY6d1GoJZqjbh3qCOgGqdsgjj7Q8Gdz1oyK+XUb4kP7+cpk/WgKL8IOjhnJkutc O6sHf4cPt4QwLzxH9gmFO0HuDLVpXMc0j+UswjKJLazAG19m7Lji8vCv7h+Ja7o= =j0fV -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
I learned today that Tor Weather is already offline since May 24 due to problems with our hosting company.
We briefly thought about recreating it from backups, but it seems that we'd rather spend that effort on other things.
Again, sorry for any inconvenience.
All the best, Karsten
On 04/04/16 16:48, Karsten Loesing wrote:
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
*Again, sorry for any inconvenience -
Oh no worries. No one used it anyway-
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of Karsten Loesing Sent: Thursday, June 2, 2016 7:56 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Tor Weather has been discontinued
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
I learned today that Tor Weather is already offline since May 24 due to problems with our hosting company.
We briefly thought about recreating it from backups, but it seems that we'd rather spend that effort on other things.
Again, sorry for any inconvenience.
All the best, Karsten
On 04/04/16 16:48, Karsten Loesing wrote:
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt. py
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Oi!
I found it extremely useful for notifications on my exits.
Is it safe to assume the code is FOSS and repo'd somewhere?
-Jason
On 6/2/2016 5:21 PM, Greg Moss wrote:
*Again, sorry for any inconvenience -
Oh no worries. No one used it anyway-
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of Karsten Loesing Sent: Thursday, June 2, 2016 7:56 AM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Tor Weather has been discontinued
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
I learned today that Tor Weather is already offline since May 24 due to problems with our hosting company.
We briefly thought about recreating it from backups, but it seems that we'd rather spend that effort on other things.
Again, sorry for any inconvenience.
All the best, Karsten
On 04/04/16 16:48, Karsten Loesing wrote:
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt. py
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXUEjoAAoJEC3ESO/4X7XBd/4IALwN5pOft2AleZNM2JVEpIcE lG+NaGWp+SfbAQ1Y94UEC69Z417/OWLcRk2eBpxEUia8PBschqiJYG39HLOzoet6 lFbz/l6oxG3dbYpO5Y46TrCt/HlgGUAFuljH4Z9VyGEg4IkW8OgSieg+c/PtKPS6 /ri0kCfc6MEoK605MexvzUnXTUsi9fk0dRvG49mKNnIe6s+j7PXbJH+QDqvp5KVS SFj+C2Zvi19QOXjPcbn5qjb4Bql6htoesDuKbyUIrSI2Tfe0awSkgSYNfc5Xnhqg ui8E4SG1wKLHCzWZtkUWnGdq0y74dHqUL+U/aFihKP+eIaq1HpSKBbEntg68AWc= =RpHg -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Jason!
On 04/04/16 16:48, Karsten Loesing wrote:
An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
I found it extremely useful for notifications on my exits. Is it safe to assume the code is FOSS and repo'd somewhere?
The code, and the new start of a rewrite that Karsten mentions in his post, are of course available. As stated in the post that you quote, the old version did not work reliably, so I don't see why you would want to run it again.
Sad to hear this. I was briefly part of the rewrite and I remember it getting selected to be part of google's summer of code.
I was under the impression that the it was running as I recently got a tshirt email for my relay. I haven't had the opportunity to look at how the new weather based on Onionoo was tested?
Thanks!
On Mon, Apr 4, 2016 at 7:48 AM, Karsten Loesing karsten@torproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dear relay operators,
as of April 4, 2016, Tor Weather has been discontinued.
Tor Weather [0] provided an email notification service to any user who wanted to monitor the status of a Tor node. Upon subscribing, they could specify what types of alerts they would like to receive. The main purpose of Tor Weather was to notify node operators via email if their node was down for longer than a specified period, but other notification types were available, including one where operators would be informed when their node was around long enough to qualify for a t-shirt.
The main reason for discontinuing Tor Weather is the fact that software requires maintenance, and Tor Weather is no exception. Tor Weather was promising t-shirts for relays that have not been around long enough or that provided too little bandwidth to be useful to the network, and it was almost impossible to deny a t-shirt after Tor Weather has promised it. Apart from that, Tor Weather was likely not offering t-shirts to people who have long earned it, thereby confusing them. An unreliable notification system is worse than not having a system at all. Relay operators shouldn't rely on Tor Weather to notify them when their relay fails. They should rather set up their own system instead.
We have tried to find a new maintainer for Tor Weather for years, but without success. We started rewriting Tor Weather [1] using Onionoo [2] as data back-end in 2014, and even though that project didn't produce working code, somebody could pick up this efforts and finish the rewrite. The Roster developers said that they're planning to include an email notification function in Roster [3]. And we developed a simple Python script that provides information about a relay operator's eligibility for acquiring a t-shirt [4]. None of these alternatives is a full replacement of Weather, though.
We encourage you, the community of Tor relay operators, to step up to start your own notification systems and to share designs and code. Tor Weather is still a good idea, it just needs somebody to implement it.
Tor Weather is discontinued in two steps. For now, new subscriptions are disabled, new welcome messages are not sent out anymore, and existing subscriptions continue working until June 30, 2016. From July 1, 2016 on, Tor Weather will not be sending out any emails.
Sorry for any inconvenience caused by this.
All the best, Karsten
[0] https://weather.torproject.org/
[1] https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014
[2] https://onionoo.torproject.org/
[3] http://www.tor-roster.org/
[4] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org
iQEcBAEBAgAGBQJXAn7HAAoJEC3ESO/4X7XBmhEIAKxWEwex5pyp5RBHkE4+1IC2 WaKjcvIT0WiZJ8prZASNSxF7ART6r2trG50+Pd2GCdu0SOjIz3eeQNSkx251RaqF xF7dw2RVhExcYOar4FG5+KkXu6X3k0svMvNeMGzcRd51yaaVeW8OaAgV0NC+CHgE ZkA7bg26jCvG8EFrKCg4fuZ3JW3+O3mvcquea+aB4q6gbuQFjgoxzfH5+XkmpA5i gDZnsIRuBDYuUW8V1ior/7DG2wGlCjWZUotoTysfsFW2FSMUrTBZOlvhpHicMfER VpLxY8+b3ZGC6Olit50ISZql8l12yO3Hik32eKIcgK2fpx6vgKE+T83I8voIpOU= =LVj8 -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
Abhiram Chintangal -
Eran Sandler -
Greg Moss -
Jason -
Karsten Loesing -
Markus Koch -
Moritz Bartl