nostr:npub1yfg0d955c2jrj2080ew7pa4xrtj7x7s7umt28wh0zurwmxgpyj9shwv6vg can you add an `i` tag on zap receipts and comments on a song? spotify has this. you could just copy their format.
spotify:track:54KIAHa71rBTDubyUPwiks is the URI for https://open.spotify.com/track/54KIAHa71rBTDubyUPwiks
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 nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5 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.
Nice 🚀
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?
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. nostr:npub1unmftuzmkpdjxyj4en8r63cm34uuvjn9hnxqz3nz6fls7l5jzzfqtvd0j2 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:
