Thread

So, right now, nostr can only be used for the feed fetching/notification part. Content delivery is all done over http, so multimedia content is not censorship resistant, only letting people know where to find it is. What I'm working on is a piece of software that basically uses bittorrent to deliver the multimedia content and nostr to deliver the message that the content is available. The infrastructure is already there for that, and paid seedboxes already exist, most bit torrent clients are already able to handle remote auth so paying for hosting is already a breeze. Censorship is nonexistent on the bittorrent network, monetization is solved with nostr. I hope to get this out the door Soon™, and am more than halfway done, but real life happens and I've got responsibilities I can't shirk. I think with this combination, there won't be a bandwidth boddleneck for content. If someone wants to ensure that their content is always made available, yes they'll need to self host or pay someone for that. That includes seeding and relays. It's probably a good idea to run a relay anyway, and for anonymity, to leave it open to others to use. But you should *always* publish to more than one relay, to ensure that your content is censorship resistant.

Replies (2)

↩ replying to Adam Curry
This is cool, but from what I can see, it's still streaming the audio over http, right? Which is fine, that's how podcasting works, notify of new content with RSS, stream over http. It's currently not hard to share a link to your followers on a nostr note that has a podcast in it, a format where a podcast player can understand and play it the way it understands RSS (versus just clicking the link in your feed and opening it in an audio player) is cool, but it's not censorship resistant, which is probably the main problem I'm trying to solve.