# E1744: MeshCore Team Feud Here's What Happened

Page: https://stenobird.com/podcast/ham-radio-2-0-461386/e1744-meshcore-team-feud-here-s-what-happened
Text version: https://stenobird.com/podcast/ham-radio-2-0-461386/e1744-meshcore-team-feud-here-s-what-happened.md
Podcast: [Ham Radio 2.0](https://stenobird.com/podcast/ham-radio-2-0-461386)
Published: 2026-05-29T19:24:38+00:00
Episode link: https://www.spreaker.com/episode/e1744-meshcore-team-feud-here-s-what-happened--72118917
Audio file: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/72118917/meshcore_team_feud_here_s_what_happened.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/ham-radio-2-0-461386/episodes/e1744-meshcore-team-feud-here-s-what-happened
Duration seconds: 680

## Resource

Discover the full story behind the dramatic MeshCore fork. In this video, we break down the official blog post from the MeshCore core team explaining "The Split" — from secret AI "vibe coding" with Claude, the surprise trademark filing, loss of trust, to the launch of the new official home at meshcore.io. Learn what this means for the 38,000+ node MeshCore network, 100,000+ app users, firmware development, and the future of human-written open-source mesh networking hardware. New Meshcore Website - https://meshcore.io Devices that work for Meshcore - https://amzn.to/4n073rH Blogpost - https://blog.meshcore.io/2026/04/23/the-split Become a supporter of this podcast: https://www.spreaker.com/podcast/ham-radio-2-0--2042782/support .

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/ham-radio-2-0-461386/episodes/e1744-meshcore-team-feud-here-s-what-happened/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/ham-radio-2-0-461386/e1744-meshcore-team-feud-here-s-what-happened.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.