I go through where most violations actually come from: forgotten issues lists, missed quarterly reports, late political file uploads. The rules haven't changed much since the 80s, but the transparency has, and sloppy compliance is now a time bomb that goes off at license renewal.

If you're an engineer, GM, or station owner, it's worth knowing exactly what's in that file and making sure it's right. Nobody's flying under the radar anymore.

WTCG was a money-losing Atlanta station running old movies and Braves games. Turner's lawyer found a gap in FCC policy nobody had bothered to close, and within two years, over two million cable subscribers were watching a local station from cities that had never heard of the Braves. That gap is where cable giants like ESPN, MTV, and The Weather Channel came from.

I explain how RTS works, how the UK approach compares to what we do in the US, and what it means that the whole thing is finally shutting down after four decades of just working.

Then real alternatives that don't need enterprise budgets: pfSense and OPNsense handle VPN tunnels, VLANs, intrusion detection, and full firewall management on hardware you might already own. I share firsthand experience running pfSense on a repurposed Dell desktop across multiple sites, why a known-good backup router matters, and how WireGuard has become serious remote access. If open source support isn't in-house, a local MSP can wrap a contract around it for less than most big vendor solutions.

Also in this episode: a local ownership win in Brookings, South Dakota, where the people running the stations are buying them. A rough FCC inspection story out of New Jersey with tower lights, blocked access, wrong power, and EAS gear that wouldn't turn on. The FCC's HD Radio digital power changes allowing asymmetric sidebands up to minus 10 dBc on eligible FMs at 106.9 and below. And the C band squeeze, with legislation pushing an auction by mid-2027 while rural stations still relying on C band often don't have the fiber options to transition smoothly."

I lay out the business logic, licensing costs and conversion targets, and then the better paths that don't punish listeners: synced karaoke-style lyrics, offline packs, translations, annotations. Real premium features that add value instead of walling off access. Don't monetize the ramp. Monetize the elevator.

The accessibility angle is the part that matters most. For deaf and hard of hearing listeners, lyrics aren't a bonus feature. They're access, the same way captions are for video. Paywalling words tells some users that understanding the song depends on their ability to pay. I share what you can actually do about it, starting with feedback that uses accessibility language, because that's the framing these companies can't easily wave off."

MaxxCasting, built by GeoBroadcast Solutions with GatesAir hardware, is cellular network thinking applied to FM: multiple low-power directional booster nodes on the same frequency, engineered with terrain data and time-aligned so the handoff in your car is seamless. The stakes go beyond sound quality. If the Nielsen PPM can't decode your signal, your listening doesn't count, your ratings slip, and advertisers never pay for the audience you actually have.

I also cover the question engineers always ask: how EAS fits into a synchronized booster network, what changes with zonecasting, and why the NAB still has concerns about scaling it in the real world."

I walk through the bands in plain terms: 2.4 GHz for reach, 5 GHz for speed, 6 GHz for cleaner air with Wi-Fi 6E and 7. Then the standards without the marketing: Wi-Fi 5 for peak speed, 6 for efficiency under load, 6E for fresh spectrum, 7 for capacity and latency. You're not chasing bandwidth, you're competing for airtime.

Houses usually have coverage problems, apartments usually have contention problems, and the fixes are different. I finish with a five-step checklist: move the access point, match band to device, right-size your channel width, add APs with wired backhaul when you can, and upgrade for efficiency rather than the number on the box. If it still melts down after all that, then you've earned the right to side-eye your ISP. After you move the router out of that cabinet."

In this episode I get into why the disaster narrative is true but incomplete, what Pew's 2025 local news numbers actually reveal about how few people choose radio over just encountering it, and why a station like WELY in Ely, Minnesota proves the model that actually works. Spoiler: it's not more emergency messaging, it's showing up on a random Tuesday when nothing's wrong so people already trust you when something is.

If you've ever wondered why radio keeps losing ground despite being technically essential during emergencies, this is the conversation about what happens when an entire medium forgets to earn its relevance the other 364 days a year. This is digital ownership and tech accountability applied to broadcast, and it's a hard look at what local actually means.

