March 2021 - tor-commits - lists.torproject.org

[community/staging] better lines for l10n
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 6f3e367acaf16be7a94b13db95d642b20e598db9 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Mar 5 08:17:04 2021 +0100 better lines for l10n --- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index e1cef75..29baea0 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -109,10 +109,8 @@ FreeBSDlatest: { ### 7. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- subtitle: How to deploy an obfs4 bridge on FreeBSD

1 0

[community/staging] Add onion guide fanzine. Fix #181
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit f87602635fefc6b0cb511f14222aa846b615a4d6 Author: gus <gus(a)torproject.org> Date: Thu Mar 4 08:56:34 2021 -0500 Add onion guide fanzine. Fix #181 --- .../outreach/print/onion-guide-fanzine-EN.pdf | Bin 0 -> 343902 bytes .../outreach/print/onion-guide-fanzine-ES.pdf | Bin 0 -> 342504 bytes .../outreach/print/onion-guide-fanzine-PT_BR.pdf | Bin 0 -> 345662 bytes .../images/outreach/print/onion-guide-fanzine.pdf | Bin 346542 -> 0 bytes databags/outreach-materials.ini | 22 +++++++++++++++++---- 5 files changed, 18 insertions(+), 4 deletions(-) diff --git a/assets/static/images/outreach/print/onion-guide-fanzine-EN.pdf b/assets/static/images/outreach/print/onion-guide-fanzine-EN.pdf new file mode 100644 index 0000000..956cdf1 Binary files /dev/null and b/assets/static/images/outreach/print/onion-guide-fanzine-EN.pdf differ diff --git a/assets/static/images/outreach/print/onion-guide-fanzine-ES.pdf b/assets/static/images/outreach/print/onion-guide-fanzine-ES.pdf new file mode 100644 index 0000000..e23752b Binary files /dev/null and b/assets/static/images/outreach/print/onion-guide-fanzine-ES.pdf differ diff --git a/assets/static/images/outreach/print/onion-guide-fanzine-PT_BR.pdf b/assets/static/images/outreach/print/onion-guide-fanzine-PT_BR.pdf new file mode 100644 index 0000000..a255de5 Binary files /dev/null and b/assets/static/images/outreach/print/onion-guide-fanzine-PT_BR.pdf differ diff --git a/assets/static/images/outreach/print/onion-guide-fanzine.pdf b/assets/static/images/outreach/print/onion-guide-fanzine.pdf deleted file mode 100644 index dd446d9..0000000 Binary files a/assets/static/images/outreach/print/onion-guide-fanzine.pdf and /dev/null differ diff --git a/databags/outreach-materials.ini b/databags/outreach-materials.ini index 4b811eb..80f2bed 100644 --- a/databags/outreach-materials.ini +++ b/databags/outreach-materials.ini @@ -1,9 +1,23 @@ -[onion-guide] +[onion-guide-EN] location = https://community.torproject.org/static/images/outreach/print/ -filename = onion-guide-fanzine.pdf -label = Onion guide fanzine +filename = onion-guide-fanzine-EN.pdf +label = Onion guide fanzine (English) type = zine -year = 2020 +year = 2021 + +[onion-guide-ES] +location = https://community.torproject.org/static/images/outreach/print/ +filename = onion-guide-fanzine-ES.pdf +label = Onion guide fanzine (Español) +type = zine +year = 2021 + +[onion-guide-PT_BR] +location = https://community.torproject.org/static/images/outreach/print/ +filename = onion-guide-fanzine-PT_BR.pdf +label = Onion guide fanzine (Português Brasil) +type = zine +year = 2021 [onion-service] location = https://community.torproject.org/static/images/outreach/print/

1 0

[community/staging] better lines for localization.
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 8c859d5bd156eaa98fb7deb0b786e17167f7860f Author: emma peel <emma.peel(a)riseup.net> Date: Fri Mar 5 09:12:04 2021 +0100 better lines for localization. --- .../tor-dmca-response/contents.lr | 23 +++++++++++++++++----- .../tor-abuse-templates/contents.lr | 9 +++------ .../technical-setup/bridge/docker/contents.lr | 16 ++++----------- 3 files changed, 25 insertions(+), 23 deletions(-) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr index 847ce19..f782b29 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr @@ -30,15 +30,28 @@ Dear [ISP]: Thank you for forwarding me the notice you received from [copyright claimant] regarding [content]. I would like to assure you that I am not hosting the claimed infringing materials, and furthermore, the Digital Millennium Copyright Act's ("DMCA") safe harbors likely protect you from liability arising from this complaint. The notice is likely based upon misunderstandings about the law and about some of the software I run. -As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their users, when the ISPs fulfill certain requirements. (17 U.S.C. 512) The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a conduit. Instead, the "conduit" safe harbor of section 512(a) of the DMCA has different and less burdensome eligibility requirements, as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see https://scholar.google.com/scholar_case?case=15815830240179540527) and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter (see https://scholar.google.com/scholar_case?case=11547531128234336420) +As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their users, when the ISPs fulfill certain requirements. (17 U.S.C. 512) +The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a conduit. +Instead, the "conduit" safe harbor of section 512(a) of the DMCA has different and less burdensome eligibility requirements, as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see https://scholar.google.com/scholar_case?case=15815830240179540527) and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter (see https://scholar.google.com/scholar_case?case=11547531128234336420) -Under DMCA 512(a), service providers like you are typically protected from damages for copyright infringement claims if you also maintain "a policy that provides for termination in appropriate circumstances of subscribers and account holders of the service provider's system or network who are repeat infringers." If you have and implement such a policy, and you otherwise qualify for the safe harbor, you should be free from fear of copyright damages. +Under DMCA 512(a), service providers like you are typically protected from damages for copyright infringement claims if you also maintain "a policy that provides for termination in appropriate circumstances of subscribers and account holders of the service provider's system or network who are repeat infringers." +If you have and implement such a policy, and you otherwise qualify for the safe harbor, you should be free from fear of copyright damages. -The copyright notice you received was likely triggered by a program I run called Tor. Tor is network software that helps users to enhance their privacy, security, and safety online. It does not host any content. Rather, it is part of a network of nodes on the Internet that simply pass packets among themselves before sending them to their destinations, just as any Internet intermediary does. The difference is that Tor tunnels the connections such that no hop can learn both the source and destination of the packets, giving users protection from nefarious snooping on network traffic. The result is that, unlike most other Internet traffic, the final IP address that the recipient receives is not the IP address of the sender. Tor protects users against hazards such as harassment, spam, and identity theft. Initial development of Tor, including deployment of a public-use Tor network, was a project of the U.S. Naval Research Laboratory, with funding from ONR and DARPA. (For more on Tor, see https://www.torproject.org/.) I hope, as an organization committed to protecting the privacy of its customers, you'll agree that this is a valuable technology. +The copyright notice you received was likely triggered by a program I run called Tor. Tor is network software that helps users to enhance their privacy, security, and safety online. +It does not host any content. Rather, it is part of a network of nodes on the Internet that simply pass packets among themselves before sending them to their destinations, just as any Internet intermediary does. +The difference is that Tor tunnels the connections such that no hop can learn both the source and destination of the packets, giving users protection from nefarious snooping on network traffic. +The result is that, unlike most other Internet traffic, the final IP address that the recipient receives is not the IP address of the sender. +Tor protects users against hazards such as harassment, spam, and identity theft. Initial development of Tor, including deployment of a public-use Tor network, was a project of the U.S. Naval Research Laboratory, with funding from ONR and DARPA. (For more on Tor, see https://www.torproject.org/.) +I hope, as an organization committed to protecting the privacy of its customers, you'll agree that this is a valuable technology. -While the Tor node that I run may appear to be the source of material that is alleged to be copyright-infringing, I do not host that material. I do not select the material transmitted through the Tor node that I run, and I have no practical means of either identifying the source of such material or preventing its transmission. I do nothing to encourage or promote the use of the Tor network for copyright infringement. For these reasons, I am not an infringer of copyright in any materials that are transmitted through the Tor node that I run, either directly or under a theory of contributory or vicarious liability. Therefore, you should continue to be protected under the DMCA 512(a) safe harbor without taking any further action. +While the Tor node that I run may appear to be the source of material that is alleged to be copyright-infringing, I do not host that material. +I do not select the material transmitted through the Tor node that I run, and I have no practical means of either identifying the source of such material or preventing its transmission. +I do nothing to encourage or promote the use of the Tor network for copyright infringement. +For these reasons, I am not an infringer of copyright in any materials that are transmitted through the Tor node that I run, either directly or under a theory of contributory or vicarious liability. +Therefore, you should continue to be protected under the DMCA 512(a) safe harbor without taking any further action. -Thank you for working with me on this matter. As a loyal subscriber, I appreciate your notifying me of this issue and hope that the protections of DMCA 512 put any concerns you may have to rest. If not, please contact me with any further questions. +Thank you for working with me on this matter. As a loyal subscriber, I appreciate your notifying me of this issue and hope that the protections of DMCA 512 put any concerns you may have to rest. +If not, please contact me with any further questions. Very truly yours, Your customer, [User] diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index 1cd12f9..3d2f00c 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -92,8 +92,7 @@ We're sorry your site is experiencing this heavy load from Tor. However, it is possible that your rate limiting alarms simply experienced a false positive due to the amount of traffic that flows through the router. We provide service to almost a gigabit of traffic per second, 98% of which is web traffic. -If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming -from Tor nodes: https://www.torproject.org/projects/tordnsel.html.en +If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming from Tor nodes: https://www.torproject.org/projects/tordnsel.html.en It is also possible to download a list of all Tor exit IPs that will connect to your server port: https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=YOUR_IP&port=80 @@ -175,11 +174,9 @@ Additionally, the Tor project provides an automated DNSRBL for you to query to f It also provides a Bulk Exit List service for retrieving the entire list: https://check.torproject.org/cgi-bin/TorBulkExitList.py -You can use this list to help you take a closer look at Tor orders, or to hold them temporarily for additional verification, without losing -legitimate customers. +You can use this list to help you take a closer look at Tor orders, or to hold them temporarily for additional verification, without losing legitimate customers. -In fact, in my experience, the fraud processing teams contracted by many ISPs simply mark all requests from Tor nodes as fraud using that -very list. +In fact, in my experience, the fraud processing teams contracted by many ISPs simply mark all requests from Tor nodes as fraud using that very list. So it is even possible this is a legitimate order, but was flagged as fraud solely based on IP, especially if you contract out fraud detection to a third party. ``` diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index eb449a8..00e26a1 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -9,11 +9,7 @@ body: ### 1. Deploy a container We provide a docker-compose file that helps you deploy the container. -First, -[download docker-compose.yml](https://dip.torproject.org/torproject/anti-censorship/d…, -and then write your bridge configuration to a new file, `.env`, which is in the -same directory as `docker-compose.yml`. Here's a -template: +First, [download docker-compose.yml](https://dip.torproject.org/torproject/anti-censorship/d…, and then write your bridge configuration to a new file, `.env`, which is in the same directory as `docker-compose.yml`. Here's a template: ``` # Your bridge's Tor port. @@ -24,18 +20,14 @@ PT_PORT=Y EMAIL=Z ``` -Replace `X` with your desired OR port, `Y` with your obfs4 port (make sure that -**both** ports are forwarded in your firewall), and `Z` with your email address, -which allows us to get in touch with you if there are problems with your bridge. -With your bridge configuration in place, you can now deploy the container by -running: +Replace `X` with your desired OR port, `Y` with your obfs4 port (make sure that **both** ports are forwarded in your firewall), and `Z` with your email address, which allows us to get in touch with you if there are problems with your bridge. +With your bridge configuration in place, you can now deploy the container by running: ``` docker-compose up -d obfs4-bridge ``` -This command will automatically load your `docker-compose.yml` file while -considering the environment variables in `.env`. +This command will automatically load your `docker-compose.yml` file while considering the environment variables in `.env`. You should now see output similar to the following:

1 0

[community/slideshow] Fix typo in "HTTPS for your onion service"
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 6d8f42fa34bab014ece610ea9bb0a55a003fa8e9 Author: Kunal Mehta <legoktm(a)member.fsf.org> Date: Tue Mar 2 20:43:40 2021 -0800 Fix typo in "HTTPS for your onion service" --- content/onion-services/advanced/https/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/onion-services/advanced/https/contents.lr b/content/onion-services/advanced/https/contents.lr index 04c249c..c49fd7a 100644 --- a/content/onion-services/advanced/https/contents.lr +++ b/content/onion-services/advanced/https/contents.lr @@ -19,7 +19,7 @@ body: When visiting a site over HTTPS (HTTP over TLS), the TLS protocol prevents data in transit from being read or manipulated by man in the middle attacks, and an x.509 certificate obtained from a Certificate Authority (CA) is validates that the user is actually connecting to a server representing the domain name in the browser address bar. Modern browsers indicate that a connection is insecure if not using TLS, and require that a TLS connection is authenticated by a CA-issued x.509 certificate. -When visiting a site over the onion services protocol, the Tor protocol prevents data in transite from being read or manipulated by man in the middle attacks, and the onion service protocol validates that the user is connected to the domain name in the browser address bar. +When visiting a site over the onion services protocol, the Tor protocol prevents data in transit from being read or manipulated by man in the middle attacks, and the onion service protocol validates that the user is connected to the domain name in the browser address bar. No certificate authority is required for this proof, because that name is the actual public key used to authenticate the underlying connection. As ".onion" is a [special top level domain name](https://tools.ietf.org/html/rfc7686), most Certificate Authorities don't have support for issuing X.509 certificates for onion sites.

1 0

[community/slideshow] Apply 4 suggestion(s) to 2 file(s)
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 0fc27502b807744da09e177fcc5aed6f8cf895ad Author: emma peel <emmapeel(a)torproject.org> Date: Wed Mar 3 17:11:03 2021 +0000 Apply 4 suggestion(s) to 2 file(s) --- content/localization/current-status/contents.lr | 6 +++--- content/localization/pick-a-project/contents.lr | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/localization/current-status/contents.lr b/content/localization/current-status/contents.lr index 274b4ea..25c2860 100644 --- a/content/localization/current-status/contents.lr +++ b/content/localization/current-status/contents.lr @@ -16,11 +16,11 @@ html: two-columns-page.html --- body: -We have some languages more active, with a number of active and committed contributors (as French, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. +Some languages are more active than others with a higher number of active and committed contributors (such as French, Russian, Portuguese). However you are still welcome to help us with these languages, even after the translations are complete. Our translations are incomplete for a lot of languages. They may be spoken by fewer people around the world, but it is still critical that we improve access to Tor for people who do not speak English. -You can see the open tickets about translation problems on our [bugtracker](https://gitlab.torproject.org/tpo/community/l10n/-/issues). +You can see the open tickets about translation issues on our [bugtracker](https://gitlab.torproject.org/tpo/community/l10n/-/issues). Our documentation is very important for users around the world to be able to use Tor and Tor Browser: -This includes the Tor Browser User Manual, the Support Portal, the Tor Project Website and this website, the Community Portal. +This includes the Tor Browser User Manual, the Support portal, the Tor Project website and the Community portal. diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index 532b24b..c8f6aa1 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -19,7 +19,7 @@ We want our tools to be available and localized for anyone who wants to use them <img class="col-lg-6" src="../../static/images/localization/stats.png"> -Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language, but don't start a regional variant of your language if there is a more general language available (for example: contribute to the French translation, instead of French-Canada). +Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language, however don't start a new regional variant of your language if there is a more general language available (for example: contribute to the French translation, instead of starting Canadian French). The reason is that every language needs resources, a set of committed translators, makes compilations take longer, and takes more space in servers. There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated, there are always updates and more pages to translate.

1 0

[community/slideshow] update l10n requirements as discussed at https://gitlab.torproject.org/tpo/community/l10n/-/issues/40020
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 60429f40196cec08a6130e45e494f423ce2c85f9 Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 2 10:04:05 2021 +0100 update l10n requirements as discussed at https://gitlab.torproject.org/tpo/community/l10n/-/issues/40020 --- content/localization/becoming-tor-translator/contents.lr | 2 +- content/localization/current-status/contents.lr | 11 ++++------- content/localization/pick-a-project/contents.lr | 12 +++++++++++- 3 files changed, 16 insertions(+), 9 deletions(-) diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index 362df91..02298b7 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -8,7 +8,7 @@ _template: layout.html --- title: Becoming a Tor translator --- -subtitle: Our localization efforts happen in the Localization Lab Hub on Transifex, a third-party translation platform. Learn how to sign up and begin contributing. +subtitle: Learn how to sign up and begin contributing. --- key: 1 --- diff --git a/content/localization/current-status/contents.lr b/content/localization/current-status/contents.lr index e9131f6..274b4ea 100644 --- a/content/localization/current-status/contents.lr +++ b/content/localization/current-status/contents.lr @@ -16,14 +16,11 @@ html: two-columns-page.html --- body: -We have some languages in very good shape, with a number of active and committed contributors (as French, Spanish, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. +We have some languages more active, with a number of active and committed contributors (as French, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. Our translations are incomplete for a lot of languages. They may be spoken by fewer people around the world, but it is still critical that we improve access to Tor for people who do not speak English. -Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language. +You can see the open tickets about translation problems on our [bugtracker](https://gitlab.torproject.org/tpo/community/l10n/-/issues). -Right now, we need the most help with Farsi (Persian), Arabic, and Korean. But many other languages are being translated, as you can see here: - -<img class="col-lg-6" src="../../static/images/localization/stats.png"> - -You can see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c…. +Our documentation is very important for users around the world to be able to use Tor and Tor Browser: +This includes the Tor Browser User Manual, the Support Portal, the Tor Project Website and this website, the Community Portal. diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index f651937..ca6122c 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -19,9 +19,19 @@ We want our tools to be available and localized for anyone who wants to use them <img class="col-lg-6" src="../../static/images/localization/stats.png"> -Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support portal: +Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language, but don't start a regional variant of your language if there is a more general language available (for example: contribute to the French translation, instead of French-Canada). + +The reason is that every language needs resources, a set of committed tranlators, makes compilations take longer, and takes more space in servers. +There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated there are always updates and more pages to translate. + +It is more scalable if we contribute to a translation that will benefit more users, and be up to date because it will count with the help of more volunteers. +For that we also ask you to form a team for your language: this way, all the contents can be reviewed by another person and the translation will be of better quality, and it is more possible that it is maintained. + +Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support Portal: * Tor Browser is translated in many different Transifex resources, but you can see the [Tor Browser total strings translated per language](https://torpat.ch/locales) to see where help is needed. * The Tor Browser User Manual is a very useful resource for new users that do not speak English, see [Tor Browser User Manual translation statistics](https://torpat.ch/manual-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. * The [Support portal](https://support.torproject.org/) is also a valuable resource for all Tor users, see [Tor Support portal translation statistics](https://torpat.ch/support-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. + +We are also translating this page, the Community Portal: * The [Community portal](https://community.torproject.org/) is this website, where you can find ways to contribute to Tor. Help us [translate](https://www.transifex.com/otf/tor-project-support-community-port… it.

1 0

[community/slideshow] Update contents.lr
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 681232c6ba8cbd43e808399724e776d3ef8b6d92 Author: Llim3s <79686472+Llim3s(a)users.noreply.github.com> Date: Tue Mar 2 17:03:42 2021 +0100 Update contents.lr read some terms of service and contacted a bunch of hosters in germany and wrote down the results --- .../community-resources/good-bad-isps/contents.lr | 35 ++++++++++++++-------- 1 file changed, 23 insertions(+), 12 deletions(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index f8da4ae..c6dca64 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -87,19 +87,30 @@ For network diversity and stronger anonymity, you should avoid providers and cou | **Company/ISP** | **ASN** | **Bridges** | **Relay** | **Exit** | **Comments** | **Last Updated** | |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [Weesly](http://weesly.de) | - | Yes | Yes | Yes | Note that you should let them know about your intention when ordering a server or in advance. | 06/2013 | -| [EUServ](http://euserv.de) | - | - | Yes | No | They have a bad support, but if you know how to maintain your server, this ISP is a good choice. | - | -| [IPX-Server](https://www.ipx-server.de/) | - | Yes | Yes | - | - | - | -| [Keyweb](https://www.keyweb.de/) | - | - | No | No | "Unfortunately this is not possible with us." | 2020 | -| [Afterburst](http://afterburst.com) | - | - | Yes | No | - | - | +| [EUServ](http://euserv.de) | AS35366 | Yes | Yes | Yes | "Relays only allowed on dedicated Servers Prime64 and Pro64, Exit nodes only allowed on Prime64 and Pro64 with Pro-Option, own subnet, RIPE entry along with publicly visible abuse and police contact." | 03/2021 | +| [IPX-Server](https://www.ipx-server.de) | - | Yes | Yes | - | - | - | +| [Keyweb](https://www.keyweb.de) | AS31103 | Yes | Yes | Yes | "Everything that is in accordance with current jurisprudence is permitted on our servers." | 03/2021 | +| [Afterburst](http://afterburst.com) | AS29761, AS8100 | - | Yes | No | - | - | | [myLoc Managed IT](https://myloc.de) | AS31010, AS24961 | Yes | Yes | No | - | 2018-10-25 | -| [linevast](https://www.linevast.de/) | - | Yes | Yes | Yes | Only allowed on dedicated servers | 13/11/2015 | -| [Server4You](https://www.server4you.de/)| - | Yes | Yes | No | Part of [Intergenia AG](http://www.intergenia.de/)), I've asked Server4You support and they state servers with complaints about Tor will be canceled immediately (see the quote in the "Bad Experience" section) | - | -| [Hetzner](http://hetzner.de/) | - | - | Yes | No | Offers good dedicated root servers for a good price. | - | -| [Contabo](https://contabo.de) | - | Yes | Yes | Yes | Has no restriction for relays or exit nodes. However, possible abuse complaints will be forwarded to the owner and need to be addressed. | 2018/06 | -| [Strato](https://strato.de) | - | - | Yes | No | Exit-Nodes are prohibited by their general terms and conditions | - | -| [PraHost](https://www.prahost.com/) | - | - | Yes | Yes | Stated in November 2014 that they allow exit nodes if abuse complaints are handled. Suspends the server if no "valid" action (read: blocking) is taken within 24 hours of an abuse ticket. Their ticket system does not reliably handle email replies, use the web interface instead. | 2017-10-31 | -| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server/) | - | - | Yes | No | - | - | -| [NetCologne](https://www.netcologne.de/) | - | - | Yes | Yes | - | - | +| [linevast](https://www.linevast.de) | AS201206 | No | No | No | | 03/2021 | +| [Server4You](https://www.server4you.de)| AS131914 | No | No | No | - | 03/2021 | +| [Hetzner](http://hetzner.de) | AS24940 | Yes | Yes | Yes | Offers good dedicated root servers for a good price. "It is not a Problem, however, abuse reports can lead to a server lock" | 03/2021 | +| [Contabo](https://contabo.de) | AS51167 | No | No | No | TOR prohibited due to terms of service | 03/2021 | +| [Strato](https://strato.de) | AS6724 | No | No | No | - | 03/2021 | +| [PraHost](https://www.prahost.com) | - | Yes | Yes | Yes | "If there is any abuse notice received, you need to solve it in given time, else your IP will be blocked until you take any action" | 03/2021 | +| [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server) | AS34011 | Yes | Yes | Yes | Only allowed on jiffybox | 03/2021 | +| [NetCologne](https://www.netcologne.de) | - | - | Yes | Yes | - | - | +| [Signaltransmitter](https://signaltransmitter.de) | AS24961 | Yes | Yes | Yes | "In principle, we do not limit our services apart from mining bitcoins" | 03/2021 | +| [Netcup](https://www.netcup.de) | AS197540 | Yes | Yes | Yes | TOR allowed on VPS and rootservers | 03/2021 | +| [Onyxhosting](https://onyxhosting.de) | - | No | No | No | - | 03/2021 | +| [IP-Projects](https://www.ip-projects.de) | AS48314 | No | No | No | - | 03/2021 | +| [Lansol](https://www.lansol.de) | - | No | No | No | - | 03/2021 | +| [delta.networks](https://www.delta-networks.de) | AS9937 | No | No | No | - | 03/2021 | +| [VPS2Day](https://www.vps2day.com) | AS58329 | Yes | Yes | No | Exit nodes prohibited due to terms of service | 03/2021 | +| [Serverprofis](https://www.serverprofis.de) | AS5539 | No | No | No | - | 03/2021 | +| [manitu](https://www.manitu.de) | AS34240 | No | No | No | "I´m sorry - even if the network has great added value for specific purposes, we have decided to prohibit TOR services on our network" | 03/2021 | +| [active-servers](https://www.active-servers.com) | AS197071 | Yes | Yes | Yes | "Usually this leads to abuse mails, which only cause trouble – but basically we have nothing against it" | 03/2021 | +| [UltraVPS](https://www.ultravps.eu) | - | No | No | No | "We are not the right host for your project" | 03/2021 | ### Hong Kong

1 0

[community/slideshow] add language redirects for homepage. will-fix: https://gitlab.torproject.org/tpo/web/community/-/issues/154
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 346bdbce7b8974a267f86baea9bb1663c1d6d7e1 Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 2 21:04:04 2021 +0100 add language redirects for homepage. will-fix: https://gitlab.torproject.org/tpo/web/community/-/issues/154 --- .htaccess | 1 + 1 file changed, 1 insertion(+) diff --git a/.htaccess b/.htaccess index 893b7b1..548371a 100644 --- a/.htaccess +++ b/.htaccess @@ -19,4 +19,5 @@ RewriteRule ^ga-IE/(.*) /ga$1 [R=302,L] # but don't have a community page # You can see them at https://dist.torproject.org/torbrowser/, pick the last alpha for the most languages # this languages are the translation priority for the community portal! +RewriteRule ^(ar|ca|cs|da|de|el|fa|fr|ga|he|hu|id|is|it|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-BR|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)$ / [R=302,L] RewriteRule ^(ar|ca|cs|da|de|el|fa|fr|ga|he|hu|id|is|it|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-BR|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)/(.*) /$2 [R=302,L]

1 0

[community/slideshow] Apply 2 suggestion(s) to 1 file(s)
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 8449708e2fa5412d5d8b63bed7cf1dd8facae6a8 Author: emma peel <emmapeel(a)torproject.org> Date: Wed Mar 3 17:45:34 2021 +0000 Apply 2 suggestion(s) to 1 file(s) --- content/localization/pick-a-project/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index a0f2c6a..72c3f4c 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -24,9 +24,9 @@ Please consider [helping with translations](/localization/becoming-tor-translato This is due to the fact that each additional language requires more resources, including a set of committed translators and space on our servers. There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated, there are always future updates and new pages needing translated too. +The more users that will benefit from a translation, the more scalable that translation becomes – as it will also benefit from the help of a larger number of volunteers keeping it up to date. -It is more scalable if we contribute to a translation that will benefit more users, and be up to date because it will count with the help of more volunteers. -For that we also ask you to form a team for your language: this way, all the contents can be reviewed by another person, and the translation will have better quality, and it is easier to maintain. +We also recommend forming a team for your language: this way, the content can be reviewed by at least one other person, producing translations that are of higher quality and are easier to maintain. Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support portal:

1 0

[community/slideshow] add ggus suggestions
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 1c18ed7b4da5c26796ef98ddf664bff478cf3295 Author: emma peel <emma.peel(a)riseup.net> Date: Wed Mar 3 15:09:02 2021 +0100 add ggus suggestions --- content/localization/pick-a-project/contents.lr | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index ca6122c..532b24b 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -21,11 +21,11 @@ We want our tools to be available and localized for anyone who wants to use them Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language, but don't start a regional variant of your language if there is a more general language available (for example: contribute to the French translation, instead of French-Canada). -The reason is that every language needs resources, a set of committed tranlators, makes compilations take longer, and takes more space in servers. -There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated there are always updates and more pages to translate. +The reason is that every language needs resources, a set of committed translators, makes compilations take longer, and takes more space in servers. +There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated, there are always updates and more pages to translate. It is more scalable if we contribute to a translation that will benefit more users, and be up to date because it will count with the help of more volunteers. -For that we also ask you to form a team for your language: this way, all the contents can be reviewed by another person and the translation will be of better quality, and it is more possible that it is maintained. +For that we also ask you to form a team for your language: this way, all the contents can be reviewed by another person, and the translation will have better quality, and it is easier to maintain. Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support Portal: @@ -33,5 +33,5 @@ Although we would value your contribution to any of the projects above, our most * The Tor Browser User Manual is a very useful resource for new users that do not speak English, see [Tor Browser User Manual translation statistics](https://torpat.ch/manual-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. * The [Support portal](https://support.torproject.org/) is also a valuable resource for all Tor users, see [Tor Support portal translation statistics](https://torpat.ch/support-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. -We are also translating this page, the Community Portal: +We are also translating this page, the Community portal: * The [Community portal](https://community.torproject.org/) is this website, where you can find ways to contribute to Tor. Help us [translate](https://www.transifex.com/otf/tor-project-support-community-port… it.

1 0