Episode 270: YOLO Guy

Podcasting 2.0 September 11th 2026 Episode 270 - "YOLO Guy Dave waves the whitflag on agentic coding and podcasting beneifts! 01 - 😂 THE PODCAST RIG ATE ITSELF — AND IS NOW RUNNING OMARCHY Sunday 6 Sep: "My Umbrel docker containers did not survive the OS upgrade from Ubuntu 20 to 24 on my podcast rig. This is why I never upgrade anything. I still have some Ubuntu 12 and 18 servers running." — a sentence that should be on a T-shirt at Podcast Movement. Tuesday, the diagnosis, and he takes it on the chin: "It was a v1 to v2 docker compose transition issue. It was very much my fault for not RTFM before doing do-release-upgrade." Plus: "doing 2 upgrades back to back to get from LTS 20 to 24." To @ericpp, same day, the two-line eulogy: "It's incredibly borked." → "I'm closing the channel you have open to me because I'm going to have to wipe this box." — note that the lightning channel was collateral damage. That matters for §02. Thursday 10 Sep, the rebuild: "Omarchy on the podcast rig now. Let's see how this goes." and then, shortly after, "Podping gossip watcher up and running on it." The genuine question underneath: the podcast rig runs podping's gossip watcher. What is actually load-bearing on that box, and should anything that the wider ecosystem depends on be sitting on a machine you're willing to wipe on a Tuesday? ------------------------------------------------------------------------------------------------------------------------------------- 09 - 🤖 THE ANTHROPIC ADVENT CALENDAR @js to you directly, 11 Sep: "@adam it's like an advent calendar until the IPO — behind today's door is..." and then the Anthropic threat-intelligence report. Anthropic — Detecting and countering misuse (11 Sep PDF) The line JS pulled out: "These actors carried out a sustained effort to develop guided weapons, using Claude to design guidance software. They did test-fire a guided rocket. This field test appears to have failed: within hours, the ac[tors]..." And the prediction, two days earlier: "can you _imagine_ what stunts anthropic has planned for around the IPO timeline in a few months? gonna be great." The board-meeting angle: every one of these reports is simultaneously a safety disclosure and a capability advertisement. Publishing "our model was used to design a guided rocket" is a warning and a brochure at the same time — and the IPO is in a few months. ------------------------------------------------------------------------------------------------------------------------------------- 00 - 🔥 STEP ONE OF THE SCARY STUFF — THE NEW 'PODCASTS' IDENTITY TABLE The lead, and it's Dave's. Wednesday 3 Sep: "#api The new `podcasts` table is now being written to by default on all new incoming feeds and the conflict queue is being populated for merge decisions. This is step 1 of the scary stuff. Let's hope nothing catches fire." @dave — the podcasts table goes live (3 Sep) Thursday 4 Sep, step one lands: "#api All feed ingestion paths now use the new 'podcasts' identity table. Spent the morning cleaning up a lot of old error log debris I've been neglecting for years so I can have clean logs for the next step." 😄 And the same morning he broke it and immediately confessed: "#api I would like to pretend (by silence) that I didn't break feed ingestion this morning for about 20 minutes by forgetting to update the env files on the aggregator servers. But, I'm sure @js will produce s[creenshots]..." — Dave knows exactly who is watching. Tuesday 9 Sep, the number of the week: "#api Refactored the weekly database dump script since it was getting slower and slower and was very old. Re-running the new one now to test. I'm anticipating 4 hour run instead of 28 hours." — twenty-eight hours to four. That is the dump the whole developer community pulls from. Podcast Index — public datasets ⭐ The board questions, and they are the show: 1. What IS the identity table — in plain language, for an app developer? If a feed changes URL, changes host, or gets duplicated, what does the new table let the Index say that it couldn't say before? 2. The conflict queue is "being populated for merge decisions" — who makes those decisions, and is it automatic or does a human rule on it? Because merging two podcasts that are actually one podcast is exactly the kind of call that goes wrong loudly. 3. You said step one. What is step two, and is that the part where something does catch fire? 4. Twenty-eight hours to four on the dump — what changed, and does that mean the public dataset can now ship more often than weekly? ------------------------------------------------------------------------------------------------------------------------------------- Last Modified 09/11/2026 14:34:15 by Freedom Controller