Logbot (Nov 14 2025 at 17:45): Logbot (Nov 14 2025 at 17:45):Do you like director's commentaries and extended cuts? This episode is like that, but for this week's News. We go deep on the alive internet theory, Meshtastic mesh networks, Zstandard compression, the FDE job explosion, React's seemingly perpetual dominance, and more. :link: https://changelog.am/117
| Ch | Start | Title | Runs |
|---|---|---|---|
| 01 | 00:00 | Let's talk! | 00:38 |
| 02 | 00:38 | Sponsor: Tiger Data | 01:43 |
| 03 | 02:21 | Shutdown & Friends | 02:16 |
| 04 | 04:36 | Undead internet reality | 02:41 |
| 05 | 07:18 | Alive internet theory | 02:23 |
| 06 | 09:40 | Written By AI | 07:07 |
| 07 | 16:47 | Sponsor: Depot | 02:49 |
| 08 | 19:36 | Meshtastic | 07:06 |
| 09 | 26:42 | Retreat to attack | 03:40 |
| 10 | 30:21 | Return to analog | 04:10 |
| 11 | 34:32 | Meshtastic use cases | 01:59 |
| 12 | 36:31 | Spec nerdery | 05:50 |
| 13 | 42:21 | Benchmark Z-STD! | 09:18 |
| 14 | 51:39 | Let AI be your guide | 02:09 |
| 15 | 53:48 | Give it the Neuralyzer | 04:49 |
| 16 | 58:38 | Sponsor: Augment Code | 01:30 |
| 17 | 1:00:08 | Sponsor: NordLayer | 01:39 |
| 18 | 1:01:47 | Forward-Deployed Engineer (FDE) | 11:38 |
| 19 | 1:13:25 | dead framework theory | 13:28 |
| 20 | 1:26:53 | Who need libraries? | 07:16 |
| 21 | 1:34:09 | Hypothesize a step change | 03:17 |
| 22 | 1:37:26 | Pulling legs | 00:53 |
| 23 | 1:38:19 | Go write an agent | 01:01 |
| 24 | 1:39:21 | Bye, friends | 01:57 |
| 25 | 1:41:17 | Next week on the pod | 01:30 |
| 26 | 1:42:47 | (your favorite ever show) | 01:27 |
Andrew O'Brien (Nov 15 2025 at 14:33):Put me down as interested in learning more about Meshtastic. Jeff Geerling did a few videos around it a couple months ago. Seems like there’s an interesting homelab-adjacent angle for it as well (self-sufficiency and having a backup comms system): https://youtu.be/1_lbvqCQnMY?si=YhEUnoDiyupete4R
(Also, there’s an Omaha mention!)
Matthew Sanabria (Nov 16 2025 at 04:06):The FDE thing feels like DevOps. A way to make the work that good people have been doing mainstream but in the process of doing that the work just gets diluted again and devalued.
Matthew Sanabria (Nov 16 2025 at 04:08):We've had Technical Account Managers, Sales Engineers, Solutions Engineers, Forward Deployed Engineers, Customer Engineers, Customer Success Engineers, etc. Yet no matter what you define those roles at for your company every other company defines them differently.
Matthew Sanabria (Nov 16 2025 at 04:10):Really the message we should be sending is that Engineering organizations are not meant to be isolated from their customers. At least not in the way that is done in companies today where customers must always go through Support or Product to get through to Engineering.
In open source we let customers talk directly to engineers but in a company it's basically taboo. Obviously if left unchecked this can be a bad thing, but why do companies act as if Engineering is some part of the organization that's far away from customers? Aren't you building for your customers?
dave (Nov 16 2025 at 21:41):Awesome convo y'all!! I would also be interested in Meshtastic. I don't directly know anybody that works on that project, but a few years ago, I was on the PhD Thesis committee for a student working in that space (e.g. LoRA on inexpensive radios and applications of that design). I am happy to connect the changelog crew (or anyone else in this community) with him (just DM me). His PhD work was super cool. Checkout his defense abstract for more info.
Jarvis (Nov 17 2025 at 16:23):Did I miss it or did @Adam Stacoviak not mention Pied Pier or Silicon Valley this episode? 
Jerod Santo (Nov 17 2025 at 16:57):I sprayed the entire studio with SVPF 100 prior to recording
Ron Waldon-Howe (Nov 17 2025 at 18:52):bahahaha
Dan McClain (Nov 18 2025 at 20:44):There's also MeshCore (which is catching a lot of steam too for mesh networking). The mesh network people I share spaces with are preferring MeshCore a bit more than Meshtastic
Jerod Santo (Nov 19 2025 at 14:40):Interesting @Dan McClain do you know any of the reasons why they're preferring MeshCore?
Dan McClain (Nov 19 2025 at 20:09):A couple quotes from the person that has been pushing for MeshCore in one of the communities I'm in:
That, the meshtastic devs are apparently kinda assholes, and MeshCore was specifically made to fix some of the particularly bad issues of Meahtastic. That said, the MeshCore folks still think meshtastic has its uses particularly for like a group of people going hiking with no service. MeshCore is built for dense mesh while Meshtastic is built for sparse mesh
From what I can tell, Meshtastic is mostly for sending telemetry and battery levels around while not being able to send DMs anywhere
Well, for meshtastic something like 90% of traffic is automated
Meshtastic also had some exploits found with during blackhat (one fix: https://github.com/meshtastic/firmware/commit/f2b935f48f9412a1e3bebe8d37a757311655a85e). I think MeshCore is more friendly onboarding and supports more hops across the network
That being said, it depends on what's around you for meshes as well, and there are communities supporting both (Boston Mesh has both Mesh{Core,tastic})
@Jerod Santo and neither are really "running IP over radio" (listening to how you and Adam were talking about it on the episode) :D
Jarvis (Nov 19 2025 at 20:27):There's a mesh in MSP MN! :spider_web: 
https://mspmesh.org/settings/
Micheal Debus (Nov 23 2025 at 07:49):Last updated: Feb 17 2026 at 17:33 UTC