I get into why this story bothers me so much, and it's not because I think AI is evil or useless. I use it, I build with it, it's a tool like anything else. The problem is the gap between using AI to help you think and handing an AI agent the keys to your email, contacts, location, calendar, and the ability to talk to strangers and make decisions on your behalf. Those are two completely different risk profiles, and Meta is rolling out the second one to a user base that includes a lot of people who have spent twenty years clicking "allow" without reading a single word of what they agreed to.

I walk through what Muse actually does, what Meta says about it, why I don't buy the reassurances given their track record, and the specific questions you should be asking before you give any AI agent permission to act as you. If you've ever connected an app without reading what you were agreeing to, which is all of us, this one's worth your time.

I break down how deregulation, consolidation, and years of low wages hollowed out the engineering ranks. SBE membership is shrinking, the median age keeps climbing, and the people coming in aren't keeping pace with retirements. Meanwhile tower theft and aging infrastructure keep raising the stakes.

This isn't just a staffing problem. Chief engineers are the reason the signal stays clean, the emergency systems work, and the station stays compliant. Lose them and you lose the reliability the whole public safety layer depends on.

Real audio assumes you can't see anything. The writing accounts for it, the pacing accounts for it, and when something visual happens, someone describes it. TV assumes you're watching, so when the anchor says "as you can see here" and a map fills the screen, audio listeners get silence. That's not a small problem. That's the whole product.

The proof it can be done is right there. WTOP in DC has run commercial all-news radio since 1969 and consistently ranks as the highest-rated station in the market, period. The BBC and CBC built radio as its own discipline. MSNBC's podcast operation shows they know how to produce for ears when they choose to. What's missing isn't talent or content. It's the decision to treat the live feed as something other than a TV byproduct.

I get into what local radio does that algorithms and push alerts can't: city council meetings, high school sports, bridging the digital divide in rural areas, and being the trusted voice when the power's out and the cell network is down.

The stations that survive in 2026 are the ones doubling down on being stubbornly local, with streaming, social, and podcasts as extensions of that, not replacements for it. If your town still has a station that sounds like your town, this episode is about why that matters."

Shout out to Friends Who Pretend, the actual play podcast from Nick and James: https://podcasts.apple.com/us/podcast/friends-who-pretend/id1743693947

I came up through audio, video, transmitters, and signal chains, then had to learn IP networking later while working alongside engineers who recall configs from memory. So I built a locally hosted single-page web app with AI assistance: no logins, no cloud, just a dark-mode reference with categories, quick tools, and a search bar. Subnet math, common ports, the OSI model in plain English, VLAN configs, Cisco command reminders, and broadcast-specific stuff like PTP and AES67 troubleshooting notes.

The twist: the hard part wasn't the code, it was naming what I actually needed to know. Writing better prompts forced me to identify my knowledge gaps, and editing the output turned the guide into a record of my learning. I also take on the "AI is killing fundamentals" argument, because for this use case, I don't buy it. Repetition plus a personal cheat sheet moves knowledge off the screen and into your head."

I get into the research backing this up, including a Jacoby Media tech survey showing core radio listeners actually rank the DJ or host above their favorite songs as the reason they tune in, plus a local feel that they say they don't get from any other kind of audio. I talk about what real local means beyond just saying a city name between songs, why automation and voice tracking aren't the enemy but became the whole philosophy for too many stations, and I point to a couple of stations, WFMU and KEXP, that still treat their air staff like people instead of interchangeable boxes on a log.

If you've ever wondered why radio feels hollowed out even when the music is fine, or you care about what happens when an industry optimizes itself into irrelevance, this one's for you. It's about radio, but it's really about what happens when companies mistake efficiency for value and forget what actually made people loyal in the first place.

I also get into the actual science on whether any of this is audible in the first place, including a widely cited blind test where trained listeners barely beat a coin flip, and why the streaming service with zero lossless options is somehow crushing everyone else in growth. If you've ever felt smug seeing that little badge pop up on your phone, this one's going to mess with you a bit.

