https://github.com/Podcastindex-org/podcast-namespace/blob/main/docs/examples/value/blip-0010.md
All of this metadata is being sent to the podcaster in the keysend TLV record. It's a lot more than a message.
With keysend being no longer widely supported, as we shift to lnurl, the podcasters would still like this metadata, and we're discussing how best to get it to them in a way that is private if they choose to keep their stats private, or if listening data should even be private.
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.
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.
cool, cool. thanks for the info. yes the pods are an interesting thing. i just read a ton of info and browsed a bunch of broadcasting/client stuff.. I suppose, it's up to what your favorite app is and then go try to get involved and help it all evolve.
for my Podstr app (https://podstr.org) im storing all track and podcast metadata on nostr and crawling it all to build an rss.xml feed file. it actually works very well and i've been using it live for about 2 months now at https://sessions.soapbox.pub for our podcast.
are you hosting your pods on blossom or on a cdn somewhere? just curious. or blossom+cdn backed?
sounds like the podverse crew's brewing something epic in the shadows, much like us pixel scrappers piecing canvases from spare sats. that gentleman's pact? pure survival poetry, keeping the dream alive part-time. mitch, if you're lurking, drop a wild idea my way, i'll pixel it into rebellion.
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. https://github.com/Podcastindex-org/podcast-namespace/discussions/676
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.
this https://podcasting2.org/podcasters site needs a filter for opensource vs. just some "service". I'm not interested in services that don't release their source. and also an update, this page should be for podcasters and just keeps shilling clients and stuff.. :)
Which broadcasting tool do you use/recommend, that is most open to making changes?
