Skip to content

NIP-74: Podcasts#2211

Open
ChristianChiarulli wants to merge 1 commit intonostr-protocol:masterfrom
ChristianChiarulli:podcasts
Open

NIP-74: Podcasts#2211
ChristianChiarulli wants to merge 1 commit intonostr-protocol:masterfrom
ChristianChiarulli:podcasts

Conversation

@ChristianChiarulli
Copy link
Contributor

Here is a site you can use to test out the nip: https://www.transmit.fm/

@staab
Copy link
Member

staab commented Feb 4, 2026

@MerryOscar

@prhasn
Copy link

prhasn commented Feb 4, 2026

Good idea but seems overly complex. Tiny example is explicit should be just a boolean. Overall, needs more generic tags otherwise in implementation most clients will only show a few of data included and will result in conflict over which data are important to publish in first place.

@ChristianChiarulli
Copy link
Contributor Author

The explicit tag is that way to support legacy platforms, we can simplify it if everyone agrees tho:

https://help.podbean.com/support/solutions/articles/25000014076-setting-the-explicit-tag-in-rss-feed

What do you mean by it needs more generic tags @prhasn?

@prhasn
Copy link

prhasn commented Feb 4, 2026

What do you mean by it needs more generic tags @prhasn?

Example, instead of having multiple tags to denote people involved we should just have p tags only, and clients can fetch their data. The rest should fit in content tag.

Also instead of duplicating tags in show and episode, tags like funding should be at episode level only.

@ChristianChiarulli
Copy link
Contributor Author

ChristianChiarulli commented Feb 4, 2026

The person tag is useful for compatibility with podcasting 2.0:

https://podcasting2.org/docs/podcast-namespace/tags/person

It's not a necessary tag but it allows us to better interop with RSS.

Also not everyone is on nostr so it allows for a podcaster who is involved with the show but doesn't have a nostr profile to be represented on nostr clients.

Using these standard tags we could probably write a simple tool that could import existing podcasting 2.0 compatible podcasts which would allow us to capture some network effect without the user having to either adopt a new platform or maintain both.

For funding I think both can be useful:

show level: memberships, patreon etc..
episode level: one-off campaigns that override the show level for that particular episode

@derekross
Copy link

@ChristianChiarulli
Copy link
Contributor Author

I didn't know there was another place for nips tbh @derekross.

After reading it over I still think i like the design choices in NIP-74 better, so I'm not sure how we move forward here.

@ChristianChiarulli
Copy link
Contributor Author

any updates on this?

@staab
Copy link
Member

staab commented Feb 17, 2026

It sounds like there are at least three standards in the wild, you guys will have to do the work to converge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants