Hi everyone,
We're launching a campaign to get more obfs4 bridges and help censored
Tor users.
The campaign will run from November 17 to January 7, 2022.
You can read all the details below, including our special reward kits
for participants:
https://blog.torproject.org/run-a-bridge-campaign/
Arlen Yaroslav via tor-relays:
The undocumented configuration option 'OverloadStatistics'
related:
https://gitlab.torproject.org/tpo/core/tor/-/issues/40504
--
https://nusenu.github.io
___
tor-relays mailing list
tor-relays@lists.torproject.org
> Some folks might consider switching to non-exit nodes to just get rid of
>
> the overload message. Please bear with us while we are debugging the
>
> problem and don't do that. :) We'll keep this list in the loop.
The undocumented configuration option 'OverloadStatistics' can be used to
Imre Jonk:
On Tue, Nov 09, 2021 at 06:25:31AM -0500, John Csuti via tor-relays wrote:
Hello all,
I would have to agree on this it appears that the DNS failure timeout is
too low. I have more then enough bandwidth to host tor exit nodes, and
my own unbound full recursive relay and yet i still
bobby stickel:
I get that too I've noticed that Tor makes a lot of quest to non-existent
domains. I run a pihole DNS without the ad blocking. I think this is a bug. They
should at least give us the ability to control the warning level
It seems only one of your exit relays is affected by a
