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.
nostr:nevent1qvzqqqqqqypzp78xcep59u0q2fyqvv8z0cgpdh8rtlp6v98xqs60aa92y5pn9r9fqyvhwumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wshsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsqgxmeq0kn7qvcq47f7lfk3ddrxsklzya5kkl6h4k2xkw85ptpmu6j5wjskas