Welcome to our new website!
Aug. 28, 2026

Episode 269: Verbal Pollution

Episode 269: Verbal Pollution
Episode 269: Verbal Pollution
Podcasting 2.0
Episode 269: Verbal Pollution

Episode 269: Verbal Pollution

Podcasting 2.0 August 28th 2026 Episode 269 - "Verbal Pollution"

Shownotes

-------------------------------------------------------------------------------------------------------------------------------------

00 - DATABASE SURGERY WEEK — AND THE THIRD EMERGENCY OF THE MONTH

<b>The lead, and it's Dave's:</b> Saturday 22 Aug — "#api I'm in the middle of a <b>big refactor with the Podcast Index database schema</b>. If I do my job right, nobody will notice it. But, the side effect will be an overall <b>huge increase in the consistency of the data</b> (duplicates, url change lag, etc)."

@dave — the big schema refactor (22 Aug)

<b>Wednesday night:</b> "<b>Podcast Index database surgery will begin in the morning.</b>" Thursday: "Step 1. Expect a brief api outage. It should last just a few minutes." — then "Done" — then "#api <b>Adding a very large table index...</b>" — and finally, Thursday evening: "<b>Finished. Butt is intact.</b>" (6 favourites. The board's favourite status update of the month.)

<b>What Adam should ask:</b> what actually changed under the hood, what does "consistency" buy an app developer in practice, and is there anything a host or an app should do differently now that duplicates and url-change lag are being cleaned up?

<b>🔥 The other half of the week — the third emergency.</b> Tuesday 25 Aug: "#api <b>Linode emergency maintenance on our db host. API is down.</b>" Then: "No update as of yet. <b>Just hard down.</b>" Then the line that is really the story: "<b>This is the third 'emergency maintenance' event that has affected us this month. Getting kind of old.</b>" And, dryly: "I guess a reboot every few years isn't too much to ask."

@dave — Linode emergency maintenance, API is down (25 Aug)

<b>Board question:</b> three unplanned outages in one month on the host that carries the Index. Is it time to talk publicly about where the database lives, and what the fallback is? The Index is infrastructure now — other people's products go down when it does.

<b>Podping shipped twice.</b> v0.13.0 across gossip writer, watcher and monitor — "<b>a dynamic memory cap to address the Iroh bug</b>" (that is last week's memory leak, now capped). Then v0.14.0 the same day — "<b>cpu architecture in the mesh announcement messages</b> to make determining what hardware a node is running on easier." Monitor updated too: ppmonitor.podcastindex.org.

@dave — podping v0.13.0, dynamic memory cap for the Iroh bug

Podping monitor

Podcast Index API docs

-------------------------------------------------------------------------------------------------------------------------------------

04 - 📌 PODCASTING'S GOLDEN OPPORTUNITY: HUMAN SPEECH

<b>Your PREP note, verbatim:</b> "<b>For PC2.0 - Podcasting's Golden opportunity! Human speech!</b>" — filed against a piece on how to spot AI writing.

Can you learn how to detect AI writing? Here are some clues

<b>The argument:</b> text is now cheap to fake, images are cheap to fake, and as of this year so is a voice. What is <b>not</b> cheap to fake is <b>a specific human, speaking unscripted, for three hours, with a transcript and a signature chain attached.</b> Podcasting is the only medium that ships that by default — and the namespace already carries the provenance parts.

<b>🔥 Evidence from this week, and it is stacked:</b>

<b>1. Apple Music is about to start labelling.</b> @js: "<b>more than a third of the music Apple receives monthly is '100% AI'</b> + usage — presumably what other humanoids would call 'listening' — of AI music on Apple Music is <b>below 0.5%</b>. = yes they are going to have to do something about it, starting with labelling." Read that ratio again: a third of the supply, half a percent of the demand.

Billboard — Apple Music to label AI-generated music

<b>2. Nobody can hear the difference in podcasting either.</b> @jaybrunet, 22 Aug: "I listened to a <b>voice clone podcast</b> last night ('Stark Reflections') and it was <b>surprisingly more concise and easier to follow</b> than his previous episodes that tend to meander off in too many directions. <b>If he hadn't said it was ElevenLabs, I wouldn't have cared or noticed the difference.</b>"

<b>3. The scale of the flood, measured.</b> Marco Arment said Overcast <b>transcribes about 30,000 hours of audio per day</b>. @js checked it against his own index: "taking a look at my 'all new episodes published' internal db for last month, <b>the world published at least 1.4m hours of new mp3 episodes for the month, or about 46k hours a day</b>... so if your 30k hours are unduplicated then you have excellent coverage — <b>the long tail is very long and, these days, full of generated audio.</b>"

@js — 1.4m hours of new mp3 in July, full of generated audio

<b>4. The shame is gone.</b> Stanley Druckenmiller, on his WSJ op-ed: "<b>I'm not embarrassed by it... I write everything using AI now for the same reason I use a calculator when I do math problems. I don't know why this is relevant. My name is on the piece. It's my message.</b>"

Notus — Druckenmiller's WSJ op-ed

<b>5. And somebody is already building the counter-stack.</b> Japanese publishers' <b>Originator Profile</b>: "OP uses <b>cryptographic digital signature technology to create tamper-proof credentials for websites</b>. Each ID card confirms <b>who published the content</b>, whether professional organizations vouch for that publisher, and information about the publisher's <b>editorial and ethical standards</b>." — that is a person tag with a signature on it.

Nieman Lab — Japanese publishers and Originator Profile

<b>⭐ The namespace question this asks:</b> we have <b>person</b> (who), <b>location</b> (where), <b>transcript</b> (what was said, word-level, timestamped). That is three quarters of a provenance stack that no AI feed can forge cheaply. <b>Do we need a fourth — a signed claim of human origin — or is the honest move the opposite: an AI-disclosure tag, because the liars won't use either one and the honest shows will?</b>

<b>The V4V angle:</b> if a third of the supply is synthetic and gets half a percent of the listening, then <b>attention is already voting for humans</b>. Value-for-value is the only monetisation model that pays for that directly — you cannot boost a bot you don't believe in.

-------------------------------------------------------------------------------------------------------------------------------------

02 - THE LOCATION TAG, WEEK TWO — IT IS INSIDE PRODUCTS NOW

<b>Last week we watched a dataset become a globe in 48 hours. This week the apps shipped it.</b>

<b>Podhome, this morning:</b> "New feature: <b>Add a location to your show and to your episodes</b>, and modern podcast apps can put your podcast on the map. You can also see your show on @alberto's fantastic radar.rss.io." — note <b>show AND episode level</b>, which is exactly the gap James flagged on the globe.

@podhome — location on shows and episodes (28 Aug)

Podhome location docs

<b>😊 The demand was already there — @rgblack316, 26 Aug:</b> "@podhome I was just about to send you a feature request to add the Location tag and <b>logged in this morning to find it already there.</b> 😁"

<b>TrueFans shipped search off it — @samsethi, this morning:</b> "<b>New location search for discovery based on @alberto radar now added to TrueFans.</b> truefans.fm/search/"

TrueFans location search

<b>😏 And @silas had it first and said nothing — 22 Aug:</b> "Listening to the episode and hearing them talk about radar. <b>I have had a map thing showing podcast locations for actually like two months.</b> Both on web and on mobile. Not yet on tv. Would be cool if I were happy with it and not still a perfectionist. <b>I'm in the car and I actually pulled over to write this.</b>"

<b>...and he already solved the flaw everyone else is about to hit:</b> "I ran into that shitty browser location thing and I solved it by, on the web version, <b>just not giving you a search near me button. Only on the phone app because that is guaranteed to have gps and an actual location</b> — not just wherever the heck a desktop computer seemingly randomly guesses where it might be located."

@silas — two months of a podcast location map

<b>The granularity problem, now with the definitive example — James Cridland on PNWR this week:</b> "You can put a building in there, a business in there, you can put <b>everything from the state of Queensland to Brisbane City Post Office</b>. If you do a podcast with a pastor — as you know, somebody who used to be on MTV with big hair does — <b>then don't just put the city where you are, put</b>..." (← that is you and Pastor Jimmy, on air, in Australia.)

<b>⭐ Sam Sethi's line, and it is the best summary of the project anyone gave this week:</b> "What we're beginning to see is <b>all the hard work from the people in the podcast 2.0 community is beginning to bear fruit now, because I see them as building blocks. The person tag, the location tag, the transcript.</b> All of these were fundamental building blocks that now you can start to build services around, which is what we've been waiting for. And of course, <b>the lag was waiting for the data to be filled in once the tags were available.</b>"

<b>Board question:</b> the globe is channel-level. Podhome now writes episode-level. Does Radar (and the dataset behind it) pick up item-level locations next — and does the Index want a <b>recommended granularity</b> in the spec, so we stop getting podcasts located in an area 2.6x the size of Texas?

radar.rss.io — the globe

Podcast Index — public datasets

-------------------------------------------------------------------------------------------------------------------------------------

03 - THE PERSON TAG GETS AN ENDPOINT

<b>Dave, 22 Aug:</b> "#api The new <b>episodes by person endpoint: /api/1.0/episodes/byperson?q=James+Cridland&max=5</b>. It reports directly what the [item] level [person] tags dictate."

@dave — the episodes/byperson endpoint (22 Aug)

<b>James wired it into Pod News, and said so on this week's PNWR:</b> "a very simple, possibly too simple, but a very simple person tag search, which is now <b>integrated into the Pod News website</b>. The first time I integrated it I didn't do it very well, but it's much better now, because <b>I've actually followed the spec</b>."

<b>😄 And he name-dropped you on purpose:</b> "if you're listening to <b>Adam Curry</b> — let's just say Adam Curry, <b>just so that his AI bot gets him to listen to this bit</b> — you can click the search next to Adam Curry and it will query the podcast index person endpoint and find all the other shows Adam Curry has been marked down as a person on." (Confirmed: the bot got you to this bit.)

<b>The drawback he found:</b> "<b>there is more than one person in the world called Dave Jones</b>" — no disambiguation. A person tag is a string, not an identity.

<b>Dave's own proposed fix, 25 Aug:</b> "I think adding a <b>toggle to the person search to switch it from extracted text to person tag only</b> would be good. Then, on the person-tag-only option, there would be a way to <b>filter for certain attributes like the href, image</b>, etc." — the href IS the disambiguator. Wikidata/website URL as identity.

@dave — toggle for person-tag-only plus attribute filters

<b>Sam Sethi, on PNWR, gently claiming priority:</b> "We've included this as a feature for two years, it's called <b>My Podcast Work</b>... If the <b>item level supersedes the channel</b>, and in podcast:person there is a <b>guest tag</b>, then if we pick up that you are a guest we'll label that as a guest rather than the host."

<b>🎯 Board bait, straight from James on PNWR:</b> "I would have expected <b>Dave Jones to have done an MCP directly with the Podcast Index by now</b>. And who knows, <b>maybe even to have stuck that behind some form of a paywall</b>. Given that Dave is working so much with AI tools in his day job these days, I would imagine he'll be pretty good at making it all work. <b>So I'm kind of surprised why they haven't done that yet.</b>" — Dave, answer that one on air.

<b>Related, same week:</b> @csb on <b>WebMCP</b> — "an emerging browser standard that lets a website explicitly declare its features as structured, callable tools for AI agents. Instead of forcing an AI agent to guess page layouts, read complex DOM trees, or parse scripts." — the question underneath both: <b>does an open index expose itself to agents, or does it get scraped anyway?</b>

-------------------------------------------------------------------------------------------------------------------------------------

01 - 🔥 V4V FAILED ON OUR OWN SHOW — THE ALBY / KEYSEND MESS

<b>The post of the week, and it is a gut-punch. @csb, Friday morning:</b> "@dave @adam bros, I tried, oh I tried, to send you <b>$15.10 via bitcoin lightning but 4 splits failing including the main one</b>, please fix it as it's embarrassing: <b>if podcasting 2.0 value for value system fails for the main podcast of the podcasting 2.0 movement then it will fail for non-celebrity podcasters too</b>, looky:"

@csb — 4 splits failing including the main one (28 Aug)

<b>Dave, same morning, and he does not dodge it:</b> "<b>Ugh. I opened a new public channel yesterday with LNServer and our AlbyHub says it's offline.</b> Idk why. I guess I'll have to open another one. [sigh]" Then: "I did test yesterday and it was working. <b>Looks like it went offline overnight.</b>" Then: "New channel is opening now and the other one just came back online." And, at 11:39: "<b>Ok, both public channels are online now.</b>"

@dave — our AlbyHub says it's offline (28 Aug)

@dave — both public channels are online now

<b>🔥 But this is not a one-morning outage — it is the third independent report of the same class of failure this week, and the other two are older:</b>

<b>1. @algrid, 25 Aug — the specific technical finding:</b> "I recently did some V4V testing and noticed that <b>podcastindex@getalby.com receives bolt11 payments successfully, but keysend payments to it fail</b>. You probably should check your channels configuration there or <b>remove the getalby.com/.well-known/keysend/podcastindex data to disable keysend completely</b> if Alby allows that."

@algrid — bolt11 works, keysend fails (25 Aug)

<b>2. @ChadF, 22 Aug — found it independently from the app side:</b> "I also don't think the <b>PI Alby address in the feed accepts keysend</b> and is causing failures every time I send a boost in boostmebitch.com. Which is strange since <b>every other Alby address is fine</b>. I do the well known lookup and do keysend if it's available for Alby addresses."

@ChadF — PI Alby address and keysend failures (22 Aug)

<b>3. @podcastguru, 21 Aug — the monitoring gap, stated plainly:</b> "<b>Looks like our Albyhub was down for a month and I had no idea.</b> 😫 Had to update the hub, re-open channels, I assume payments still worked. Just kind of annoyed <b>how the hub can go offline and we don't get any type of notification.</b>"

@podcastguru — our Albyhub was down for a month (21 Aug)

<b>⭐ The board question, and it is the show:</b> we run a <b>podping monitor</b> that tells the world when notifications stop. We run an <b>API status</b> nobody has to guess at. <b>We do not monitor our own money endpoint.</b> Should the Index publish a V4V health check — a small bot that sends itself one sat an hour to every address in the value block and screams when one fails? Every app developer in the community would use it.

<b>The channel side of the story:</b> @ericpp opened a channel to the Index this week — Dave: "03011dfdeeb31113db15620fbc0bc102f23e7d09f952b60615642ae2107e7db594 is the public key." Then the LNServer dance: "It says I can only have <b>either all public or all private channels</b> so I guess I'll have to close our existing one first." → "the new public LNServer channel is open now with <b>2,000,000 sat capacity</b>." → and this morning, after it went dark: "<b>Well, at least we know why it's cheap now. Lol</b>"

@dave — well, at least we know why it's cheap now (28 Aug)

<b>💡 And the standing idea this all feeds — @ChadF on your single-QR ask:</b> "Adam mentioned having a single QR for boosts but that requires something like <b>The Split Box</b> that StevenB made. Easy if you run a node as a backend, <b>but then you're taking a user's payments, splitting it and sending the split payments out, which is in the money transmitter area so I'm not touching it.</b>" His alternative: "when we update the [value] tag we add an entry for a <b>single lightning address</b> then apps like mine can offer a QR option and just make an invoice for that one address. That removes splits but it's no different than having a PayPal donation to a single account."

@ChadF — the single-lightning-address idea in the value tag

<b>Namespace question that falls straight out of it:</b> does the value block want an optional <b>fallback address</b> — one that an app can use for a QR, and that a sender can retry against when the split fails? Today, when a split fails, the money simply does not arrive and nobody is told.

Last Modified 08/28/2026 14:25:49 by Freedom Controller
Chapters

00:00 - Welcome to the Boardroom — Dead Hanging Safari

03:11 - radar.rss.io — Alberto Built the Globe

08:00 - Location Is In — Watching Ourselves Appear on the Map

13:08 - Shadow Banned by the Globe

17:03 - Find Podcasts Near Me, 1,200 Miles Out

21:05 - This Is a Beautiful Product

22:10 - Episode-Level Geolocation, and We Don't Want to Be Your Player

24:09 - Merged Within a Week — Dave's WebKit Submission

25:10 - Godcaster, Live365 and the Metadata That Would Not Load

31:06 - Headers Can Be Dangerous — CORS, Explained Properly

37:06 - Total Guesswork — What the Edge Node Was Actually Doing

41:02 - Safari, and the Ambiguity in the CORS Spec

41:32 - A Dead Hanging Safari — the Episode Gets Its Name

43:02 - Nobody Had Ever Reported It

46:00 - Claude Is So Chatty — Coding With Agents

48:03 - ASD-STE100, Simplified Technical English

52:10 - The Linode VM, Qwen 3 and the ActivityPub Bridge

01:00:04 - Put a Big Funding-Tag Button On Your App

01:02:06 - New in the API — episodes/byperson

01:10:07 - The Master and His Emissary — LLMs as a Standalone Left Hemisphere

01:18:04 - Boosts, a Row of Ducks, and the Albi Hub Export Fix

01:27:14 - The Audiobook, and Sign-Off

Transcript

0:00 Podcasting 2.0 for August 21st, 2026, episode 268, Dead Hanging Safari. We'll be right back. It's summer. That's right, everybody. And when it's summer, it's time to do a podcast. It's time to do a podcast. This is Podcasting 2.0, the board meeting of all of the boys and girls who make up the band of misfits that create better podcasting for you. This is where we meet. In fact, we are the only board meeting you can't find on a map. I'm Adam Curry here in the heart of the Texas Hill Country, and in Alabama, the man whose database is still backfilling longitude and latitude digits, say hello to my friend on the other end, the one, the only, the Podsage, Mr. Dave Jones! You've got... something happened with the audio there. Oh? What happened? I don't know.

0:56 Suddenly you got very... you got far away. I got far away? Now you sound normal again. Oh, I know. But when you went into the intro... Yeah, hold on. Hold on. I know what it is. Hold on. Okay. Okay, this may help. I had to... I had to set it to voice only yesterday for Rob. Do I had Sir Dusa for Rob do on no agenda? OK, and he had he was probably the Alex Jones studio and had some kind of crappy connection. So I had to drop him down to voice only on clean feed so that we wouldn't have a delay. Okay, it was wigging me out because you sounded normal and then you went to the intro and it was like... I was like, wait, where'd you go? You're like in the next room. I'm here, I'm here, I'm here, don't worry, I'm here. It was that, but faint. I'm like, wait, this can't be, this is not right. I'm sorry, I'm sorry.

1:50 Do you mute me while you're doing the intro? No, you can jump up and down and do all kinds of stuff. Have you considered doing it? I've considered lots of things, but I was getting – I was eating some chips. And some potato chips. And I was like, wait. Oh, no, you'd never hear that. Am I coming through? No, no, you'd never hear that. No. Why? Why would you never hear that? Because my processing is overriding you. Oh, so you would not get any of that? Probably not. No, probably not. People don't understand. When you do a podcast, you've got to process that thing, man. You've got to process it. Process it hard. You've got to process it. I need a flat line on the waveform. I don't even know what that means. Nothing. You're gating me out. If you look at the waveform of any podcast I produce, you won't see peaks and valleys.

2:49 You just see a flat top and a flat bottom. That's compression. That's compression. Exactly. I'm a little heartbroken. Uh, I'm here for you. I know you are. I'm just tell me, tell me, tell me where you were hurt. I was so excited to see radar.rss.io, which is, of course, um, The boys over there at RSS.com. They made a beautiful map out of the location data, out of the endpoint that you provided. I was so excited. I'm going on the map. I use RSS.com. I could not find my podcast anywhere. Which one? Okay, let's do this.

3:41 We get to do this. Radar. Is on RSS.com. I diligently fill out location every single show. Well, maybe you've not been picked up yet by the index. Oh, well, then that's an incomplete release. Yeah, of course it is. Look, I make no promises, okay? Oh, well, I was disappointed. If somebody... If somebody's at fault here, it's clearly me and not Alberto. It's a beautiful vibe-coded project. I presume it's vibe-coded. Oh, I doubt it is. I bet you it's not. Do you think he went in there with a text editor and did all that? I think that... Well, it says there's a link to the GitHub.

4:32 Let's see if we can see anything. Contributors, Alberto. If you look at my GitHub. All Claude. It all lists, Claude lists itself. Yeah. I don't think, I think, Alberto is a... I mean, I think he's got like a PhD or something in computer science. No, he does not need it. He has a PhD in AI, man. I think he actually studied for that stuff. Maybe he wrote the course. I don't know. Yeah, he knows what he's talking about. I just feel like there may be some... Some help from AI or something, maybe. Oh, hold on a second. But I feel like 90% of this is him. Hold on a second. So Eric PP, this is interesting. Eric PP says it needs podcast location tag at the channel level. Yeah. Oh, yes. That is true. That was not explained to me. Is yours not at the channel level? Well, let me take a look. I fear now. This is only channel level. Let me see. I'm afeard. I'm afeard. There is no interface on RSS.com to add it at the channel level. Well, this is an outrage. No, that's not true. What do you mean it's not true? It's not true. What do you mean? I'm looking at it. This is misinformation. Hold on. Oh, wait.

6:00 Oh, wait. Hold on a second. Hold on a second. See, I told you. Well, it's not where you'd expect it to be. You are going to show up on NewsGuard. Like gonna? Really? Gonna? Yeah, that's true. You're in the list already. Okay, location added success. I'll tell you why I didn't see it. Because if you go to your dashboard, the dashboard, the RSS.com dashboard, Yes. I go to the dashboard. Yeah. Then I select my podcast and says, edit my podcast. I edit the podcast and it says, edit podcast title, description, public website and podcast feed.

6:43 Then it has podcast details, category, language, author details, copyright notice. So, no, but then you go to settings, which I then guess, does that go for all of my podcasts? Which is wrong. Probably not. I wouldn't think so. I wouldn't think that would be all of them, would it? Well, so here on settings, let me see if it changes, if I change it to a different podcast. Let me see. I bet it does. Well, let's check it out. Check it out. Yeah, you're right. You're right. I'm wrong. I'm wrong as usual. You've been wrong twice, and we're only 10 minutes into this podcast. Not even 10 minutes in. Okay. So how soon before this updates?

7:30 Am I there yet? let's see I could probably run it let me see if I would have to did you pod ping I don't know You made a change. I bet the pod ping went out. Let me give it like 10 minutes, and then I'll rerun it. Let me check my feed here for a second. Let me see if it's in there already. Location, location, location. I don't think it's in. Oh, yeah, location. Yeah, location is in there. It's in. Yeah, I'm in. Location is in. All right, let me run. Yeah, run it, baby. Then I'm going to go. I want to see myself pop up. But that is an interesting point. If I'm doing a podcast from different locations around the world, That's not going to show up because the item level is ignored.

8:23 It's just like a second-class citizen. Yeah, well, why is that a problem, though? Well, isn't the whole beauty point, beauty part, the whole beautiness of having location? Because there's two ways you can use it. You can use it, and both of those interfaces are Surface on RSS.com's interface. You can use it where this podcast is created or what this podcast is about, a boot. So if I'm in Canada and I want to show people that this is a boot Canada, and the week after I'm in Rotterdam, You can't do that by individual level. This is just, this is a thought mistake. This is clearly a violation of all of the Cridler's standards. What do you want to say? What do you say to that? What I say to that is I just noticed something. What did you notice? That we've crossed the 8 million mark on podcast index ID numbers. Holy moly. That's a lot.

9:31 Congratulations. The newest one that just went. Yeah. Congratulations to nobody. The most recent. one that we just went in is 8,757,000. We didn't even have a banquet or a... No, we did not have a celebration at all. No celebration at all. No, nothing. One of those ones where when your car rolls over to a million miles or whatever that you get out and Push it the last tenth of a mile just to celebrate. We needed to do that. I'm trying to check to see which one. You know who's there? Paul's Wildwood Assembly podcast shows up. Nice. Nice. He's there. But I'm still not. Podcast location. Well, I'm about to run the thing. Run the thing. Right. Generate location list.php. Enter. This is very cool, though. I like this. But still, I think there's a, you know, are we not going to do episode level location tags? Yeah. I mean, I. i can't speak i'm not alberto i cannot speak but wait are you are you exposing those though is my question well i he he wanted you're putting this on alberto this you are pushing off responsibility onto a man who doesn't even he's not even from america It's a disability.

11:00 It is a disability. Yeah. What does he even know about podcasting? He's not Merkin. Seriously, he's not Merkin. No. Why is he even in this company? So, yes, I'm going to – I'll load all of the problems that I can't explain onto him because he's not here. It's super easy to do that. Don't say that because then I'd be like, hey, I want to be on the show next week to talk about why I'm to blame for everything. I want to blame for everything. Can't have that. The location stuff picked me right up, KDAV. Boom. Right on the top. Yeah. There's other things. There's one in Homewood. Yeah, but I don't care. I want to see me. I'm trying to find you. This is so unimportant. I'm trying to find you. How do you search?

11:51 Globe. No, I'm doing a near me. Near me. All, I've even set 30 miles. Where's the radar.rss.io? But there's a search where you can search by name, right? No, I don't see a search. Where do I see a search? I could have sworn I saw that. Okay, here, do this. Go back to the homepage, radar.rss.io, and do force refresh at the bottom. Okay. to make it pull the newest cash from where I just rebuilt it. Oh, okay. My number went up. 3,339 located podcasts. Number went up? Number go up? Number go up. Cash locally zero minutes ago. No. Okay. Now try to find yourself. I'm looking at it. There's nothing. You did the podcast near me and it's still not. What is your location set to? My location is right here in Fredericksburg. I clicked a little location thingy. I'll do it again. You say, I got a map. You are here. Okay. That looks accurate. I am here. Reset. Made here, about here. I'm on a bozo filter. That's what's going on here. I'm being shadow banned. I'm being shadow banned. You're shadow banning me. That's what that's Alberto's like, we can't have him on here. This is just not going to work. It violates his terms of service. I'm getting as far as

13:23 Austin, Texas and Dripping Springs. So I should be, which is which is actually incorrect because I'm set to 15 miles and I should not be getting Austin. Because it even says 21 miles. The whole thing is bogus. We get to do this, right? Dude, we get to do this. There's no search, though. There's no search bar. I'm looking. I don't know what you're talking about. I see no search. No, I was wrong about the search. I could have sworn there was one, but I guess I'm thinking of something different. I'm trying to find your podcast index ID. It's 747-3440. That's what I was about to say. Uh-huh. Now, let me look. I'm looking directly in the... In the database. You're looking in my personal table.

14:19 In the NF locations table. Search. Feed ID. Okay, yeah, you're in there now. Okay, so now let me regenerate it. Okay. You may get picked up after I did it. Okay, so generate. Now, currently, I have 3,339 located podcasts listed on the page, so I'm going to refresh. Force refresh. Oh, it went up by one. 3340. Okay. So I'll refresh. All right, you do it now. You do force refresh, and let's see if you get 3340. Force refresh. What do you mean? 43, 4340 located podcasts ready to search right there, like above the force refresh button, like in the little box. Where it says all made here, about here, right under that, I should tell you. Oh, 3,340. Okay, yeah, so now see if you show up. Nope. really no really i'll uh i'll refresh i'll refresh force refresh i got new brawn falls lake travis uh lots of austin i should be at the top no is your did you put your coordinate geo coordinates in there Did he ask for that? No, it just – it gives you a list. You type in your – you type in your, like, Fredericksburg, Texas. It gives you the – it auto-completes. So there you go, Fredericksburg, Texas, Gillespie County, 78624. I select – It was

15:50 probably not even in the feed. Well, let's find out. We got to get to the bottom of this. I agree because the whole point is that you get the RSS.com dude. Who made this is all jitty about how cool it is. And then his customers, actual customers. okay geo geo not yet it's all in there it's in there yeah yeah i see it it's in there i'm in this geo geo geo geo i am geo 30.2752011 comma minus nine or eight dot 8719843 and how far away are you from me Fredericksburg About four hours in my airplane I can't type that into Google What is OSM? I'm an OSM OpenStreetMap Oh, cool Yeah Finally, you're enjoying something. No, I am enjoying this debugging process. This is exactly how we have always done everything. Okay, you are 862 miles away from me. So I'm going to extend my search to 1,200 miles and say find podcasts near me, which is actually not a very accurate statement now that I've exerted it. None of this is near me. uh 138 miles what's the show we get to

17:21 do this all right i'm up to 347 i have my location my open street map everything is in everything is good but yet but i'm up to 613 miles no no let's keep going 658 707 i'm just gonna go to true fans i'm sure they support it yes you know you know that they do 862 miles okay we're in the ballpark now please hey true 860 miles Truefans.com is something different. That's interesting. Did it change? No, it's, I don't think it's, I think it's .fm. There we go. Oh, yeah, .fm. Truefans.com is, what is that?

18:09 Probably. Let me see what that is. Hmm. uh 2027 be the tailwind we get to what is this i say it's there i'm looking at it we get to do this it's right here in the list says it's 744 miles away from me okay fredericksburg gillespie county texas well how come i'm not seeing it online It was very, very strange. Matt, we'll see. Yep, links out to the map. Yep, there's Fredericksburg. Yeah, I see it. Now I see it, but it says, oh, okay, I see the problem. Apparently... This podcast made here. And I am literally, I'm literally five minutes from the church is 62 miles away from me. Well, it's a – Fredericksburg is a big area. It's a big town. I mean, you're just putting in Fredericksburg. You didn't give it the exact street address of the church. That would have been more accurate. But Fredericksburg is – no. You're almost – No.

19:22 No. No. 62 miles away, you're almost in Austin. So – I don't know why it has me. Well, where does it think? But it's using your browser location. Where does your browser think that it is? Well, how do I ask it that? Use the robot or something. Where are you? Let me go to maps. Let me see. Let me go to maps. Let's see what Google thinks I am. Google? Google? Ask Maps. What is this? Ask Maps? Oh, brother. More AI slob. Google crap. Yeah. Yeah. Uh... Well, it puts me... It puts me... I bet you it puts you somewhere goofy, like Austin. No, not at all. No, it puts me... Where are you getting this information? What do you mean? I'm just... From Google Maps?

20:14 Yeah, I'm just opening up Google Maps, and then it shows... What does it show me? I mean, it opened up Fredericksburg approximately where I am, so... I'm just wondering, like, yeah, it's if you deal. It's centered right here. This is it says I am a 30 dot three one one six two eight eight comma minus ninety eight eight eight three nine nine four eight. Ah, that's your problem. No, it's not. It should be a three three one four seven dot seven seven. Bingo. Bingo. Anyway, we just debug this in real time. That's clearly the problem.

20:54 No matter what you say, it's not 62 miles away. It's the lat-line triangulation hypothalamus inversion. That's your problem. Okay. Well, we're fixed now. Hmm. This is a beautiful product. It's a beautiful product. Yes, it is. Is the stream going down? Is it? Oh, it looks like it did go down for a minute. Yeah. It's back up. Yeah, it's back up. Okay. Yeah. Stuff happens. Anyway. Stuff happens. Radar.rss.io. Your results may vary due to road and weather conditions, but it's a beautiful product. It's a beautiful product.

21:39 Due to browser geolocation and static. Yeah. Okay. But it's great, though. I love it. I can't wait to see what else people make with this wonderful new endpoint. I guarantee you this was handcrafted line by line by Alberto in the way that somebody would coil a coffee mug on a – On a one of those clay spinner things. Anyway, I. Are you ingesting episode level geolocation? Oh, yeah. Okay. For sure. All right. We were doing that first before we did the channel level. Okay. Okay. And so all that stuff is in there. Okay. Actually, the part I had to build was the channel. Right. Location.

22:32 It's interesting, though, that it has to be channeled. That's not you. That's not you. That's not you. That's not you. No, I would assume that he's probably just going to, you know, add that later or something. Well, this is a new podcast. Or maybe this is a proof of concept. This is a new podcast app the way I see it. How come I can't play a podcast? Oh, good question. This is what I would be doing. Very good question. Well, I mean, you can click through the podcast index website, but we don't want to we don't want to be your player. No, no, we're not a good player. No, it's a player. We're not that either. We're not very good at that. This should be integrated into pod dot link. Daniel J. Lewis, stop it.

23:23 Just stop. What did he say? What did he say? He said, are you ingesting chapter level location information? Man, I've only got so many hours in the day, brother. Like, I'm lucky to have gotten out what I got out this week, which this is not – location is not the only location. thing that I provided to the world this week. No, what you provided to the world this week, an unbelievable, just an amazing... Now I'm not sure what you're about to say. You fixed a bug.

24:05 That not only did you fix it, but it was it was merged within like a week. Pretty quick. To a repo where there's a bunch of probably like – I don't want to say anything disparaging, but most of, you know, kind of like, you know, who are you, man? We know what we're doing over here. The WebKit people. And you want to explain this? Because this was merged with, and seriously, I think it was in a week or something. It's a little bit longer than that. It's a couple weeks. Explain the problem and how you fix it. Because this is a, you're right, it's a gift to the world. I provided the well it's July 30th so what three weeks yes I did provide a gift to the world in the form of a bug submission to the WebKit repository. So let me explain what was happening. So as part of the work we're doing with Godcaster, we were ingesting a lot of live 365 audio streams. And... The first issue that we had was getting the metadata out of the ICY interleave that happens in the – so these Live365 broadcasts a few different stream types. They do HLS as well, but – The

25:38 main one that most people ingest is the MP3 stream. And that stream is just... uh mp3 frames um you know in in an endless stream just so it's basically the it's essentially the same file format as the mp3 file itself and then you if you want to get metadata so like album art and uh, song title. Yeah. All the groovy stuff, the stuff, all the cool stuff looks good. Yeah. Yeah. If you want to get all that to display, then you have to, uh, you have to request it from the icy Y serve, sir, from the ice cast server. Um, And the way you do that is through a request is sending a header. along with the request of ICY-Metadata1. And so when you do that, the stream that you get back, the response, the byte stream response that you get back from the ICAST server will contain the metadata interleaved into the frames, the MP3 frames. All right, well... The problem with This the problem with the number one problem is cores. But wait a minute. It wasn't DNS because that's always the number one problem. But we ruled that one out. The number

27:09 two problem is cores. So cores, a C-O-R-S is cross origin resource sharing. And that means it's. It's a core part of the security principles that govern web browsers and how they operate. So for security, the main browser firewall against shenanigans is cross-origin. So you cannot execute code in one domain directly. That came from another domain unless it's permitted. Yes. By the server of that other domain. So you had the solution to allow this in certain trusted cases that was settled upon was CORS, C-O-R-S, cross-origin resource sharing. So a server can... Send A course or a course request. And if – excuse me – a client can send a CORS request, and if the server supports CORS, if it wants to allow its code to be touched by other domains, it can say, yes, this is fine. And it can – there's a whole protocol for how to respond to that with – in the response headers. Mm-hmm. So... The issue is... So cores by default

28:42 only responds with get requests. I believe by default, maybe post, but there's only a certain set of methods and headers that are sort of part that are part of like the base default. So a course request is allowed to think to do get and post and also by default and also. have certain base headers like range request, date, all the normal headers, content type, content disposition. If you add any headers in your course request that are not part of the standard set, you have to do a second call before you do that call to alert the browser of what this course request is going to be capable of sending. So if we want to send from our – this begins to get pretty complicated. No kidding. If we want to send – so think about this app, okay?

30:00 If this browser app wants to start playing a live 365 audio stream with metadata, it's The browser page code itself has to send a course request to... Because it's going to be sending this ICY metadata header, which is nonstandard. And you want to display it in the player, which is on the webpage. I'll just help you around here. Exactly. So if you're going to send that nonstandard ICY metadata header, you have to send what's called a CORS pre-flight request. Pre-flight? Why is it pre-flight? Because it's before your main request. Why is it before your main request? Because it's going to check with the server ahead of time to see... If that header, if those headers you're requesting are supported by cores. Ah, okay. I got you. So headers, and this is just as an aside, headers can be dangerous. Some people may not realize this.

31:13 But headers themselves can be dangerous in certain circumstances. Buffer overflows can happen that way. Dave, hold on a second. I've got a buzz. Are you eating chocolate again? No, no. No chocolate love today. Take the chocolate love away, man. Okay, you're good. Okay. So headers themselves can be dangerous. And that's why cores limits them and call. And so you have to go. You're like, OK, I'm going to call 365. I'm going to call live 365 with the IC metadata header. When you do that, the browser is going to send a course preflight request. Right. And that uses the HTTP options method. Wow. So the options method is sent to the destination host with the request headers that you're asking for. The server then will either deny it or respond with the appropriate header saying, yeah, this is fine. That is just standard behavior. Right. As part of the core's documentation, I think, What it says is that the body of the response of this options pre-flight response, the body can be – a text description

32:45 Of some sort, like like a header allowed or this is fine or just some piece of text. Here's what I think happened. You put in this you put in this PR, you put in this pull request and the guys who are maintaining would like to this guy sounds so knowledgeable. Just merge it. Just merge it already. That is not. I promise you that's not what happened. Merge it in. I'm sure this is exactly right. Whatever Dave Jones is saying, merge it. Yeah, that's – whatever happened, that's not it. Okay, so you fixed it. Well, let me finish. Let me finish. We're going super nerd here.

33:29 The members of the board are falling asleep. No, this – even Eric PP said this is way too complicated. Yeah. So – oh, he said, what happens if you just throw the headers at the server without the options check? Well, it's the browser that's enforcing this. Yeah, and that's Safari specifically, right? Well, you can't – all of them. Oh, okay. You can't stop – It from sending this. If you if you have nonstandard headers, it's going to check. It's going to send a pre-flight request no matter what you do. So you have to deal with this. And the so what was happening was every time you send the request, every time we sent this request.

34:15 It would work. First, we had to get Live 365 to fix – to add cores properly. And props to those people over there at Live 365. Props to them, man. That was beautiful. And I love that they just went, oh, yeah, okay, we'll work on this. And they didn't quite do it at the first time. Then the second time, like, oh, okay, we'll fix it. They did it. That was really – I was impressed by – that was the internet of the old days, like 90s. Hey, man. Oh, so much. Your stuff is broken. Okay, I'll fix it. That was beautiful. And they're not a small company. But the two attempts to fix it actually is – is part of this story. That's what caused us to find this bug. Exactly. So did you credit them on the PR? No. Absolutely. Oh, you did? No, I did. Yes, I did. I totally did. Yes, I said. Well, if you call credit saying that it was their fault. Give me some credit, man. Give me some credit. It was their fault. I just need some credit.

35:16 The – okay, so the first time – You've got me giggling now. Did Adam even read the PR? Of course he didn't read the PR. He read it. You know what I did? I said, robot, give me a summary of what just happened here. So – The issue – the first – so what I did was I contacted them and I said, look, I can't – it was weird because they – the way their system works is they have a sort of a front door node. I mean this is typical CDN behavior. They had like a front door – A node that you would hit, so something.live3c5.com or FM or whatever it is, you would hit that trying to get the audio stream, and that node, that server would respond properly with a course response saying, yeah, you're good. Hmm. The next thing it does is it 302 redirects you to an edge node on their CDN. So you get bounced to a different server.

36:22 And that's where it failed. That server would deny the course request. Right. Got it. And so this to us looks like. That's exactly what I read in the pull request. You did not. So this... So what we told them was like, hey, look, this looks like maybe a misconfiguration on your part because you clearly are allowing cores in the front door. But then when you bounce over to the actual stream box, it's killing it. And whoever I talked to said, oh, let me – Let me check with the engineer team And they were like yeah We've got it fixed now And so they – what they did – and now this part is total guesswork on me, and Paul thinks this is the case as well, but we don't have any way of knowing this.

37:17 I think what they did was they just cloned – And the – not clone. They aliased all the possible – Oh, to the main server. Routes. Yeah. Yeah, so what they did was they like – they made get, post, all the – basically all the different methods of HTTP respond the same way. Mm-hmm. So if you think about this for a second – If. If you have a box that responds over HTTP to a GET request for audio streams... When I send you a GET request, it's going to begin streaming MP3, endless MP3 bytes to me. If I also make that same get request... Respond that route on the server if I make that same route respond also to options request or head request or any other HTTP method. All of those methods are just going to begin to get the same thing. They're going to get a stream of MP3 bytes. So they just aliased options method to respond in the same way that a get request responds. Which could be a security issue.

38:50 I mean, maybe. I just threw that out there. I have no idea what I'm talking about. I mean, it's possible, but I don't. But here's the confusing part. So when he came back and he said, yeah, it's fixed. We got you covered. I ran the tests, the little demo to check all the things. Yeah, you even gave them a little demo app to check. You're so good, man. I saw it. So I ran that, and I was like, okay, yeah, it works. I checked it on Chrome. I'm like, this is great. And I checked it on Android. It looks great. And on iPhone, it just crapped out. Bombed. It just crapped. And I was like, wait, this something doesn't make sense. And I could not figure this out. And so I had to go – I had to get into the clawed session, and I'm like, look, I'm trying to play this thing on the iPhone. I cannot figure out why this thing is not working. And so it starts just hitting it with different things, you know, like it, It starts following the chain over and over and over.

40:03 And it finally came back and it said – It said it basically said this is strange because when I send an options method request to the CDN edge node. It responds with a 200, but then it also starts streaming audio. Ooh. Is that when it said, ugh, I confuse myself. Let me do this carefully. No, that was it. I love those. I love those little stupid things. This was not it, though. But he said, and I was like, wait, that's probably not good, I guess. Well, it turns out that Chrome and Firefox... They... Properly, and I say properly in very loose quotes because this is actually not very well specified in the CORS documentation. So this really doesn't come down to a matter of WebKit Safari not following the core spec because this actually is ambiguous in the spec. Hmm. It's more of an issue of it's just... Probably the best behavior because if you don't ignore the body, what was happening was Safari was properly sending the course preflight request, and the request was replying with an MP3 string. Not what we wanted. And what that was doing, that was dead-hanging Safari. It would

41:36 never move past the pre-flight. So the page itself would just freeze. It could not move past that. Whereas Chrome, what it does, and Firefox and other browsers, as soon as they see the 200 or the 202 come back. They're good. They move on. They're like, good. They completely ignore the body. They don't try to ingest it. Is a dead-hanging safari, is that a mission trip I can take to Africa? It's a ride at Disney World. You're sharp today, Dave Jones. I like it. I like this Dave Jones. Yeah. I got my chocolate. It's not Choco Love, though. No Choco Love. No Choco Love money back.

42:26 So, yeah, so that was the bug report. The bug report was basically you're getting hung up. By the sir that if you want to boil it down to what the problem is, the problem is Safari was letting the server dictate its behavior. Yeah. And you get that's no good. You can't do that. Right. And so they fixed it. And this will help other people, not just Live 365 and browsers? This will be helpful for other applications in the future or current? Yeah, absolutely. Yeah, that's great. I think what's – I could not find this bug reported anywhere. Clearly it wasn't because it got accepted and merged. So I couldn't find this bug reported anywhere anywhere.

43:11 And the – so I think probably what happens is people just – it was such a confusing thing to watch that it was hard to diagnose, and people probably just figured out a workaround or just made do with never fixing it. Yeah. But the product that we're building specifically for this, though, that was like a complete deal killer. It was going to be very hard to work around that. So we really had to fix this. And this concludes Dave's Bug Report of the Day. Dave. of the month. Of the month, baby. Thank you, Eric PP.

43:55 And then, of course, you introduced the bug into Podping and ate up everybody's RAM. That was great. RAM is so cheap right now. It shouldn't matter. Wow. Just throw more at it. Just throw more. We'll get there. I got it. I'm not even halfway done yet. What? You got more? Yeah, I did more this week. Oh, no, I thought you had more on the on the Coors Report. The Coors Report. There's another great podcast title. Welcome to the Coors Report. The most boring podcast ever. The Coors Report. The Coors Report. Okay. What else you got, man? What else did you do? Oh, well, I... A podcast person tag. Wait before you get there. Okay. Pausing.

44:50 Thank you. Thank you, John Spurlock. You know, Spurlock just I always when the first thing I do in the morning, I wake up. It's like, let me go see what what Spurlock put to what he posted about, except when he when he's going through like that. Here's all the Apple. What is the what is Apple's IDE? What is that called? Oh, Xcode. Yeah. Here's all the Xcode diffs. Like, no, no. That's horrible stuff. No, no, no. That is horrible. That is like that just that's a pollution of my browser. But he posted a link. To the, what is it, the ASD-STE100 Simplified Technical English. which you can tell your robot to use, and it has improved my quality of life just with a magnitude. And I'm so grateful for that. Please describe this. Well, if you've been using Claude Code as your robot, which I do, um... And Claude is just, it's so chatty and it's like, I found the smoking gun. This is the load-bearing issue we need to look at. But in my honest opinion, hey, just say the word. I'll go and fix that. Wait, I have the full picture now. You're right to push back. This shapes the entire conversation. I

46:21 was so sick of that nonsense. Gated? Everything's gated. Well, the gates I kind of like because I have a lot of – Load bearing. Well, the gates are important for me because gates is like, well, this thing doesn't pass the gate. And then I know what it is. Okay, so I understand what the gate is doing. The gate means you don't go to the next step. I'm okay with that. But just this on and on and on, I just... And every single time I'd say, please, just speak in simple English. Don't talk like an agent. And they're right. My bad. And then it writes, let me record this to memory so I don't do it again. Five minutes later. It's back to, but when you...

47:11 See, what is the... Claude, the right – wait a minute. What is it? There's – here. You post into Claude, only report to me an ASD-STE100 simplified technical English. And you tell it to make a memory of this. It does it. It does it. And now it's like it's still chatty, but it's not as annoying. It's a big difference. I feel it's a big, big difference. I'm happy with it. Thank you, John Spurlock. Let's see. I'll just post that at ASDSTE100. Dash, dash, dash, STE100. We have to say make a memory of it. You got to say make a memory of it. European Union trademark.

47:57 I don't know what you're looking at. I'm on the – they got a homepage. They do? Oh, yeah. Yeah, asd-ste100.org. Yeah. Simplified standards for technical documentation. Yes. Hey, request your free official copy. This is nice. This seems very European to me. Well, I don't know what it is, but it is stop my robot from spewing out verbal diarrhea. Very, very pleased with it. Very pleased. Yeah. I like how part of the definition of this thing, I can't – you sent me this, and I looked it up. It's a fact. Let's see what their fact is.

48:40 Fact. What is ASD, SDE 100 Simplified Technical English? It says something about the dictionary. Approved words that a writer can use. The approved words were selected because they were simple, easy to recognize. In general, each word has only one meaning and is approved with only one part of speech. Nice. Nice. For example, to fall has the approved meaning of to move down by the force of gravity and not to decrease. I don't know about – this seems like a stretch to me, but if it makes the robot less stupid, then fine. Oh, yeah. You can always undo it. Yeah, sure, yeah. Maybe, maybe there for every standard, there's always a competing standard. So I wonder what the competing standard to the ASD SDE 100 is.

49:32 Speaking of what happened to what happened to Dave Weiner? Something happened to Dave Weiner. What do you mean happened? Uh, he like blew up half his stuff. Yeah. I think that's what happened. Is that because of Claude? Yeah, probably. Claude wrote test file. Oh yeah. Yeah. Okay. Yeah. He blew away like important things. I have no idea how useful these things would be if it destroyed stuff and deployed projects with real users. Uh, It will do it. That's what it does. Yep. Which brings me to some things that I've been working on. Okay. But wait, there's more. Ew. The well, I'll we'll talk about the person tag in a second. So one thing I've been doing, I'm not I'm not going to actually say what the project is. Yeah. Alex Gates, he spotted a little bit of it. But I'm trying to challenge myself to not really use AI more because I use it every day in various ways. Oh, I know what this is. You deployed a Linode and had Claude do something. Yeah. No, no, no, not Claude. Not Claude.

50:47 Oh, pie. Pie? Pie. Pie. Yes. So. Which according to ASD is a tasty dessert treat. There's only one meaning. There's only one meaning. Apple pie. Yes. So one thing I've not done much of because it just terrifies me. Because you don't live like me on the edge. I'm not a YOLO kind of fellow. Oh, I'm not YOLO. Uh-uh. I'm not YOLO. What would you use? What's a better term then for the way that you handle your robot? Dangerous would be the term. Dangerous. That's worse than YOLO. Dangerous. That's intentionally sketchy. Completely dangerous, yes. Right. reckless.

51:37 Reckless, yes. Reckless is good. Hashtag reckless. I'm like, Gordon, go ahead. Deploy to customers. I'm good. It works. The interaction between you two is really funny because you're like, wait, wait, you put this live on a customer? He's like, yeah. And you're like, you weren't supposed to do that, and then like five minutes. later you're like, oh, I'm fixing it. Don't worry about it. It's all good. We're doing it live. You're like, hey, that actually worked out. Let's keep going. Yeah, exactly. Exactly. Okay. So what I did was I... I created a Linode VM in an account that had nothing else in it. Okay. Oh, wow. So this thing is in a silo. It's walled off. It's siloed. Yes. It's gated. It's behind a gate.

52:29 It's gated. It's gated. So I did that, and then I've had this idea for a project forever. I mean, for like I don't know, three years now. Oh, wow. It's always been in the back of my mind, and I've always kind of thought, hmm, I wonder if that would work. And I actually started writing it before AI was even a thing. or LLMs or even a thing. And so maybe, I don't know, 2022 or something. And I had some stuff written, and I was like, you know, this would be a really good project to test out like a fully autonomous agent setup. Because that's something I just really never do. The way I use AI is I have this – I have – a problem that I can't solve, and I go and I get some help with it. and that's because I just don't trust it. Are you familiar with the Claude setting that is basically go ahead, do anything you want, live dangerously?

53:44 That will never happen. I'll never do that. It's awesome. No, no. Well, that's what pie does out of the box. Oh, okay, good. Yeah, that's basically it in a nutshell. It has no guardrails. And so I thought, OK, well, let me just point this thing at this repo that I've been having cities that has sitting here for years. And so this is Pi connected to – what I use Pi for mostly is podcast index-related things, so helping me build the model – The local model for on the DGX Spark for classification, spam classification. It runs the classifier. So it's basically anything podcast index related is usually I don't typically do clawed stuff with that. And sometimes the only project I've really done on that is – help with that is Podping because I just didn't understand Eero enough. So I've had – I did that.

54:58 But everything really like core podcast index related usually goes through the local DGX with Pi. And I thought, okay. I want to try out this new Quinn 3.827B model. It's supposed to be the new hotness. And I also want to get a feeling for just like autonomous agent stuff. So I threw the 27B model onto the DGX, and I just aimed pi at this repo of this project that I've been brainstorming for years and said – Here's a VM in Linode. Here's an SSH key. Go try to build this thing. And I was just like, I'm just going to step back and go have lunch and come back later and just see what it did.

55:54 This thing worked for like three hours. Wow. Non-stop. Chugging non-stop. Didn't ask you to... Is this okay? Can I move ahead? None of them. Never asked me a single question. That's cool. Yeah, I love it. Just chug, chug, chug, chug it SSH into the server. It started launching stuff. It started doing like it started creating accounts. I mean, like it's horrifying. It's all it's all horrifying. Creating accounts on the server. Yes Yes To run things under As non-root And all this kind of stuff You know And I have it That's great Sort of I have it sort of like Loosely attached To the podcast index That social Mastodon And so I saw it posting stuff DMs And I'm like – I'm just like trying not to lose my lunch. And so – but it's been a fun experience. And I'll talk about what it actually is later if it ever gets to some sort of like state that is usable. It's all just a fun project, and I want to see what these things – do and how they handle stuff just it's just learning it's a learning tool it's fun to watch i agree it's super fun to watch and and i can tell you this it's like it gets so when it comes to the podcast index such as the mastodon thing the activity pub parts of it Um, It stopped a couple

57:28 of times and was like – it was having trouble getting that right, like server – excuse me, Mastodon HTTP signing, and it was like – it looks like you're – It looks like the Mastodon server is just – it's not set up right. You need to contact the administrator. And I'm like, this is BS. That's why I said – I was like, look. I'm surprised it didn't send me an email. Man, yeah. It has no email access. I'm not that crazy. But I said, look. Go here's a here's a repository. And I pointed it at the podcast index activity pub bridge. I said, go look at this repo. and learn all the right ways to do this. And it did. And it said, oh, you know what? You're right. I was doing it wrong. I'm like, yeah, I know you were doing it wrong. My bad. My bad. Yeah, my bad. My bad. And that's all handwritten code over there, baby. Yeah. So, yeah, but it's been a fun. Yeah, it's been fun. It's chugging along on something right now. I got no idea. The fun part about Pi is, is that you can see all of the thinking that's happening. So all the reasoning mode? Yeah. Which all gets hidden from you in Claude.

58:48 No, you can do Control-O and it shows up. But that shows you tool calling, but it doesn't show you the reasoning. Control-B. Control B shows you the chain of reasoning? I think so. Maybe not. I don't know. Okay, I'll check. I thought they hid that by default, like maybe a few months ago. Possible. Possible. But you see the thinking, and I like that because you can – when you see it going off the rails, you can stop it. Yes, exactly. And in Claude, you just type stop, all uppercase, and it goes, okay, waiting for input. It stops right away. Yeah. Yeah, so anyway, it's just fun. It's a fun project, and I'll throw it out there at some point, if it works. But it got me thinking, though. I mean, like, if... It is good to have like this one like throwaway environment. Oh, yeah.

59:47 That's not important where you can really just let something loose and see, you know, it's not going to hurt anything, you know. And here is Adam's begging of the day. Begging once again, could you please put a big button for funding tag on your podcast apps? A big one, like right there in the episode. Put it right there, right underneath the picture. What prompted that? Because what prompts it is our own app. Every single time I play something in the Godcaster app, there's a big button, a big blue button that says whatever's in the feed, like, support the show. It's right there. It's right there. And it's just calling out to me, and I love it.

1:00:34 Yeah, true. I love it. I know. Did anybody move any further with the splits in Stripe or anything like that? I have not kept up with it. I haven't seen anything about it. I mean, Daniel was doing stuff. Nah, he's doing location tags in chapters, super chapters. No, I thought he was doing the funding thing. I don't know. People are doing stuff. That's what I thought. Yeah. I think it would be great. Just saying. I added a new person endpoint, though, in the API. Okay. What can we do with it? Um, Well, let me get the name of the endpoint first. That would be helpful, wouldn't it? Yeah, because I can't wait to ping it.

1:01:27 don't just ping it request it Daniel J. Lewis says I'm figuring out the stripe splits it's unfortunately not as easy as I expected alright I got you brother I'm going to tell my robot to look at it come on robot fix it Uh-oh, Linode's chat.podcastindex.org emergency maintenance. Uh-oh. she's going down she's going down hard did you just get an email about that Yeah. I'm trying to find the end point. Oh, here it is. Okay, so the new API endpoint in the index is episodes slash by person. Oh, that's cool. And so you can give it a Q equals and then the name of the person.

1:02:20 So let me – With spaces? Yeah. Yeah. Okay. You are URL encoded. Do rob space do D E W. See if he shows up on no agenda from yesterday. Rob D.E.W. Let me open Postman. The postman always rings twice. Old movie. That's Jack Nicklaus, right? Yep. Okay, so here we go. So, ROB space DEW. Mm-hmm. He already has 15 karma points in the boardroom. That's amazing. I love that. Yeah, episode 1896, just do it. Nice. Nice.

1:03:05 And it gives you – so here's the – let me post this. Copy. I'll put this in the boardroom. That's going to be the... That was fast, too. Was that an actual database query? Nice. It is. Yeah, it goes straight. So it gives you the... It gives you the episode... And the Jack Nicholson, I'm sorry, not Nicholas, Jack Nicholson. It gives you the episode metadata and it attaches the person object to it. So the person tag object to it as well. So you get it all back in one sort of big blob. Copy that. Yes, PP monitor is down, baby. Wait, what? ppmonitor.podcastindex.org. It's down.

1:04:02 It's down. Down hard? Down, yes. Oh, that's the emergency maintenance. It's running on chat.podcastindex.org. That's why. Wow, okay. Yeah, they're emergency migration to a new host. Wow. Wow. That's Linode. Yeah, we're down hard. Down hard, people. All right. Oh, this is cool. I see it here. Oh, I don't have my authentication header value set. Oh, you got to fire a postman, man. You're buzzing. I don't know what I'm doing. I'm not doing anything. You're buzzing. You're buzzing. Whenever you do that, it seems to help. What, shake the ice? Yeah. There we go. All right. I'll just shake it every now and then. Why is Postman not responding? Postman. Postman. I don't know where it went.

1:04:58 Yeah, so that's – so the person tag – is we... There's two... We've always had search by person. And that's just like a raw text search that we're sort of munging on the back end to get it to recognize people's names. But that's just searching the text, the descriptions and the titles. This is just a text-based search. This is actually – zeroing in on the title of the person's name in the podcast person tag in the feed. So now you kind of have two ways to search for people in the index now. Nice. Mm-hmm. Yeah, I was asked for it by somebody, and I was like, you know, that's a great idea. Let's go ahead and do that as fast as possible because that data is in there. Yeah. But it's, again, just because of time constraints, I never finished making an endpoint that would make it usable. So it was like this, you know, just half finished thing. I'm like, okay, well, this is an easy win, you know. You're amazing. That's not true.

1:06:18 You're an amazing man, Derek Jones. Yes, you are. It is an honor and a privilege to work with you. It is. Oh, well, I agree with that. I love working with you guys. Simmer down, Scooby. No, I'm talking about you, not me. I agree. I am a privilege to work with. Sorry, misunderstood. No, it's – I love – I love working on stuff like this because it's – when people ask for things, that's something I do when I – it just got weird. It did get weird. No, Alan, you're amazing. Oh, brother. Yeah. I love working on stuff like this because people ask for things and you realize – whole things you missed you know when they say hey how about this could you give me this i'm like oh you know what why did i never think about that yeah that's cool there's a power of it's just the power of like social you know community stuff community it's about community We have such a good little community. We do have a good community.

1:07:35 This community has been going for six years, man. And we never had a fight. Not a single one. Not a single fight. It's fantastic. No one blew up. No one shut down the repo. No one deleted the repo. I've seen it all. I've seen it all. Paul Therod on Windows Weekly this week. He used a phrase that made me chuckle. I was laughing out loud in the car. He called some – I forgot what product he was. Maybe it was like some old Microsoft product. He said it was briefly excellent. I just thought that was a funny thing. Briefly excellent. Well, that's most software these days is briefly excellent, it seems. Yeah. It perfectly describes the world we live in. Yeah, no kidding. Everything is briefly excellent. Yeah, it really, truly is. I was talking to a buddy of mine who works at Databricks. You familiar with Databricks? I've heard of that. Yeah, Databricks. Yeah, what is that? Data center company, right? Well, he's a sales guy, so he gave me the spiel, and my eyes glazed over, rolled up inside my forehead. I'm like, stop it. As much as the Coors conversation we had?

1:08:50 No, because I understand the Coors problem. They're like a middleware somehow. They protect your data as you onboard into their silo. Anyway, and he was telling me something that – that you and Paul were discussing, not Paul Theriot, but Paul Bailey, that all this... Um, Enterprise level software, this just shipping full of bugs and crap. Yes. And the company where you work at depends on this type of enterprise software. Well, we all do. I mean, you know, well, yeah, to some degree. I mean, if you know, it's a huge problem. And I think it's directly related to speed of code coming out of these agents.

1:09:50 I just think people are not thinking carefully. Thank you. So, The problem is, You know, I've told you I've been reading this book, The Master and His Emissary. No, I don't think you told me that. No, it's been a few weeks. I told you. It's by a guy named Ian McGilchrist. And it's about the hemisphere, the brain hemispheres, the right and left hemispheres. Oh, yes, of course. Of course we talked about this, yes. Mm-hmm. You know, it's going to be very difficult to... Give broad strokes on a book like this because it's just such a sweeping type thing. It's so deep, man. It's deep. It's dense.

1:10:46 Dense. It's super dense. Dense. But I think what we have built – When it comes to LLMs, um, The... What we've essentially built is a left hemisphere. That stands on its own without the guardianship of the right hemisphere of the right hemisphere. Um, The, you know, there's a very, I think maybe we talked about before, like the brain structure, the left and right hemisphere, they're joined by the corpus callosum, that big bundle of neuronal cords that separate. Connect them together. Yeah. And there is a theory that... One of the purposes of that corpus callosum bundle of nerves is not to facilitate communication, but Always, but in certain terms to prohibit. It's a gate. It's a gate. Yeah, it's gating. It's gating. And you can't tell this from brain scans. You can't see, okay, you just see activity. You can't tell what the activity is. So you can't tell if it's like stopping something from happening

1:12:17 or allowing something to happen or what? And so this idea that So there's an idea that there may be sort of an adversarial relationship between the hemispheres. Sure, I believe that. That sounds right, sure. By necessity. And that without that adversarial relationship. You delete your repo. You, yeah, you hard, you hard down your server. Mm hmm. And so because the left hemisphere is really – it sees the world in terms of – the picture it has of the world is built up from parts. It sees – it's what we – It's focused on tool use and seeing – building its view of the world up from pieces. But the world's not really built that way.

1:13:25 Well, hold on a second. If true, and I'll take it at face value, wouldn't we be enhancing and sharpening our right hemispheric skills when watching the world? The AI do stuff. For sure. Which is not a bad thing. Right. So that's – I think that's one of the reasons that I enjoy why we were talking about a while ago, watching the reasoning chain that's happening as this thing is doing its deal. Because I'm sort of – Being the overseer and trying to spot things because I'm engaging the right hemisphere, which sees the world as a whole, not built up from parts. It sees – It sees the world as a fully functioning system in itself.

1:14:25 And... That's why one of the premises of the book is that The right hemisphere needs to be in control. There's this old idea of – we call them left and right hemispheres nowadays, but they used to be called the major and the minor hemisphere. Hmm. And if you think about it in that context, the right hemisphere needs to be the major hemisphere. The left hemisphere really is a tool because it has no awareness – of the world as a whole. It just sees pieces. And I think what has happened is we've, with LLMs, we've built essentially a standalone left hemisphere And when you let it run the show, you really do end up with very bad outcomes. Dead. You can wind up dead. Yes. Interesting.

1:15:22 Yeah, because you have no – there's no – There's no adversary there that's pushing back and saying, hey, hey, hey, whoa, whoa, no, no, you don't understand. What's the name of this book again? It's called The Master and His Emissary. I'm having trouble sleeping, so I want to make sure I ask. You will not sleep with this book, I promise. It's actually a page turner. Oh, it's a page turner. Now, this is a condensed version. This is of a larger work that he did that will put you to sleep. But this is the sort of accessible version of this material. And yeah, I think that when you – one of the hallmarks of the left hemisphere is that it lies. It lies all the time.

1:16:09 And if you enjoy this type of deep analysis from Dave Jones, along with his extremely detailed bug report, please support Podcast Index. that was a good I'm segwaying I'm segwaying us out golly it's like 10 till 2 holy cow where did the time go uh Coors Yeah, I'm sorry. No, actually, no. I apologize to everyone in the boardroom. No, no. It was the location tag, I think, is what ate up 50% of the show. Probably. Yeah, that's true. That's your fault. That was you. It's completely my fault. Not Alberto. It was my fault. That's right.

1:16:55 If you would like to support the index, the entire project is funded by the people who support it. And this is just a catch up between Dave, myself and the boardroom. Now, we do not we're not funded at all by any of this. Only the index is for the machines that run it. And we feel it's a very valuable project. It's been going for six years. We hope to keep it running forever. So support us by going to. podcastindex.org. Now at the bottom, you will see a big red donate button and you can support us with PayPal. Can people still support us with boosts? Are we still receiving boosts? Yes. Oh, we're 100%. And have you put my, I guess I'd have to see myself on the splits here. It's kind of complicated. What? What are you looking for? I'm looking to see. Wow. Okay.

1:17:46 I'm seeing. Here we go. I'm looking. I see a boost here. Uh, no, that's because my, uh, my heli, my heli pad is still channelless. So I can't see any boost that came in now, except I do see Martin Lindeskog, who gave us a row of ducks, because it came through as a true fan's comment. Which is kind of nice. Have you not opened channels to anywhere else? No. Well, you should try doing that. Yes, thank you. But the whole start nine shuts down and then everything breaks. And there's no way – it doesn't – It's the tour. It's the tour part of start nine that fails every couple of weeks. And it's not something I've been able to figure out. But then it just fails and then it silently fails, which is not good.

1:18:43 No. Silent failure is the worst type of failure. Yes. Yes. So can you – are you able to pull out the boost that we've had so far? Because we'll just do the boost for this week for next week. It's just – there's no real-time interaction. I'm sorry, people. I will open the channel. You know what? I've been on fire this week. I not only have – Um, done all those other things but i also fixed the export the albi hub x oh oh good so i can actually read boost now oh excellent good good in in a sane way but uh let's see i'll read the paypal's first though oh sorry that thing yeah a new media show $22.20. Oh, is that right? That's a new media show. Wait, or is that Martin Lindeskog? Eric PP, yes. Oh, Eric PP says I should have a channel. Eric PP, you rock, man. Let me check. He says I should have a channel. Let me check. Yes.

1:19:46 Buckfeet. No, this is from Martin Lindeskog. He says, here's a row of ducks. Yeah. The support support this show button is working on true fans. All the best. Twenty two dollars and twenty two cents. Beautiful. Thank you, Martin. Of course. Of course. fan supports everything. Let me check and see helipad. Let me see if it'll open up. Yeah? Yeah? I love the stay logged in for 30 days. It never works. Never. Nope. You get about a day and a half. If that. Let me see. Hold on a second, Dave. Let me check. Let me see what I got here. Okay. Thank you, Eric PP. Eric PP. Yes. There we go. There we go. One minute ago. You got a channel. 3,333 sats from Eric PP. Thank you very much.

1:20:33 We have 59 sats here. That's Martin Lindeskog. Okay, 2222222222. Yes, beautiful. We got... 100 sats from boostmebitch.com. Thank you. Yeah. I saw that one too. Yes. I got 100. What is it? 400. Oh, and 1,000 from boostmebitch.com. What is this? Is this Chad F? I think this is Chad F. It's great. Beautiful. Okay. And then anonymous podcast guru user with 10 sets. Thank you very much. Thank you. Okay. Hey, thanks, Eric PP. Eric PP is a good man. He's a good man. Michael Goggin, $5. Thank you, Michael. Jorge Hernandez, $5. The boys and girls at Buzzsprout, $1,000. Ho, ho. Baller, shot caller, 20-inch blades on the Impala. Keeping the vibe alive. Thank you. Silicon Florist, $10. Paul Allen, he says note emailed. $20. Did you get an e-mail note? Let me check. You know, that's a very good question. Let me check. Maybe I got...

1:21:54 I got... I don't see Adam and Dave. Dear Adam and Dave, says Paul Allen. But I guess this is recent. If you're frustrated with Bitcoin and lightning, here are some quotes from a guy who worked in the industry that confirms it's not just us old farts who are struggling. Quotes from Mechanic on a recent episode of Guy Swan's Roundtable show. Quote, 99% of my time in support is BitEx people trying to use lightning. Once a week... Once a week, I get an email and support for Ocean where someone says, you just paid me, but I don't have any coins in my wallet. What happened? And then I do some digging and find out this wallet has no way to deal with Coinbase payouts because it's never happened before to anyone that's ever used this wallet.

1:22:39 And I usually email support for whoever that company is. It happened with Coinbase. The company Coinbase that named itself after the Coinbase transaction. Didn't know how to process Coinbase transactions. Thank you, Paul. That was great. Yes, confirmation. Yes, got it. Josh Hoover, $20. He says, keep up the good work. Thank you. We will. We plan on it. We try to. Michael Hall, $5.50. Todd Cochran, rest in peace, $30. Thank you, Todd. Boosting from heaven. Gene Liverman, $5. Thank you, Gene. And we got some boosts. Here we go. I also have some boostmebitch.com. Boost. 279 sats with a test message, test received. We got a 58 sats. That's good. Let's see. Here's another one. Chad F.

1:23:40 at Fountain.fm. He says, 185 sats. He says, no Nostra login needed for BoostMeBitch.com. I've got to take a look at BoostMeBitch.com now. Yeah, I guess I've got to do that, too. Let's see. BoostMeBitch.com. oh okay all right you guys are nuts this is cool okay oh this is nice i like it so i could put this oh it's but underneath it says live on nostr he said no nostr uh necessary right okay so maybe it's optional podcast index podcast Ding 2.0. And we're way down on the list. Okay. We get to do this. So I can do boost. Enter amount. Okay. 1,000 sats. Optional message.

1:24:34 Boost. Okay. Why can I not boost we get to do this, though? I don't think we have it set up. Oh, okay. Oh, and now it's asking for my Albie. Okay. Pod news. Let's go pod news. Okay. Let's see. Okay. Okay. Bunnies Weekly Review. Boost Me Bitch Connect. Oh, yeah. Boost Me Bitch. Confirm. Error. Undefined. Request failed with status code 500. Okay. That makes sense. Yep. Okay. That's too bad. I would – I'd love BoostMeBitch.com. Can you just pop up a QR code? That would be – Oh, that would even be better. Now this window won't go away. That's hilarious. They close the window, it keeps popping up. It really wants you to boost that.

1:25:23 It really wants me to figure this out. That's amazing. With a name like Boost Me Bitch, I don't think it's going to take no for an answer. All right. I love the idea. I would love a QR code, just a QR code. Uh, let's see. Oh, the delimiter. Comic strip blogger. There he is. 1-1, 1-1-1 sats. Howdy, Dave and Adam. Please tell your audience to subscribe to Podcast Made in Texas, www.just2goodoldboys.com. A podcast by Gene and Ben. They talk not only guns but also content creators, things, etc. Fun fact. Ben gave me interview about how to run big LLMs on home NAS on the cheap.

1:26:13 See my YouTube channel, YoCSVAIArchWizard. ArchWizard. ArchWizard. ArchWizard. That's it? That's our group. All right. Good group. Thank you very much, group. Thank you, Boardroom, for sticking with us. Believe it or not, I enjoy it when you have a bug report followed by a bug. A brain report. It's good. A brain report. No, it's good. I am going to get this book because the more I think about it, the more I see the issues in society. Do you – are you somebody who likes to read on paper or do you do audiobooks? I do audiobooks, but I enjoy paper books. I've never been able to really get into Kindle or anything like that. If anybody likes the audiobooks, likes audiobooks. The narrator for this book on Audible is very, very good. It's very easy to listen to and a nice pace. It's just a very good listen. Yeah. Nice for walking the dog. My favorite audio book. is the kid stays in the picture. Oh, I don't know this one. Let me look at it. Robert Evans. Robert Evans. Why does that name sound like that?

1:27:38 Robert Evans produced The Godfather, Love Story. He produced so many Hollywood movies you would know. Okay. And he narrated it himself. And it's brash. It's funny. He was married to Ali McGraw. I mean, it's a boomer book for sure. but hey everyone likes Godfather there's something about his reading style that just it drew me, it's like six hours it just drew me in and I barely even stopped listening to it when I listened to it the first time, it was so good It makes a difference. A good read makes a difference. I just got it on Audible, so I will queue it up. Did you get it with one of your free 12 credits, which always seem to expire? My son has always had really bad dyslexia, and so he's a good reader now. But through school, we always supplemented what he had, his reading with Audible. So we always had like the max subscription of Audible. And so we – we were like – And it's still going. I haven't even discontinued it yet because we have like a thousand Audible books in there, man. Every single thing you can think of. So many credits. You got created, man. You got created. You got created. You got created. All right, everybody. Thank you for

1:29:09 being here at the board meeting. Brother Dave, thank you so much. Have a great weekend. You too, sir. See you next week, everybody, right here at Podcasting 2.0. Thank you. You have been listening to Podcasting 2.0. Visit podcastindex.org for more information. Go podcasting! The whole thing is bogus.