Saudi Arabia Bought Twitter to Hunt and Jail Critics. Now It’s Attacking the ADL

The Kingdom of Saudi Arabia is the biggest shareholder of Twitter behind Elon Musk. And I mean they are literally behind Elon Musk.

The gist of it is a true story that they threatened back in 2011 to ban all Jewish birds trying to enter their country. But seriously, they told Twitter executives that unless Saudi government informants were on staff and Saudi money could steer management decisions (e.g. censor women, promote Nazism), there would be no tweeting allowed.

The latest news is thus related to an old case.

Between July and December 2015, Twitter granted the kingdom information requests “significantly more often” than most other countries at that time, including Canada, the UK, Australia and Spain, the lawsuit alleges.

On 5 November 2015, just days before Twitter was confronted by the FBI about its concerns about a Saudi infiltration of the company, it promoted Alzabarah – now a fugitive living in Saudi. In response, Alzabarah sent his Saudi government contact, al-Asaker, a note, conveying his “unimaginable happiness” for the promotion. The note, the lawsuit claims, is evidence that Alzabarah believed al-Asaker had “arranged” or “been influential” in connection to the promotion.

Once Twitter was made aware of the FBI’s concerns, it put Alzabarah on leave and confiscated his laptop, but not his phone, which he has used extensively to contact his Saudi state contacts. Twitter, the lawsuit alleges, “had every reason to expect that Alzabarah would immediately flee to Saudi Arabia, which is exactly what he did”.

Fast forward to today…

Does anyone really wonder why the Kingdom of Saudi Arabia now would want to use their platform to pick a huge fight with its critics at the ADL? Examples of ADL reports:

Elon Musk seems to be inconsistent, yet he’s consistently a coin-operated mule for China and Saudi Arabia.

He backs Russia against Ukraine whenever China yanks his leash. He attacks speech and demands censorship of Jews when Saudis give him a pull.

So of course a lapdog of Saudi Arabia is jumping up and down pretending he is very upset with the ADL.

Lawsuit: https://acrobat.adobe.com/id/urn:aaid:sc:us:d204dd50-60eb-493a-b7d7-bc2c3c54641f
Exhibits: https://acrobat.adobe.com/id/urn:aaid:sc:us:4e84a8d4-76b3-48f9-b97d-8ed84a89f5e6

Cruise is Fighting With SFFD Over a Pedestrian Death. The Robots Might Be Right.

Allow me to divulge a bit of behind-the-scenes intrigue regarding the San Francisco Fire Department (SFFD): they have an undying affection for oversized, cumbersome, and fiscally extravagant trucks.

In fact, their adoration for these mammoth vehicles knows no bounds, leading them into a protracted skirmish with advocates for pedestrian safety. You see, the streets of San Francisco can’t undergo the sort of straightforward, commonsense traffic improvements (such as narrower lanes or strategically placed “bulb outs”) to enhance pedestrian safety. Why? Because the SFFD fervently argues that their trucks must meet the most exacting standards for a “proper job”.

SFFD Assistant Deputy Chief Ken Lombardi told KQED that the department isn’t necessarily opposed to buying more maneuverable equipment. “It’s not that simple,” he said. “We’re trying to buy a smaller engine. We just need to make sure that engine’s going to do the proper job.”

“Proper job,” you say? Well, when it comes to fitting snugly into the intricate urban tapestry, SFFD seems to be missing the mark in a rather grandiose fashion. In fact, there’s nary a trace of effort from them in the direction of procuring more petite fire-fighting vehicles.

Now, the question of whether the SFFD could swiftly acquire smaller trucks is akin to pondering if chickens possess lips – the answer is glaringly obvious! Yes, they could easily adopt compact vehicles, much like the rest of the civilized world.

Unfortunately, the SFFD’s progress report in this regard appears to be a blank slate, and as a consequence, the safety of pedestrians in San Francisco remains a precarious affair. This, quite ironically, places the fire department at the center of a contentious debate concerning the causes of pedestrian fatalities.

And now, armed with this vital context, the SFFD contends that the driverless Cruise vehicles failed to provide ample space for their sizable emergency trucks to maneuver and save a critically injured pedestrian.

Dear SFFD, it’s high time you caught on to the fact that your penchant for excessive size and this “minimum 20 foot clearance” notion is not only perilous but also entirely unworkable.

“Other cities and towns across the country also have small streets and sharp turns and have purchased specialized vehicles that can operate in these environments,” Rose said in his 17-page report.