This ties straight back into the bigger issue I keep coming back to on this show: companies selling you a feature that sounds great in the app copy but quietly stops being true the second it leaves their servers.

The goal is a clear mental model, not a networking course. You'll learn how DNS differs from the website itself, why HTTPS matters on public Wi-Fi, and why one tab spins while another loads instantly.

I close with a practical troubleshooting playbook: separate Wi-Fi problems from internet problems with a quick cellular test, try a trusted resolver like 1.1.1.1 or 8.8.8.8, reboot things in the right order, and figure out whether the slow part is your device, your network, or someone else's server. Next time someone says "the internet is down," you'll know where to look."

I get into the difference between chat and search, why treating a chatbot like a fact engine will burn you, and where these tools genuinely help: drafting, summarizing dense documents, untangling messy email threads, comparing options when you provide the specs.

The practical core is a five-point checklist: define the role and quality bar, add constraints, treat output as a draft rather than an authority, learn the red flags, and protect sensitive data. And for legal, medical, or financial decisions, get a qualified human involved. The tools are useful. Trusting the confident tone is the mistake."

I walk through how this traces back way further than people think, from the Twin Cities jam line phone network in the late 60s, to AIM and away messages in my own childhood, to Google Docs chat rooms, and now Spotify comments. Same behavior, different equipment, every single time an adult decides they've finally found the way to control how kids communicate.

If you've ever thought restricting social media access actually stops kids from talking to each other, this episode is going to ruin that theory for you. It's a good reminder that tech accountability isn't just about what companies build, it's about what people actually do with it once it's out in the world.

I break down what Weather Radio Canada actually does, who loses when it goes dark, and why it's not just remote northern communities. It's older folks with SAME-capable radios, truckers, farmers, and volunteer groups using it as a backup feed.

The question underneath all of it: what does redundancy actually mean in 2026, when climate change is driving longer outages and we keep removing the durable layers because they don't look modern on a budget sheet?"

I also get into the AT&T versus Spectrum lawsuit, because AT&T is suing Charter over the fiber powered branding and they're not wrong. But AT&T pulled the same trick with fake 5G labels on 4G phones a few years back, so nobody in this fight is innocent. I explain what HFC networks are, why your upload speed gets choked on shared coax, and what the fine print is actually admitting when you read it closely.

This is a consumer rights problem dressed up as a tech story. If you're paying for internet every month, you deserve to know what wire is actually running to your house.

I trace how an electronic program guide became a full-time channel, the shift from Preview to the TV Guide Channel in 1999, and how smarter set-top boxes eventually killed the linear scroll by letting you search and filter instead of waiting.

The bigger point: television has been software for a long time, running on real-time rendering and uptime engineering that never got credit. And the psychology of that scroll, the looped promise that your thing was coming back, was doomscrolling before we had a word for it."

The key is separating the layers people mix up. HDD versus SSD is the technology, mechanical versus solid state. SATA versus NVMe is the interface, which sets the speed ceiling. M.2 is just the physical shape, not a performance guarantee, which is exactly how people end up paying premium prices for SATA-limited hardware.

I walk through the common scenarios: the brand-new but suspiciously cheap laptop that ships with a spinning disk, the gamer stuck on loading screens, the creator who needs smooth scrubbing and faster exports. You'll leave knowing which words on the spec sheet matter, NVMe and PCIe, and how to buy the upgrade that changes how the computer feels instead of the one that just looks good on paper."

I get into what tropospheric ducting and sporadic e-skip actually are, why the ITU and the FCC both account for this stuff as normal radio propagation, and why a hundred watt LPFM station picking up interference from stations hundreds of miles away isn't evidence of hacked ham radio equipment or a secret relay. I also cover the legal side, including why 47 USC 333 requires willful or malicious intent, something that doesn't apply to weather doing what weather does. And I get into why LPFM's status as a secondary service matters here, whether you like that fact or not.

This one covers real engineering, a real regulatory structure, and a station that keeps rejecting both in favor of a story that feels better. If you care about how spectrum actually works, how the FCC evaluates interference, or just want to watch what happens when people replace data with a grudge, this is for you.

