So this takes Nostr stuff and adds it to an RSS feed like how nostr:npub196qvw7utjs0cnztlg4aww98ekql9svm6c4wlv6sug70nzz0uujxsprafme does?
Podcasting works the other way where you add your stuff to the feed and the apps display it.
Maybe the same thing kind of idk this is all new territory but very cool.
The only requirement in PC 2.0 is that it's using an RSS feed that uses the name space. Everything else is up to you. You can even add experimental stuff as long as apps know what to do with it.
That's how chapters, transcripts, lightning etc got added to PC 2.0. The podcasting 2.0 show added it the their feed as a test for apps to use.
Lost the point of this post but TLDR happy to see people in Nostr looking into PC 2.0 for real.
Similar I guess to Castr, but architecture is very different. Castr uses kind:1.
I've been working with Oscar at fountain to see how their adding Nostr and they are using kind:1 but I don't know what any of this means thb but what to say that lol.
Oscar is working on a write up but I got this now posting to Nostr.
A fork of a fork of a fork or a restarted project.
Lighting is a bigger issue for us but sharing the metadata is part of that.
https://itdv-lightning-fixed-git-zaps-chadfs-projects.vercel.app/
nostr:npub1k34lqqeqa90e269gtw4r5z3h0hgejj9hnf8lpkmc2jzq5tl2ru8qqkwhjf
They use kind:1 for sharing podcasts. Oscar and I talked about Podstr and the spec when I first worked on it over a month ago. We discussed making a NIP for podcasts.
Cool. He's our Nostr rep in PC 2.0 so we're following his lead on this so if anyone build to what he's doing we should be good.
and by were I mean maybe 3 other people and that's not a joke 😁.
myself and nostr:npub1gfh3zdy07r37mgk4hyr0njmajapswk4ct6anc9w407uqkn39aslqqkalqc mainly at least on the getting working code side of things.
Thread collapsed
Thread collapsed
Thread collapsed
Thread collapsed
