7 ms·
Why I changed my mind about Section 230
- nobody9999 6y agoNote to Steve Waldman: Please read this: https://www.techdirt.com/articles/20200531/23325444617/hello-youve-been-referred-here-because-youre-wrong-about-section-230-communications-decency-act.shtml https://www.techdirt.com/articles/20200531/23325444617/hello...
- olliej 6y agothe stupid problem here is that he's saying "because monopolies like twitter, Facebook, etc exist, section 230 should be repealed", while ignoring entirely that those giant businesses would be the only ones able to afford to host user content at all, and would actively suppress all remotely controversial content, including, but not limited to, reviews, social commentary, political commentary, etc. Or alternatively they censor absolutely nothing, so all the terrible content the author is complaining about would proliferate and be unblockable - goodbye "report tweet" button, etc that would be moderation that implies twitter is a publisher. Goodbye muting, etc because again: filtering the content risks making you a publisher. Goodbye spam filtering, that makes you a publisher. No small company could afford this, so would necessarily remove all comment sections, etc. It's questionable whether wikipedia could have any kind of restrictions on what people could say or do in articles.
- austincheney 6y agoYou are confounding publishing for hosting as convenient for your argument. A publisher need not host anything and likewise a content host need not publish anything.
- nobody9999 6y ago>You are confounding publishing for hosting as convenient for your argument. A publisher need not host anything and likewise a content host need not publish anything. Those are true statements, however Section 230 doesn't say anything even approaching that, nor are those statements relevant to what section 230 does or how it is applied. I've already been downvoted in this discussion for this (although posting a link to actual facts seems an odd thing to downvote, but I don't judge), but I'll take the hit again to share some facts with you. The title may be snarky, but the information is actually quite good and provides specific examples as to why section 230 helps you, me, HackerNews, maintainers of git repositories, mirror sites, forwarders of email and many, many others much more than it helps Twitter or Facebook: https://www.techdirt.com/articles/20200531/23325444617/hello-youve-been-referred-here-because-youre-wrong-about-section-230-communications-decency-act.shtml https://www.techdirt.com/articles/20200531/23325444617/hello... Edit: Fixed typo.
- austincheney 6y agoIt says exactly that. Section 230(c)(1): 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. So then be a publisher or content host but not both and then you don't need section 230 for protection at all, according to the letter of law. That said section 230 was intended to protect things like ISPs and email providers from frivolous lawsuits, but in practice primarily benefits online advertising companies and social media from valid lawsuits. Even if section 230 were to evaporate tomorrow Hacker News remains in no greater danger of lawsuits than any other medium currently not protected by section 230.
- nobody9999 6y ago>So then be a publisher or content host but not both and then you don't need section 230 for protection at all, according to the letter of law Really? Tell that to the judge who decided Stratton Oakmont v. Prodigy[0]. The law does distinguish between "interactive computer services" and "information content providers," but that is not, as some imply, a fancy legalistic ways of saying "platform" or "publisher." There is no "certification" or "decision" that a website needs to make to get 230 protections. It protects all websites and all users of websites when there is content posted on the sites by someone else. [0] https://en.wikipedia.org/wiki/Stratton_Oakmont,_Inc._v._Prodigy_Services_Co https://en.wikipedia.org/wiki/Stratton_Oakmont,_Inc._v._Prod....
- austincheney 6y agoStratton was distinguished from an earlier Compuserve case due to content moderation and that is all the case is notable for. The case was never decided by a judge as Section 230 had gone into effect before judgement rendering any judgement moot. > It protects all websites and all users of websites when there is content posted on the sites by someone else. No, it only protects the web site, as a service provider. Users of the web sites are not protected by Section 230 and can still be sued. This has happened frequently in the past when the RIAA would sue users of various media sharing tools.
- IG_Semmelweiss 6y agoI don't see why this needs to a binary decision. Clearly we can't allow monopolies to use laws intended to protect small players. So why not apply the protections selectively ? Take 230 protections off any player that achieves $$ X billion revenue, Y DAUs, IPOs, Total funding, total staff, whatever. Make a red line of what constitutes an internet forum monopoly , and just enforce it. I am not sure why this option is never mentioned ?
- qball 6y agoBecause it's not a sound bite, and because it's more about "owning the Democrats in Silicon Valley" than it is about solving the actual problem. Also, the more effective solutions would diminish government power and is thus undesirable; restricting the ability of CloudFlare or hosting companies to turn away customers means that they no longer get to lean on CloudFlare to take down websites that they don't want, much like how they currently use financial institutions to do the same kind of thing (Operation Chokepoint).
- nobody9999 6y ago>Clearly we can't allow monopolies to use laws intended to protect small players. On what basis do you make the judgement that section 230 was enacted to protect only small players? That doesn't appear to have been Congress' intent at all. In fact, while Congress was debating[1] section 230, Representative Christopher Cox[0] said: "But another New York court, the New York Supreme Court, held that Prodigy, CompuServe's competitor, could be held liable in a $200 million defamation case because someone had posted on one of their bulletin boards, a financial bulletin board, some remarks that apparently were untrue about an investment bank, that the investment bank would go out of business and was run by crooks. Prodigy said, ``No, no; just like CompuServe, we did not control or edit that information, nor could we, frankly. We have over 60,000 of these messages each day, we have over 2 million subscribers, and so you cannot proceed with this kind of a case against us.'' The court said, ``No, no, no, no, you are different; you are different than CompuServe because you are a family-friendly network. You advertise yourself as such. You employ screening and blocking software that keeps obscenity off of your network. You have people who are hired to exercise an emergency delete function to keep that kind of material away from your subscribers. You don't permit nudity on your system. You have content guidelines. You, therefore, are going to face higher, stricker liability because you tried to exercise some control over offensive material.'' Mr. Chairman, that is backward. We want to encourage people like Prodigy, like CompuServe, like America Online, like the new Microsoft network, to do everything possible for us, the customer, to help us control, at the portals of our computer, at the front door of our house, what comes in and what our children see. This technology is very quickly becoming available, and in fact every one of us will be able to tailor what we see to our own tastes." Note that the folks Rep. Cox was talking about, Compuserve, AOL, Prodigy and Microsoft were the big boys back then. So I'm not sure where you get the idea that only the small players were the intended beneficiaries of section 230. To be clear, I have no objection if you (and others) think there should be changes to section 230, then we should have a discussion about what changes should be made and why. I just think we should deal in facts and data and not make unsupported assertions about, well, anything -- especially when it comes to proposed legislative changes. [0] https://en.wikipedia.org/wiki/Christopher_Cox https://en.wikipedia.org/wiki/Christopher_Cox [1] https://www.congress.gov/congressional-record/1995/08/04/house-section/article/H8460-1 https://www.congress.gov/congressional-record/1995/08/04/hou...
- MuffinFlavored 6y agoWhat would really change if Section 230 was repealed? Facebook and Twitter are already moderating + flagging content on their own. Now they just would be held... legally liable for bad/opinionated fact checking? I doubt that would up in court?
- olliej 6y agoit's more that it would make them legally liable for the content itself, unless they stopped moderating and filtering. Currently if someone posts a shitty review, the company can sue them, not Facebook. That's what 230 does. If you remove section 230, then Facebook itself becomes liable for the comment. So now if the comment actually is libelous then Facebook would have to pay money. Unless they don't filter or moderate - filtering includes spam, etc. YCombinator would become liable for comments on hacker news - because it filters spammers. Facebook might be able to afford the presumably heavy handed filtering, but ycombinator probably can't, and a basic dev blog almost certainly can't, so would have to remove support for comments. Public bug reports also can't filter spam bug reports, for the same reason.
- nobody9999 6y ago>What would really change if Section 230 was repealed? Facebook and Twitter are already moderating + flagging content on their own. Now they just would be held... legally liable for bad/opinionated fact checking? I doubt that would up in court? What would change if section 230 were repealed? Well, among many other things, if you have a git repo and you delete any PRs (say, someone posts spam or links to porn or other material irrelevant to the repo and its underlying purpose), you can then be sued if someone (not you) posts a bug report or an opinion about anything that a third-party doesn't like. Or if you host a mirror of lkml[0] and Linus posts a snarky response to a patch merge request, without section 230, you can be sued. Or if you host a web site and someone posts a comment to which a third-party objects, without section 230, you can be sued. I'm not sure how you feel about that, but that's not the kind of world in which I want to live. [0] https://lkml.org/ https://lkml.org/
- tticvs 6y agoDoes it need to be a binary publisher/distributor distinction? Why not create a legal culpability for "editorial" decisions only. For example: if Twitter/Facebook/Youtube shows you content from users you follow in chronological order they would be exempt from responsibility. But, if they recommend you content based on some more advanced algorithm then they would have an "editorial" responsibility for the content of that content. So if youtube recommends some insane conspiracy videos denouncing HRC as a lizard person, then they would be open to a libel lawsuit. But if they just hosted it and only showed it to subscribers or on search the platform would not be liable. I guess "search" could be considered a recommendation algorithm but that could be carved out. And I don't think that search is really driving the social pollution of these large online platforms. Seems like a fair compromise to me since it wouldn't affect fundamentally what could be posted online, but only affect how the platforms are processing those posts.
- amadeuspagel 6y agoAlgorithms are not editorial decisions. This kind of change would make any kind of recommendation algorithm unviable.
- jdsully 6y agoI remember being vehemently against the DMCA along with the rest of the slashdot crowd. While I still think it is too frequently abused, I've come to accept that overall it is a reasonable compromise between copyright owners and publishers (in fact it's far more generous than youtube's alternative system). I think a similar system would be a reasonable compromise here as well.
- dredmorbius 6y agoThe DMCA has two notable provisions. Section 1201, anti-circumvention, is pure evil. As with the Youtube-dl case: https://joindiaspora.com/posts/808cf690f8e801381778002590d8e506 https://joindiaspora.com/posts/808cf690f8e801381778002590d8e... (https://news.ycombinator.com/item?id=24888234 https://news.ycombinator.com/item?id=24888234) Section 512, content take-down, is a mixed bag. It protects small players, but also opens the door to abuse or abusive interpretations such as YouTube's Content ID. See the Adam Neely - Katy Perry incident: https://www.dailydot.com/upstream/adam-neely-youtube-copyright-claim-katy-perry/ https://www.dailydot.com/upstream/adam-neely-youtube-copyrig... Discussed in this HN thread: https://news.ycombinator.com/item?id=22489373 https://news.ycombinator.com/item?id=22489373
- nobody9999 6y ago>I think a similar system would be a reasonable compromise here as well. How would something like you're suggesting work? Under what circumstances would it be appropriate to moderate and under what other circumstances would it be inappropriate? Just as importantly, who gets to decide what's appropriate/inappropriate? And to whom would this apply? Section 230 applies to everyone, including you, me, HackerNews and your great aunt Sally. If we limit section 230's applicability, who decides where it should apply and where it shouldn't? I'm not objecting to your suggestion, I'd just like to understand how you see such a 'compromise' being implemented. I'd welcome your thoughts!
- IG_Semmelweiss 6y agoIsn't this a set it and forget it, issue ? All that is in play is defining what a monopoly looks like, and codify it into law. Once that is set, it will be difficult to change without significant consensus. Making (weakening) changes after the fact would become toxic as it would look like corporate givewaways, optically not the best for any aspiring congressman.
- bni 6y agoWhy do Trump want to repel section 203, seems like it has worked in his interest all along?
- weare138 6y agoThe article seems to gloss over an important aspect of Section 230, shielding sites and providers from legal liability from 3rd party content. It would open sites and providers to frivolous libel lawsuits, something most small sites couldn't afford to fight in court, leaving only sites like Facebook and Twitter who could afford to deal with the legal ramifications.