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 β