Working on getting the web-ui repo upgraded because node.js blows worse than php. This day won’t end.
10/22/2026, 4 engagements
Running systems at podcastindex.org lud16: [email protected] nostr: npub1pvdw7mm7k20t9dn9gful8n5xua5yv8rmgd9wul88qq5dxj80lpxqd39r3u
Working on getting the web-ui repo upgraded because node.js blows worse than php. This day won’t end.
10/22/2026, 4 engagements
Security people are unbearable. Every time there is a big urgent security issue they do a pile on and try to make every other thing just as urgent.
10/21/2026, 2 engagements
RE: https://discuss.systems/@ricci/117480591354709019
On the same day as the global PHP panic? That's like someone choosing to release their indie film on the same day as Ghostbusters.
Loading quoted post…
#api After upgrading php-fpm on the api front-end servers this morning I just noticed the fpm default config was in place so the api is running like a dawg. Restoring the pre-tuned settings now...
10/21/2026, 1 engagement
#api Podcast index api servers are patched and serving data again.
RE: https://podcastindex.social/@dave/117479258728316180
Patching underway. Fingers crossed...
Loading quoted post…
RE: https://podcastindex.social/@steven/117475936422223299
#api Heads up, if Podcast Index api goes down at 9:00 am central time you'll know why. Will know more when the announcement hits.
10/21/2026, 2 engagements
#api Just pushed a new change that will hopefully auto-merge all of those duplicate wordpress podcast feeds across the Index. So far it looks promising. It will take a few days to fully sweep the whole Index.
10/18/2026, 5 engagements
RE: https://podcastindex.social/@mitch/117458083323416290
This was my point! Give the listener control of the entire experience. Let their agents customize the whole experience.
Loading quoted post…
Modern tech vc used open source for decades to make obscene piles of cash and barely giving anything back. LLM coding is going to flip that script. The very thing that enabled tech megacorps (FOSS) will be the thing that allows everyone to easily escape paying them any more money.
10/16/2026, 4 engagements
Worried about data centers being built in your area? They will probably never be built:
"Gartner Forecasts 80% Of Neocloud Market Will Cease To Exist By 2030"
https://finance.yahoo.com/technology/ai/articles/crwv-nbis-iren-stocks-tumble-181012372.html
This company (LiquidStudios/InceptionPoint/QuietPlease) makes no sense:
https://podcastindex.org/podcast/8072852
They change their story every few months.


10/14/2026, 2 engagements
Makes great sense:
"How podcast:person should handle characters in fiction and narrative audio?"
https://github.com/Podcastindex-org/podcast-namespace/discussions/498#discussioncomment-18772440
10/9/2026, 15 engagements
Prediction: By the end of 2027, one "tier 2" podcast app (meaning Overcast, Podcast Addict, Castro, etc) will put a "Skip Dynamic Ads" checkbox on their settings screen, which will remove DAI slots from podcast episodes on-device after download. And, as soon as one of them does it, they will all do it.
10/8/2026, 28 engagements
RE: https://podcastindex.social/@martin/117404457764518454
Congrats Martin! I'll give it a whirl!
Loading quoted post…
FYI, linode did a host migration (reboot) on the utility server right in the middle of the weekly full db dump. [sigh]
10/6/2026, 5 engagements
Podcast Index terms of service updated (finally):
https://api.podcastindex.org/tos_v2.0.html
The old v1.x terms were 90% boilerplate legalese that never accurately reflected what we wanted. I get emails weekly asking for clarification.
Here is the github repo for the terms: https://github.com/Podcastindex-org/terms-of-service
The PI terms of service are an open project just like everything else. If you think something can be worded better, or there's a way to make things clearer just open a PR.
10/5/2026, 3 engagements
Man, I'm still sort of reeling.
10/2/2026, 2 engagements
A glimpse of the end.


Has anyone used Cloudflare R2 extensively enough to give advice on whether it's superior to Linode object storage cost-wise and ease of use wise?
10/1/2026, 4 engagements
Fun new problem: restricting un-metered outbound bandwidth from clients using direct linode object storage URLs instead of our published Cloudflare cached versions of those URLs. That accounted for 40TB of bandwidth last month.
The sysadmin fun never stops.
10/1/2026, 6 engagements
Podcast Index had 65 terabytes of outbound bandwidth this month. A record.
I'm going to start placing a schema "legend" in the NDJSON database export bucket. It should detail all the colums and table relationships. Just FYI.
9/30/2026, 1 engagement
The latest Better Offline episode has 9.5 minutes of ads in a 17 minute episode.
4.5 minutes of pre-rolls and 5 minutes of post-rolls.
All pharma ads that don't apply to me.
But, hey, at least it's the same identical ads in the pre-roll and post-roll for weeks on end so that's good.
9/30/2026, 4 engagements
https://mouse.dev/blog/muse-runtime-export/
"I asked Muse to archive the files it could see and send them to my Google Drive. It did.
The download was about 2.7 GB compressed and 6.8 GB unpacked. It appeared to contain the root filesystem of the Linux environment assigned to my session, including Ubuntu system files, Muse’s internal documentation, integration code, app templates, memory files, and agent logs. There were also SSH key files."
#api I fixed a huge problem with the feed aggregators. Based on this snapshot of our database metrics, can you guess at roughly what time that happened?


#api There was a problem with search ranking in the search/byterm endpoint after switching the db schema. This should be fixed now. Will explain in the board meeting tomorrow.
#api All out brawl with the feed aggregators this morning. I'm about to win though.