Connect with us
Twitter and the FBI Belly Button revealed in new Twitter Files Twitter and the FBI Belly Button revealed in new Twitter Files

News

Twitter Files reveal FBI’s role as “belly button”

Credit: Matt Taibbi

Published

on

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.

Advertisement

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.”

Advertisement

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.”

Advertisement

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.”

Advertisement

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.

Advertisement

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 LinkedInTwitter, Instagram, and Facebook.

Johnna Crider is a Baton Rouge writer covering Tesla, Elon Musk, EVs, and clean energy & supports Tesla's mission. Johnna also interviewed Elon Musk and you can listen here

Advertisement
Comments

News

Tesla Cybercab stands to gain from new Trump autonomy rules

Published

on

Credit: Teslarati

Tesla Cybercab stands to gain from new rules that the Trump Administration is aiming to enforce on autonomous vehicles. On Thursday, NHTSA, under the Trump Administration’s U.S. Department of Transportation, commenced rulemaking on the Federal Motor Vehicle Safety Standards (FMVSS).

This effort aims to eliminate the mandate for manual brake pedals in vehicles that are designed to be driven exclusively by automated driving systems. This would impact the Tesla Cybercab, which the company has stated would operate without a steering wheel or pedals.

Tesla Cybercab launch is imminent after latest sighting at Giga Texas

The Trump Administration is looking to revise FMVSS No. 135, which requires standard braking systems on light-duty vehicles.

Advertisement

Currently, the regulation requires light-duty cars to use traditional manual braking systems that allow operators to slow the vehicle. With the advent of self-driving in the U.S., these regulations need updating, and these are the changes that could come to FMVSS No. 135:

  • Removes requirements for hand- or foot-operated brake controls for vehicles designed never to be operated by a human. Existing rules still apply to AVs that retain manual controls.
  • All subject vehicles must still meet the same stopping distance performance criteria via alternative testing procedures.
  • While this update ensures AVs can physically stop when commanded, NHTSA is separately developing safety performance requirements for AVs in real-world driving scenarios.
  • NHTSA will continue to use its broad defect enforcement authority to investigate unsafe ADS behavior and oversee recalls.

As autonomy becomes a greater part of passenger travel, these types of rule adjustments will be more than reasonable. It will give manufacturers the ability to self-certify their vehicles and avoid any red tape that could ultimately delay the deployment of these vehicles.

Administrators are also incredibly excited about the opportunity to play a role in the advancement of self-driving vehicles.

“We are at the cusp of the greatest technological revolution in vehicle technology since the innovation of the Model T,” NHTSA Administrator Jonathan Morrison said. “If we want America to lead the way, we have to reimagine our regulatory framework. That’s why under Secretary Sean Duffy’s AV Framework, NHTSA is tearing down pointless barriers to innovative designs while strengthening the fundamental safety requirements that matter and holding AV developers accountable for safe performance.”

The Cybercab entered mass production at Gigafactory Texas in April. Tesla ultimately plans to push the vehicle into its Robotaxi fleet, potentially when frameworks like these are established.

Advertisement
Continue Reading

News

Tesla plans production boost at Giga Berlin following rebound in Europe

Published

on

Credit: Andre Thierig | X

Tesla plans to boost production at its Gigafactory Berlin plant in Germany following a sharp rebound in sales and demand in Europe after a softer 2025.

The plans put Tesla in a better position to compete with strengthening companies in Europe and potentially other markets; demand indicators show Tesla is much better off than in 2025.

Last year was a tough year for Tesla in terms of overall demand in Europe. The company produced over 200,000 vehicles at the German plant last year, a soft figure compared to the 375,000 vehicles Tesla lists as its current capacity at the factory.

Tesla’s overall European sales dropped significantly last year due to a variety of factors. However, sales are rebounding, and demand is strong once again, and only getting stronger. Tesla is now planning to bump production of Model Y vehicles at Giga Berlin upward by about 20 percent. It will also bring 1,000 new jobs to the plant.

Tesla confirmed the details of its planned production expansion in Germany this morning. It is a strategy to keep up with strengthening demand.

Advertisement

In Q1, Tesla saw a record 61,000 vehicles produced at Giga Berlin. European registrations rebounded sharply, with Model Y seeing 117 percent increases in March 2026 compared to last year. Germany alone saw stark increases, with a quadrupling in registrations to 9,252 units.

This trend continued in other key European markets, including France, Denmark and Sweden. Tesla registrations were up over 46 percent in some of these markets, and Model Y continued its trend as a top BEV in the market.

Demand has been recovering strongly in 2026, giving Tesla a reason to expand production efforts at the factory. These increases signal management’s confidence in sustained or growing European pull for Berlin-built vehicles.

Advertisement
Continue Reading

News

Tesla and driver sued by family of woman killed in Texas crash: what we know

Published

on

Credit: CNBC

Tesla is being sued by the family of the woman who was killed in a Texas crash involving a Model 3. The driver, who is also being sued, claimed the vehicle was operating on Autopilot mode, but Tesla executives have come out challenging that claim, stating that the driver of the vehicle overrode the system.

The lawsuit was filed by 76-year-old Martha Avila’s daughter and her husband, who allege a “design defect” involving a Tesla and a failure to warn. The suit alleges negligence against Tesla and the driver, Michael Butler.

Butler “stated he was operating with an automated driving assistance system engaged at the time of the crash,” the Harris County Sheriff’s Office said in a statement. He showed no signs of intoxication and was cooperative, the Sheriff’s Office said, according to NBC News.

Just after reports of the crash and numerous headlines that immediately blamed Tesla’s Autopilot suite, both Tesla CEO Elon Musk and Head of AI Ashok Elluswamy challenged that. Musk said the crash made “no sense” given that Tesla Autopilot and Full Self-Driving do not travel at the speeds the door cameras captured the car traveling at, which Tesla says was 73 MPH.

Advertisement

Tesla finally clarifies fatal Texas crash, confirms driver manually overrode acceleration

Elluswamy also revealed that Tesla data showed Butler overrode the system by pressing the accelerator to 100%, and that the pedal was compressed fully even after the car had crashed. Tesla has not released this data to the public, likely because it is communicating with agencies like the NHTSA on an investigation.

The suit uses a Washington Post analysis of government data that “identified at least 17 fatal incidents linked to Tesla Autopilot.”

This is far from the first time an accident has been blamed on Autopilot. A fatal crash in Texas was blamed on Autopilot several years ago, but when Tesla released data to the NTSB, which was investigating the crash, Autopilot was not available where the crash occurred, and Autosteer was never enabled, meaning the car was manually controlled at the time of the accident.

Advertisement

More information on the accident will be released as Tesla works with agencies to find the cause of the crash. From personal experience, it is hard to imagine Tesla Autopilot or FSD operating in this manner. It drives sometimes too cautiously in residential areas in parking lots, at least in my experience. Speeding happens, but at this rate in this type of area, it is hard to believe.

We look forward to more details being released with time.

Advertisement
Continue Reading