Zero mention of nostr in the comments too.

Used nostrudel for the first time today. What the fuck.

came back from riga and my desktop notedeck has 41000 notes loaded in my home timeline. ya'll post a lot!

I am not building a nip-35 client. I do not like the torrent specification in nip-35. I don't actually need a specification for an event type for this, and IMO most applications seeking to use nostr don't either. I am building what I'm building without submitting a NIP and without any application specific protocol implementations at all. This is something that a user should be able to subscribe to content producers with any existing nostr client and view with existing client software, such as an external torrent streaming application.

I don't like the specification for several reasons, first is that there are application specific tag definitions in the spec. A general torrent spec should not have an IMDB specific tag. It seems this is built with a particular application in mind to support someone's torrent client for piracy (and I'm all for piracy but what I'm building is not a piracy specific tool) and not for generally sharing torrents.

That said, I'm probably going to give users the option to publish their torrents as kind 2003, but in MVP initially, and later by default, notes will be published kind 1.

Well then I think the best way to solve this would be a tool that enables content creators to publish a torrent and then a note notifying followers of that content, and discussion about it happening in the replies to that content. I think this could be a censorship resistant way to distribute video content, podcasts, music, even images, and it separates hosting of media from relays, it makes the barrier to entry to hosting your own content very low, and allows basically anyone to begin hosting content for others and so democratizes content hosting. I think this is such a good idea in fact that I'm currently building software that does this as we speak.

If one wanted to launch a new podcast today and make it Nostr-native what would be the best way?

kind 1 and Base64

If these are the worst issues then we have come a long way 😅

The client links there are very outdated

I have put in hours and hours researching this and I can't keep this hidden from you all anymore.

What I have learnt is extremely problematic.

A 🧵 in the comments

Not a bad idea. Relay-based feeds would make that reasonably easy if there are places that curate non-bitcoin stuff (doing it client side would be expensive)

Damus Labs talk is at 11:40 at the proof of talk stage. Come check out how damus operates behind the scenes, and more importantly, grab some shiny damus stickers 😎