Twitter Files #3: Banning the President
We’re finally into the FBI stuff.
James Baker, FBI attorney employed by Twitter, was blocking all of this during Twitter Files #1. He’s now fired and we’re getting the truth.
That Jew Yolo was behind banning Donald Trump. Not surprising at all.
This is a very good news story. The only one available today, actually.
(Yes, there are some problems with the numbering.)
1. THREAD: The Twitter Files
THE REMOVAL OF DONALD TRUMP
Part One: October 2020-January 6th— Matt Taibbi (@mtaibbi) December 9, 2022
3. We’ll show you what hasn’t been revealed: the erosion of standards within the company in months before J6, decisions by high-ranking executives to violate their own policies, and more, against the backdrop of ongoing, documented interaction with federal agencies.
— Matt Taibbi (@mtaibbi) December 9, 2022
5. Whatever your opinion on the decision to remove Trump that day, the internal communications at Twitter between January 6th-January 8th have clear historical import. Even Twitter’s employees understood in the moment it was a landmark moment in the annals of speech. pic.twitter.com/tQ01n58XFc
— Matt Taibbi (@mtaibbi) December 9, 2022
7. Twitter executives removed Trump in part over what one executive called the “context surrounding”: actions by Trump and supporters “over the course of the election and frankly last 4+ years.” In the end, they looked at a broad picture. But that approach can cut both ways. pic.twitter.com/Trgvq5jmhS
— Matt Taibbi (@mtaibbi) December 9, 2022
9. Before J6, Twitter was a unique mix of automated, rules-based enforcement, and more subjective moderation by senior executives. As @BariWeiss reported, the firm had a vast array of tools for manipulating visibility, most all of which were thrown at Trump (and others) pre-J6.
— Matt Taibbi (@mtaibbi) December 9, 2022
11. After J6, internal Slacks show Twitter executives getting a kick out of intensified relationships with federal agencies. Here’s Trust and Safety head Yoel Roth, lamenting a lack of “generic enough” calendar descriptions to concealing his “very interesting” meeting partners. pic.twitter.com/kgC4eGykcO
— Matt Taibbi (@mtaibbi) December 9, 2022
13. One particular slack channel offers an unique window into the evolving thinking of top officials in late 2020 and early 2021.
— Matt Taibbi (@mtaibbi) December 9, 2022
15. There was at least some tension between Safety Operations – a larger department whose staffers used a more rules-based process for addressing issues like porn, scams, and threats – and a smaller, more powerful cadre of senior policy execs like Roth and Gadde.
— Matt Taibbi (@mtaibbi) December 9, 2022
17. During this time, executives were also clearly liaising with federal enforcement and intelligence agencies about moderation of election-related content. While we’re still at the start of reviewing the #TwitterFiles, we’re finding out more about these interactions every day.
— Matt Taibbi (@mtaibbi) December 9, 2022
19. Pickles quickly asks if they could “just say “partnerships.” After a pause, he says, “e.g. not sure we’d describe the FBI/DHS as experts.” pic.twitter.com/d3EaYJb5eR
— Matt Taibbi (@mtaibbi) December 9, 2022
21. Roth’s report to FBI/DHS/DNI is almost farcical in its self-flagellating tone:
“We blocked the NYP story, then unblocked it (but said the opposite)… comms is angry, reporters think we’re idiots… in short, FML” (fuck my life). pic.twitter.com/sTaWglhaJt— Matt Taibbi (@mtaibbi) December 9, 2022
24. Here, the FBI sends reports about a pair of tweets, the second of which involves a former Tippecanoe County, Indiana Councilor and Republican named @JohnBasham claiming “Between 2% and 25% of Ballots by Mail are Being Rejected for Errors.” pic.twitter.com/KtigHOiEwF
— Matt Taibbi (@mtaibbi) December 10, 2022
25. The FBI-flagged tweet then got circulated in the enforcement Slack. Twitter cited Politifact to say the first story was “proven to be false,” then noted the second was already deemed “no vio on numerous occasions.” pic.twitter.com/LyyZ1opWAh
— Matt Taibbi (@mtaibbi) December 10, 2022
27. Examining the entire election enforcement Slack, we didn’t see one reference to moderation requests from the Trump campaign, the Trump White House, or Republicans generally. We looked. They may exist: we were told they do. However, they were absent here.
— Matt Taibbi (@mtaibbi) December 10, 2022
31. In one case, former Arkansas governor Mike Huckabee joke-tweets about mailing in ballots for his “deceased parents and grandparents.” pic.twitter.com/ZRpmwJa7K1
— Matt Taibbi (@mtaibbi) December 10, 2022
The group declares Huck’s an “edge case,” and though one notes, “we don’t make exceptions for jokes or satire,” they ultimately decide to leave him be, because “we’ve poked enough bears.”
— Matt Taibbi (@mtaibbi) December 10, 2022
33. Roth suggests moderation even in this absurd case could depend on whether or not the joke results in “confusion.” This seemingly silly case actually foreshadows serious later issues: pic.twitter.com/nOi50BdeaC
— Matt Taibbi (@mtaibbi) December 10, 2022
35. In another example, Twitter employees prepare to slap a “mail-in voting is safe” warning label on a Trump tweet about a postal screwup in Ohio, before realizing “the events took place,” which meant the tweet was “factually accurate”: pic.twitter.com/4r6nJ3JDmY
— Matt Taibbi (@mtaibbi) December 10, 2022
"VERY WELL DONE ON SPEED": the group is pleased the Trump tweet is dealt with quickly pic.twitter.com/WMyQjbWqNW
— Matt Taibbi (@mtaibbi) December 10, 2022
38. After Woods angrily quote-tweeted about Trump’s warning label, Twitter staff – in a preview of what ended up happening after J6 – despaired of a reason for action, but resolved to “hit him hard on future vio.” pic.twitter.com/dusFylxAXS
— Matt Taibbi (@mtaibbi) December 10, 2022
40. Twitter teams went easy on Hice, only applying “soft intervention,” with Roth worrying about a “wah wah censorship” optics backlash: pic.twitter.com/PGuihwNSu6
— Matt Taibbi (@mtaibbi) December 10, 2022
42. “THAT’S UNDERSTANDABLE”: Even the hashtag #StealOurVotes – referencing a theory that a combo of Amy Coney Barrett and Trump will steal the election – is approved by Twitter brass, because it’s “understandable” and a “reference to… a US Supreme Court decision.” pic.twitter.com/6BjJhjypD2
— Matt Taibbi (@mtaibbi) December 10, 2022
44. Later in November 2020, Roth asked if staff had a “debunk moment” on the “SCYTL/Smartmantic vote-counting” stories, which his DHS contacts told him were a combination of “about 47” conspiracy theories: pic.twitter.com/QiYGlZE202
— Matt Taibbi (@mtaibbi) December 10, 2022
46. Some executives wanted to use the new deamplification tool to silently limit Trump’s reach more right away, beginning with the following tweet: pic.twitter.com/U7AJLF2wIt
— Matt Taibbi (@mtaibbi) December 10, 2022
48. The significance is that it shows that Twitter, in 2020 at least, was deploying a vast range of visible and invisible tools to rein in Trump’s engagement, long before J6. The ban will come after other avenues are exhausted
— Matt Taibbi (@mtaibbi) December 10, 2022
50. In this instance, it appears moderators added a bot for a Trump claim made on Breitbart. The bot ends up becoming an automated tool invisibly watching both Trump and, apparently, Breitbart (“will add media ID to bot”). Trump by J6 was quickly covered in bots. pic.twitter.com/UhYQ31qIgn
— Matt Taibbi (@mtaibbi) December 10, 2022
52. To “bounce” an account is to put it in timeout, usually for a 12-hour review/cool-off: pic.twitter.com/rGUIhGF6w8
— Matt Taibbi (@mtaibbi) December 10, 2022
54. PII has multiple meanings, one being “Public Interest Interstitial,” i.e. a covering label applied for “public interest” reasons. The post below also references “proactive V,” i.e. proactive visibility filtering. pic.twitter.com/GSCjAPaBjG
— Matt Taibbi (@mtaibbi) December 10, 2022
This project was preposterous yet its leaders were unable to see this, having become infected with groupthing, coming to believe – sincerely – that it was Twitter's responsibility to control, as much as possible, what people could talk about, how often, and with whom.
— Matt Taibbi (@mtaibbi) December 10, 2022
57. This “Freedom or Death” tweet from #StopTheSteal gadfly Mike Coudrey elicits heated reactions: pic.twitter.com/NeBnL4e5YB
— Matt Taibbi (@mtaibbi) December 10, 2022
59. At 2:39 p.m. PST, a comms official asked Roth to confirm or deny a story that they’d restricted Trump’s ability to tweet. Roth says, “We have not.” pic.twitter.com/MeaHgN0FUQ
— Matt Taibbi (@mtaibbi) December 10, 2022
This theme of Policy perhaps being stressed by queries from Communications executives – who themselves have to answer the public’s questions – occasionally appears. Two days later, you see chatter about pulling Comms out of the loop: pic.twitter.com/sPxGcXtOpy
— Matt Taibbi (@mtaibbi) December 10, 2022
62. “WHAT THE ACTUAL FUCK?” Safe to say Trump’s “Go home with love & in peace” tweet mid-riot didn’t go over well at Twitter HQ: pic.twitter.com/yhi5uv4QXI
— Matt Taibbi (@mtaibbi) December 10, 2022
64. By the end of the first day, the top execs are still trying to apply rules. By the next day, they will contemplate a major change in approach. Watch @shellenbergerMD this weekend for the play-by-play of how all that went down.
— Matt Taibbi (@mtaibbi) December 10, 2022
66. Lastly, people on the left, right, and in between want to know what else is in the #TwitterFiles, from suppression/shadow-banning of leftists to lab-leak theorists, or amplification of military propaganda or conservative accounts. We know everyone has questions.
— Matt Taibbi (@mtaibbi) December 10, 2022
67. And while we’ve stumbled on tidbits here and there about topics ranging from COVID to foreign policy, the reality is the data sets are enormous and we’re still working through them.
More is coming. Good night, all.
— Matt Taibbi (@mtaibbi) December 10, 2022