Connect with us
Twitter files Twitter files

News

Twitter Files part 14 sheds light on “Russian bots” and #ReleaseTheMemo

Published

on

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.

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.

Advertisement

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

Advertisement

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

Advertisement

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.

Advertisement

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

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.

Elon Musk

‘I don’t understand TSLAQ:’ notable investor backs Tesla, Elon Musk

Published

on

tesla showroom
(Credit: Tesla)

One notable investor that many people will recognize said today on X that he does not understand Tesla shorts, otherwise known as $TSLAQ, and he’s giving some interesting reasons.

Martin Shkreli was long known as “Pharmabro.” For years, he was known as the guy who bought the rights to a drug called Daraprim, hiked the prices, and spent a few years in Federal prison for securities fraud and conspiracy.

Shkreli is now an investor who co-founded several hedge funds, including Elea Capital, MSMB Capital Management, and MSMB Healthcare. He is also known for his frank, blunt, and straightforward responses on X.

His LinkedIn currently shows he is the Co-Founder of DL Software Inc.

One of his most recent posts on X criticized those who choose to short Tesla stock, stating he does not understand their perspective. He gave a list of reasons, which I’ll link here, as they’re not necessarily PG. I’ll list a few:

Advertisement
  • Fundamentals always have and will always matter
  • TSLAQ was beaten by Tesla because it’s “a great company with great management,” and they made a mistake “by betting against Elon.”
  • When Shkreli shorts stocks, he is “shorting FRAUDS and pipe dreams”

After Shkreli continued to question the idea behind shorting Tesla, he continued as he pondered the mentality behind those who choose to bet against the stock:

“I don’t understand ‘TSLAQ.’ Guy is the richest man in the world. He won. It’s over. He’s more successful with his 2nd, 3rd, and 4th largest companies than you will ever be, x100.

You can admit you are wrong, it’s just a feeling which will dissipate with time, trust me.”

Advertisement

According to reports from both Fortune and Business Insider, Tesla short sellers have lost a cumulative $64.5 billion since Tesla’s IPO in 2010.

Elon Musk issues dire warning to Tesla (TSLA) shorts

Shorts did accumulate a temporary profit of $16.2 billion earlier this year.

Continue Reading

News

Tesla will let you bring back this removed Model 3 part for a price

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

Published

on

Credit: Tesla Asia/X

Tesla is now letting Model 3 owners in the United States bring back one part that the company decided to remove after it refreshed the all-electric sedan last year. Of course, you can do it for a price.

With the Model 3 “Highland” refresh that Tesla launched last year, one of the most monumental changes the company made was to ditch the turn signal stalk altogether. Instead, Tesla opted for turn signal buttons, which have been met with mixed reviews.

I drove the new Tesla Model 3, here’s what got better

The change was widely regarded as Tesla preparing for more autonomous driving in its vehicles, especially as its interiors have gotten even more minimalistic.

The lack of a stalk in the new Model 3 was just another move the company made to adjust drivers and passengers to seeing less at the steering wheel column.

Advertisement

However, many drivers did not prefer the use of buttons and wanted the stalk reinstalled. Tesla allowed it in several regions, launching a retrofit kit. It has now made its way to the United States:

It will cost $595 and is available on Tesla’s website. You will have to have a Model 3 on your Tesla account to purchase the stalk retrofit kit.

It is interesting to note that despite Tesla’s strategy to remove the stalk with the new Model 3, which was released in early 2024, the company did not choose to make the same move with the new Model Y.

Advertisement

The new Model Y launched in the United States in early 2025, and Tesla chose to install a stalk in this vehicle.

It seemed as if the turn signal buttons were too much of a polarizing feature, and although the company technically could have given orderers an option, it would not have been the most efficient thing for manufacturing.

Continue Reading

News

Tesla Full Self-Driving v14.1 first impressions: Robotaxi-like features arrive

Tesla Full Self-Driving v14.1 is here, and we got to experience it for ourselves.

Published

on

Tesla rolled out its Full Self-Driving v14.1 yesterday, its first public launch of its most robust and accurate FSD iteration yet. Luckily, I was able to get my hands on it through the Early Access Program.

The major changes in FSD v14.1 were revealed in the release notes, which outline several notable improvements in areas such as driving styles, parking, and overall navigation. Here’s what Tesla outlined fully in its release notes:

  • Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
  • Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
  • Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
  • Added additional Speed Profile to further customize driving style preference.
  • Improved handling for static and dynamic gates.
  • Improved offsetting for road debris (e.g. tires, tree branches, boxes).
  • Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
  • Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
  • Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!

I wanted to try it for myself. My big must-dos were my complaints with v13.2.9, which included parking when arriving at a destination, Navigation when leaving a destination, and definitely a general improvement in the car traveling at an acceptable rate of speed, even when using the “Hurry” driving style.

Here’s what I noticed with the new Full Self-Driving v14.1:

Speed Profiles are More Realistic

I am driving on “Hurry” about 95% of the time when utilizing Full Self-Driving. In past versions, most notably v13.2.9, my Tesla would slowly reach the speed limit, and it would tend to hang out at about 1-2 MPH either above or below it.

