The latest installment of the Twitter Files revealed the FBI’s desire for Twitter to rely on it to be the belly button of the U.S. government (USG). The first Twitter Files installment of 2023 revealed shared the events that led up to the intelligence community’s influence on Twitter. Following that installment, journalist Matt Taibbi released another, which revealed the Global Engagement Center’s (GEC) role.
Taibbi described the GEC as “a fledgling analytic/intelligence arms of the State Department,” and screenshots revealed how this new entity would go directly to the media. In one such instance, a report titled, Russian Disinformation Apparatus Taking Advantage of Coronavirus Concerns, was released, which wrecked a bit of havoc for Twitter.
1.THREAD: The Twitter Files
Twitter and the FBI “Belly Button” pic.twitter.com/nfOGQGlvUM— Matt Taibbi (@mtaibbi) January 3, 2023
Twitter’s then Trust and Safety head, Yoel Roth, pointed out the motives of Clemson’s Media Forensic Hub when it complained that Twitter hadn’t “made a Russia attribution” in some time.

Credit: Matt Taibbi

Credit: Matt Taibbi
Roth told researchers like Clemson that Twitter would be happy to work directly with them instead of the media. He was unsuccessful. Simultaneously, Twitter was trying to reduce the number of agencies that had access to Roth. Twitter’s then-policy director, Carlos Monje, pointed out that once Twitter gave these agencies, such as the Department of Homeland Security, access to Roth.
“If these folks are like House Homeland Committee and DHS, once we give them direct contact with Yoel, they will want to come back to him again and again,” Monje said.
Taibbi noted that the GEC report appeared to be based on DHS data that was circulated earlier that week. The data included accounts that followed two or more Chinese diplomatic accounts and ended up with a list “nearly 250,000” names long. The list included Canadian officials and a CNN account.

Credit: Matt Taibbi
In an email, Roth said that the GEC attempted to insert itself into conversations Twitter had with several government agencies, including the FBI and DHS. The GEC began to agree to loop Twitter in before going public; however, the agency used a technique that trapped Twitter previously.
“The delta between when they share material and when they go to the press continues to be problematic,” a comms official wrote, adding that they primed the media to be “curios and inquisitive of this dynamic, too.”

Credit: Matt Taibbi
This led to Twitter’s disputing a State Department claim that China coordinated coronavirus disinformation accounts. The FBI then informed Twitter that the GEC wanted to be included in their regular “industry call” between companies like Twitter and Facebook and the DHS and FBI. At first, Twitter didn’t want to go this route. Executives at Facebook and Google were united with Twitter in its opposition to the GEC’s inclusion.
“The GEC’s mandate for offensive IO to promote American interests. The relative lack of discretion and caution from senior GEC leadership in sharing reports/analysis based on shaky methodology. A limited track record of successful collaboration with industry.”
Roth noted that an actor such as GEC being introduced to a stable and trusted group of practitioners and experts, especially with the election heating up, posed major risks.

Credit: Matt Taibbi
Roth added that another reason was that the DHS and FBI were “apolitical,” whereas the GEC was “political.”
“GEC has a track record of actively advancing specific ideological agendas (e.g., their work w/r/t Iran). We should not lose sight of this distinction,” Roth wrote.

Credit: Matt Taibbi
The FBI argued for a compromise solution that would allow other U.S. government (USG) agencies to participate in the industry calls, with the FBI and DHS acting as sole conduits. When Roth reached out to FBI agent Elvis Chan with concerns, Chan reassured the Twitter executive that it would be a “one-way” channel and “State/GEC, NSA, and CIA have expressed interest in being allowed on in listen mode only.”
“We can give you everything we’re seeing from the FBI and USIC agencies,” Chan told Roth, adding that the DHS agency Cybersecurity and Infrastructure Security Agency (CISA) “will know what’s going on in each state.” Chan then asked if the industry could “rely on the FBI to be the belly button of the USG.”

Credit: Matt Taibbi
The group eventually chose Signal due to its operational security. Following that, Twitter began taking requests from various government bodies starting with the Senate Intel Committee (SSCI), which needed reassurance that Twitter was taking FBI direction.
Twitter also received various requests from officials wanting individuals they didn’t like to be banned from the platform. In the screenshot below, the office for Democrat and House Intel Committee chief Adam Schiff asked Twitter to ban journalist Paul Sperry.

