Tech Censorship

Note From San Francisco

On the way home after the holidays, notes on “cherry-picking” and a few other odds and ends

Having seen the redwoods with the boys by day, sampled dim sum last evening, and overdosed nights on San Francisco movies (Bullitt, Vertigo, the underrated Zodiac), I’m headed home tonight. A terrific trip, which I won’t forget.

In the coming days you’ll find a new thread on Twitter, along with a two-part article here at TK explaining the latest #TwitterFiles findings. Even as someone in the middle of it, naturally jazzed by everything I’m reading, I feel the necessity of explaining why it’s important to keep hammering at this.

Any lawyer who’s ever sifted though a large discovery file will report the task is like archaeology. You dig a little, find a bit of a claw, dust some more and find a tooth, then hours later it’s the outline of a pelvis bone, and so on. After a while you think you’re looking at something that was alive once, but what?

Who knows? At the moment, all we can do is show a few pieces of what we think might be a larger story. I believe the broader picture will eventually describe a company that was directly or indirectly blamed for allowing Donald Trump to get elected, and whose subjugation and takeover by a furious combination of politicians, enforcement officials, and media then became a priority as soon as Trump took office.

These next few pieces are the result of looking at two discrete data sets, one ranging from mid-2017 to early 2018, and the other spanning from roughly March 2020 through the present. In the first piece focused on that late 2017 period, you see how Washington politicians learned that Twitter could be trained quickly to cooperate and cede control over its moderation process through a combination of threatened legislation and bad press.


Categories: Tech Censorship

Leave a Reply