yo nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 are Fountain podcasts published as nostr events? I don't mean live events but podcast episodes. Where I can see the kinds Fountain is using? Curious about how boosts work too, I want to support as much as possible in nostr:npub1gm7gw8q6akeft2pjt270we35vlff0v9g2fene6cxkz2h68q5hl6qls0fte
Discussion
support kinds yo episodes. I nostr:npub1gm7gw8q6akeft2pjt270we35vlff0v9g2fene6cxkz2h68q5hl6qls0fte as in is nostr can Curious I possible see mean about events I live Fountain but don't nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 boosts too, Where how Fountain podcast work the to much published are as podcasts as want events? using?
https://github.com/nostr-protocol/nips/pull/1043 afaik Fanfares (and maybe Fountain) plan on using this
awesome, I did a quick search for these kinds and it's mostly old and test events :_(
- podcast episodes are not nostr events no - the reason being is that we want the social aspect of nostr to apply to all podcasts without podcasters having to make a conscious choice to use nostr
- podcasts are referenced in events using NIP-73 External Content IDs i + k tags, the k tag represents the external content id kind so you can query all the events for that kind from any relay (all events referencing podcasts), and the i tag has the podcast show / episode guid value so you can query all events for a specific show / episode - the guids are an rss podcast spec unique id that is maintained even if you switch hosting companies
- boosts work using a quoted zap event - the zap receipt (kind 9735) is embedded in the kind1 note in the same way quoted notes are - with the nostr:nevent1... encoding
- also for comments we plan to switch from kind 1 to kind 1111 - should have this done soon
awesome thank you, all makes sense. I'll take a look at NIP-73 and `i` and `k` tags to make sure notes referencing a podcast link to it somehow. big fan of Fountain btw, keep up the great work!