It's not fully decentralized and more focused on reducing bandwidth load on the actual site than anonymity or resilience, but the sadpanda's H@H system is one example of such a thing: https://ehwiki.org/wiki/Hentai@Home

e: this is mainly interesting because it demonstrates that there are people willing to donate storage/compute/bw to p2p nsfw image hosting, not because the underlying tech is particularly revolutionary or should be used as a model for future systems

We're working on an IPFS based FB Groups solution. We're not running after NSFW content, but people will be able to create private groups, encrypt and self-host their content, and encrypt it. We're also planning on having web support so you can load content from your node. So I think eventually people will consume the app this way too! Would love your feedback: https://permaweb.io

IPFS seems like a really good solution. I've read other posts on here on how it's difficult to setup websites on IPFS, but just straight up media (images and video) seem like a perfect use case.

Practical IPFS image hosting looks an awful lot like image hosting without IPFS. Most of your traffic's gonna be through gateways, not over IPFS proper. You've still gotta have always-on servers pinning (storing) everything for reliability. There also doesn't seem to be a good way to make mobile devices—most of the clients out there—useful parts of the distributed network.

HN throws IPFS around a lot as if it's free storage + free bandwidth. But as you point out, you still must run an origin server. At which point it's just a slower, crappier CDN where you stand up your other CDN nodes yourself. Your content doesn't just magically spread to random nodes once you broadcast it.

Will people use a service for NSFW contents? I doubt.