This post delves into the impact of #Israeli#surveillance technologies in #Palestine, illustrating how localized instances of its use can have extensive repercussions that pave the way for the widespread acceptance and global adoption of such oppressive practices
"As a developer on the Network Team, you will be part of a small team that develops and maintains the networking software at the core of the Tor network, keeping it secure and improving it for the future." #FediHire
In this role, you will:
- Help design, develop, and improve Arti, our Rust implementation of the Tor protocol. - Contribute to other free, open-source Rust projects
No #MastoAdmin / #FediAdmin should be allowing #Tor IPs to signup if they're doing open registrations in their #fediverse instance anyway. That's just inviting trouble.
If #Wikipedia blocks them, you probably should too. :seija_coffee:
I never said anything about preventing #Tor users from accessing Mastodon. Not even logging-in to their account (so they can sign-up from a "clearnet" IP and then login via Tor afterwards, just like how it's done in #liberachat#IRC). All I'm saying is, if your instance has open registrations without any form of manual vetting or approval before activating the account, then you should prevent #Tor users from just being able to register an account in your instance so your instance isn't just an easy target for spammers to use.
And yes, block the #VPN users too from registering an account. That's what #Misskey's flagship instance at misskey.io already do to prevent non-Japanese users from creating an account there.
It is a very simple tool that checks whether a connection has been made through #Tor or not and returns the result in plain ASCII, without any HTML bloat or HTTPS redirect.
I wish I would have had something like that when I've originally wrote my Elixir implementation of Tor earlier this year.
So, back in 2015, there were multiple groups creating encrypted, anonymizing networks (many of which are still in operation today): #I2P, #Tor, #GNU, #Namecoin.
They went to the #IETF to standardize how browsers would handle their special top-level domains.
(I warned you this was nerdy).
The idea here was that if a user typed domain.i2p or domain.onion into a browser, the browser would leak that request to search engines or DNS servers.
Hey, remember when I said that #HTTP2's spec doesn't require TLS for it to be used, but de-facto it is necessary anyway because mainstream browsers like #Firefox and #Chrome will not support #HTTP/2 without #HTTPS?
Well I just realized now that thanks to #Mozilla and #Google's arbitrary limitations, they've actually made browsing the web with #I2P, #Tor (via onion/hidden services), and #Yggdrassil slower than it should be! The latency in Tor is so damn high that you essentially have to sacrifice speed if you're going to use an onion service that doesn't have an HTTPS certificate (which is unnecessary in the #encryption front because your connection to the onion is already encrypted!).
And I'm not even alone in this thought, look at this comment in bug 1418832 which never got a response from Mozilla.
Basically if you're a Tor hidden service operator, Firefox's devs are telling you to chalk up that $30 TLS certificate from harica.gr for the HTTP/2, and if you're operating a website over I2P or Yggdrasil, well "fuck your #privacy, get stuck in HTTP/1.1 lol"
I normally dunk on HTTP/2 (and personally I'm not even a fan of Tor) but this stupid decision by Mozilla as well as the equally stupid decision to drop HTTP/1.1 #pipelining means downstream (which Tor Browser is) will have to deal with this bullshit speed bump. HTTP/2's #multiplexing would've helped greatly in these average high latency situations!
This is why you never let politician-wannabes control your development
Das #französische Innenministerium und Staatsanwaltschaft in Verbindung mit der Polizei versucht in einem Prozess*, die Verwendung von Consumer-Apps zur #Verschlüsselung wie #WhatsApp, #Signal, #VPN, #TOR, #ProtonMail sowie für Massenspeicher zu kriminalsieren.
Sollte sich das bewahrheiten, was in dem untenstehenden Artikel* steht und es tatsächlich...
Looks very interesting. This service rewrites activities, so in theory it can work as a bridge between disconnected parts of Fediverse, for example between two defederated servers, or between server-centered Fediverse and client-centered Fediverse, or between #Tor instances and clearnet instances.
List of some useful links, news sites, and open web search engines that also provide .Onion service access through Tor :tor:. Each searx site varies on their up time, so it pays to visit the 🗂️SearXNG Index to find alternatives.