I separate three things that get lumped together as smart. Optional convenience, like a fridge door notification, can be genuinely useful. Remote diagnostics can legitimately improve support. The real problem is the third category: core features locked behind connectivity, accounts, or cloud services, including a high end oven that needed Wi-Fi to unlock convection roast.

Independent testing shows appliances phoning home with megabytes of data weekly, and companion apps stuffed with third party trackers.

The playbook: decide if you need connectivity at all, connect only for warranty diagnostics if you must, isolate devices on a guest network, and stop paying premiums for embedded screens that age badly and invite ads. Buy appliances that work fully offline, with connectivity as an option, not a gate.

I walk through the mechanics in plain English. Monetization reshaped the first screen, SEO turned into an adversarial game, click metrics misread satisfaction, and AI made polished but shallow content nearly free to produce at scale. The result is a feedback loop where high-effort content declines and users get served summaries of summaries.

Then the practical part: surgical search operators, favoring vendor docs and standards over listicles, verifying AI answers against at least two solid sources, and building your own trust graph with bookmarks, RSS, and notes on who was right last time. Search is how we fix gear, pick tools, and check claims. Bad incentives become bad decisions, and it's worth knowing how to route around them."

I cover what actually changes when Windows support ends, why Zorin's Ubuntu LTS base matters, the Windows like layout, and how the Web Apps feature makes tools like Outlook, Google Docs, and Slack feel native.

Then the honest part: compatibility. Wine handles simple tools fine, but Adobe Creative Cloud, full fat Office, and niche vendor apps are dealbreakers, and gaming still favors Windows for anti cheat titles even with Proton doing heavy lifting.

The plan: test everything from a live USB before touching your disk, use dual boot as a safety net, and for small businesses, keep one or two Windows anchor machines for stubborn line of business software while moving browser centric roles over.

I cover where the standard came from, how it actually works at the technical level, and why it still matters for modern radio and modern vehicles.

I cover where RSS and the enclosure tag came from, how Spotify spent big trying to control the medium anyway, why a download is not a listen, and what Podcasting 2.0 is doing to extend the open standard without breaking it.

I explain how everyday data ends up on satellites in the first place, remote towers, ships, aircraft, rural networks, and why so much of it stays unencrypted while TV signals have been scrambled for years. Vendors sell encryption as an extra license, carriers downplay the risk, and recent telecom cybersecurity rules got rolled back.

Then the part you can control: end-to-end encrypted messaging instead of SMS, a trusted VPN in remote areas or in flight, and HTTPS and official apps for anything sensitive.

I start with the familiar pain: emailing yourself photos, juggling cloud links, hitting the wall when AirDrop meets Windows. Then the design that fixes it: local discovery, a small HTTPS server on each device, and direct encrypted transfers at LAN speed. No relays, no Bluetooth handshakes, and the no-internet requirement is sometimes a feature, like on a travel router when hotel Wi-Fi is garbage.

I also cover the failure modes honestly, because "devices don't see each other" has real causes: mismatched SSIDs, AP isolation, strict firewalls, and VPNs hijacking local subnets. There's a short checklist that fixes most of it. If you know someone who still emails themselves attachments, send them this one."

I break down both forces. The structure: metal roofs reflect and absorb radio waves, concrete and rebar soak up what's left, steel racks and coolers scatter the rest, and even that sleek glass storefront can have a metallic coating bouncing your signal back out. The people: hundreds of shoppers and staff devices sharing finite tower capacity, so a busy Saturday turns decent bars into unusable bandwidth.

The fix takes seconds: turn on Wi-Fi calling, force your phone onto Wi-Fi with airplane mode when needed, and drift toward the leaky spots near doors and big windows. If your signal only dies on weekends, that's your congestion clue right there."

I go back to school, when neurodivergence was poorly understood and kids like me got parked under vague labels like "specific learning disability" without real answers. Then forward to parenting, where my son's autism and ADHD diagnosis made me recognize patterns I've carried for decades. The turning point came while studying for the CCNA, when technical learning felt like eight radio stations competing at once.

