Connect with us
Elon Musk's Twitter Files reveals executives' abuse of power, trust & safety Elon Musk's Twitter Files reveals executives' abuse of power, trust & safety

News

First Twitter Files of 2023 shows how intelligence community gained influence over the platform

Credit: Photo Credit: @PainefulTruths2

Published

on

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

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

Advertisement

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

Advertisement

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

Advertisement

 

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

Advertisement

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

Advertisement

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.

Advertisement

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

 

Advertisement

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 urges New Jersey owners to oppose new bill that could block Robotaxi

Published

on

Credit: Grok

Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.

The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.

According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.

Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.

The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.

Advertisement

In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.

Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.

In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.

Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.

Advertisement

Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.

This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.

As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.

Advertisement
Continue Reading

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

Turn-by-turn navigation is not new technology.

For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.

Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

Advertisement

Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.

Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.

Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.

But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.

Advertisement

This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.

More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.

It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?

Multiple Data Sources

First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.

Advertisement

Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.

Persistent Learning

FSD seems to struggle with persistent learning from driver interventions.

Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.

This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.

Advertisement

I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.

Reasoning, Scaling, and Intuition

Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.

Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.

Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.

Advertisement

Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.

Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.

Continue Reading

Cybertruck

Tesla Cybertruck driver gets pickup seized for ‘legitimate concerns’ in UK

Published

on

A Tesla Cybertruck driver in the United Kingdom had their all-electric pickup seized by local police in the Greater Manchester area after the department cited “legitimate concerns.”

Last Thursday, police saw the pickup on the roads and decided to pull the driver over. Greater Manchester Police said:

“Whilst this may seem trivial to some, legitimate concerns exist around the safety of other road users or pedestrians if they were involved in a collision with the Cybertruck.”

The Cybertruck in question was, according to the BBC, registered and insured abroad and was confiscated. The driver, who is a UK resident, was reported.

The Greater Manchester Police Department then added:

Advertisement

“The Tesla Cybertruck is not road-legal in the UK and does not hold a certificate of conformity.”

The Cybertruck cannot be legally driven in the UK because it has no UK Type Approval for operation in the country. This is due to some safety concerns, which are related to its angular shape and design. The stainless steel exoskeleton has sharp edges and projections that violate UK/EU rules on pedestrian protection.

Tesla has considered creating what it referred to as an “international version” that would be approved for operation in Europe. However, there has been no real movement on that front by the company, as it has been focused on the Robotaxi rollout primarily.

Advertisement
Continue Reading