<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: The Social Reckoning Is Perfectly Written and Perfectly Late	</title>
	<atom:link href="https://taylorholmes.com/2026/10/11/the-social-reckoning-is-perfectly-written-and-perfectly-late/feed/" rel="self" type="application/rss+xml" />
	<link>https://taylorholmes.com/2026/10/11/the-social-reckoning-is-perfectly-written-and-perfectly-late/</link>
	<description>Movies, Books &#38; TV for people who like to think..</description>
	<lastBuildDate>Mon, 02 Nov 2026 14:47:41 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.5</generator>
	<item>
		<title>
		By: Owen Blake		</title>
		<link>https://taylorholmes.com/2026/10/11/the-social-reckoning-is-perfectly-written-and-perfectly-late/#comment-1196106</link>

		<dc:creator><![CDATA[Owen Blake]]></dc:creator>
		<pubDate>Mon, 02 Nov 2026 14:47:41 +0000</pubDate>
		<guid isPermaLink="false">https://taylorholmes.com/?p=34233#comment-1196106</guid>

					<description><![CDATA[Your distinction between explaining an algorithm and making the audience feel its trade-offs is useful. A system procedural could show the same recommendation decision from the engineer, user and business team perspectives, then let the consequences connect. That would make the mechanism concrete even for viewers who already understand the broad criticism of engagement-driven platforms. The one-percent engagement trade-off you describe seems a particularly strong place to dramatize those competing incentives.]]></description>
			<content:encoded><![CDATA[<p>Your distinction between explaining an algorithm and making the audience feel its trade-offs is useful. A system procedural could show the same recommendation decision from the engineer, user and business team perspectives, then let the consequences connect. That would make the mechanism concrete even for viewers who already understand the broad criticism of engagement-driven platforms. The one-percent engagement trade-off you describe seems a particularly strong place to dramatize those competing incentives.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
