@dan613 @js @DamonHD I think the index is even less at 768 because that is the longest an mb4 varchar column index can be.

#api Discussion on full episode search in the Index:

https://github.com/Podcastindex-org/docs-api/issues/132

...if anyone wants to weigh in. I've always avoided it because of substandard results but I'm open to trying again.

...and, now @Podnews says today that they are going to start listing "political skew" information. I think they are getting into semi-dangerous waters with this stuff. Listing brands on shows they haven't sponsored is one thing. But, labeling my politics from analyzing my language in a transcript is a step too far.

My politics change sometimes daily as I read things and become more informed. Being politically labeled is a great way to just piss people off.

Podchaser's "Insights" page tells me that the following brands have sponsored the No Agenda podcast. No Agenda doesn't accept advertising or sponsorships.

@js “Complexifier”. Sounds like the title of a Tool song.

Time for the board meeting! We're running with scissors live with episode 198! They're eating the onions!

https://episodes.fm/1584274529

U.S. Podcasters: If you run your podcast as an LLC, remember that every LLC must register the personal details of it's partners with FinCEN by January 1, 2025. The penalties are stiff if you dont:

https://www.taxpayeradvocate.irs.gov/news/tax-news/january-1-deadline-approaching-for-reporting-beneficial-ownership-information/2024/10/

@nathan Actually, maybe that was the feed urls that were being restricted so hard and not the enclosures now that I think more about it.

@js: have you seen anything like that?

@nathan Have you seen any negative consequences of sending the &_from= search param along with your enclosure urls? I know there was at least one hosting company that I can't remember which would return 403's if anything other than their strictly defined set of search params were present in the enclosure url. For some reason I'm thinking it's Podbean, but I can't remember.

Can one of the 36 people on the This American Life podcast staff please enable CORS on their RSS feed's image url?

@js @brianoflondon @agates Yes, that's right. I think audiomeans and spreaker go primarily through that host.

@js @brianoflondon @agates Podping europe ran out of disk space. Should be fixed now. I need a log rotation mechanism for the docker logs. I thought I had solved this once before but I must not have done it right.

@js Shocking.

@russell @fresh7at7 Hang in there!

@js Right, but the objects being socialized need to be represented in some way as objects first. If we’re adding ratings to AP for the purpose of rating a podcast, the podcast has to exist as an object to rate. Right now that would have to be rating some Note version of the episode’s data which seems unfaithful to the original data.

The existing types are probably fine for most of the subclasses we need. So, the transcript property can just reference an Attachment object or set of Attachments if multiple.

The Podcast object itself can subclass Object of course, and then perhaps things like Podroll can just be a collection of Podcast objects since each will contain a guid and feedUrl.

That would allow bringing in the properties needed for both podcast apps and Fediverse apps to treat them the same way.

An example would be the transcript uri. Where does that go? It doesn’t fit into a Document or any of its sub-types cleanly. There will be many such properties.

#activitypub It seems like we will need to define a Podcast ActivityStreams object type. I’ve been trying to see if we can just transmute a podcast into an Audio or Video object type. But the loss of fidelity is so high. I think a dedicated object type is going to be pretty necessary.

@js