Good reminder today. When building for the sovereign web, 𝐚𝐥𝐰𝐚𝐲𝐬 think decentralization first. And when convenience really requires the implementation of a potential bottleneck or single point of failure, at least implement some kind of fallback or timeout callback that would allow the client to try another path. Until recently, I was a strong supporter of IPFS, as it solved this kind of problem (moved the resolver by the client). My opinion has now changed, and I agree with most of the criticism of IPFS, mainly regarding its overall performance. But content addressing wasn't such a bad idea. Blossom developers should at least try to salvage the good ideas that were in IPFS. View quoted note →

Running Bitcoin Core... 𝚟𝟸𝟿.𝟸.𝟶 until a proper independent and unbiased devs community will properly handle continuous development of the humanity's critical system that Bitcoin is !

L'excellent "Objective Thune", par @Jacques Favier et Philippe Ratte, édité par @PVH éditions est maintenant disponible librement:

/ipfs/bafybeih4dd25xzj45srzv46xnyb756yd5atocpihi35ad4ucbrhg2yo7pi/

A directory of content-addressed files hosted on IPFS.

Satoshi Nakamoto wanted an alternative to the fiat financial system, which is broken and certainly the cause of much, if not almost all, of the suffering in the world today. To achieve that, he first built an alternative. Building first is always the path. But to some, destroying is easier.