do Tor operators outside of the EU need to have, and publicly disclose, an EU rep because of DSA? ("mere conduit")

@torproject

We're excited to have published a new @torproject WebTunnel bridge hosted by disobey.net!

Details are on https://emeraldonion.org/bridges

boop boop

back in the top 10!

our tor exit relays seem to be more performant after doubling the RAM from 64GB to 128GB

top 10 again

https://metrics.torproject.org/rs.html#aggregate/as/flag:exit

Tor Project documents a list of Relay Associations:

https://community.torproject.org/relay/community-resources/relay-associations/

On this #GivingTuesday, we are launching 10 public @torproject #obfs4 bridges!

We don't expect these bridges to be particularly good at evading #government #censorship since they are in the same IPv4 /24 subnet as our exit relays. Countries like China and Russia undoubtably already block our subnet. However, we think they are a trustworthy (and fast) guard node when configured.

If you'd like to try one of our bridges, we have published them here:

https://bridge.emeraldonion.org

Please consider #donating to U.S. 501(c)(3) tax-deductible #nonprofit Tor network operators before the end of the year:

Emerald Onion: https://emeraldonion.org/donate/

Calyx Institute @calyxinstitute: https://members.calyxinstitute.org/donate

Stormy Cloud @stormycloud: https://stormycloud.org/donate/

Riseup @riseup: https://riseup.net/donate

(if there are any other that we missed, please let us know!)

From @torproject: #tor stable release 0.4.7.15 and 0.4.8.6

"We are today releasing both 0.4.7.15 and 0.4.8.6 with an important fix for onion services regarding congestion control and its reliability. We strongly encourage all onion service operators to upgrade as soon as possible to the latest stable that is the 0.4.8.x series.

We also address the issue with the annoying “compression bomb” log message that some relay operators have been noticing a lot lately.

Important to remember that we are expecting to end of life the 0.4.7.x series in a couple of months (likely around November) after the majority of the network has migrated and Tor Browser stable no longer ships it. That being said, please upgrade to the 0.4.8.x latest stable as soon as you can."

From forum post: https://forum.torproject.org/t/stable-release-0-4-7-15-and-0-4-8-6/9292

0.4.8.x Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes

#Tor stable release 0.4.8.5

"We are quickly releasing a new version after last week stable release in order to fix #BSD compilation issues and an annoying BUG() stacktrace in the logs for relay operators.

As usual, we strongly encourage everyone to upgrade to this version as soon as possible."

Forum post: https://forum.torproject.org/t/stable-release-0-4-8-5/8996

Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes

Tarballs: https://dist.torproject.org

Tor has a new Stable release, 0.4.7.14

"This version fixes several minor bugfixes and one major bugfix affecting vanguards (onion service). And as usual, we do recommend to upgrade to this version.

Nothing more to say about this release. Not a big one ;)."

Release notes: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.7/ReleaseNotes

#Tor operators should update!

Randomly, we are 3rd in the world right now for #Tor exit probability (4.9118%)

Advertised bandwidth is 1,907 MiB's but our real throughput has peaked at 5.2 Gbps symmetrical

.@torproject Tor 0.4.7.11 has been released

tor (0.4.7.10-1~jammy+1 => 0.4.7.11-1~jammy+1)