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 released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.
Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.
However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.
With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.
Turning Hesitancy, Inaccuracy
I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
-
Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.
I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.
FSD Disregards Manual Turn Signals
This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.
If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.
FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.
This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.
-
This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.
Bird Braking is a Thing of the Past
The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.
There have been zero issues with this so far in v14.3.6, which is an excellent improvement.
FSD Might Already Be Taking Note of Driver Preferences
Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.
This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.
Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
-✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.
It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.
As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.
-
Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.
“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.
Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry
Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.
The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.
In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.
However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.
-
Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.
-
“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”
He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”
SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.
Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.
All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.
— Elon Musk (@elonmusk) July 25, 2026
However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.
Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:
-
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.
Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.
The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.
-
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
Musk’s massive Terafab project will get final location soon
