AI Detection Can't Measure Meaning: What It Actually Sees

AI Detection Can't Measure Meaning: What It Actually Sees

I sit down with Substack co-founder and CEO Chris Best for a wide-ranging conversation about AI slop, what it does to the public square, and how writers can use powerful tools without outsourcing their judgment. We discuss Pangram's finding that roughly 40% of long-form writing on LinkedIn was fully AI-generated, why low-intent automation behaves like a denial-of-service attack on online communities, and what Substack is doing to add transparency without policing creators' tools. The conversation also covers thin versus thick wrappers around AI, proof of work, Claude-fishing, the future of video, and why human attention may be the last truly scarce resource. Chris Best: https://cb.substack.com [https://cb.substack.com/] Nate Jones: https://natesnewsletter.substack.com [https://natesnewsletter.substack.com/] ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

Kimi K3: China's Open AI Model and the Real Cost to Run It

For deeper playbooks and analysis: https://natesnewsletter.substack.com/ [https://natesnewsletter.substack.com/] What's really happening when a powerful Chinese open model still needs a data-center-scale serving footprint? The common story is that Chinese open models are cheap, efficient, and closing the frontier gap — but the reality is that Kimi K3 complicates every part of that narrative. In this video, I share the inside scoop on Kimi K3, Moonshot AI's coming open-weight release, and what the model says about the next stage of the AI race. * Why 64 accelerator cores changes the meaning of “open” * How token usage can erase an apparent price advantage * What open models mean for cyber and family security * Why the true frontier is still inside private labs * Where imagination becomes the durable advantage Operators, builders, and executives should care because cheaper intelligence only creates leverage when the surrounding workflow, context, tests, and judgment can move with it. Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information. ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

How to Use AI on Work You Can't Upload - Offline & Local

For deeper playbooks and analysis: https://natesnewsletter.substack.com/ [https://natesnewsletter.substack.com/] Clean sensitive documents locally: https://unlock-ai.natebjones.com/guides/clean-sensitive-docs-locally [https://unlock-ai.natebjones.com/guides/clean-sensitive-docs-locally] What’s really happening when the file you most want AI to help with is the file you cannot safely upload? The common story is that sensitive work has to stay manual — but the reality is that downloaded models, controlled enterprise systems, and narrow specialist workflows now create several practical paths between “send it to a chatbot” and “do not use AI.” In this episode, I share the inside scoop on how Bayer and Discovery Bank are building private AI specialists, then demonstrates the small version with LM Studio and a synthetic contract on a laptop with the network disconnected. * Why model instructions are not the same thing as a secure product boundary * How a local sensitivity router can flag, mask, and route potentially private material * What LoRA changes when a company tunes a specialist for one narrow job * Where laptop-scale processing ends and managed infrastructure begins * Why open weights do not automatically eliminate platform dependence This matters for operators, builders, security teams, and executives who need useful AI without losing control of confidential files or the learning loop created around them. Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information. ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

I asked Fable and Codex what to automate. They disagreed.

For deeper playbooks and analysis: https://natesnewsletter.substack.com/p/let-ai-pick-what-to-automate [https://natesnewsletter.substack.com/p/let-ai-pick-what-to-automate] What's really happening when you stop telling an AI what to automate and ask it to discover the problem itself? The common story is that AI agents need a tightly specified task — but the reality is that the strongest systems can inspect real work, identify recurring friction, and propose different high-leverage automations. In this video, I share the inside scoop on giving Fable and Codex the same open brief and getting two very different answers. * Why picking the problem is becoming part of the agent's job * How Fable found a strategic editorial preflight opportunity * What Codex built to validate completed content handoffs * Where human judgment still matters * How to turn the method into a reusable automation-discovery skill * For operators, builders, and leaders, the shift is from asking which tool to use to asking which recurring problem is worth solving completely. Subscribe for daily AI strategy and news. Hosted on Acast. See acast.com/privacy for more information. ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.

The AI Harness Audit: Clean Your Setup Before You Upgrade

Every time an AI missed something, I added another rule. Eventually, the accumulated skills, memories, system prompts, checks, and permissions became a hidden system of their own—and that system was getting in the models' way. In this episode, I audit the harness around my AI and compare what happens when Fable 5 and ChatGPT 5.6 meet compact versus overloaded instruction systems. The audit found 66 skill routes, 172 instruction assets, repeated governance rules, and a discovery layer far beyond Codex's stated budget. The lesson is not simply to shorten every prompt. It is to give each surviving instruction one owner and one reason, load specialist context when the work needs it, and enforce deterministic requirements with hard checks. Privacy Policy: https://www.acast.com/privacy ---------------------------------------- Hosted on Acast. See acast.com/privacy [https://acast.com/privacy] for more information.