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.
News
SpaceX Starship Flight 13 faces wrath of the Texas skies
SpaceX pushed Starship Flight 13 to Friday, blaming weather instead of the previous engine issues.
SpaceX called off Thursday’s launch attempt of Starship Flight 13, pushing the mission to Friday because of weather tied to Tropical Storm Bertha. The company confirmed the delay on X, noting “Now targeting Friday, July 24 for Starship’s thirteenth flight test, due to weather. A key objective for the flight test is to get clear imagery from the ground of Starship’s heatshield as it flies at a higher dynamic pressure during ascent, which won’t be possible with today’s weather conditions.”
This is the second delay for Flight 13 in two weeks. SpaceX first tried to launch the mission on July 16, but the countdown ended in an automated abort at T-0 when four of Super Heavy Booster 20’s 33 Raptor engines failed to ignite. Musk said at the time that two Raptors would need to be removed and replaced, as Teslarati reported. The company spent the following week destacking Ship 40 and Booster 20, swapping engines, and running leak checks before restacking the vehicle on Pad 2 Wednesday night, according to Spaceflight Now’s live coverage.
Unlike the engine problem, Thursday’s delay has nothing to do with the hardware. SpaceX wants clean footage of Starship’s heat shield captured from the ground as the vehicle flies through max dynamic pressure, something the storm’s cloud cover over South Texas would not allow. The company said visibility should improve for Friday’s attempt, with the same 90 minute window opening at 5:45 p.m. CT.
Flight 13 will be the second outing for the V3 versions of Starship and Super Heavy, following their debut on Flight 12 in May. The mission carries 20 production Starlink V3 satellites, the first time SpaceX has flown operational satellites rather than mass simulators on Starship. Six of those satellites are fitted with cameras to inspect the heat shield from a different angle during ascent, giving engineers a second data source beyond the ground imagery the weather is currently blocking.
Booster 20 will attempt a boostback burn and a splashdown landing burn in the Gulf of America, while Ship 40 follows a suborbital trajectory toward a landing in the Indian Ocean. The flight plan largely mirrors Flight 12, though the booster will run a more aggressive ascent burn after max Q this time, and the ship’s heat shield includes load sensing tiles meant to measure stress at the higher dynamic pressure SpaceX is targeting.
If Friday’s attempt succeeds, Flight 13 could be the last suborbital test in the program. SpaceX is already looking to push for an orbital flight on Flight 14.
Investor's Corner
Tesla stock tumbles after earnings, one of its sharpest single-day declines
Tesla stock (NASDAQ: TSLA) endured one of its sharpest single-day declines in years on July 23, tumbling approximately 14.5 percent and closing near $320 after opening the session around $374. The drop erased more than $140 billion in market value amid heavy trading volume and left the shares at multi-week lows.
The sell-off followed the company’s second-quarter 2026 results, released the previous evening. Tesla reported record revenue of $28.2 billion, up 26 percent year over year, driven by a Q2-record 480,126 vehicle deliveries. Energy storage deployments also rose strongly.
Tesla (TSLA) Q2 2026 earnings results: miss on EPS, beat on revenue
Yet profitability disappointed sharply. Operating income fell 57 percent to $398 million, compressing the operating margin to just 1.4 percent. Non-GAAP earnings per share came in at $0.33, well below the roughly $0.53 analysts had expected. Free cash flow turned negative by $1.1 billion as capital expenditures surged 142 percent to $5.8 billion, largely tied to accelerated spending on artificial intelligence, robotics, and autonomous systems.
The losses on capex were expected, as Tesla said it would be spending heavily in 2026.
Investors also reacted to lingering uncertainty surrounding key product timelines. During the Earnings Call, management reiterated ambitions for Robotaxi deployment and the Optimus humanoid robot, but offered limited new concrete milestones, renewing questions about execution pace that have long accompanied Tesla’s ambitious roadmap.
The magnitude of the decline places it among Tesla’s more severe one-day percentage losses since its 2010 initial public offering. Historically, the two largest single-day drops (split-adjusted) remain September 8, 2020, when shares fell 21.1 percent amid broader market volatility and valuation concerns, and January 13, 2012, with a 19.3 percent plunge during the company’s early growth struggles.
Other notable declines include an 18.6 percent drop on March 16, 2020, at the onset of pandemic-related market turmoil. Thursday’s move ranks roughly ninth on the all-time list but stands out as the steepest in more than a year.
Despite the short-term pain, Tesla’s long-term trajectory has repeatedly recovered from such volatility. The latest results underscore both the strength of its core automotive and energy businesses and the near-term costs of heavy investment in next-generation technologies.
Elon Musk
Elon Musk is not happy about this Tesla Full Self-Driving approval delay
Elon Musk clapped back at France’s decision to withhold the approval for Tesla’s Full Self-Driving (FSD) Supervised system, projecting a clear and blunt message to French Transport Minister Phillippe Tabarot, after he publicly rejected the technology in its current form.
Tabarot outlines several concerns with Tesla Full Self-Driving in a detailed video statement, where he said, “The safety trade-offs are not yet sufficient to authorize it as it currently stands,” he said. He emphasized that FSD is not a true self-driving system and that the driver remains fully responsible.
Key issues Tabarot also brought up included allowing speeding when surrounding traffic exceeds limits and what he believes are insufficient guarantees of driver attention during complex urban maneuvers such as lane changes, intersections, and roundabouts.
Delaying the approval of FSD in France will cost lives
— Elon Musk (@elonmusk) July 22, 2026
While acknowledging technological progress and France’s support for autonomous innovation, Tabarot stressed that deployment must prioritize road safety. He noted ongoing technical discussions with Tesla, the Netherlands, and other European partners, with further ecosystem meetings planned for the fall.
Musk’s rebuke highlights the human cost of regulatory caution. Tesla’s latest safety reports provide compelling data supporting accelerated adoption. In the most recent 12-month period, vehicles using FSD (Supervised) recorded one major collision per approximately 5.1 million miles driven, dramatically better than the U.S. national average of one crash per 698,000 miles.
Even Tesla vehicles driven manually with active safety features outperform the average by a wide margin. These figures come from billions of real-world miles of telemetry, showing FSD vehicles involved in far fewer incidents than both manual Teslas and the broader U.S. fleet.
Critics argue Tesla’s comparisons require careful scrutiny regarding reporting thresholds and fleet demographics, yet the data consistently positions FSD as a potential lifesaver. With road fatalities remaining a leading cause of death worldwide, Musk contends that proven safer technology should not face prolonged bureaucratic hurdles.
France’s measured approach reflects the broader European regulatory caution, which many, especially Musk, have been critical of in the past. However, as autonomous systems from Tesla and competitors like Waymo demonstrate superior safety in independent studies, pressure is mounting for harmonized approvals.
Musk’s warning carries the belief that every month of delay may equate to avoidable tragedies on European roads.