News
Twitter Files part 14 sheds light on “Russian bots” and #ReleaseTheMemo
The Twitter Files part 14, written by independent journalist, Matt Taibbi, shed light on a false narrative of Russian bots and the hashtag #ReleaseTheMemo. Taibbi, who was given access to the internal documents at Twitter by Elon Musk, released a new installment on Thursday.
1.THREAD: Twitter Files #14
THE RUSSIAGATE LIES
One: The Fake Tale of Russian Bots and the #ReleaseTheMemo Hashtag— Matt Taibbi (@mtaibbi) January 12, 2023
It began in 2018 when Senators Dianne Feinstein and Adam Schiff wrote the platform a letter regarding trending hashtags and Russian disinformation campaigns. Twitter pointed out that both the politicians and the media didn’t only lack the evidence but had evidence the accounts were not Russian. However, the platform was “roundly ignored.”
Backtracking to a week before Twitter received the letter, Republican Devin Nunes submitted a classified memo to the House Intel Committee that detailed the abuses by the FBI in obtaining Foreign Intelligence Surveillance Act (FISA) surveillance authority against those connected to former President Trump. Included was the role played by the Steele Dossier.
Credit: Matt Taibbi
In December 2019, a report by Justice Department Inspector General Michael Horowitz verified Nunes’ assertions virtually.
“We also found that the FBI’s interviews of Steele, his Primary Sub-Source, a second sub-source, and other investigative activity revealed potentially serious problems with Steele’s descriptions of information in his reports,” the report read. “Among other things, regarding the allegations attributed to Person 1, the Primary Sub-source’s account of these communications, if true, was not consistent with and, in fact, contradicted the allegations of a “well-developed conspiracy” in Reports 95 and 102 attributed to Person 1.”
The report also pointed out that the FBI filed three renewal applications with the FISC in 2017, repeating the seven “significant errors contained in the first FISA application.” Yet, the report found another ten errors in the three renewal applications. Taibbi noted that despite that, the national media denounced Nunes’ report in January and February 2018 in “oddly identical language, calling it a ‘joke.’
Senators Feinstein and Schiff also wrote an open letter claiming that the hashtag “gained the immediate attention and assistance of social media accounts linked to Russian influence operations.
The senators claimed that Nunes’ memo “distorts” classified information. “But note they didn’t call it incorrect,” Taibbi wrote.
Connecticut Senator Richard Blumenthal also wrote a letter. “We find it reprehensible that Russian agents have so eagerly manipulated innocent Americans citizens and undermined our democratic processes through our elections and public policy debates.”
The letter asked Twitter to notify users who interacted with tweets created by the accounts tracked by the Alliance for Securing Democracy (ASD). The senators and members of the media pointed to the Hamilton 68 dashboard created by Clint Watts, a former FBI counterintelligence official, created The letter asked Twitter to notify users who interacted with tweets created by the accounts tracked by the Alliance for Securing Democracy.”
The Hamilton 68 dashboard was described as a project with the Alliance for Securing Democracy at the German Marshal Fund and tracked around 600 accounts that it claimed were tied to Russian-sponsored influence and disinformation campaigns. Bret Schafer, an analyst who helped run the project, spoke about the #ReleaseTheMemo hashtag.
“I’ve never seen any single hashtag that has had this amount of activity behind it,” he said. Taibbi noted that the dashboard “was vague in how it reached its conclusions.”
Twitter executives didn’t quite trust the dashboard and the key complaints were that Hamilton 68 seemed to be the only source of information and no one was checking with Twitter. Global Policy Communications Chief Emily Horne encouraged skepticism of the dashboard’s take. In the screenshots below, Horne pointed out that it was a comms play for ASD.
“They’ve made a very strong media push in the last week, piggybacking on Clint’s testimony.”
Off the record, she said, “I encourage you to be skeptical of Hamilton 68’s take on this, which, as best as I can tell, is the only source for these stories. 1) Hamilton 68 does not release the accounts that make up their dashboard, so no one can verify the accounts they include are, in fact, Russian automated accounts, and 2) it is extraordinarily difficult for outside researchers, who do not have access to our full API and internal account signals, to say with any degree of certainty that an account they believe is behaving suspiciously is 1) automated and 2) Russian.”
“If you speak with them, I encourage you to press them on how they can be sure of both of these claims when they do not have access to internal signals and data.”
Twitter’s former head of safety, Yoel Roth, wasn’t able to find any Russian connection to the hashtag and noted that after reviewing accounts that posted the first 50 tweets with the hashtag, none showed any signs or affiliation to Russia. Instead, Twitter found that the engagement was “overwhelmingly organing and driven by strong VIT engagement). VIT is an acronym for very important Tweeters, and these included Wikileaks, Donald Trump Jr., and Congressman Steve King.
When Twitter brought this up to a Blumenthal staffer, the staffer tried to wave them off “because we don’t believe these are bots.”
Another Twitter executive pointed out that if Blumenthal would lay off on this, “it seems like there are other wins we could offer him.” However, the senator published his letter, which led to the platform’s executives being frustrated over what they viewed as a circular process.
“Twitter spent a lot of resources to respond to the initial request, and the reward from Blumental shouldn’t be round after round of requests for user notice. It also doesn’t do anything to fix the problem. That distracts our team from the real iq fight.”
Twitter executives later realized that they were”feeding congressional trolls” and compared the requests to a popular children’s book, If You Give a Mouse a Cookie.
Although Twitter believed that there were no Russians in the story, it stopped challenging Russia’s claims on the record. Outside counsel from firms advised Twitter to use language such as “With respect to particular hashtags, we take seriously any activity that may represent an abuse of our platform.”
This resulted in reports from several mainstream media outlets pushing the “Russian bots” story without any evidence. Taibbi noted that several media outlets that played up the “Russian bots” story declined to comment. So did the staff for Senators Feinstein, Schiff, and Blumenthal. Nunes shared a comment.
“Schiff and the Democrats falsely claimed Russians were behind the Release the Memo hashtag, all my investigative work… By spreading the Russia collusion hoax, they instigated one of the greatest outbreaks of mass delusion in U.S. history.”
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 AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.
The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.
next month or so. the next tech to merge on the v15 plan will enable it.
— Ashok Elluswamy (@aelluswamy) September 4, 2026
That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.
Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.
Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.
By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.
Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.
Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.
If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.
That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.
Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.
Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.
FSD Supervised v14.3.9 starting to roll out shortly
This release includes a new active safety feature set: FSD Supervised can now activate on your behalf when an imminent collision is detected and Automatic Emergency Braking (AEB) may not be enough.
It may also engage if we…
— Tesla AI (@Tesla_AI) September 4, 2026
The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.
The intervention is meant as a last-resort safety net, not a replacement for attentive driving.
Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident
Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.
After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.
The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.
Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.
The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.
If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.
Tesla launched the all-electric, steering wheel-less, and pedal-less Cybercab last night at a quiet and small event in downtown Austin, Texas.
The launch, which marked the beginning of unsupervised ride-hailing for Tesla’s Robotaxi platform with Cybercab, has already caught the attention of the National Highway Traffic Safety Administration (NHTSA) who has more questions.
NHTSA opened an Audit Query (AQ) into the Cybercab’s Federal Motor Vehicle Safety Standards (FMVSS) certification that Tesla gave the vehicle. Manufacturers self-certify vehicles much of the time to avoid excessive regulatory delays.
Tesla Cybercab interior, note the lack of steering wheel and pedals. (Credit: @niccruzpatane/X< /a>)
However, the agency needs more information; it said in a summary:
“On September 3, 2026, Tesla began commercial deployment with a small number of its Cybercab vehicles in Austin, Texas. Tesla notified the Agency that it certified those Cybercab vehicles as compliant with all applicable Federal Motor Vehicle Safety Standards (FMVSS). Tesla also notified the Agency that it plans to gradually expand commercial deployment of the Cybercab to include additional vehicles and locations.”
It also went on to state that the Cybercab lacks traditional automotive controls, which is a groundbreaking move. The process is entirely new to the NHTSA, which gives the agency some leverage to put Tesla’s launch under a microscope:
“The vehicles lack permanently attached, conventional manual controls, such as a brake pedal, gas pedal, steering wheel, and mirrors. NHTSA is opening this AQ to examine the process and technical data on which Tesla relied when certifying the Cybercab and related issues. Among other things, NHTSA will consider the extent to which Tesla’s certification depended on determinations that certain FMVSS are inapplicable to the Cybercab.”
Tesla has added 45 Cybercab units to its fleet of Robotaxi-enabled cars in Austin, according to public documents the company submitted to the State of Texas over the past week. Enabling this level of self-driving is something Tesla has worked toward for many years, and now that it is finally here, it seems more than reasonable that regulatory agencies will have some questions.
Many outlets might try to frame this as a negative, but it is truly an agency looking to gain more information about groundbreaking tech that Tesla has been developing for years.
In an effort to keep riders, pedestrians, and property safe, any and all data accumulated from these first days, weeks, and months of rides will likely be shared with the NHTSA to enable broader rollout strategies across the United States and more in the future.
Tesla Robotaxi will be a 24/7 service: here’s when
Tesla Full Self-Driving will now overtake manual driving to avoid disaster
