On 09.07.2020 00:20, Jonas wrote:
If you can detect the "bad relays", why not simply flag them and move
on?
I agree with you for publicizing bad relays and locking them faster.
Personally, I blocked some exits in my Tor browser. E.g. these expensive
high bandwith (unnamed & without mail contac
Excerpts from trinity Pointard's message of July 11, 2020 7:12 am:
> Hi,
>
> Since a few days, my relay A8503903F97FF27F5D1C3CA38817329F581925E6
> appear down according to metrics.torproject.org, and is not getting
> the Running flag from 6 out of 9 authorities according to
> consensus-health.torp
17CC4D25E33993D011CDA6E68806435FFFD2E6C7
‐‐‐ Original Message ‐‐‐
On Friday, July 10, 2020 3:02 PM, Bakullama wrote:
> 90B64F9E18B59AF322EBD28B8F8CD65C53E10CE1
>
> ~ Bakullama
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, 10 July 2020 13:00, tor-relays-requ...@lists.torproject.org
Hi,
On Sunday, July 5, 2020 at 8:45 PM, Imre Jonk wrote:
Hi nusenu,
On Sun, 2020-07-05 at 18:35 +0200, nusenu wrote:
[...]
b) require a verified physical address for large operators (>=0.5%
exit or guard probability)
(manual verification, low number of operators).
It is not required
Hi,
Since a few days, my relay A8503903F97FF27F5D1C3CA38817329F581925E6
appear down according to metrics.torproject.org, and is not getting
the Running flag from 6 out of 9 authorities according to
consensus-health.torproject.org.
This happened when my ISP got an issue and my network falled back t
90B64F9E18B59AF322EBD28B8F8CD65C53E10CE1
~ Bakullama
‐‐‐ Original Message ‐‐‐
On Friday, 10 July 2020 13:00, wrote:
> Send tor-relays mailing list submissions to
> tor-relays@lists.torproject.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.torproject.o
My relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) is
currently flagged as fallback dir.
The relay runs on a dynamic ip address that will change rarely. I have
over the years tried multiple times to get the relay excluded from the
fallback dir list but it keeps popping back in there.
C
