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.7 yesterday, and after about 90 miles of testing today, it is evident there are some definite fixes from version 14.3.6, which I wrote about last week and called a regression.
Within the first 40 minutes of my drive on v14.3.7, it saved me from getting into an accident with an unaware Dodge Charger driver, and some of the things Tesla seemed to miss in v14.3.6 were definitely improved. All in all, the release so far has some really great performance, and I’m looking forward to testing it further.
For now, here’s everything I noticed with v14.3.7:
Overall Improvement
Just generally speaking from a ride perspective, this was a really great experience. A lot of the hesitancy I experienced on v14.3.6 was gone. There were no instances of brake-stabbing, wheel-jerking, or any uncertain or unconfident movements. It was void of anything that I felt made it timid with v14.3.6.
The one thing I do hope to see down the road is a smaller need to adjust Speed Profiles so often. Because Tesla calls FSD “Supervised,” I’m okay with needing to hit the scroll wheel a few times a drive.
However, I hope that things can be incrementally improved upon with speed. Sometimes it’s too fast; other times it’s too slow. It’s a difficult thing to hone in and refine, but I hope it eventually gets there.
I didn’t notice any significant left lane camping or any behaviors that were completely out of line. I am hopeful that this opinion does not change, but after driving a few days with this version and putting it in a variety of different situations, you are exposed to more behaviors, some of which are not necessarily what I’d prefer.
-
The big things to notice, at least in my experience thus far, are that the major issues with previous versions — meaning the braking stabbing and wheel jerking — simply weren’t there. That’s enough to already consider this progress compared to .6.
Manual Signal Override is More Responsive
On .6, I had quite a few issues with FSD ignoring my manually input turn signals. If Tesla wants to call it “Supervised,” then the car should not ignore any input the driver gives. If I touch the accelerator on FSD, the car speeds up.
🚨 Tesla FSD v14.3.7 obeying manual turn signals https://t.co/6eqToXpQfC pic.twitter.com/vHBlFQ4PDV
— TESLARATI (@Teslarati) August 2, 2026
The car did a great job of obeying my turn signals when I wanted it to change lanes, which is welcome.
Parking Lot Performance
Before .6, I traditionally took over in nearly every parking lot my car entered, because I knew it would not park somewhere that I wanted, and usually, it was just a tad too timid in this setting.
The one bright spot of .6 was how well it handled parking lots. This continued with v14.3.7:
-
I’m always really happy to see progress at all, but once parking preferences come to FSD, as long as this performance is still around, that could potentially be the biggest improvement I’ve seen in FSD in the year I’ve been using it personally on a daily basis.
Full Self-Driving Averts Disaster
A Dodge Charger changed into my lane without checking if I was there, running me off the road. FSD made the initial avoidance maneuver; I grabbed the wheel out of instinct, looked in my side mirror to ensure I had nobody following closely behind, hit the brake, and straightened the car back up to avoid a curb:
🚨 Guys this is why you all NEED to stay vigilant behind the wheel, even on Tesla Full Self-Driving
Human drivers are UNHINGED and have no idea what they’re doing anymore. This was a kid obviously younger than 20 years old with zero awareness.
First drive with v14.3.7 https://t.co/1vTbCMpCn8 pic.twitter.com/lz7KKEF6bj
— TESLARATI (@Teslarati) August 2, 2026
-
There have been quite a few responses to this video stating that I should never have grabbed the wheel. To be honest, I really wish I had not done so, because I do believe FSD would have avoided any sort of collision with anything, including the car or the curb.
However, this was the first time I had ever been this close to being hit while using FSD. My natural reaction was to take over. I think if I had had something like this happen before, my reaction might have been different.
Hitting the brake avoided hitting the curb, while FSD swerved to avoid the car. My concern after the car was clear of my front end was the curb. All in all, I’m really happy with how things turned out, and I think anyone could be a critic of how I handled it. I only had a split second to really make a decision, and thankfully, any damage was avoided.
It is clear FSD managed to avoid the car coming down before I was able to. I truly credit FSD for avoiding the collision.
What Needs to Improve
Better Recognition of Potholes, Uneven Roads, Sharp Changes in Roadway/Bumps
On Friday, my Fianceè and I were in the car, and FSD was driving us. We crossed over a roadway that has a traffic light, and FSD was traveling at 40 MPH on Standard, 5 MPH over the speed limit. Everything was more than reasonable.
However, the road we were crossing at the light has a major bump both as you start and finish crossing it. Without a speed reduction, your car can go airborne. The Tesla did just this on Friday on v14.3.6; it was an uncomfortable bounce that pretty much confirmed I would not ever let FSD go over again unless we were sitting at that intersection when there is a red light.
I even tried scrolling down into Sloth quickly, but I ended up just taking over:
-
This is that big bounce that I mentioned in the quoted post.
It’s just a tad too drastic to take at the speed FSD wants to go over it. You can see me quickly swipe down into Sloth, but I intervened. https://t.co/K20PK9ysBg pic.twitter.com/81Oc82ZJcZ
— TESLARATI (@Teslarati) August 2, 2026
A few people have said it remains related to the vision-based approach and its difficulty comprehending 3D. This is a huge issue because this can cause serious damage at certain speeds.
Navigation
Nothing new here. I still turn off “Online Routing” quite frequently to get the car to take logical routes from time to time.
Auto Wipers
Auto Wipers are just plain bad. I really hope Tesla just uses a rain sensor. I thought they had improved at one point, but I still get dry wipes, Speed 4 on a drizzle, and Speed 2 on a steady rain. In reality, these should be switched.
You can watch our full review of Tesla Full Self-Driving v14.3.7 below:
-
🚨 Tesla Full Self-Driving v14.3.7 saved me from an accident! FULL REVIEW: https://t.co/1vTbCMpCn8 pic.twitter.com/9mHmKVoMVA
— TESLARATI (@Teslarati) August 2, 2026
SpaceX will report second quarter results after the market closes on Tuesday, August 4, marking the first time the company has opened its books to the public since its record IPO in June. Management will host a live audio only webcast at 4:30 p.m. ET, streamed on X, with no dial in option.
The debut carries more weight than a typical first quarter as a public company. Two trading days after the release, on August 6, the first tranche of SpaceX’s lockup expires, freeing roughly 911.5 million insider and employee shares, worth well over $100 billion at current prices and the largest such release in Wall Street history. A second, larger tranche tied to the stock trading 30 percent above its $135 IPO price never triggered, since shares have spent most of July trading below that price.
Wall Street’s models point to revenue near $6.9 billion for the quarter, up sharply from the $4.69 billion SpaceX reported in the first quarter, with a narrower per share loss than the $1.27 posted three months earlier, according to estimates compiled by Motley Fool. Those numbers will be the first look at how SpaceX’s three segments, Starlink, launch and AI, are performing independently.
SpaceX scores another massive Pentagon deal to support military satellites
Investors heading into the call have a specific list of questions. How many net new Starlink subscribers did SpaceX add after ending March with 10.3 million, and is average revenue per user holding up as the service expands into lower income markets. How much of the AI segment’s revenue reflects contract signings with Anthropic, Google and Reflection AI this year, deals that combined could annualize to nearly $28 billion if fully ramped. Whether capital expenditures, which nearly doubled in the AI segment alone between 2024 and 2025, are still accelerating or starting to plateau. And whether management offers any forward guidance at all, something SpaceX has never done publicly.
The report will also land days after Elon Musk publicly denied a Wall Street Journal report describing internal planning to separate Tesla’s China business ahead of a potential Tesla-SpaceX merger. Whether Musk or SpaceX executives address that speculation on the call, even indirectly, maybe something investors will be listening for on Tuesday.
As Teslarati reported after Musk’s own warning to short sellers last week, the CEO has made clear he expects skeptics to be proven wrong over time. Tuesday will be the first chance for the numbers themselves to make that case.
-
Elon Musk
SpaceX’s Starship just got filmed by its own cargo
SpaceX released new footage of Starship in space captured by the Starlink satellites it deployed.
SpaceX released a new video Friday evening showing Starship from an angle showcased by its own Starlink satellites, watching the rocket drift away in orbit.
The 65 second clip, posted on X, stitches together footage from four cameras mounted on a single Starlink V3 satellite. It opens with a close view of Starship’s 171 foot upper stage, still catching sunlight, then pulls back as the two spacecraft separate.
The footage comes from Starship’s 13th flight test, which launched July 24 from Starbase after a scrubbed attempt and an abort caused by an engine issue the week before. When Flight 13 finally flew, it carried the first batch of functional Starlink V3 satellites Starship has ever deployed, twenty of them, with six equipped with cameras meant to scan the ship’s heat shield during reentry.
View of Starship in space from a Starlink V3 satellite on Flight 13.
This composite is made of imagery from four separate cameras on a single satellite. Six of the satellites were equipped with cameras to scan Starship’s heat shield and transmit imagery down to operators to… pic.twitter.com/sNTHHz5vLr
— SpaceX (@SpaceX) July 31, 2026
Flight 13 checked most of its boxes. Starship deployed all 20 satellites, relit a Raptor engine in space, and splashed down softly in the Indian Ocean off Western Australia. Musk’s longer term plan calls for a Starlink V3 constellation of 100,000 satellites, according to a recent FCC filing, with Starship as the only vehicle capable of launching them at the volume that requires. Each Starship flight is designed to carry up to 60 V3 satellites once the vehicle reaches routine service, well beyond what Falcon 9 can carry in a single mission.
-
Starship is next expected to fly with an attempt at catching the ship itself with the launch tower’s mechanical arms, a maneuver SpaceX has so far reserved for the Super Heavy booster.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
SpaceX’s biggest test yet arrives this week and it’s not a rocket launch
