100%? Impossible. But they can effectively ban it.
Pass a law that makes any US company, or company doing business in the US, not allowed to host E2EE-enabled apps. This now bans them from the App Store and Play Store. 99% of users won't find or choose to side-load for android users. Then they can make E2EE actually illegal to distribute in the US. They'll almost never bother going after individuals, but this effectively makes hosting a US-based website unable to distribute E2EE programs. So people will need to use foreign sites. Which the US can force ISPs to block via a whack-a-mole on individual sites.
This isn't very likely, but hell Congress was decently close to banning TikTok for no real reason so who knows?
They're all uppity that to use cloudflare proxy they have to terminate the ssl connection there. So technically cloudflare can sniff all the traffic. But that's kind of the point of WAFs and Reverse Proxies.
I would argue that the sheer amount of data throughput that Cloudflare has, you'd have to really be on a list to be monitored... and they certainly cannot just log all data willy nilly.
I suppose this one is quite simple. How can they cache, if they don't MitM the connection? I don't think it would be technically possible. If you want the cache/CDN you just need to use a company you trust. If you don't trust them then you don't get the cache/CDN.
I might be missing something but the document seems to be comparing Cloudflare to the great firewall of China and calling them criminal because of things they could potentially do?
On the other hand I got a different protocol (& implementation up and running) that can be used right away. It's like IPFS but easy to "install" (a double click and a port forward is all that's needed), you are also in control of your data and of course you can change the data without changing the link.
Don't get me wrong, IPFS paved the road. But today we have better ways to do things.
Close, but with the added possibility to change the data (like a website/blog/chat) and not only have static data.
So on this protocol, you can have a website with a link to my website, who has a link to yours. Maybe that doesn't sound crazy cool :-) but filecoin, IPFS etc just does not have that functionality (with them you have a key/link, and it is locked to 1 data. Fix a typo in your text and you have to redistribute a new key/link on the old web or similar, it's totally static), and for me it's a must if you want to provide a functioning "new web".