The Discourse on the post-coup tech platform rejection of violent fascism is giving me hives so I just have to get my ~hot take~ in here.

Sorry for the massive thread; Pascal’s apology applies.

Everybody loves to talk about “precedent” when a decision is made like kicking tr*mp off Twitter or pa*ler off of AWS, usually when making some fallacious slippery slope argument about what this “precedent” will mean for some completely non-comparable follow-up situation.
In some narrow colloquial sense, I admit there’s a precedent being set, in that when an analogous situation arises, the decision makers in that situation might do their research and look at this preceding (hence: “precedent”) event, and base some reasoning on it.
But this is a rhetorical trick—maybe one that those making the argument are playing on themselves as much as they’re playing it on you—because they’re trying to get you to consider the word in its legal-jargon sense: that future decision makers *must* consider these events.
This often goes along with the frankly bananas implication that by “setting the precedent” the decision makers (tech platforms or whoever) are arrogating to themselves a power which they did not *already have*, and it is thus dangerous and opens the door for future abuses.
And just as an aside here, if they didn’t already have this power legally and practically, how on earth are they granting it to themselves? What legislative authority do the sysadmins at Twitter have exactly?
So: first of all, the platforms already have this power to police speech in their purview as they see fit, they just haven’t exercised it on anyone this powerful before (arguably since nobody this powerful exists).
It doesn’t make the evening news when a queer teenager gets permabanned for telling a bluecheck TERF to die in a fire because they said something horribly bigoted. That is a worse abuse of this power than deplatforming violent fascists, and it happens *all the time*.
Second, these “precedents” are in no way *binding* on future decision makers. They could do whatever the fuck they wanted before this, they can do whatever the fuck they want after this.
Nothing has changed except that they used their (concerningly broad) power (which maybe they shouldn’t have for *other* reasons) to do something good for once.
When Batman makes everybody’s cell phone a secret surveillance device to catch the Joker, it’s not bad that he caught the Joker! The Joker is a piece of shit, fuck the Joker! The problem is that Batman should not have that power *lest it tempt him to do other, worse stuff later*.
So if you’re worried about what this sequence of events might mean because it highlights the unaccountable power that tech companies have and you don’t want to cheer for it because you’re worried about what they might do “next time”, relax. Cheer.
They already did worse stuff last time. You just didn’t hear about it. The horse isn’t just out of the barn, the horse was born wild and has never seen the inside of a barn.
Maybe we should, in fact, build a barn! It’s pretty messed up that this horse is running our society somehow! Maybe a horse shouldn’t be in charge.
There’s a robust debate to be had about how we might want to treat these big tech platforms as institutions, or how we might break them up, and believe me, I have *lots* of feelings about that discussion. It’s a necessary discussion. Like… existentially, for our civilization.
(For the record, regardless of your other political views, if you think the way to start here is “repeal section 230”... you’re not ready to participate in that discussion yet. Please do some more reading.)
But the answer is not to ask tech platforms not to suppress violent fascism. If anything, the fact that they *can* and sometimes *do* use their current vast and unaccountable power to combat the influence of violent fascists is an argument in favor of letting them keep it.
By all means let’s take it away. But not for this.

More from Tech

I think about this a lot, both in IT and civil infrastructure. It looks so trivial to “fix” from the outside. In fact, it is incredibly draining to do the entirely crushing work of real policy changes internally. It’s harder than drafting a blank page of how the world should be.


I’m at a sort of career crisis point. In my job before, three people could contain the entire complexity of a nation-wide company’s IT infrastructure in their head.

Once you move above that mark, it becomes exponentially, far and away beyond anything I dreamed, more difficult.

And I look at candidates and know-everything’s who think it’s all so easy. Or, people who think we could burn it down with no losses and start over.

God I wish I lived in that world of triviality. In moments, I find myself regretting leaving that place of self-directed autonomy.

For ten years I knew I could build something and see results that same day. Now I’m adjusting to building something in my mind in one day, and it taking a year to do the due-diligence and edge cases and documentation and familiarization and roll-out.

That’s the hard work. It’s not technical. It’s not becoming a rockstar to peers.
These people look at me and just see another self-important idiot in Security who thinks they understand the system others live. Who thinks “bad” designs were made for no reason.
Who wasn’t there.
On Wednesday, The New York Times published a blockbuster report on the failures of Facebook’s management team during the past three years. It's.... not flattering, to say the least. Here are six follow-up questions that merit more investigation. 1/

1) During the past year, most of the anger at Facebook has been directed at Mark Zuckerberg. The question now is whether Sheryl Sandberg, the executive charged with solving Facebook’s hardest problems, has caused a few too many of her own. 2/
https://t.co/DTsc3g0hQf


2) One of the juiciest sentences in @nytimes’ piece involves a research group called Definers Public Affairs, which Facebook hired to look into the funding of the company’s opposition. What other tech company was paying Definers to smear Apple? 3/ https://t.co/DTsc3g0hQf


3) The leadership of the Democratic Party has, generally, supported Facebook over the years. But as public opinion turns against the company, prominent Democrats have started to turn, too. What will that relationship look like now? 4/

4) According to the @nytimes, Facebook worked to paint its critics as anti-Semitic, while simultaneously working to spread the idea that George Soros was supporting its critics—a classic tactic of anti-Semitic conspiracy theorists. What exactly were they trying to do there? 5/
Next.js has taken the web dev world by storm

It’s the @reactjs framework devs rave about praising its power, flexibility, and dev experience

Don't feel like you're missing out!

Here's everything you need to know in 10 tweets

Let’s dive in 🧵


Next.js is a @reactjs framework from @vercel

It couples a great dev experience with an opinionated feature set to make it easy to spin up new performant, dynamic web apps

It's used by many high-profile teams like @hulu, @apple, @Nike, & more

https://t.co/whCdm5ytuk


@vercel @hulu @Apple @Nike The team at @vercel, formerly Zeit, originally and launched v1 of the framework on Oct 26, 2016 in the pursuit of universal JavaScript apps

Since then, the team & community has grown expotentially, including contributions from giants like @Google

https://t.co/xPPTOtHoKW


@vercel @hulu @Apple @Nike @Google In the #jamstack world, Next.js pulled a hefty 58.6% share of framework adoption in 2020

Compared to other popular @reactjs frameworks like Gatsby, which pulled in 12%

*The Next.js stats likely include some SSR, arguably not Jamstack

https://t.co/acNawfcM4z


@vercel @hulu @Apple @Nike @Google The easiest way to get started with a new Next.js app is with Create Next App

Simply run:

yarn create next-app

or

npx create-next-app

You can even start from a git-based template with the -e flag

yarn create next-app -e https://t.co/JMQ87gi1ue

https://t.co/rwKhp7zlys

You May Also Like

Still wondering about this 🤔


save as q