Podcasting 2.0 August 21st 2026 Episode 268 - "Dead Hanging Safari" It's always DNS or CORS - and how your right brain is gating bad robots Show Notes ------------------------------------------------------------------------------------------------------------------------------------- 00 - THE LOCATION TAG — SPEC TO DATASET TO GLOBE IN 48 HOURS <b>The lead, and it's yours:</b> Wednesday afternoon Dave posted — "There is a new <b>locations</b> data set on the public datasets page... The db tables are still back-filling since I updated the db and aggregators to support the <b>new &lt;podcast:location&gt; tag format</b>. After a couple of days it should be mostly complete." He cc'd <b>@james, @alberto, @js</b> and then @DavidMarzalC. That cc list is the whole story — within 48 hours all four had done something with it. @dave — the locations dataset post (20 Aug) <b>The shipping trail:</b> web-ui <b>PR #608</b>, "add locations export to public data sets," branch <code>public_datasets</code> → merged to master the same afternoon. This is the first public dataset built on the new location tag format rather than the old one. <b>Then somebody built the map.</b> By Friday morning <b>Alberto</b> had <b>radar.rss.io/#globe</b> up — a spinning globe of podcasts made in or about places on earth, drawn from the free dataset, most entries carrying full OpenStreetMap references. James put it in front of the OpenStreetMap community directly: "One for excellent people using @openstreetmap." <b>James's review, and the two asks:</b> "This is so cool. Really shows the power of the location tag. The globe — would be nice to add <b>filters</b> to that (made in vs about). Or maybe just colour the dots differently? The next trick would be some <b>OSM lookups on the IDs</b> to work out what the places are." <b>🔥 The flaw he found, and it's a good one:</b> "One drawback is that some people have chosen <b>'Queensland' as a location, which is 2.6x larger than Texas.</b>" — the granularity problem in one line. A location tag is only as useful as the smallest box someone is willing to put themselves in. <b>Dave, on seeing it — and he is in Birmingham, Alabama:</b> "Wow, this is incredible. I already see a podcast from Birmingham that I didn't know was based here." ❤️ ❤️ <b>Dave, Friday:</b> "It's beautiful. I can see this data powering so many cool app and platform features." @dave — Wow, this is incredible / Birmingham (20 Aug) @dave — It's beautiful (21 Aug) <b>The bug found by using it:</b> @alberto and @james noticed the <code>rel</code> property missing from the export. Dave: "That column is in there but I had to add it. I bet I left it out when I copied over the episode level response build code." Then: "I found the issue. I had made the change but <b>not deployed the new export script to production</b>. The 'rel' property should be in there now." Also confirmed: <b>channel-level only</b> in that dataset, not episode-level. @dave — that column is in there but I had to add it @dave — channel level only / rel now deployed