{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/6a737f7d2578a0c7e2a39347?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"What AI Slop Actually Costs, and Who Ends Up Paying","description":"<p>Full post: <a href=\"https://natesnewsletter.substack.com/p/ai-slop-cost\" rel=\"noopener noreferrer\" target=\"_blank\">https://natesnewsletter.substack.com/p/ai-slop-cost</a></p><p>For deeper playbooks and analysis: <a href=\"https://natesnewsletter.substack.com/\" rel=\"noopener noreferrer\" target=\"_blank\">https://natesnewsletter.substack.com/</a></p><p><br></p><p>What's really happening when AI makes writing faster but leaves someone else with more work?</p><p><br></p><p>The common story is that AI slop is a style problem — but the reality is that it is an authorship problem. Shared rulebooks and banned-phrase lists can simply push everyone toward a different version of the same generic output.</p><p><br></p><p>In this episode, Nate shares the inside scoop on why authorship matters in the age of AI:</p><p><br></p><ul><li>Why AI slop pushes work downstream instead of making it disappear</li><li>How model convergence produces the same hill-climbing behavior</li><li>Why universal anti-slop checklists cannot create a distinctive voice</li><li>What a pro-authorship process looks like in practice</li><li>How better drafts protect scarce human attention</li></ul><p><br></p><p>For operators, builders, marketers, and executives, the standard is simple: use AI to stay in the work—not to escape responsibility for it.</p><p>Subscribe for daily AI strategy and news.</p><p>Hosted on Acast. See acast.com/privacy for more information.</p>","author_name":"Nate B. Jones"}