Like I said, Iโm not going to educate you. But if you think the problem with 230 is that bad people post bad things on the internet, you donโt have a problem with 230, you have a problem with the First Amendment.
https://www.techdirt.com/2020/11/02/your-problem-is-not-with-section-230-1st-amendment/
And besides, without 230 sites would have LESS incentive to moderate content, not more. 230 PROTECTS MODERATION.
If you have a problem with bad content on bad sites, you have a problem with THOSE SITES, NOT 230.
I spent a career trying to get sites to moderate better and it was fucking hard, but I remember the web before 230, and back then the lawyers told us NOT TO MODERATE AT ALL because doing so could create liability. Thatโs not a situation anyone should want to go back to.
You want an internet where the nazis can post whatever they want and the sites canโt take it down? Or where no one is willing to host a masto server for fear of getting sued for something a user posts?
You really donโt.
@fraying
"You want an internet where the nazis can post whatever they want and the sites canโt take it down?"
That's a considerable part of why certain politicians are trying to undo it.
Hence the brilliance of the Fediverse. Those bad sites: disconnected. The ultimate in moderation.
@boelder what if sites are wrongly disconnected without any real evidence? and what if this is then spread virally to people who don't even know why the site was blocked to begin with?
it can happen to you! ๐ฎ
@fraying My problem isn't "bad people posting bad things". My problem is places like YouTube artificially boosting them to people not searching those things.
There have been scientific studies that show YouTube pushes more extreme content on viewers. Make the algorithm transparent and then making manipulating the algorithm against the TOS.
@fraying not everyone running a fedi server is in the US
(I say, from a server with an admin in the US)
@film_girl @fraying last month i gave a talk in a law school class, where the prof first split the class up into two groups, one had to defend 230 and the other had to explain why it was bad. Both groups gave talks on why it was bad. The "defense" was "it was good at first, but now it's not."
The talk I gave to them very quickly changed...
@fraying @mmasnick @film_girl A real turning point for me was being asked a direct question by the main investor in the company I helped start, if I would have a problem promoting stories and/or talking points I knew were false.
Shortly after that, I no longer worked with that company.
If you havenโt read it yet, I highly recommend reading the latest Wired cover story by Nicholas Thompson and Fred Vogelstein, detailing the past two years at Facebook and how the company has โฆ
Yes. I'm sharing the following mostly for others since I went and looked it up myself.
And you're right, if we lose Section 230, so many of us would be unable to host our own servers, and the Fediverse would be in danger.
This is upsetting. Stripping away our ability to talk to each other online.
Quote from article: "โThe primary thing we do on the internet is we talk to each other. It might be email, it might be social media, might be message boards, but we talk to each other. And a lot of those conversations are enabled by Section 230, which says that whoeverโs allowing us to talk to each other isnโt liable for our conversations,โ said Eric Goldman, a professor at Santa Clara University specializing in internet law. โThe Supreme Court could easily disturb or eliminate that basic proposition and say that the people allowing us to talk to each other are liable for those conversations. At which point they wonโt allow us to talk to each other anymore.โ
Very important...for #US admins/owners:
@fraying I certainly donโt think 230 should be repealed, but it needs revision.
I think sites should not be responsible for user generated content, but they should be responsible for manual or automated editorializing that user generated content.
So direct timelines would not be affected, but if Yelp reorders posts, they assume some liability, if Facebook or Twitter reorder content then they are responsible for what they are promoting or hiding.
@fraying There are two provisions called Section 230. Although striking down either of them has significant concerns, I think we should at least distinguish between them.
230(c)(2) is the one that shields providers from liability for blocking or removing contents. This is what GOP hates, and this is what every website relies on for moderation.
230(c)(1) is the one that shields providers from liability for NOT blocking or removing contents. This is still useful, because certain states claim that LGBT related contents must be blocked because they are inappropriate to children. 230(c)(1) effectively nullifies such claims.
FOSTA (and perhaps DMCA) is the one to blame here. It created an exception to 230(c)(1), and guess what, people across the U.S. now demand certain "illegal" things to be outside 230(c)(1) protection, and certain politicians use this effort to ALSO dismantle 230(c)(2).
@apple502j that is some crazy shit man.
Crazy shit.
@fraying First, there's Anti-Terrorism Act at issue in Gonzalez. Blue states might see 230(c)(1) as an issue in enforcing data protection laws. Or the Sherman Act that was at issue with Malwarebytes v. Enigma, notable for Justice Thomas's dissent. While hate speech laws are probably unconstitutional anyway, 230(c)(1) also shields companies from hate speech related liabilities, which I understand some of you don't like.
But then there is the other category of things. Things like SLAPP suits, copyright trolls, and subjects like "critical race theory" or LGBT people's existence that GOP claims is discriminatory or obscene. If 230(c)(1) did not exist, the platforms are forced to censor everything except maybe cat pictures, and you can't sue the platform for the removal.
Hi Derek!
And greetings from the remote mountain regions of #Humboldt where we export the genetics for those ๐บ flowers ๐ค๐๐ค
Anyway...
I'm trying to your post in which you both misconstrued and misinformed the reader with alarmist, and generally misunderstood narrative.
Specifically, and respectfully:
>***"I wonder if people using mastodon know that, without section 230, no one could legally afford to run a mastodon instance in the US. Section 230 protects what we do here every day. Politicians threatening 230 are threatening free speech on the internet."***
Although we'll go over both sentences, the part that I really take exception to is the first one:
- "I wonder if people using mastodon know that, without section 230, no one could legally afford to run a mastodon instance in the US."
I quoted you twice for emphasis, because what you said is simply NOT TRUE, at all Derek, but who would want to run a single user mastodon server instance anyway?
Okay a select few, but it's not economical to do so - here's why:
It's such #bloatware and a #resource_hog compared to other, more capable and featureful #Fediverse servers, like #Pleroma, #Takahฤ, #Epicyon, #Akkoma, #Calckey, #Soapbox, #Friendica, #Socialhome, #MicroblogPub, #Misskey, #Smithereen, and the list goes on and on for a while; a veritable laundry list of platforms endowed with more feature rich, more resource and energy conserving footprints.
You could call mastodon the white elephant in the room when it comes to kruft, waste of energy and resources, or lack of the most desired features by it's traditional userbase (although people are nowadays migrating their accounts to these other Fediverse platforms in ever increasing numbers).
Like you, I'm also a staunch proponent of Section 230, as it was originally intended and written - to protect publishers, NOT editors. But most of the conservative agendas to which you refer only seek to remove protections for sites that cross that line between that of #publisher to that of #editor anyway - so as long as you don't interfere with a user's #speech those deprecated silos would have nothing to worry about.
It's the Marxist/Leftist agendas in Congress that you need to worry about - they're proposing complete evisceration of section 230 - and yes, that would jeopardize, probably even put those monolithic deprecated silos out of business for good.
- I see very little that is bad about killing a rabid animal... Or a fox in the henhouse.
But... riddle me this Batman:
What would be so bad about that? It would destroy the surveillance plutocracy and data farming of individuals and their identities by those socalled, "Big-Tech" subjugation engines like #Faceplant, #InstaSPAM, #Reddit, #Twitter, and to a large degree, #Google too... (It won't do anything to stop the likes of Amazon or Apple though wrt their surveillance programs).
All if that, while at the same time encourage the migration of people to a fully decentralized and safer social media network where there are either no platforms (only censor proof protocols), as in #nostr; or #federated #SmallWeb and single user #ActivityPub platform instances; or those #Fediverse platforms that vow not to #molest_users who #publish on those platforms by imposing draconian #editorializing (censorship) upon their users.
Either way you can certainly look at this as a win-win situation for the #individual in #social_media networking. The question really is therefore, "How badly do you wish to punish the privacy disrespecting subjugation farms that comprise that deprecated, monolithic silo space?"
I hope that helps, Enjoy!
โต
.
@fraying Section 230 might be cast aside & something better instituted. It's also possible that servers/instances/Internet providers that ONLY provide a place for people to say stuff, NOT manipulate readers with algorithm-driven whatnot, NOT curate material, NOT scrape others' materials off the Internet & repurpose it, NOT commission their own content โ might remain protected under 230, while Meta-FB-etc. are justifiably sued.
@fraying Sure. Here's the Brookings summation from Feb of the then-upcoming proceedings: https://www.brookings.edu/blog/techtank/2023/01/31/the-supreme-court-takes-up-section-230/ . Here's Cornell's text of 230: https://www.law.cornell.edu/uscode/text/47/230
Here's the EFF version (I loved them back in the early-mid 1990s. Guess what? It's not the early-mid 1990s anymore). https://www.eff.org/issues/cda230
Hope that's useful.