And this also means the PI catalog contains a lot of corrupt or invalid data, and thus is unreliable for industry analysis by people like myself, @jamescridland, and others.

And if people truly don't want to be in Apple Podcasts but _do_ want to be in PI, then we can, of course, let them opt-in and submit.

But I think the feed-discovery approach is faulty and leading to catalog-pollution or data-corruption.

Show thread

So we end up with a huge catalog of feeds, with tens of thousands or hundreds of thousands of duplicates or feeds that were never intended for public consumption. Just because a "podcast" feed exists doesn't mean we should index it and make it available in podcast apps.

@adam was upset when he thought Spotify or Amazon Music indexed No Agenda (but would have required someone, probably a listener, to submit). And PI is doing that same thing.

Show thread

I have concerns about our scraping the web for podcast feeds.

1. This is asking for duplicates. WordPress's multiple feeds, hosting-provider feeds, and third-party services (like Spreaker) that make feeds. It'll be a mess of invalid data.
2. This is requiring those who truly don't want their feeds discovered to opt out of something they don't know about and never consented to. Credit score, anyone?
3. I'm not sure we can assume people _wanted_ the feeds publicized if they didn't submit them.

I have some really cool ideas to extend the chapter spec! I just need to write up the proposal.

Here's good feedback:

"I’ll be honest I still don’t really fully understand haha. The website really didn’t answer much. All I know is it’s a free podcast index? Not sure on much else. Just seems very advertisement-ish with the name. Like it came straight outta a marketing class lol. And again I don’t really understand what exactly it’s doing besides being a podcast index. And I really did try going through the whole website. The information presented isn’t very clear at all"

I'm trying a new work/sleep schedule that might help me stay in my "zone of genius" without compromising any time with my son.

So far, it's working better for me.

@adam I have two suggestions you could try to eliminate the dimmer hum:


I found this to work very well in several circumstances when I have everything plugged into a single surge-protector through this adapter.

Also, you could look at a Furman power conditioner, which can also help reduce the hum but especially keep your connected equipment at a consistent voltage.

I agree that chat, comments, and reviews should be 3 separate things. I suggest chat and live should go together because of their direct relationship.

Reviews would probably be easier to implement than comments.

For comments, it would be great if they could crosspost/integrate with existing WordPress comments and commenting systems (even, if possible, third-party systems like Disqus, and such).

@adam @dave

@dave Talking to Transistor, too?

I'm trying to think of all the podcast-hosting providers we can get on board so we can go back to Simplecast and say, "Hey, all your competitors are doing this, why aren't you?"

I think we should let Podchaser take the lead on cross-platform ratings and reviews, and we can encourage developers to support that instead of trying to build our own system for it (which would require centralization).

I should probably take this discussion to GitHub, so it would be easier to track, link to, and discuss.

Show thread

The certification process would be simple: applicants checkmark a list of features that they support and provide evidence, someone reviews and verifies that those features are truly supported and then awards the certification.

Show thread

What would you think of a "Podcasting 2.0 Certified" program and badge? It could be a simple requirement, like supporting at least 75% (or so) of the finalized features, but provides a certifications that apps and publishing tools can proudly display.

Think of how being IAB 2 certified is badge of honor and validity among podcast-hosting providers. "Are you Podcasting 2.0 certified?" could be the new litmus test.

I'm talking to Brenden, creator of Podpage, and he's looking for a couple good example feeds using all the finalized tags so he can work to support them on Podpage. Any suggestions?

Here's an example of why I think it's a mistake to scrape the web for podcast feeds that haven't been submitted anywhere:

Not only was this a test feed, but the feed is now dead and _never_ contained all these episodes. Something is wrong.

A good example of why it's best to get the .com: Podland told their audience to visit 🤦‍♂️

Show older
PodcastIndex Social

Intended for all stake holders of podcasting who are interested in improving the eco system