Rose said those vehicles are not necessarily shorter, or lacking features of a more traditional engine, but are designed to make them more maneuverable.

The report was requested by Supervisor Scott Wiener, who has been frustrated by the Fire Department’s insistence on maintaining a 20-foot — or sometimes wider — minimum street width.

Enough of this nonsense already.

SFFD has not been “voicing concerns” about pedestrian safety — the department has been interfering with street redesigns that improve pedestrian safety. And the inexcusable part is that SFFD’s pushback against measures to calm traffic and make it safer for people to cross the street appears to be based on unfounded fears.

As a long-time constant critic of driverless engineering, I reluctantly have to admit Cruise is falsely accused here of obstruction by SFFD.

The actual obstructionist to saving pedestrian life has been the SFFD. They are apparently not based in any safety reality.

…”the most significant relationship to injury accidents” was street width. “As street widths widen, accidents per mile per year increases exponentially, and the safest residential street width are the narrowest (curb face).” […] SFFD Fire Chief Johanne Hayes-White also made the erroneous yet unchallenged claim in a recent Examiner article that 74 percent of pedestrians were at fault for their own injuries, though she later said she was “misinformed.”

Yeah, misinformed is putting it lightly.

They know the Bayview doesn’t even have any crosswalks, so how could a dead pedestrian there ever avoid being blamed given the city’s failure to provide any safe zones?! Nice one SFFD.

This fire department has displayed so much incompetence, generated a reputation on safety so bad, that it sets up an ignorant and unhinged robot company, of all things, to look like the good guys in a pedestrian safety fight.

I’ve looked at the evidence of this incident and what I see is SFFD trying to gin up their old dull “special city” saw about fear of clearance.

I must confess, I’ve never been a fan of taxis, and these mostly fraudulent driverless taxis have only intensified my dislike. However, it’s impossible to deny that the SFFD’s insistence on brandishing their antiquated “clearance room” banner in such a brazen manner is nothing short of absurd. It’s the very definition of hubris. If you take a gander at the video, it’s clear that Cruise isn’t in the wrong when it comes to clearances.

With AI entering the news scene this one particular showdown over a pedestrian fatality has garnered significant attention, unlike countless other pedestrian harm the SFFD may have been involved in. Exposure is a good thing, as a showy AI operation may just be the thing that ushers in greater scrutiny of the SFFD’s pedestrian policies.

Perhaps, just perhaps, Cruise, armed with their deep pockets and formidable legal team, can shine a spotlight on the SFFD’s longstanding errors in judgment. The streets need to be narrowed, and the SFFD’s obstructions and negligence should be subjected to meticulous examination.

In their legal battle, Cruise’s attorneys could argue that the SFFD has knowingly permitted casualties by insisting on unnecessarily wider streets and deploying heavy large vehicles clearly ill-suited for urban emergencies.

Texas State Censorship of Internet Struck Down in Court

The American political party of self-proclaimed small limited government and personal responsibility brings you this ugly mess:

…Texas anti-porn law that requires age verification… would have exposed consumers to “significant privacy risks” by forcing adult-website visitors to show digital IDs. …these laws give states “the power to harass and censor legal businesses” and that allowing states “to suppress certain speech by requiring invasive and burdensome systems that consumers refuse to engage with is simply state censorship.”

At this rate “invasive and burdensome suppression of rights” should become the Texas state motto.

US District Court blocked the Texas censorship law a day before it was to take effect, calling it unconstitutional.

NHTSA ADAS SGO and TeslaDeaths.com Compared

TeslaDeaths.com has 41 ADAS fatalities in their latest tally (out of many hundreds killed by Tesla), yet NHTSA was reported by the Washington Post in January 2023 to be investigating far fewer fatalities.

17 fatalities, 736 crashes: The shocking toll of Tesla’s Autopilot. Driver-assistance system has been involved in far more crashes than previously reported

I bring this up because people lately are asking me if it is ok to use the Washington Post 17 an “official” number, instead of using the clearly documented much higher number of official deaths recorded by TeslaDeaths.com.

No is the answer. The Washington Post number is misleading, arguably wrong.

And you won’t believe how easy it is to explain the difference.