My first observation with v14.1 was the vehicle’s tendency to get right up to speed and, since I was still on Hurry, drive slightly above the speed limit. It never got out of line; it traveled at speeds I would typically drive at manually.

Advertisement

I think this is a big improvement on its own, because I felt that I was pressing the accelerator too frequently in past FSD versions. Oftentimes, it just wasn’t going fast enough to justify the “Hurry” label; it felt more conservative and more like a student driver than anything.

Check it out:

This was among my favorite improvements, and it was the first thing I noticed as the car navigated me to the Supercharger, where my next positive is.

Navigating into parking lots, self-parking at Supercharger

One of the changes noted in the Release Notes was the addition of Arrival Options, which allows the car to select the appropriate parking situation. Since I was going to charge, the car had already chosen “Charger” as the parking option.

Pulling into a gas station or convenience store, especially during work days, can be stressful, as they are usually congested and full of foot and vehicle traffic. In past FSD versions, I have noticed the car being slightly “jumpy” and even hesitant to proceed through the lot.

Driving through parking lots was a noticeable improvement. It seems as if the car is much more confident in making its way through, while still being aware and cautious enough to safely navigate to the Supercharger.

Advertisement

It then backed straight into a Supercharger stall, which was recently repaired and is once again active. I was actually upset it chose this specific stall because it had been inactive for a while. However, Tesla got this stall back up and running, the car chose it, and backed into the spot flawlessly:

This was super cool to experience, and I think it is a testament to how hard the Tesla AI team has worked. CEO Elon Musk recently stated that FSD would enable automatic parking at Superchargers, which was really awesome to experience firsthand.

Advertisement

I decided to leave the Supercharger and go to an auto parts store to pick up some interior cleaner and some microfiber towels. I love keeping my Tesla clean!

I also thought it would be a great opportunity to see how it would react to another parking lot, how it would navigate it, and let it choose a parking spot. It did it all flawlessly:

Advertisement

I had zero complaints about everything here. All of it was done really well.

Making a choice after being caught in the middle of an intersection

I arrived at a tight intersection in Dallastown, PA, and what my car did next has catalyzed quite a conversation on X.

It proceeded out into the middle of the intersection as the light was green. It had to yield to oncoming traffic, and while waiting, the light turned yellow, then red.

Most people, including myself, would have turned right and proceeded through the intersection since the car was already past the line. However, FSD chose to back up and wait for the next light cycle, which I felt was also a more than acceptable option:

There are some conflicting perspectives on what it chose to do here. Some said they would have proceeded and would want FSD to also proceed. I can agree with that perspective, but I also think it is not the worst thing in the world to back up. In Pennsylvania, I couldn’t find the exact law that says what is right or wrong. Instead, I did see that a left turn on red is only feasible when you’re going from a One-Way street to another One-Way.

I’m not totally sure what is “correct” here, but I think either option is fine. I have personally done both, and I’ve seen other drivers do both. I was more than fine with the car doing this, and I was honestly impressed that it did.

Navigated a busy grocery store lot, found suitable parking

This is not the busiest my local grocery store gets, but it was still congested enough for me to be impressed.

Advertisement

FSD decided to do one loop in the parking lot before it found a spot that it felt was good enough for me. I was perfectly fine with where it chose to park, and I thought it did a really great job. I was impressed with how stress-free I felt, as I have noted in the past that parking lots are definitely an area where Tesla needs to improve.

I was happy with its performance:

Strange right turn signal as if it saw an emergency vehicle

This was the first bug I noticed with FSD v14.1. While traveling on a local road, it put the right turn signal on and approached the curb as if it was pulling over for an emergency vehicle or as if it was going to park on the street.

It then realized its mistake and proceeded:

I’m not super sure what caused this, but I was a tad bit confused. There were no police cars, ambulances, or anyone with flashing lights to my rear. There was a dump truck on the other side of the road, and I almost felt like the way it navigated “around” that was probably what triggered it.

Navigation is still making strange decisions

I’ve written about navigation and my discontent with some of its decisions. It seems v14.1 didn’t resolve much of anything with navigation, and it did a couple of things wrong.

The first was that it tried to take the illogical and pointless path out of the Supercharger. I wrote about this a few days ago, as FSD tried to take my car the wrong way.

Advertisement

It did it again, but I overrode the decision, and it was all okay:

This is a minor issue, but it is still pretty frustrating. Hopefully, the navigation will learn after performing this adjustment after enough times.

Advertisement

The next navigation issue was more frustrating than the Supercharger one, especially considering it completely ignored the route. The navigation had the vehicle very clearly heading straight, but out of nowhere, the right turn signal went on. I overrode it, but the car still turned right, ignoring the navigation completely:

I ended up taking over here and driving until I could get to a stop sign.

Advertisement

Final Thoughts

I am really impressed with all of the changes Tesla made with FSD v14.1, and while there were a handful of bugs, things were tremendously better than v13.2.9.

Continue Reading

Trending