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.
-
Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
-
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
-
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
-✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
