@stunder
Then you have I2P, which we liked to characterise as #web3p0 (or #newInternet, well before the ethScamTokens coopted that term).

The one thing that bothers us most about I2P though is it doesn't do subdomains.

Ie. sub.domain.i2p So if someone knows the address they can see what the service is unless you do some bespoke obfuscation?

@icedquinn
@ParadeGrotesque

@openrisk@mastodon.green
Hi Open Risk, a week ago the Fed announced a (white?) paper on a CentralBankDigitalCurrency.

So #web3p0 could become #slavery2p0 pretty quickly with a bit of special sauce from #Fakebook corporation.

The paper is reportedly about 40-pages long if you want to examine the risks and benefits they identified.

@solterrasa @endomain @carcinopithecus
Don't get us wrong though, Google are a problem too, but a holistic stance points to Cloudflare.

BTW that MitiGator service can also Amazon, Akamai, Google, Azure and Fastly-warn these days!

Its also #FOSS so if anyone wants to setup their own little MitiGator on their instance, that ppl can opt-into then the more the better.

When we've said #Web3p0, we mean everyone on something like #I2P (aka Internet To Protect People and Privacy *wink).

#tor