Oddbean

@fce803cc thanks, it shouldn't be very complicated. I'll just need a solid few hours to make all the changes needed, and I'm having a hard time getting a few hours at a time to dedicate to PV lately.

@fce803cc so I just console logged the TLV records we send for P2.0, and it seems like at least feedID should be going through? Could it not be showing up for you because we're passing an integer instead of a string? We are also passing the PI ID in 7629175. Is that deprecated for feedID? https://cdn.masto.host/podcastindexsocial/media_attachments/files/111/055/116/237/733/647/original/7d70b7b450121660.png

@fce803cc just a reminder on this. I am curious if Podverse is always missing the feedID, or if it sometimes comes through, and sometimes doesn't. In all my tests so far is appears we are passing a feedID with an integer value, but there could be a case (edge case?) where we are missing it.

@fce803cc another question...passing the feedUrl is going to be trickier than passing the podcastGuid for us...I would have to re-write our ORM queries to specify each individual SELECT for podcast data, from both our podcast and episodes controllers...it's certainly doable, but a lot more more work and more room for error. I'm thinking of just releasing an update with the `guid` TLV for now? I feel like the vast majority of V4V enabled feeds should have a podcastGuid at this point anyway?

@fce803cc ok great. I should be able to add podcastGuid no problem, although why feedID is missing is still a mystery to me. I just sent a boost from our prod mobile app for today's P2.0 episode around 1:10:00 in when the time split is active for 5555 sats, in case you need an example to look for.

@fce803cc yeah...our traffic and downloads keep going up for Podverse, which is great, but the day-to-day overhead grows with it until I've been up over my ears in tasks. We're systematizing and organizing though and I think we'll be back on top of things and making more visible progress soon.