ic. yes, that's a lot of stuff. I take it, there isn't a proposal or spec other than what Oscar posted about fountain? Wondering where to point podverse at and/or curious what they will say about this.
Login to reply
Replies (2)
Podverse has also been working on V2 for over a year so i dont know what the new version will have but Mitch over there is always open to ideas but hes heads down coding.
The PC 2.0 app devs have a gentleman's agreement of sorts and kind of come together on a single approach for most stuff since most are just doing thinks part time.
Right now there's a discussion if we shift that data over to nostr, or if it gets POSTed to server the podcaster or their host controls. metaBoost is the current proposal I'm most behind. 
My 2 cents, send it to the podcaster's server, and if they want to post it on nostr, they can have a function that takes care of that. But there's a lot going on, like keeping track of how many sats were sent and the time sent that the podcaster is going to want to keep track of for potential tax reasons, so they'll want to store all of that data in their own data base.
Not saying signing a nostr note and sending it via relay isn't viable, but converting the JSON to a flat array, signing the note, etc is part of the discussion of how metadata should be handled.
GitHub
Proposal: <podcast:metaBoost> tag and API standard · Podcastindex-org/podcast-namespace · Discussion #676
This proposal is to add a new <podcast:metaBoost> (Boost Metadata) tag which specifies an API where the podcaster would like the application to sen...