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.org/cgi-bin/mailman/listinfo/tor-relays
or, via email, send a message with subject or body 'help' to
tor-relays-request@lists.torproject.org
You can reach the person managing the list at
tor-relays-owner@lists.torproject.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-relays digest..."
Today's Topics:
1. Responding to Tor censorship in Russia (gus)
2. Re: Responding to Tor censorship in Russia (John Ricketts)
----------------------------------------------------------------------
Message: 1
Date: Tue, 7 Dec 2021 17:16:05 -0300
From: gus <gus@torproject.org>
To: tor-relays@lists.torproject.org
Subject: [tor-relays] Responding to Tor censorship in Russia
Message-ID: <20211207201605.GN2321@localhost>
Content-Type: text/plain; charset="utf-8"
Dear relay operators,
Today the torproject.org was officially blocked in Russia. You can read
more about the situation here[1].
Russia is the country with the second largest number of Tor users, with
more than 300,000 daily users or 15% of all Tor users.
As it seems this situation could quickly escalate to a country-wide Tor
block, it's urgent that we respond to this censorship!
We need your help NOW to keep Russians connected to Tor!
We are calling on everyone to spin up a Tor bridge.
If you've ever considered running a bridge, now is an excellent time to
get started, as your help is urgently needed. You can find the
requirements and instructions for starting a bridge in the Help Censored
Users, Run a Tor Bridge blog post: https://blog.torproject.org/run-a-bridge-campaign/
Gus
[1]
https://blog.torproject.org/tor-censorship-in-russia/
https://gitlab.torproject.org/tpo/community/support/-/issues/40050
--
The Tor Project
Community Team Lead
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20211207/7ae42f7d/attachment-0001.sig>
------------------------------
Message: 2
Date: Tue, 7 Dec 2021 20:40:24 +0000
From: John Ricketts <john@quintex.com>
To: "tor-relays@lists.torproject.org"
<tor-relays@lists.torproject.org>
Subject: Re: [tor-relays] Responding to Tor censorship in Russia
Message-ID: <3c372b4b21f14a019ed973582b931c6d@xch-sjt-01.quintex.com>
Content-Type: text/plain; charset="utf-8"
gus,
Since all of my exit nodes are within the same /16 - would I have to run bridges on newly acquired IPv4 space?
John
-----Original Message-----
From: tor-relays <tor-relays-bounces@lists.torproject.org> On Behalf Of gus
Sent: Tuesday, December 7, 2021 2:16 PM
To: tor-relays@lists.torproject.org
Subject: [tor-relays] Responding to Tor censorship in Russia
Dear relay operators,
Today the torproject.org was officially blocked in Russia. You can read more about the situation here[1].
Russia is the country with the second largest number of Tor users, with more than 300,000 daily users or 15% of all Tor users.
As it seems this situation could quickly escalate to a country-wide Tor block, it's urgent that we respond to this censorship!
We need your help NOW to keep Russians connected to Tor!
We are calling on everyone to spin up a Tor bridge.
If you've ever considered running a bridge, now is an excellent time to get started, as your help is urgently needed. You can find the requirements and instructions for starting a bridge in the Help Censored Users, Run a Tor Bridge blog post: https://blog.torproject.org/run-a-bridge-campaign/
Gus
[1]
https://blog.torproject.org/tor-censorship-in-russia/
https://gitlab.torproject.org/tpo/community/support/-/issues/40050
--
The Tor Project
Community Team Lead
------------------------------
Subject: Digest Footer
_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
------------------------------
End of tor-relays Digest, Vol 131, Issue 4
******************************************