| ... | @@ -22,7 +22,7 @@ This project would involve the implementation of an email notification service t |
... | @@ -22,7 +22,7 @@ This project would involve the implementation of an email notification service t |
|
|
|
|
|
|
|
This project already existed and was known as "Tor Weather". It was unfortunately discontinued due to lack of maintenance and resources to keep the project alive. However, we think that this is still a great idea and the most efficient way to achieve and maintain a healthy Tor network on the long run. The resulting service should conform to our current styleguide.
|
|
This project already existed and was known as "Tor Weather". It was unfortunately discontinued due to lack of maintenance and resources to keep the project alive. However, we think that this is still a great idea and the most efficient way to achieve and maintain a healthy Tor network on the long run. The resulting service should conform to our current styleguide.
|
|
|
|
|
|
|
|
There is a repository, maintained independently from the Tor project, with code that can be reuse and expand for implementing this proposal. You can find it in https://github.com/thingless/torweather/ .
|
|
There is a repository, maintained independently from the Tor project, with code that we could think about reusing and expanding upon for implementing this proposal. It's at https://github.com/thingless/torweather/. There are additional resources below which should get evaluated to find the right design choice for a new Tor Weather service.
|
|
|
|
|
|
|
|
This notification service should support subscribing via single relay fingerprint or MyFamily groups. Additionally, it should not need any subscription change if a new relay gets added to the family. As this service would store email addresses of potential tor relay operators, they should be kept private and safeguarded. However, a passive observer can collect them by watching outbound email traffic if no TLS is used. As such, this service should suggest using a dedicated email address for this service.
|
|
This notification service should support subscribing via single relay fingerprint or MyFamily groups. Additionally, it should not need any subscription change if a new relay gets added to the family. As this service would store email addresses of potential tor relay operators, they should be kept private and safeguarded. However, a passive observer can collect them by watching outbound email traffic if no TLS is used. As such, this service should suggest using a dedicated email address for this service.
|
|
|
|
|
|
| ... | @@ -44,9 +44,11 @@ Once a basic email notification service is implemented, these are some ideas for |
... | @@ -44,9 +44,11 @@ Once a basic email notification service is implemented, these are some ideas for |
|
|
|
|
|
|
|
For each notification implemented, there should be a corresponding specification written to describe the meaning of each notification type.
|
|
For each notification implemented, there should be a corresponding specification written to describe the meaning of each notification type.
|
|
|
|
|
|
|
|
|
|
### Resources:
|
|
|
|
|
Current issue in our bug tracker: [https://gitlab.torproject.org/tpo/network-health/team/-/issues/107](https://gitlab.torproject.org/tpo/network-health/team/-/issues/107)
|
|
|
|
|
Another Tor Weather code base: [https://github.com/meejah/tor-weather](https://github.com/meejah/tor-weather)
|
|
|
|
Old Tor Weather experience: [https://web.archive.org/web/20141004055709/https://weather.torproject.org/subscribe/](https://web.archive.org/web/20141004055709/https://weather.torproject.org/subscribe/)
|
|
|
|
Our old code base: [https://gitweb.torproject.org/weather.git/](https://gitweb.torproject.org/weather.git/)
|
|
|
|
|
|
|
|
-----------
|
|
-----------
|
|
|
|
|
|
| ... | | ... | |
