<?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: Buffalo&#8217;s Mass-Murder Leads to a Wrong Section 230 Decision&#8211;Jones v. Mean	</title>
	<atom:link href="https://blog.ericgoldman.org/archives/2024/03/buffalos-mass-murder-leads-to-a-wrong-section-230-decision-jones-v-mean.htm/feed" rel="self" type="application/rss+xml" />
	<link>https://blog.ericgoldman.org/archives/2024/03/buffalos-mass-murder-leads-to-a-wrong-section-230-decision-jones-v-mean.htm</link>
	<description></description>
	<lastBuildDate>Mon, 03 Jun 2024 01:09:43 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Bob		</title>
		<link>https://blog.ericgoldman.org/archives/2024/03/buffalos-mass-murder-leads-to-a-wrong-section-230-decision-jones-v-mean.htm#comment-4194</link>

		<dc:creator><![CDATA[Bob]]></dc:creator>
		<pubDate>Wed, 20 Mar 2024 02:18:00 +0000</pubDate>
		<guid isPermaLink="false">https://blog.ericgoldman.org/?p=26213#comment-4194</guid>

					<description><![CDATA[It&#039;s disappointing to see that every part of the opinion is backed by reasoning about as opaque as the parts you&#039;ve quoted. I don&#039;t know if they had been raised, but the opinion also completely ignores some critical points. In Anderson (1974), New York&#039;s highest court rejected the allegation a telephone company could be liable for the communications of its customers, regardless of its knowledge. The court was explicit that this rule of law generally encompassed providers of services that help customers to speak or publish content of their own design.

In Lunney (1999), the court made clear that even when a company chooses to exercise editorial control over some of the content produced by its users, it continues to have no liability with regard to any of the other content that it helps to publish. Although algorithmic recommendations were not at issue in Lunney, it&#039;s hard to imagine that such would matter, given the court&#039;s hostility not only to holding service providers liable for harm they cannot specifically predict, but also to imposing a duty to investigate the conduct of customers.

Even if a plaintiff could adequately allege recommendation conduct by a social media outlet that gives rise to liability (still have to ignore section 230), it&#039;s unnerving to see this opinion give the impression that, under New York law, publishing services are subject to the same product liability standards as any other service.

Even the most damning allegations about YouTube&#039;s algorithm, drawn from cherry-picked studies and expert interviews, would clearly establish that YouTube viewers train their own instance of that recommendation algorithm. That is, even as alleged, the algorithm only continues to present extremist content to users who actually view it when offered.

I could spend days picking apart the tortured logic of the complaint, but it all boils down to the same thing: the plaintiffs concede there is nothing unlawful about the content or its hosting per se, but insist that making it easy to find is a dangerous activity that must be undertaken with care. They pretend the freedom to publish somehow does not include helping people find what was published.]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s disappointing to see that every part of the opinion is backed by reasoning about as opaque as the parts you&#8217;ve quoted. I don&#8217;t know if they had been raised, but the opinion also completely ignores some critical points. In Anderson (1974), New York&#8217;s highest court rejected the allegation a telephone company could be liable for the communications of its customers, regardless of its knowledge. The court was explicit that this rule of law generally encompassed providers of services that help customers to speak or publish content of their own design.</p>
<p>In Lunney (1999), the court made clear that even when a company chooses to exercise editorial control over some of the content produced by its users, it continues to have no liability with regard to any of the other content that it helps to publish. Although algorithmic recommendations were not at issue in Lunney, it&#8217;s hard to imagine that such would matter, given the court&#8217;s hostility not only to holding service providers liable for harm they cannot specifically predict, but also to imposing a duty to investigate the conduct of customers.</p>
<p>Even if a plaintiff could adequately allege recommendation conduct by a social media outlet that gives rise to liability (still have to ignore section 230), it&#8217;s unnerving to see this opinion give the impression that, under New York law, publishing services are subject to the same product liability standards as any other service.</p>
<p>Even the most damning allegations about YouTube&#8217;s algorithm, drawn from cherry-picked studies and expert interviews, would clearly establish that YouTube viewers train their own instance of that recommendation algorithm. That is, even as alleged, the algorithm only continues to present extremist content to users who actually view it when offered.</p>
<p>I could spend days picking apart the tortured logic of the complaint, but it all boils down to the same thing: the plaintiffs concede there is nothing unlawful about the content or its hosting per se, but insist that making it easy to find is a dangerous activity that must be undertaken with care. They pretend the freedom to publish somehow does not include helping people find what was published.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
