@jawarajabbi
That's where one is showing signs of not having done the research, bitcoin (and monero) are hosted all over the world by people who use it, tens of thousands have a copy of the ledger, in the form of a blockchain. It is #uncensorable but *does* have certain risks if one's device has malware (#nonFreeSoftware).

It helped #Wikileaks when #Paypal and #Visa (now #CloudGlare) dropped them, for revealing #warCrimes by the US.

Bitcoin does require #computers/people be better, though. 😑

@kev I’ve detected a bit of intellectual dishonesty here. #Fosstodon used the standard default #Cloudflare configs as early as March & for months thereafter, certainly at least as late as May 29th confirmed by someone’s complaint specifically about the block screen.The timeline shows complaints about CF are littered around before & after that point. If you expand some of the threads in that timeline, it’s clear the default CF configs persisted despite Fosstodon staff being told that the default configs were resulting in users being forced to run non-free software & that the configs needed to change. That change never happened because I know I saw the block screen whenever I tried to directly visit fosstodon.

Fosstodon finally made a recent move from CF proxy to CF NS, which was just yesterday announced, a day after my post. I am not checking every day to see what fosstodon does next.

Under the current config, you can spontaneously switch on the CF reverse proxy at any moment with immediate effect without even telling users all their traffic will be seen by Cloudflare (including passwords). It’s in fact the only way that the reverse proxy can work. If you don’t use the MitM certs, CF cannot process the requests for you during an attack.

So the compromise is still in place. The only difference is that now it’s spontaneous instead of continuously ongoing. And most likely you’ve probably not fixed the CF configs, so when you flip that switch users will get a captcha that pushes #nonfreesoftware. The goal should be to get off CF entirely including nameservers.