News
First Twitter Files of 2023 shows how intelligence community gained influence over the platform
The first Twitter Files of 2023 have been released by journalist Matt Taibbi, and they reveal how the intelligence community gained the influence it had over the platform. It begins in August 2017 when Facebook suspended 300 accounts with “suspected Russian origin.”
1.THREAD: The Twitter Files
How Twitter Let the Intelligence Community In— Matt Taibbi (@mtaibbi) January 3, 2023
However, Twitter’s leaders weren’t worried because they were sure there wasn’t a Russia problem. Screenshots of emails from Twitter’s former Vice President, Global Public Policy & Philanthropy, Colin Crowell, and Twitter’s former legal head, Vijaya Gadde, confirm that Twitter had been in contact with Facebook and agreed that the best public relations strategy was to say nothing on record and to issue a statement bringing them “closer to Facebook, their vulnerabilities on this issue, and the follow-up stories on Russia.”
In another email, Crowell noted that Twitter wasn’t the focus of inquiry into Russian election meddling but that the spotlight was on Facebook. The screenshot revealed that a group of Twitter executives were “due to see the Democratic staff of the Senate Intelligence Committee” in a non-public and private meeting.
In the section of the email titled Important Context, Crowell wrote: “Twitter is not the focus of inquiry into Russian election meddling right now – the spotlight is on FB because FB has better targeting ability than we have for campaign-related advertising; and, because the Trump campaign spent massively on FB during the election compared to what they spent w/us.”
Credit: Matt Taibbi
Following that, Twitter suspended 22 possible Russian accounts and 179 others with “possible links” to those accounts out of a larger set of 2,700 suspects that were manually examined. Senator Mark Warner of Virginia, the ranking Democrat on the Intelligence Committee, wasn’t too happy with Twitter. He held a press conference to denounce Twitter’s report as “frankly inadequate on every level.”
Crowell’s response was “#Irony” after he received an email from Warner’s re-election campaign asking for $5. Following that, Crowell met with congressional leaders and told his team at Twitter to keep producing material.
“Warner has political incentive to keep this issue at the top of the news, maintain pressure on us and rest of industry to keep producing material for them.”
Credit: Matt Taibbi
He added that the Democrats were taking cues from Hillary Clinton, who said, “It’s time for Twitter to stop dragging its heels and live up to the fact that its platform is being used as a tool for cyber-warfare.”
Credit: Matt Taibbi
This led Twitter to form a Russia Task Force due to anxiety over its PR problems. The task force began with data shared from counterparts at Facebook; however, Taibbi noted that those searches of accounts tied to Russia’s Internet Research Agency (IRA) were a dud.
One screenshot read: “No evidence of a coordinated approach, all of the accounts found seem to be lone-wolf type activity.”
Another one pointed out that after manually reviewing 2,500 accounts, they thought it was exhaustive. “32 suspicious accounts and only 17 of those are connected with Russia, only 2 of those have significant spend one of which is Russia Today…remaining <$10k in spend.”
Taibbi noted that the search found “only 2” significant accounts based on the same data that later inspired panic headlines such as “Russian Influence Reached 126 million through Facebook alone.”
Twitter’s failure of its Russian task force to produce material made its PR crisis worse. Several stories sourced into the Intel Committee were reported on in the news. This led Twitter to change its thoughts on the smallness of its Russia problem.
Senate staff told Twitter leaders that Senator Warner felt like the tech industry was in denial for months, and Twitter “pledged to work with them on their desire to legislate.”
Following that, Twitter’s Policy Director, Carlos Monje, shared key highlights of the legislation that Senators Warner, Klobuchar, and McCain were introducing.
“Knowing that our ads policy and product changes are an effort to anticipate congressional oversight, I wanted to share some relevant highlights of the legislation Senators Warner, Klobuchar and McCain will be introducing,”
Credit: Matt Taibbi
As Twitter began preparing its ads policy and removing RT and Sputnik to placate Washington, the committees leaked the larger list of 2,700 accounts. This led to a media circus, with Twitter being the star of the show. Internally, Twitter didn’t want to endorse the findings by Buzzfeed and the University of Sheffield, which said they found a new network on Twitter with close connections to Russian-linked bot accounts.
Credit: Matt Taibbi
Credit: Matt Taibbi
The Senate asked Twitter for a write-up of what happened when the Buzzfeed piece came out. Twitter then apologized for the same accounts it initially told the Senate was not a problem. This led to a new revelation. “Reporters now know this is a model that works.”
Taibbi noted that this cycle would later be formalized in partnerships with federal law enforcement. And this is how the intelligence community gained its influence over Twitter. In public, Twitter would remove content “at our sole discretion.”
Privately, the platform would “off-board” anything that was “identified by the U.S. intelligence community as state-sponsored entity conducting cyber-operations.”
If you would like to access all of the Twitter files, an archival website has been built, which includes all of the threads as organized, long-form blog posts and links to articles written by the independent journalists who have released the Twitter Files.
Your feedback is welcome. If you have any comments or concerns or see a typo, you can email me at johnna@teslarati.com. You can also reach me on Twitter at @JohnnaCrider1.
Teslarati is now on TikTok. Follow us for interactive news & more. Teslarati is now on TikTok. Follow us for interactive news & more. You can also follow Teslarati on LinkedIn, Twitter, Instagram, and Facebook.
Tesla CEO Elon Musk teased the insane capabilities of the next major Full Self-Driving update just hours after the company rolled out version 14.2 to owners.
Tesla Full Self-Driving v14.2 had some major improvements from the previous iteration of v14.1.x. We were on v14.1.7, the most advanced configuration of the v14.1 family, before Tesla transitioned us and others to v14.2.
However, Musk has said that the improvements coming in the next major update, which will be v14.3, will be where “the last big piece of the puzzle finally lands.”
14.3 is where the last big piece of the puzzle finally lands
— Elon Musk (@elonmusk) November 21, 2025
There were some major improvements with v14.2, most notably, Tesla seemed to narrow in on the triggers that caused issues with hesitation and brake stabbing in v14.1.x.
One of the most discussed issues with the past rollout was that of brake stabbing, where the vehicle would contemplate proceeding with a route as traffic was coming from other directions.
We experienced it most frequently at intersections, especially four-way stop signs.
Elon Musk hints at when Tesla can fix this FSD complaint with v14
In our review of it yesterday, it was evident that this issue had been resolved, at least to the extent that we had no issues with it in a 62-minute drive, which you can watch here.
Some owners also reported a more relaxed driver monitoring system, which is something Tesla said it was working on as it hopes to allow drivers to text during operation in the coming months. We did not test this, as laws in Pennsylvania prohibit the use of phones at any time due to the new Paul Miller’s Law, which took effect earlier this year.
However, the improvements indicate that Tesla is certainly headed toward a much more sentient FSD experience, so much so that Musk’s language seems to be more indicative of a more relaxed experience in terms of overall supervision from the driver, especially with v14.3.
Musk did not release or discuss a definitive timeline for the release of v14.3, especially as v14.2 just rolled out to Early Access Program (EAP) members yesterday. However, v14.1 rolled out to Tesla owners just a few weeks ago in late 2025. There is the potential that v14.3 could be part of the coming Holiday Update, or potentially in a release of its own before the New Year.
Tesla rolled out Full Self-Driving version 14.2 yesterday to members of the Early Access Program (EAP). Expectations were high, and Tesla surely delivered.
With the rollout of Tesla FSD v14.2, there were major benchmarks for improvement from the v14.1 suite, which spanned across seven improvements. Our final experience with v14.1 was with v14.1.7, and to be honest, things were good, but it felt like there were a handful of regressions from previous iterations.
While there were improvements in brake stabbing and hesitation, we did experience a few small interventions related to navigation and just overall performance. It was nothing major; there were no critical takeovers that required any major publicity, as they were more or less subjective things that I was not particularly comfortable with. Other drivers might have been more relaxed.
With v14.2 hitting our cars yesterday, there were a handful of things we truly noticed in terms of improvement, most notably the lack of brake stabbing and hesitation, a major complaint with v14.1.x.
However, in a 62-minute drive that was fully recorded, there were a lot of positives, and only one true complaint, which was something we haven’t had issues with in the past.
The Good
Lack of Brake Stabbing and Hesitation
Perhaps the most notable and publicized issue with v14.1.x was the presence of brake stabbing and hesitation. Arriving at intersections was particularly nerve-racking on the previous version simply because of this. At four-way stops, the car would not be assertive enough to take its turn, especially when other vehicles at the same intersection would inch forward or start to move.
This was a major problem.
However, there were no instances of this yesterday on our lengthy drive. It was much more assertive when arriving at these types of scenarios, but was also more patient when FSD knew it was not the car’s turn to proceed.
Can report on v14.2 today there were ZERO instances of break stabbing or hesitation at intersections today
It was a significant improvement from v14.1.x
— TESLARATI (@Teslarati) November 21, 2025
This improvement was the most noticeable throughout the drive, along with fixes in overall smoothness.
Speed Profiles Seem to Be More Reasonable
There were a handful of FSD v14 users who felt as if the loss of a Max Speed setting was a negative. However, these complaints will, in our opinion, begin to subside, especially as things have seemed to be refined quite nicely with v14.2.
Freeway driving is where this is especially noticeable. If it’s traveling too slow, just switch to a faster profile. If it’s too fast, switch to a slower profile. However, the speeds seem to be much more defined with each Speed Profile, which is something that I really find to be a huge advantage. Previously, you could tell the difference in speeds, but not in driving styles. At times, Standard felt a lot like Hurry. Now, you can clearly tell the difference between the two.
It seems as if Tesla made a goal that drivers should be able to tell which Speed Profile is active if it was not shown on the screen. With v14.1.x, this was not necessarily something that could be done. With v14.2, if someone tested me on which Speed Profile was being used, I’m fairly certain I could pick each one.
Better Overall Operation
I felt, at times, especially with v14.1.7, there were some jerky movements. Nothing that was super alarming, but there were times when things just felt a little more finicky than others.
v14.2 feels much smoother overall, with really great decision-making, lane changes that feel second nature, and a great speed of travel. It was a very comfortable ride.
The Bad
Parking
It feels as if there was a slight regression in parking quality, as both times v14.2 pulled into parking spots, I would have felt compelled to adjust manually if I were staying at my destinations. For the sake of testing, at my first destination, I arrived, allowed the car to park, and then left. At the tail-end of testing, I walked inside the store that FSD v14.2 drove me to, so I had to adjust the parking manually.
This was pretty disappointing. Apart from parking at Superchargers, which is always flawless, parking performance is something that needs some attention. The release notes for v14.2. state that parking spot selection and parking quality will improve with future versions.
Any issues with parking on your end? 14.1.7 didn’t have this trouble with parking pic.twitter.com/JPLRO2obUj
— TESLARATI (@Teslarati) November 21, 2025
However, this was truly my only complaint about v14.2.
You can check out our full 62-minute ride-along below:
Elon Musk
SpaceX issues statement on Starship V3 Booster 18 anomaly
The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX has issued an initial statement about Starship Booster 18’s anomaly early Friday. The incident unfolded during gas-system pressure testing at the company’s Massey facility in Starbase, Texas.
SpaceX’s initial comment
As per SpaceX in a post on its official account on social media platform X, Booster 18 was undergoing gas system pressure tests when the anomaly happened. Despite the nature of the incident, the company emphasized that no propellant was loaded, no engines were installed, and personnel were kept at a safe distance from the booster, resulting in zero injuries.
“Booster 18 suffered an anomaly during gas system pressure testing that we were conducting in advance of structural proof testing. No propellant was on the vehicle, and engines were not yet installed. The teams need time to investigate before we are confident of the cause. No one was injured as we maintain a safe distance for personnel during this type of testing. The site remains clear and we are working plans to safely reenter the site,” SpaceX wrote in its post on X.
Incident and aftermath
Livestream footage from LabPadre showed Booster 18’s lower half crumpling around the liquid oxygen tank area at approximately 4:04 a.m. CT. Subsequent images posted by on-site observers revealed extensive deformation across the booster’s lower structure. Needless to say, spaceflight observers have noted that Booster 18 would likely be a complete loss due to its anomaly.
Booster 18 had rolled out only a day earlier and was one of the first vehicles in the Starship V3 program. The V3 series incorporates structural reinforcements and reliability upgrades intended to prepare Starship for rapid-reuse testing and eventual tower-catch operations. Elon Musk has been optimistic about Starship V3, previously noting on X that the spacecraft might be able to complete initial missions to Mars.
Tesla CEO Elon Musk teases insane capabilities of next major FSD update
Tesla Full Self-Driving v14.2 – Full Review, the Good and the Bad
