Replying to @⁨Sibbo@sopuli.xyz⁩

@Sibbo I do not see any problem with Letsencrypt. Any CA which is widely trusted has to follow the same rules. This rules are set up by the CA Browser Forum. Which metadata does LE collect? My server's IP address, domain and subdomain, mail address. These are logged in the CT logs. Every CA has to log all certificates in a public CT log. Regardless which CA I choose, these data are public. There are not any critical data or metadata that LE can collect.

Replying to @⁨veniasilente@lemmy.dbzer0.com⁩

You do understand that a P2P proof of work backed global store is just infrastructure? And as egalitarian as DNS servers? And it doesn’t have the storage/compute footprint of a full bitcoin node.

The space of human-readable names is quite small, so proof of work is needed to protect it from being flooded. An alternative is to have your servers have names to be or derived from their public keys, or dissolve content from its location. Which brings its own problems.