after learning about Blossom, IPFS sounds over engineered solution.

yes you can use IPFS similar to Blossom, extract hash from gateway URL, try it on other gateways, etc. but with IPFS the nodes themselves has to discover the content, which takes forever or never. its more expensive to run an IPFS node.

but Blossom is just a CDN endpoint protocol. its lightweight compare to IPFS, cheaper, easier to setup or implement. you can even use it with existing CDN solutions like S3/R2 by proxying endpoints.

not to mention that it doesnt try to encourage something like ipfs:// URIs. you just use a normal URL to a Blossom CDN, and the content is just there like a normal CDN. but if its not there, you can extract the hash and try it on other Blossom CDNs. and also Nostr clients might mirror content you see or interact with on behalf of you. for example if you zap or like a post with a media, your client can automatically tell the Blossom CDNs it knows to mirror that content if they havent already. So instead of Blossom CDNs discovering each-other, clients make the discovery for them. which is amazing and more straight forward.

its like IPFS but all fat is removed.