Let’s look first at the latest raw NHTSA fatality data, based on “Reporting Entity” of Tesla. This isn’t rocket science. Take 1088 rows from the U.S. Agency data file published for public review, sort the rows on severity and… ALL these fatalities sitting at the top are ALL Tesla:

  1. 13781-5835: 2 Dead
  2. 13781-5785: 1 Dead
  3. 13781-5685: 1 Dead
  4. 13781-5673: 1 Dead
  5. 13781-5609: 1 Dead
  6. 13781-5372: 2 Dead
  7. 13781-5248: 1 Dead
  8. 13781-5165: 1 Dead
  9. 13781-4963: 1 Dead
  10. 13781-4011: 1 Dead
  11. 13781-3900: 1 Dead
  12. 13781-3847: 1 Dead
  13. 13781-3713: 1 Dead
  14. 13781-3710: 2 Dead
  15. 13781-3513: 1 Dead
  16. 13781-3488: 1 Dead
  17. 13781-3470: 1 Dead
  18. 13781-3332: 1 Dead
  19. 13781-3327: 2 Dead
  20. 13781-3279: 1 Dead
  21. 13781-3074: 1 Dead
  22. 13781-2600: 1 Dead
  23. 13781-2423: 1 Dead
  24. 13781-1979: 1 Dead
  25. 13781-1785: 1 Dead
  26. 13781-21: 1 Dead

To put things into perspective, approximately 80% (878 rows) of all crashes involving Advanced Driver Assistance Systems (ADAS) are linked to a single company, Tesla. What’s even more significant is that, with the exception of one incident in 2021, every fatality associated with these crashes can be attributed to Tesla.

Another way of looking at it is Tesla crashes went from 736 to 878 (142 new) since January and their death count jumped to 30. That’s 13 new deaths from 142 crashes in just a few months, meaning Tesla ADAS reports a new death for every 10 crashes.

We’re talking nearly double the amount of deaths now versus what the Washington Post reported as a “shocking toll” nine months ago. Nobody should be talking about 17 anymore, because the Tesla death rate is so high.

Thirty (30) and growing

Ok, but that’s still not the full 41 as recorded outside the NHTSA data. Let’s now find what causes there to be 11 other fatalities on TeslaDeaths.com.

  1. May 2020 Norway
  2. Dec 2019 USA
  3. Dec 2019 (2 Dead) USA
  4. Aug 2019 USA
  5. April 2019 USA
  6. Mar 2019 USA
  7. Apr 2018 Japan
  8. Mar 2018 USA
  9. May 2016 USA
  10. Jan 2016 China

So there you have it. They all are documented ADAS deaths. May 2016 is a great example because the NHTSA investigated it very publicly, yet it’s not in their SGO list. Why are these 11 missing from the NHTSA count of just 30?

Spoiler alert: American politics.

Eleven dead in those four years from Jan 2016 to May 2020 weren’t recorded by the NHTSA… due to very obvious political corruption. After the 2016 Presidential election the agency head stepped down a month later and a Senate-confirmed administrator then didn’t happen. There was not even a nominee to run the NHTSA after 2019.

Tesla was getting away with murder of Americans because the NHTSA seemed blinded on purpose. The safety regulator was not systematically recording ADAS fatalities, it was not even keeping up with reports in the news.

Or, to put it another way, the CEO of Tesla was immediately appointed to the U.S. President’s advisory council in December 2016.

Source: Twitter

Musk’s surprise rapport with Trump means 40% rally for Tesla.

Musk serves on the president’s economic advisory board and regularly meets with either Trump or his top aides. He was one of a dozen chief executive officers who met with Trump at the White House on Monday to talk manufacturing, taxes and trade. “Elon Musk has an important line of communication to Donald Trump,” Morgan Stanley analyst Adam Jonas wrote in a note last week as he raised his price target to $305 from $242. “This strategic relationship between Tesla leadership and the new administration is an important development.”

The NHTSA in 2017 was blocked from dealing even the most egregious and suspicious Tesla deaths.

What changed November 2020 with regard to their ADAS safety monitoring? Why were fatalities recorded in a public data format?

Simple. A new U.S. President was elected, flushing out Tesla corruption.

January 2021 Steven Cliff was appointed to the NHTSA. A few months later in June of 2021 crash reporting for ADAS was inititated and the Tesla numbers grew quickly.

When the Tesla CEO no longer could corrupt regulators, the fraud of his ADAS was exposed in a new NHTSA database.

The difference from the 17 reported by the Washingtom Post is primarily that TeslaDeaths.com keeps official records from before the NHTSA was able to start functioning again, which adds another 11 fatalities. To be fair, the SGO means a specific reporting mandate and format that started in 2021. It doesn’t include the earlier numbers. Also note the NHTSA is recording U.S. data, which could obviously leave out fatalities in Norway, Japan and China.