I talk about the moment I realized this isn't laziness or a character flaw, why I finally messaged my doctor, and what scares me about the evaluation, including the possibility of being told I'm fine, or grieving a late diagnosis. And what I'm hoping for: options, language, better strategies, and the relief of not carrying it alone. If an adult evaluation has been on your mind, maybe some of this sounds familiar."

I connect it to the business model: margins on the panel are thin, the real money is the platform. That's why opt-out toggles are buried, renamed, or quietly reset after updates. The Vizio settlement proved this isn't hypothetical, and even the simpler platforms keep trying to re-enable personalization.

The most reliable fix is structural, not a scavenger hunt through menus: keep the TV offline entirely. Treat the panel as a dumb screen and put streaming on a separate box you control. If it has to connect, isolate it on a guest network or VLAN and use Pi-hole or NextDNS to cut the tracking traffic down, knowing DNS blocks are partial. The goal is leverage. Swap a small box instead of a big screen, and stop the profiling at the network boundary."

I walk through what Google, Microsoft, Meta, and Apple actually do with your data versus what people assume, then break down the 2022 LastPass breach as the clearest example of what happens when everyone's information gets piled into one company's server. From there I get into what self hosting actually looks like now, from a box on a shelf in your house to a rented VPS, plus tools like Vaultwarden and Immich ("Image") that let you run your own passwords and photos without handing them over to a corporation.

This isn't a burn it all down pitch. I still use iCloud myself and I say so. It's a real look at how much control you're giving away by default and what it would actually take to get some of it back, which is exactly what digital ownership and tech accountability are supposed to be about.

The soft claim holds up: bots, SEO farms, and AI pipelines really are flooding feeds and search. The hard claim doesn't: humans haven't vanished. What changed is the layer you see, curated by algorithms that maximize engagement. If you can publish 10,000 posts and only 10 need to hit to pay, volume wins, and the ranking loop gets gamed with fake likes and coordinated replies. Trust takes the hit.

I tour the damage across search, social, short video, and forums, then get practical: treat feeds as outputs rather than reality, curate aggressively, learn the quick tells for bots and source-free videos, lean on RSS and reputable newsletters, and harden your browser. One rule holds through all of it: authenticity costs something. Real people have constraints and histories. Industrial content is smooth and interchangeable. If you want the internet to feel alive again, go where humans pay a cost to be present."

The top-of-hour newscast is infrastructure. Local stations build their clocks, staffing, and listener habits around it. When it's reliable, it makes a station sound like a community service instead of a stream with a transmitter attached. "Challenging economic realities" doesn't explain shutting that off, especially against the backdrop of Paramount's broader cuts.

And then there's the part that burns trust: reports that some affiliates found out from the press release. Radio is a relationship business. When your partners learn the news in public, the message is clear about where they stand. I get into the human cost, the union's reaction, and what this means for local journalism going forward."

I walk through the whole chain: who issues the alert, how it gets distributed, how your local station receives it and puts it to air, and what happens after the test when stations report back on what worked and what didn't. I also get into why this broadcast based system isn't the same as the wireless alerts on your phone, and why that's actually a good thing. Redundancy matters. You don't want a tornado warning depending on one app, one carrier, or one piece of tech working perfectly.

This one's short, but it matters if you've ever wondered why that annoying tone exists or why it's supposed to be annoying. A boring Tuesday afternoon test is exactly how you find the broken piece in the system before you actually need it during a real emergency, and that's the whole point of testing anything that's supposed to keep people safe.

I break down what diesel actually costs to run a generator at a radio site or cell tower right now compared to a year ago, and the numbers are ugly. I run the math on different generator sizes, look at what happened at WMIT in North Carolina after Hurricane Helene, and talk about the FCC's numbers on how long cell sites actually run on batteries and backup fuel before someone has to physically drive more diesel out there. Spoiler: it's not as long as you'd hope.

Everyone treats backup power like a checkbox: station has a generator, cool, done. But a generator without fuel, fuel trucks, and people who can actually get to the site is just an expensive lawn ornament. If you care about what keeps communication infrastructure running when everything else fails, and who actually pays for that, this one's for you.