Credit: Matt Taibbi
At the time, Twitter refused. However, Sperry was later suspended. “No, this isn’t feasible/we don’t do this,” Twitter replied.
Twitter honored many of the requests, including those from the GEC, to ban accounts the GEC identified as “GRU-controlled” and linked “to the Russian government.”
A former CIA staffer working at Twitter called the GEC requests “Our window on that is closing,” which meant that the days Twitter could say no to serious requests were over. In the Twitter Files that were released earlier today, Taibbi noted that in public, Twitter would remove content at its “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.” That was in 2017. By 2020, agencies were flooding Twitter with “identifications” or users that it wanted Twitter to remove.

Credit: Matt Taibbi
Taibbi pointed out that some reports were only a paragraph long and that Twitter would be forwarded an Excel document without further explanation. Twitter was also warned about the publicity surrounding a book written by former Ukraine prosecutor Viktor Shokhin, who alleged “corruption by the U.S. government” – specifically by Joe Biden.
Screenshots reveal that by mere weeks before the 2020 election, Twitter was so confused by the multiple streams of incoming requests that staffers had to ask the FBI which was which.

Credit: Matt Taibbi
Taibbi noted that this led to the situation described in an earlier Twitter Files release by Michael Shellenberger on December 19, 2022.
In that release, it was revealed that Twitter was paid $3,415,323. Taibbi noted that Twitter wasn’t just paid but underpaid for the amount of work it did for the government.
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.
Elon Musk
Elon Musk reveals unfortunate truth of Tesla Full Self-Driving development
In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.
Tesla’s Full Self-Driving suite is one of the most significant technological developments in terms of passenger travel in decades, but it is not all sunshine and rainbows, even with major strides in safety, CEO Elon Musk revealed.
In a candid reply to a dramatic video of Tesla’s Full Self-Driving (FSD) system averting disaster, Elon Musk laid bare a harsh reality facing autonomous vehicle technology.
The clip shows a Model 3 traveling at over 65 mph on a foggy, rain-soaked highway when a pedestrian suddenly steps into traffic.
Full Self-Driving instantly detects the threat and swerves safely, preventing what could have been a fatal collision for both the pedestrian and the driver’s cousin.
Musk’s response was unequivocal:
“Tesla self-driving saves a lot of lives – the statistics are unequivocal. That doesn’t mean it’s perfect, of course.” Even with a projected 10x safety improvement over human drivers, FSD would still prevent roughly 90% of the world’s approximately one million annual auto fatalities. The remaining 10%—roughly 100,000 deaths—would expose Tesla to relentless lawsuits. Meanwhile, the vast majority of lives saved would go unnoticed. “The 90% who are still alive mostly won’t even know that Tesla saved them. Nonetheless, it is the right thing to do.”
This “unfortunate truth,” as Musk implicitly framed it, highlights a fundamental asymmetry in how society perceives safety technology. Human drivers cause the overwhelming majority of crashes through distraction, fatigue, or error.
Tesla self-driving saves a lot of lives – the statistics are unequivocal.
That doesn’t mean it’s perfect, of course.
Even when we improve safety 10X, saving 90% of the million lives lost in auto accidents every year, Tesla will still get sued for the 10% who did die. The 90%… https://t.co/OrNB1mO5eF
— Elon Musk (@elonmusk) April 6, 2026
Yet when FSD errs, the incident becomes headline news and a courtroom target. Prevented tragedies, by contrast, leave no trace.
Survivors simply continue their journeys, unaware of the split-second intervention that kept them alive. The result is a distorted public narrative that amplifies failures while rendering successes invisible.
We have seen this through various headlines throughout the years, including the mainstream media’s obsession with only mentioning the manufacturer’s name in the instance of an accident when it is “Tesla.”
Opinion: Tesla Autopilot NHTSA investigation headlines are out of control
The video’s real-world example underscores FSD’s current capabilities. In near-zero visibility, the system’s cameras and neural network reacted faster than any human could, demonstrating the life-saving potential Musk cites.
Tesla’s latest safety data already shows FSD (Supervised) performing significantly better than the U.S. average, with crashes occurring far less frequently per mile driven.
Still, regulatory scrutiny, liability concerns, and media focus on edge-case failures continue to slow widespread adoption. Musk’s frank admission suggests Tesla is prepared to push forward despite the legal and perceptual headwinds.
As FSD edges closer to unsupervised autonomy, Musk’s post serves as both a progress report and a reality check. The technology is already saving lives today.
The unfortunate truth is that proving it and scaling it responsibly will require society to value statistical lives saved as much as dramatic stories of those lost. In the race toward safer roads, perception may prove as formidable an obstacle as the fog and rain in that viral video.
News
Tesla Full Self-Driving v14.3: First Impressions
Tesla started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members earlier today, and I had the opportunity to see some of the improvements that were made from v14.2.2.5.
While a lot of things got better, and I truly enjoyed using Full Self-Driving again after being stuck with the widely confusing and frustrating v14.2.2.5, Tesla still has one major problem on its hands, and it has to do with Navigation and Routing. I truly believe those issues will be the biggest challenges Tesla will face with autonomy: the car simply going the correct way, not conflicting with what the navigation says, and taking the simplest and most ideal route to a destination.
Here’s what I noticed as an improvement with my first hour with v14.3. This is not a full review, nor is it reflective of everything I will likely experience with this new version. This is simply what I saw as a noticeable improvement from the past version, v14.2.2.5.
There is also a more streamlined version on X, available at the thread below:
Tesla Full Self-Driving v14.3 testing now: pic.twitter.com/9UuP11Fv9f
— TESLARATI (@Teslarati) April 7, 2026
Yellow Light Behavior is Significantly Better
On v14.2.2.5, I had so many instances of the car slamming the brakes on to stop at a yellow light when it was clearly the safer option to proceed through. There were several times when the car would be about 20 feet from the line, traveling at 15-20 MPH, the light would turn yellow, and it would slam the brakes to stop. I would nudge it through yellow lights constantly because of this by putting my foot on the accelerator.
The instances I’m talking about here would not have been close calls — the car would have likely moved through the intersection completely before the light would turn red.
On multiple occasions this evening, FSD proceeded through yellow lights safely, without hesitation or any brake stabbing. It was refreshing:
🚨 Here’s an EXCELLENT example:
v14.2.2.5 would have slammed the brakes and stopped at this stop sign. I would have tapped the accelerator to proceed.
You can see the light turns yellow and the car makes — in my opinion — the correct decision to proceed. https://t.co/hHMikimkbp pic.twitter.com/Iesta1OYoV
— TESLARATI (@Teslarati) April 7, 2026
This was a huge complaint with v14.2.2.5. Sometimes, it’s a safer option to go through a yellow light, especially when you have traffic behind you. It’s a great way to get rear-ended.
Parking Performance
I had four instances of parking, and FSD v14.3 really did a flawless job. I was very impressed with how solid it was, but also with how efficiently it moved into the spot. When there was traffic around with past versions, I usually chose to park manually just because FSD took its time getting into a spot. I don’t see that being an issue anymore.
I complained about parking a lot and shared several images on X and Facebook of those examples:
Still a few issues with parking on FSD v14.2.2.4 pic.twitter.com/BphvVWDPqe
— TESLARATI (@Teslarati) February 5, 2026
No issues with it this evening. 4/4. Here are two looks:
Highway Performance
FSD v14.3 passed the five cars shown in this image:
The sixth was 200-300 yards ahead of the fifth. In v14.2.2.5, FSD would usually stay in the left lane, especially on Hurry and Mad Max. It did not do that, as it instead chose to get back over in the right lane after passing the final car.
Speed was not much of a concern here, even though it was going 21 MPH over. Although it was fast, I did have a line of cars behind me traveling at the same speed, and FSD had just merged about a half mile prior, so I chose to let it continue.
There were no instances of camping in the left lane for extended periods of time. I do want to do more testing with the Speed Profiles because they were in need of some work with the previous version. I am starting to side with those who want a Max Speed setting, which was removed last year.
Navigation and Routing Still Need Work
I was heading back toward where I came from, so I turned “Avoid Highways” on to take a different way. This confused the Routing system, and instead of turning left, then right, as the Routing said, the car turned right, then indicated for another right, basically going in a big rectangle. The car ignored the second right-hand turn and continued straight. I ended up turning “Avoid Highways” off and letting the car pick the same routing option as what took me here.
I have truly complained so much about Navigation and Routing that I’m starting to feel sort of bad. It is obviously such a massive challenge for some reason, but I am confident it will improve. I recall seeing Tesla hiring someone for this role a few months back, so perhaps there is hope for it to get better.
Smarter Behavior When Approaching Exits/Routing
This probably should be grouped in with Highway Behavior, but I wanted to highlight it on its own.
The highway exit pictured was always frustrating for v14.2.2.5. In the Hurry speed profile, I have seen it try to execute passes on multiple cars with as little as 0.6 miles to spare before taking the exit.
With three cars ahead of it, it chose to reduce speed and just wait until the exit. It was refreshing to see an improvement here, so I hope this behavior persists. Sometimes there’s just no reason to pass when you’re less than a mile from getting off the highway anyway.
Larger Visibility Warnings
Tesla seems to have increased the size of these “Camera Visibility Limited” warnings. Previously, they were just small thumbnails:
🚨 The warnings of “Camera Visibility Limited” appear to be larger with v14.3
Previously, it was a small thumbnail. Haven’t seen it this magnified before. https://t.co/iKJLsZ8P4Q pic.twitter.com/qRWwFyIZNd
— TESLARATI (@Teslarati) April 7, 2026
Stop Sign Behavior
This is probably the biggest improvement of all, because how it behaved at Stop Signs in v14.2.2.5 was so incredibly terrible and disruptive to the flow of a busy intersection.
There are several four-way, all-stop intersections near me. In the past, FSD would stop well behind the Stop Sign or the white-painted line on the road. It would then inch forward, stopping again at this line, essentially making two stops at a single intersection.
If there is visibility, I don’t truly care where FSD stops, as long as it stops once. Stopping twice just isn’t ideal or logical. I can’t imagine many humans would do it, I know I wouldn’t.
I didn’t have that issue this evening:
🚨 Here’s a look with some commentary – Previously, FSD would stop where it did in this video, then again at the white line, before proceeding. https://t.co/xwyVGMy28y pic.twitter.com/MObgUa7DoA
— TESLARATI (@Teslarati) April 7, 2026
This was pretty tight, too, in the sense that both my car and the other one got to the intersection at the same time. FSD may have stopped first, but the other vehicle was probably around the same point that I was when FSD decided to stop. I was happy to see the assertiveness to proceed; it felt like it was ideal to just go through. I was happy it didn’t stop a second time up at the line. I’d be fine if it stopped at the line, as long as that was the only stop it made.
News
Tesla Full Self-Driving v14.3 rolls out: here’s what’s new
We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.
Tesla has officially started rolling out Full Self-Driving v14.3 to Early Access Program (EAP) members, and there are a lot of new improvements.
We are in EAP and will be on the road with v14.3 in the coming hours, so we’ll have a lot of things to discuss over the next few days, especially coming from v14.2.2.5, which I called the most “confusing” FSD release of all time.
🚨 Tesla Full Self-Driving v14.3 is here and it is coming with so many new features
Looks like there will be some MAJOR improvements to the general performance.
Truly seems like it will be significantly different than v14.2 pic.twitter.com/mhdfBLuDup
— TESLARATI (@Teslarati) April 7, 2026
Tesla brought out a lot of improvements, according to the v14.3 release notes, which list a vast number of fixes, new features, and new capabilities.
Here’s what Tesla’s release notes for the v14.3 release state:
- Improved parking location pin prediction, now shown on a map with a P icon.
- Increased decisiveness of parking spot selection and maneuvering.
- Rewrote the Al compiler and runtime from the ground up with MLIR, resulting in 20% faster reaction time and improving model iteration speed.
- Enhanced response to emergency vehicles, school buses, right-of-way violators, and other rare vehicles.
- Mitigated unnecessary lane biasing and minor tailgating behaviors.
- Improved handling of small animals by focusing RL training on harder examples and adding rewards for better proactive safety.
- Improved traffic light handling at complex intersections with compound lights, curved roads, and yellow light stopping – driven by training on hard RL examples sourced from the Tesla fleet.
- Upgraded the Reinforcement Learning (RL) stage of training the FSD neural network, resulting in improvements in a wide variety of driving scenarios.
- Upgraded the neural network vision encoder, improving understanding in rare and low-visibility scenarios, strengthening 3D geometry understanding, and expanding traffic sign understanding.
- Improved handling for rare and unusual objects extending, hanging, or leaning into the vehicle path by sourcing infrequent events from the fleet.
- Improved handling of temporary system degradations by maintaining control and automatically recovering without driver intervention, reducing unnecessary disengagements.
Tesla also listed a handful of future improvements as well:
- Expand reasoning to all behaviors beyond destination handling
- Add pothole avoidance
- Improve driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting situations
CEO Elon Musk has said that v14.3 could be “where the last big piece of the puzzle finally lands.” We have high expectations for this release because, in a lot of ways, v14.2’s final version was extremely disappointing and seemed to be a regression more than anything.
Nevertheless, Full Self-Driving v14.3 is going to be quite an interesting test, considering this is also the first time Musk has stated it will feel like the car will be “sentient.”
Reasoning will be a bigger piece of the puzzle with this release, although there were some elements of it in v14.2.
Tesla AI Head says future FSD feature has already partially shipped
We plan to travel plenty of miles with it over the next few days, so we’ll keep you posted on what our thoughts are.

