-
Notifications
You must be signed in to change notification settings - Fork 72
Site going offline blutmagie.yml
(https://torstatus.blutmagie.de/)
#91
Comments
Thanks @simonsigre. Probably the best replacement is the tor exit address list: https://github.com/PaloAltoNetworks/minemeld-node-prototypes/blob/master/prototypes/tor.yml#L9 What do you think? |
Yeah that's probably better, I am actually using both because the fact they have a 'checker' implies that certain exit nodes are blocking traffic to certain places and given its decentralised I can only imagine to build the |
I am seeing a pretty large discrepancy (against https://github.com/PaloAltoNetworks/minemeld-node-prototypes/blob/master/prototypes/tor.yml#L9) however this can be time based. |
For whatever reason I am seeing a huge discrepancy still.. happy to close it out though |
@jtschichold I think this discrepancy may be a simple matter of timing etc (bring data in, age out etc) .. I think its fine to mark this as resolved. |
@jtschichold this one is good to mark as resolved |
Signed-off-by: Luigi Mori <l@isidora.org>
Signed-off-by: Luigi Mori <l@isidora.org>
Marked blutmagie as deperecated |
As per https://torstatus.blutmagie.de;
Attention: This Tor Network Status site will be discontinued 11/06/2018, olaf.selke@blutmagie.de
This site will no longer function after 6th November. Suggest migrating to using the
torproject
exit node listhttps://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=1.1.1.1
The text was updated successfully, but these errors were encountered: