Oddbean

Yea new domain. "Use Fleek to upload, store & fetch files from IPFS in an easy to use, performant, and familiar way including UI, API and CLI interfaces. With S3 & Minio compatability, built in pinning orchestration, compression, image resizing, & global CDN, Fleek’s storage solution has everything you need built into one seamless product. "

IDK why, but node reputation seems to make a HUGE difference to file propagation on IPFS. My IPFS node couldn't propagate to save its life at first, but after ignoring it for a year I found my content appears very quickly at gateways across the globe. Of course, my node in Tor-only, so YMMV considerably. Your nostr analogy is very accurate.

ipfs has a non-equity-financing shitcoin-style consensus blossom is not encumbered by this nonsense, and lets you add whatever broadcast mechanism you want to in Domain Driven Design this is exactly the methodology recommended: keep the separate things separated, don't mix them up in Golang and Java programming theory, it's the difference between an interface and an implementation the whole purpose of interfaces (which predate objects by a long time) is to allow simple implementation of some functionality without any assumptions or opinions outside of a simple API this is the right way to do things, and bitcoin does this, lightning does this on top of bitcoin, this is why they are both winners in terms of architecture lightning has a brittleness problem though, and a fog of war around the availability of paths in the state channel web i think that this does maybe indicate the use of chaumian e-cash systems to enable async payments and failover mechanisms, but there may be other options, the Ark protocol might help, either solve or inspire a better solution

i think it will become the glue for the future web with user content on nostr and media hosted on blossom and there will be numerous ways that both are spread around, including using a blossom based protocol to store events