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.

Reply to this note

Please Login to reply.

Discussion

strongly suggest you look at https://ipfspodcasting.net/

I thought about IPFS also. But IPFS has a ton of problems and isn't very robust. There's massive maintenance overhead attempting to implement something with IPFS. Bittorrent is very, very robust. It's only real downsides are that swarms connect p2p and so share IP addresses with each other, and that it's mostly labelled as a piracy tool. But for multimedia delivery it can't be beat.

this projects is very stable and is also available on umbrel and start9 already, with integrated lightning splits payments.

I’ve been running ipfspodcating.net for over a year on my Start9 and it works great. Also made 13k in sats from the splits Adam mentioned just for hosting files.

nostr:npub1uqwyafrvsf9z8tyn8gtk40au72znradyla29852uvmdl6lnpz8nsyz43la and nostr:npub15z2javq62eh2xpms7yew0uzqsk4dr7t3q3dq4903uuxdyw2ca3kstx6q95 use it a ton to help distribute their podcasts and music.

I’m at about 12 sats after a month. Not much, but something. Maybe there are some settings I need to adjust to be a better media host.

Most of mine are from when there weren’t as many people running nodes (less nodes bigger piece of the pie). The person using IPFS podcasting picks the percentage of each Boost they want to share with the node runners.

Here’s PC 2.0 for example. 5% of the Boost gets divided by the 46 nodes (that have a lightning wallet connected). I’m not sure what the threshold is but I think it has to be at least 1 sat after all that to send a payment to the nodes.

What I did was go to the active feeds section and pin every feed offering a split.

This is more of a proof of concept but I think it’s really cool even if I don’t get any sats for it.

https://ipfspodcasting.net/Feed

Thanks nostr:npub177fz5zkm87jdmf0we2nz7mm7uc2e7l64uzqrv6rvdrsg8qkrg7yqx0aaq7. Ive added a bunch more favorites. One thing I’ve noticed (I’m very new to IPFS) is that my peer count can vary pretty widely from < 20 to 100+.

I’ve checked to confirm that my port is open but I’m wondering if the variability in peer count indicates some kind of instability I need to look into.

Cool. I could never figure the peer thing out either but mine seems to be working just fine so I stopped worrying about it. Currently at 26 fwiw.

Good to know. At least I’m in good company :-)

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.