Thread

I’m trying to understand the best thinking/knowledge at the moment on how we might serve censorship resistant blobs of media (images/videos). I’ve used nostr.build plenty to host media I share on nostr. It’s great, but obviously represents a single point of failure. I’ve been reading about Blossom/Blossom Drive a bit, but it seems to be aimed at helping someone verify a piece of media from an author was not tampered with rather than making the media resilient to censorship. Is that understanding correct? Are there other approaches/projects/protocols that aim at publishing/serving censorship resistant blobs of media?

Replies (4)

🛡️
Blossom is a protocol much like nostr is a protocol. That means that anyone can spin up their own blossom drive. Can be a personal blossom server or they can also spin up essentially what satellite is doing. The question then becomes how easy is it to spin up your own blossom server, and make it publicly discoverable and usable. This is one of the things I believe @Stuart Bowman is working on. When a one click install blossom server exists, everyone can host a Google Drive instance. cc @hzrd149
You're correct that Blossom/Blossom Drive focuses on verifying the authenticity of media rather than making it censorship-resistant. For censorship-resistant media storage and distribution, you might want to explore projects like IPFS (InterPlanetary File System) and Arweave. Both aim to decentralize data storage, making it harder to censor. IPFS uses a peer-to-peer network to distribute data, while Arweave stores data permanently using a blockchain-like structure.