@switchingsocial @L1Cafe @rnickson I really don't know. But they do know what Tor is, and blocking its IPs just because they produce a lot of traffic is just playing dumb in order to avoid facing their real task (identify and stop genuine attacks), if not something else (and here I could readily accuse them of interfering with net neutrality).
If they're not willing (or not able) to provide the service they should be stopped.
@antonlopez @switchingsocial@mastodon.at @rnickson unfortunately, that is simply not true. They don’t just block Tor because they “produce a lot of traffic”, but because malicious actors often abuse the Tor service. This is a fact.
And given the fact that a single Tor exit node could be serving both a malicious actor and (for example) a journalist reporting on an oppressive regime, if both use Tor browser, Cloudflare is unable to perform fingerprinting, and thus serve challenges to both users.
@L1Cafe @switchingsocial @rnickson
That's what @rnickson said, not me. Either way, they block a huge percentage of genuine traffic, thus providing a lousy service to their customers (most of them unaware, I guess), and more importantly, restraining net access to Tor users, which I think it's shameful.
Btw, not only journalists under oppressive regimes use Tor on a daily basis. A lot of people just don't want to be traced given the state of affairs, and I think that's quite reasonable.
@sheogorath Cloudflare onion service? That is very interesting. Where can I learn more?
@antonlopez @switchingsocial@mastodon.at @rnickson
@sheogorath nice! I will definitely be implementing this over the summer, many thanks!
@L1Cafe
Here you go: https://blog.cloudflare.com/cloudflare-onion-service/
And if you want to implement it yourself, you can have a look at my article about an own, self-hosted version:
https://shivering-isles.com/Shivering-Isles-onion-service
@antonlopez @switchingsocial @rnickson