Oddbean new post about | logout
▲ ▼
JoshR | 3 months ago (raw) | root | parent | reply | flag 
 We started adding an `i` tag like this just last week, though it only applies to zaps coming from the mobile app. Have chatted a bit with  @fountain_app about the format. Here's the mobile code: https://github.com/wavlake/mobile/blob/main/hooks/useZap.ts#L39

There is also the `a` tag that references the track/episode id, that'll likely change though once we update how we're publishing tracks as nostr events.
▲ ▼
NotBiebs | 3 months ago (raw) | root | parent | reply | flag 
 Nice 🚀
▲ ▼
NotBiebs | 3 months ago (raw) | root | parent | reply | flag 
 Looking at it now. You’re using the podcast prefix for songs. Wouldn’t it make more sense to make a new wavlake prefix since songs are not podcasts?
▲ ▼
JoshR | 3 months ago (raw) | root | parent | reply | flag 
 Yeah probably, I think this is so a client is able to locate the corresponding RSS feed for all the content metadata, which is within the podcast namespace.  @merryoscar Does that sound right? https://github.com/Podcastindex-org/podcast-namespace

I suppose this is a transitional period until everything becomes nostr native in the future? Not sure how the RSS/nostr relationship will wind up looking down the road. Could wind up being redundant/parallel systems? 🤷‍♂️ 

Here is a fountain example using the same `i` tag format: 
nostr:nevent1qqsvuu996n42u4swzgysp5sh6grgeladcvjrc8vm0kdzx4kre0aeraszyrrtam5st3nvh0kwwuupx7jj775dyyl42gx2cce9gzusslyx8qqf5lxcdvl