mastodon 4.7.3open source developer @ podverse.fm / fediverse / foss / javascript / node.js / podcasts / react / react native / typescript
The Podverse NextGen website, admin portal, database, and infrastructure are basically completely finished, and mobile is still in progress. Here is a quick demo I recorded clicking some buttons in the NextGen mobile app. Many of the core prices are in place and it is coming together faster, and I intend for it to be finished this year / asap.
Very sad news from the best podcast in the universe today. Rest in peace JCD. Thank you for all the years of levity and insight to help us get by in this crazy world. Our weeks will never be quite the same.
Podverse NextGen Update 🛠️
Been working on audio + video playback enhancements. Here's a demo of what we call the "alt enclosure" system in podcasting 2.0 RSS feeds.
Listeners can set if they want audio or video to load by default. In this demo the user has video on by default.
The "wave" icon indicates that an episode or music track has both an audio and video version.
@sirtjthewrathful@podcastindex.social and the Doerfels have an alt enclosure feed that really showcases what it can do
New Embed players for Podverse NextGen 🛠️
Trying to make these as top-notch as we can. There are two designs: compact (audio only) and responsive (video and audio). They include chapter and alt enclosure support
Demo page live at: https://alpha.podcastdj.com/embed
PV2.0 status update:
The goal of this infrastructure is to support ALL podcasting 2.0 features, and full feature parity between web and mobile.
Work on the new database and parser system is mostly finished.
Progress on the data API is going well. Added basic channel and item (aka podcast and episode) endpoints, and a new auth system for login.
The improved separation of concerns of Podverse modules (10 REPOS 😳) has made coding PV2.0 much cleaner and easier.
I just saw a 6969 sats boost from @HeyCitizen@podcastindex.social in the podverse@getalby.com wallet.
Thanks man! I'll be using these sats for Alpha testing.
@dave@podcastindex.social one for the "what does LLM mean by that" list. Do I want LLM to "scrub" this directory?
"If you want .llm scrubbed in the metaboost monorepo too (not only metaboost.cc), say so and we can add that as an explicit todo; right now it’s scoped to metaboost.cc .llm/ plus “don’t contradict” guidance elsewhere."
@dave@podcastindex.social @suorcd@podcastindex.social I notice in our PV alpha that we are getting 500 errors when we request "get a list of feeds that have updates over the last X amount of time".
We make a series of paginated requests until we get the full list. It seems like the process works fine for most of those requests, but eventually we get a 500 error response from one of the pages. Is this a known issue?
I think I'm just going to add some retry handling for when this happens and see if that resolves it.
@mikek999@podcastindex.social what's the project here? Are you downloading all the RSS feeds referenced in Podcast Index? Converting to JSON?
@dave@podcastindex.social listening to last week's P2.0...the nextgen Podverse schema (and ogen) relies heavily on the Podcast Index IDs as basically the authority on feed uniqueness. It sounds like we may need/want to do a substantial rewrite to account for how Podcast Index API nextgen will handle ids?
I don't fully understand what we'll need to do differently yet. Just mentioning it for awareness.
@dave@podcastindex.social have you setup an "entity expansion limit" for RSS parsing before?
LLM advises me to set an entity expansion limit to avoid "XML bombs." I guess it means a feed is trying to waste your CPU resources.
It tells me 5,000 - 10,000 characters is sensible, but I saw what appears to be a valid (I think?) Arabic language feed from PI that exceeds our current 50,000 limit.
Any thoughts? I'm leaning towards keeping 50,000 as a limit and worrying about this if people complain about a feed missing.