An important new argument for #federation is the new #cloudact. You don't want your data stored by a US company anywhere in the world.
It's also an argument for #e2e #encryption.
But actually it's mostly sad to see how people throw other people #privacy away without being interested in the consequences.
The tweet that inspired me to write this toot said: "When privacy is criminalized, only criminals have privacy. We got sold out, again."
We are all affected.
Oh and to make this clear, #cloudact not only affects the obvious services like Facebook, Twitter, Google,…
It's a real danger for the fediverse as well as long as instances are hosted on #digitalocean, #AWS, etc. servers because they are also affected.
As I said before everyone is effected.
@sheogorath tor people have been criticizing (yelling actually) cloudflare for a long time, as it is MITM-as-a-service. No doubt it should be raised earlier. Ironically this instance uses cloudflare as well. @PeterCxy
@sheogorath @PeterCxy It is justifiable as centralized is usually more efficient than decentralized, but for people willing to sacrifice 500ms and 10$/mo it just smells disgusting. Yet "people are using it"
@sheogorath @PeterCxy I still remember that knownsec used a metaphor to explain their CDN service - joining a mall so that you don't need to setup your own chain stores everywhere. Didn't think about centralisation back then.
@ghost @PeterCxy Tor people criticized Cloudflare for blocking tor users, not for being a CDN. The problem is that people tend to no longer user the tor browser because it's blocked on so many web pages and instead use their insecure default browser.
Has nothing to do with the current problem.
And yes, Cloudflare is a big MITM but that's how reverse proxies/WAF works ^^ I wouldn't blame them for that.
@sheogorath @PeterCxy I remember someone even suggested to block cloudflare IPs by raising a security error (treat it as a TLS error), so I think it's beyond discrimination against Tor.
@ghost Are you sure this was a member of the tor project and not just an enthusiast who "overdid" it?
It's over-blocking for no reason as the use-case itself is completely valid. I'm also wondering if cloudflare will make their promise true to provide .onion services once hidden services no longer rely on SHA1 hashes. (Which they no longer do with V3)
We will see ^^
@ghost @sheogorath The only point I am still using Cloudflare on this instance is that the beast VM I am running Mastodon on has no public IPv4 addresses. The only reverse proxy I had back then was a Aliyun VPS which is a worse idea to me than using Cloudflare.
Oh and as it just came up to my mind: #cloudflare is also affected by #cloudact.
So basically 30% of the web are now open for all kinds of attacks on user's #privacy.
Thanks US for breaking the entire trust on the internet…