<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns:idx="urn:atom-extension:indexing" xmlns="http://www.w3.org/2005/Atom" xmlns:dw="https://www.dreamwidth.org" idx:index="no">
  <id>tag:dreamwidth.org,2009-04-14:58489</id>
  <title>Monica</title>
  <subtitle>Monica</subtitle>
  <author>
    <name>Monica</name>
  </author>
  <link rel="alternate" type="text/html" href="https://cellio.dreamwidth.org/"/>
  <link rel="self" type="text/xml" href="https://cellio.dreamwidth.org/data/atom"/>
  <updated>2023-02-20T18:59:30Z</updated>
  <dw:journal username="cellio" type="personal"/>
  <entry>
    <id>tag:dreamwidth.org,2009-04-14:58489:2120545</id>
    <link rel="alternate" type="text/html" href="https://cellio.dreamwidth.org/2120545.html"/>
    <link rel="self" type="text/xml" href="https://cellio.dreamwidth.org/data/atom/?itemid=2120545"/>
    <title>Section 230</title>
    <published>2023-02-20T18:59:30Z</published>
    <updated>2023-02-20T18:59:30Z</updated>
    <category term="tech"/>
    <category term="politics"/>
    <category term="internet"/>
    <dw:security>public</dw:security>
    <dw:reply-count>0</dw:reply-count>
    <content type="html">&lt;p&gt;The Supreme Court will soon hear a case that -- according to most articles I've read -- could upend "Section 230", the law that protects Internet platforms from consequences of user-contributed content.  For example, if you post something on Facebook and there's some legal problem with you, that falls on &lt;em&gt;you&lt;/em&gt;, as the author, and not on &lt;em&gt;Facebook&lt;/em&gt;, who merely hosted it.  This law was written in the days of CompuServe and AOL, when message boards and the like were the dominant Internet discourse.  While there's a significant difference between these platforms and the phone company -- that is, platforms can alter or delete content -- this still feels like basically the "common carrier" argument.  This makes sense to me: you're responsible for your words; the place you happened to post it in public isn't.&lt;/p&gt;

&lt;p&gt;&lt;span style='white-space: nowrap;'&gt;&lt;a href='https://osewalrus.dreamwidth.org/profile'&gt;&lt;img src='https://www.dreamwidth.org/img/silk/identity/user.png' alt='[personal profile] ' width='17' height='17' style='vertical-align: text-bottom; border: 0; padding-right: 1px;' /&gt;&lt;/a&gt;&lt;a href='https://osewalrus.dreamwidth.org/'&gt;&lt;b&gt;osewalrus&lt;/b&gt;&lt;/a&gt;&lt;/span&gt; has written a lot about Section 230 over the years -- he explains this stuff better and way more authoritatively than I do.  (Errors are mine, credit is his, opinions are mine.)&lt;/p&gt;

&lt;p&gt;When platforms moderate content things get more complicated, and I'm seeing a lot of framing of the current case that's rooted in this difference.  From what I understand, that aspect is irrelevant, and unless the Supreme Court is going to be an activist court that legislates, hosting user-contributed content &lt;em&gt;shouldn't&lt;/em&gt; be in danger.  But we live in the highly-polarized US of 2023 with politically-motivated judges, so this isn't at all a safe bet.&lt;/p&gt;

&lt;p&gt;The reason none of that should matter is that the case the court is hearing, &lt;em&gt;Gonzales vs. Google&lt;/em&gt;, &lt;a href="https://www.washingtonpost.com/technology/2023/02/20/google-v-gonzalez-section-230/"&gt;isn't about content &lt;em&gt;per se&lt;/em&gt;&lt;/a&gt;.  It's about the &lt;em&gt;recommendation algorithm&lt;/em&gt;, Google's choice to &lt;em&gt;promote&lt;/em&gt; objectionable content.  This is not passive hosting.  That &lt;em&gt;should&lt;/em&gt; matter.&lt;/p&gt;

&lt;p&gt;The key part of Section 230 &lt;a href="https://www.law.cornell.edu/uscode/text/47/230"&gt;says&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
  &lt;p&gt;No provider or user of an interactive computer service shall be treated as the publisher or speaker of any information provided by another information content provider. (47 U.S.C. § 230(c)(1)).&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The court can rule against Google without affecting this clause at all.  The decision shouldn't be about whether Google is the "publisher" or "speaker".  Rather, in this case Google is the &lt;em&gt;advertiser&lt;/em&gt;, and Section 230 doesn't appear to cover promotion at all.&lt;/p&gt;

&lt;p&gt;I'm not a lawyer, and I'm not especially knowledgeable about Section 230.  I'm a regular person on the Internet with concerns about the proper placement of accountability.  Google, Twitter, Facebook, and others &lt;em&gt;choose&lt;/em&gt; to promote user-contributed content, while platforms like Dreamwidth, Mastodon, and many forums merely present content in the order in which it arrives.  That should matter.  Will it?  No idea.&lt;/p&gt;

&lt;p&gt;Moderation is orthogonal.  Platform owners should be able to remove content they do not want to host, just like the owner of a physical bulletin board can.  In a just world, they would share culpability &lt;em&gt;only&lt;/em&gt; if objectionable content was brought to their attention and they did not act.  At that point they've said it's ok, as opposed to saying nothing at all because nobody can read &lt;em&gt;everything&lt;/em&gt; on a platform of even moderate size.  This is how I understand the "safe harbor" provision of the Digital Millennium Copyright Act to work, and the same principle should apply.  In a just world, as I said, which isn't the world we live in.  (I, or rather my job title, am a registered agent for DMCA claims, and I have to respond to claims I receive.)&lt;/p&gt;

&lt;p&gt;I really hope that the court, even a US court in 2023, focuses on the key points and doesn't use this case to muck with things not related to the case at hand.&lt;/p&gt;
&lt;br /&gt;&lt;br /&gt;&lt;img src="https://www.dreamwidth.org/tools/commentcount?user=cellio&amp;ditemid=2120545" width="30" height="12" alt="comment count unavailable" style="vertical-align: middle;"/&gt; comments</content>
  </entry>
</feed>
