Mitch Downey @mitch@podcastindex.social

@hypercatcher here's the chapter where @adam explains his "dream about commenting" https://podverse.fm/clip/-b2-2OvCo

In last week's Podcasting 2.0 with @hypercatcher @adam brought up the idea of leaving a publicly visible timestamped comment on an episode along with a crypto payment. It sounds to me like "superchats on the blockchain" and I think you might be onto something.

Re: "that one magical piece in the middle", I imagine many blockchains can work as the database/processor, so maybe our goal in PI should be to define the open standards that would enable media file superchats to work with any blockchain?

Thank you to the ~10 people from the Podcast Index community who helped us with Beta testing the iOS and Android builds 🙏 you were enormously helpful with identifying bugs and areas of improvement.

If anyone else would be interested in joining our Beta testing program, please let me know here or email contact@podverse.fm and we can get you setup to receive the pre-released versions of the app.

Podverse 3.0 is not yet live on F-Droid, but a PR for the build is ready for the F-Droid developers to review and publish, so if all goes well I'd guess it will go live on F-Droid within a couple weeks.

Link to the PR: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/8404

This update also includes support for password protected RSS feeds. Here's a video demo of the feature using a premium RSS feed for The Higherside Chats.

https://screencast-o-matic.com/watch/crnYesS97e

Podverse 3.0 is now live on iOS and Android 🎉

This update includes a major UI redesign, and full support for the <podcast:chapters> feature.

Check out the link below for a demo of the chapters feature. Any questions or feedback would be appreciated!

https://screencast-o-matic.com/watch/crnYeOS9Ju

@dave we noticed a podcast not updating properly in the index. "React Native Radio", while it is in the index, uses the old RSS feed URL. That feed URL however should redirect to the new one, so I'm surprised PI has old data.

I went ahead and added the new RSS feed to the index, but realized afterwards I probably created a 2nd React Native Radio for you, when really I'd think we need to update the existing listing. Is there a different process for updating feed URLs vs adding a new one?

@adam @dave Podcasting 2.0 mentioned on Timcast https://podverse.fm/clip/MS55JEk-0

“Every single industry is a software industry...and the ultimate software is Bitcoin.” - Max Keiser podverse.fm/clip/PnT0riTUs

Attn Podverse 3.0 beta testers: we should have an update with a round of bug fixes out tonight, including a bunch for chapters. If you run into bugs feel free to hold off on reporting them until after this update. Thank you!

Podverse 3.0 is now in Beta for iOS and Android ⚠️

This update features an all-new design, a ton of under the hood improvements, and full support for chapters!

If anyone is interested in trying the Beta before it goes live, please let me know here or email contact@podverse.fm.

All we will need is your email address and your device type (iOS or Android), then we can send you a link to install the app.

Any feedback or bug reports would be greatly appreciated!

Podchaser raises $4 million to build a comprehensive podcast database 😯 https://techcrunch-com.cdn.ampproject.org/c/s/techcrunch.com/2021/01/19/podchaser-raises-4m-to-build-a-comprehensive-podcast-database/amp/

@mitch @dave I guess a slightly different process would be:

- Get all podcast feed IDs from the latest PI dump

- Get all podcast feed IDs from Podverse’s db

- Remove all IDs that are in both

- Take the IDs that remain, and remove them from Podverse’s db.

That seems simple enough, but scary. If the PI dump were incomplete for some reason I would run into BIG trouble 😳

How about a PI endpoint that returns the IDs of all feeds that have been deleted/deactivated since beginning of time?

@dave as you know Podverse’s db is currently syncing with PI’s, but we don’t currently have a way to automatically delete feeds when they are deleted from PI. Are there any endpoints we can use for that purpose?

I suppose what we can do now is using the PI db dump, take all of the PI feed IDs, then get all of the podcasts in our db with IDs that are *not* in the dump, then remove them. That seems like a massive select query though and I’m not sure how to handle that...am I on the right track?