PA Tesla Kills Three in “Veered” Head-on Crash

Another day, another Tesla causing a tragic loss of innocent lives. It already appears from the police report that, as in so many previous instances and despite its longevity in the market promising future safety, Tesla’s poor engineering quality and “manslaughtering” design defects led to a “veered” collision with oncoming traffic.

Three people were killed in a car crash in Springfield Township, Fayette County on Sunday, state police said. It happened on Springfield Pike near Mt. Tabor Road around 5:55 p.m.. State Police Trooper Kalee Barnhart said two cars were involved in the crash. Barnart said both cars were sedans. One was a Tesla.

Of course State Police Trooper looking at the scene in rural Pennsylvania said one was a Tesla.

Springfield Pike and Mt. Tabor Road, Pennsylvania. A common two-lane highway very reminiscent of other recent tragic “veered” head-on crashes (Bean Hollow, Lake Tahoe, Idaho).

Police seeing the Tesla deaths first hand, the unusual spike in fatalities caused by Tesla, are warning us don’t get in a Tesla. Don’t let our friends or family get in a Tesla. NHTSA data since January 2023 reveals Tesla has been quietly reporting one fatality in every ten crashes.

Just think for a minute how bad at basic engineering a company has to be to spend a decade enriching themselves with false promises of future safety while building such an unsafe robot that it operates worse and worse every year. Bernie Madoff was jailed for far less fraud.

Source: Tesladeaths.com

Encounter a Tesla? Take cover and have the police on speed dial. You’re looking at a loaded rocket launcher being casually waved around in public as if by a big blind and deaf white South African. One might ponder why such humanity-destroying-by-design devices reminiscent of Dr. Death were ever permitted on any public roads.

Guess how long Tesla has known about this exact problem and refused to admit fault, sending customers to a predictable death?

…on the launch of the driver assistance tech, Musk would learn firsthand that a curve on Interstate 405 caused Autopilot, thrown off by the road’s faded lane lines, to steer into and “almost hit” oncoming traffic. Whenever this happened, Musk would “furiously” storm into the Tesla office and proceed to chew out his engineers. “Do something to program this right,” he repeatedly demanded…. “There was just such a gulf between Elon’s goal and the possible” [according to Tesla senior vice president Andrew Baglino]. “He just wasn’t aware of the challenges.”

Clearly documented, from the start Tesla knew they had a head-on collision problem with slight bends in a road. Tesla staff know exactly why they never fixed it. Now guess why they don’t want anyone to talk about it.

Or let’s ask instead, why did the CEO stop making demands it be fixed?

Hint: he doesn’t understand technology. He was thus tricked by his own staff, who played a very cynical game with the sole purpose of stopping his abuse of them even if hundreds of people would die as a result.

…he kept coming back to the fact that people have just two eyes and they can drive the car. […] Clearly, nothing was getting through to Musk. It was only his chief of staff Sam Teller that was able to appease his CEO’s complaints. He came up with a simple solution: getting the lane lines repainted on that pesky curve — which of course, didn’t actually address the underlying problem. “After that, Musk’s Autopilot handled the curve well”.

It handled one curve well because they changed the curve, leaving the car unsafe to drive everywhere else. They altered surroundings to deceive a very gullible CEO, using a simple ruse to make him stop shouting. Handling tin-pot dictator tantrums took precedence over safety engineering and work to preserve lives. These Potemkin villagers failed basic engineering ethics and enabled criminal-level negligence.

The conman promises people things they want, not things that can be delivered.

The CEO, obsessed by fantasy and easily deceived, was manipulated by his own staff into swallowing his own dumb argument that “two eyes” are sufficient enough for safety. They’re NOT, proven by the fact that his own eyes were then easily fooled into dangerous overconfidence. The ruse sadly only worked to stop him from berating them, and the company then continued on an obvious track to kill more and more people unnecessarily.

The engineering inconsistency is a very concerning paradox that proves AI unfit for cars, which those with common sense should recognize as the fundamental issue contributing to a decade of avoidable deadly crashes involving Tesla owners, both as victims and perpetrators.

The Black Women of Arlington Hall Who Kept Tabs on American Companies Doing Business With Nazis

The United States is gradually advancing its efforts in the field of expanding awareness about codebreakers and the origins of modern computing, akin to the remarkable work undertaken by historians at Bletchley Park in England. An article featured in DCist sheds light on significant revelations associated with “Building E on the Foreign Service Institute’s leafy Arlington campus”.

“The codebreakers who worked here saved countless American lives and shortened the war by what many historians estimate to be at least two years,” [institute director] Polaschik said.

A group of Black women who worked at Arlington Hall — they were segregated from their white counterparts — kept tabs on messages from the private sector, ensuring that American companies were not doing business with Nazi Germany or Japanese companies.

Overall, women made up 70% of the American domestic codebreaking force, noted Adam Howard, the director of the Office of the Historian at the State Department.

[…]

At the end of the war, the women were mostly pushed out of their jobs to make way for men…

Listening to companies doing business with Nazi Germany? Like *cough, cough* Ford, IBM and Coke?

How awkward to enlist Black women to surveil the most powerful American brands for evidence of treason. I am sure it wasn’t hard for them to find America’s worst offenders, given evidence was so often out in the open while being ignored.

Furthermore, the conclusion of the Arlington story features a memorable quote that underscores potential injustices within America. However, it may not fully capture the nuanced and intricate web of challenges faced by women. A perfect example can be found in the case of Agnes Driscoll who expanded and thrived in intelligence work after her role in World War I ended, as documented in the NSA Hall of Honor.

In her thirty-year career, Mrs. Driscoll broke Japanese Navy manual codes — the Red Book Code in the 1920s, the Blue Book Code in 1930, and, in 1940, she made critical inroads into JN-25, the Japanese fleet’s operational code, which the U.S. Navy exploited after the attack on Pearl Harbor for the rest of the Pacific War. In early 1935, Mrs. Driscoll led the attack on the Japanese M-1 cipher machine (also known to the U.S. as the ORANGE machine), used to encrypt the messages of Japanese naval attaches around the world. At the same time, Agnes sponsored the introduction of early machine support for cryptanalysis against Japanese naval code systems. Early in World War II, Mrs. Driscoll was engaged in the U.S. Navy’s effort against the German naval Enigma machine, although this work was superceded by the U.S.-U.K. cryptologic exchanges in 1942-43. Mrs. Driscoll was part of the navy contingent that joined the new national cryptologic agencies, first the Armed Forces Security Agency in 1949 and then the National Security Agency in 1952.

Driscoll’s postwar career experienced a remarkable ascent, rather than being obstructed by male colleagues. It’s intriguing to observe that the greater a woman’s success in the field of cryptology, the less recognition she tends to receive especially if Black. This phenomenon could be attributed to a paradox: the less they are forced out, the more they are drawn into the shadows, if that conceptually aligns.

One might ponder whether any Black woman listening to the overtly racist white men driving American private sector to support Hitler and genocide (let alone the racists around them at work) would truly desire corporations like Ford, IBM, and Coca-Cola (among others) to unveil the extent of knowledge she possessed.

Here’s a medal. Now you’re dead.

On that note, the NSA claiming “work was superceded by the U.S.- U.K. cryptologic exchanges in 1942-43” completely obscures the critical role of Polish codebreakers. I wonder how this keeps happening to extremely important yet humble men in history like Rejewski.

It’s necessary for individuals, regardless of gender, to practice self-limiting humility when discussing their role in intelligence. Seeking attention and recognition for such roles is generally considered inappropriate, and yet we see men far earlier and more often breaking the most basic rule about breaking rules (e.g. spying often is by definition illegal). It’s not about encouraging women to become boastful too, and rather about protecting the necessary culture where both men and women are expected to refrain from stealing the limelight and instead focus on collective morally justified achievements of the team.

For example, a man received a recognition for supervising Black women at Arlington, while all of them apparently remained unknown and unrecognized.

Whereas stories of their white counterparts have come to light as records have been declassified, the identities of most of Arlington’s Black code breakers remain unknown.

In researching her book, Mundy scoured National Security Agency records, among many other sources, and uncovered only two names of Arlington’s Black women code breakers: Annie Briggs, who headed up the production unit, which worked to identify and decipher codes; and Ethel Just, who led a team of translators.

William Coffee, a Black man, supervised the women and recruited many of them, later winning an award for his wartime leadership.

Black women in a WWII non-machine special unit of American military intelligence, led by cryptographic clerk William Coffee, Assistant Civilian In Charge of B-3-b. Source: NPS.gov (NSA)

The percentage of women to men in that photo is typical of codebreakers, if you ask the NSA historians. So let me also make an important point about the book-writing and touring reference in the above article quote:

Mundy scoured National Security Agency records…and uncovered only two names of Arlington’s Black women code breakers

Twenty years before Mundy the NSA Center for Cryptologic History published a book in 2001 called “The Invisible Cryptologists: African-Americans, WWII to 1956″ by Jeannette Williams with Yolande Dickerson (researcher).

In early 1996, the History Center received as a donation a book of rather monotonous photographs of civilian employees at one of NSA’s predecessors receiving citations for important contributions. Out of several hundred photographs, only two included African-Americans – an employee receiving an award from Colonel Preston Corderman (reproduced on page 14) and the same employee posing with his family. […] the war came, and we needed to expand. They bought Arlington Hall, and built two buildings – A Building and B Building – and we moved on Thanksgiving Day of ‘42. I’m not sure when the first blacks came, but Geneva Arthur was one of the early ones [in 1947].

Geneva Arthur.

Just saying, Mundy allegedly “scoured” NSA records and then left out Geneva Arthur in the machine section, a Black woman who rose all the way to being section head before retiring in 1973 as documented in 2001 by the NSA. Annie Briggs and Ethel Just also were mentioned in the same book by the NSA.

I suppose the real question here is whether, like Driscoll, Black women in intelligence became so accomplished they were promoted quietly and intentionally restricted by race into being further buried in secrecy — deciphering Soviet communications on the Venona project based on Genevieve Grotjan’s celebrated work. Yet very unlike the celebrated Grotjan the very many other names have been completely written out of history.

We really have to put this in proper perspective, because it used to be a given that computers meant women and then essential career-motivating factors (e.g. taking care of others, doing the right things, optimism and hope that things were going to get better) were used against them.

In June 1942, when the US government took over Arlington Hall under the War Powers Act to become their center for military intelligence and cryptanalysis, it was an all-female Junior College and boarding school.

A year later something like 2,500 civilians and 800 military staff had been assigned to the station. To put it another way, women codebreakers initially were signed on as lesser civilians, as men directly entered above them into the benefits, recognition and status of being military.

[Eunice Russell Willson Rice] joined the Office of Naval Intelligence as a language analyst in 1935 and transferred to OP-20-G—the Office of Naval Communication’s Code and Cipher Section—as a civilian cryptanalyst in 1939. During WWII, Rice led the team working Italian ciphers and codes, then learned enough Japanese on her own to lead the team charged with recovery and analysis of the vital Japanese Water Transport code.

The monotony of repetitive precision work with letters and numbers (likened to crossword puzzles), let alone huge patterns of tiny thread-like wires, was treated as women’s work and famously called computing. In all aspects of software and hardware, therefore, computers in America initially were being quietly developed and operated predominantly by women as credit flowed into the hands of men around them.

Ms. Blum was one of the pioneers in writing computer software at NSA. She led the effort to recruit Agency employees to learn how to program cryptanalytic techniques. She was aware of and taking advantage of the computer language FORTRAN at least three years before it became publicly available in 1957.

Official American history tells us that IBM released the first commercially available computer language “Formula Translation” (FORTRAN), giving credit to John Backus. Is that right? Probably not.

The NSA tells us instead half-a-century later that Dottie Blum was given a special role at IBM and was developing FORTRAN by 1954. Dottie had for years worked on U.S. Army BOMBE hardware for decoding Enigma, before she worked on the 1950 Standards Easter Automatic Computer (SEAC). Therefore her seasoned influence into FORTRAN is likely much larger than ever stated, just like her mostly unknown colleague Henriette Avram (who also wrote programs for the IBM 701) much later was credited only with developing MARC.

These are the giants of history we know a little about, leaving the large question of what the ghosted Black women of Arlington Hall accomplished that made their secrecy so important. Were they just trying to stay alive by never revealing what they knew about notoriously racist American private sector corporations who had backed Hitler, or trying to fit into a work environment that did little to prohibit or end racism?

According to [chief of the Russian plaintext exploitation branch in 1948] Jack Gurin, the critical need for clerical support prompted him to approach the personnel officer with a request for additional typists. He was told that “Code 1’s” were not available, but “Code 2’s” could be obtained. The coding, it was explained, was used on personnel records to designate race. “Code 1” was white; “Code 2” was “colored.” On the advice of the personnel officer, Gurin discussed with the existing branch personnel the possibility of bringing “Negroes” into the unit. One person, “a very dignified, good-looking Alabama lady, objected, stating that she could not ‘sit next to a colored person and work’.” Gurin relocated her desk…

Jack Gurin, anti-racist agent of change, stands as a good example of white men we should also hear more about.

But what were the names of all the Black women and what credit are they missing? The NSA notoriously built a reputation of hiring single young white women from the American south. I mean Black women apparently were instrumental in monitoring private sector companies during WWII yet afterwards we hear only about white women tasked and trusted with big IBM research roles…

I came to be interviewed at Arlington Hall in 1951, and there was a woman. I don’t know her name, but she was white… she vowed that I would not be ‘going down in the hole’… Most of the blacks at that time were assigned to the basement.

Have you read it?

Fatuous Howler: Elon Musk Biography by Isaacson “misleading and even flat wrong”

An impressively astute book review has been published on Defector.

He welcomes the return of a space race, not between rival superpowers, but between capitalists indulging in healthy competition “like that of the railway barons a century earlier.” This is fatuous in a familiar way, but also wrong: The American railway boom was 150 years ago, and brought about not by “competition” but continental-level corruption, kickbacks, bribes, and unfettered monopoly—all of it built on the backs of ruthlessly abused workers. (The injury rate at Tesla’s Fremont, Calif. facility, per a report from 2017, was 31 percent higher than the rest of the industry.)

Ouch.

The biography lacks basic truth about history.

Oh, but then it gets so much worse. The book lacks basic truth about the present, thus enabling fraud.

Even the release of Elon Musk was marred by one of Isaacson’s howlers. The biography was launched with a much-trumpeted “exclusive” published by CNN, Isaacson’s old haunt. The story, based on reporting in the book, detailed how Elon Musk personally ordered the Starlink internet service used by the Ukrainian army to be switched off as they prepared for a strike on a naval base in Russian-occupied Crimea. If you turned that upside down and tickled its tummy, it would still not resemble an exclusive. The details of the story had been reported six months prior by Oliver Carroll in the Economist, and were repeated by Ronan Farrow in the New Yorker in late August along with the tidbit, missed by Isaacson, that Musk may have turned off Starlink after speaking to Vladimir Putin.

Isaacson subsequently issued a correction (on Twitter, of all places), clarifying that the Ukrainians “asked Musk to enable [Starlink] for their drone sub attack on the Russian fleet. Musk did not enable it.” Musk himself is now on to a third version of this event—it’s hard to parse, but he blames U.S. sanctions—but whatever was claimed in the biography is now, by its own author’s own admission, apparently untrue

“Fatuous Hitler’s Turd Reich” was suggested to me by a predictive algorithm, as I started to type the word “howler” for the headline of this blog post.

The computer algorithm isn’t far off the mark. Accurate prediction.

Please read the very sharp book review in Defector instead of the fascism fluff book by Isaacson.

2023 Hot eBike Bakeoff: QuietKat Lynx vs Talaria xXx

I’ve been asked more and more to review eBikes coming online, so in the interest of time here’s a quick comparison of two that caught my eye:

2023 Lynx. Source: QuietKat

QuietKat Lynx (cafe moto) — $3,999

  • Motor: 1000W 2 Speed Hub Drive (Variable Power Output)
  • Range: 63mi
  • Battery: 20Ah/48V/960Wh
  • Power: 83Nm Torque/1440 Peak
  • Max load: 300lbs
  • Top Speed: 28mph
  • Weight: 100lbs
  • Regenerative: No
2023 xXx. Source: Sur Ronster

Talaria xXx (stunt) — €2.400 ($2,500)

  • Motor: Interior Permanent Magnet (IPM)
  • Range: 60k (40mi)
  • Battery: 40Ah/60V/2400Wh
  • Power: 45Nm Torque
  • Max load: 165lbs
  • Top Speed: 46mph
  • Weight: 125lbs
  • Regenerative: Yes

There are a ton of eBike reviews floating around already. They never seem to appeal to me, so maybe that’s why I’m being asked to add mine to the growing pile. I’ve not yet seen these two compared. Here goes:

A simple bake-off had a surprising result for me because the winner turned out opposite to first impressions:

  • Weight: Lynx 100lbs
  • Speed: xXx 46mph
  • Strength: Lynx 300lbs
  • Range: Lynx 63mi
  • Cost: xXx $2500

3 for the Lynx vs 2 for the xXx, and if I properly weight (pun not intended) the categories I care most about the Lynx is much further ahead.

I mean on first glance (maybe it was price tag) I felt the pull of a stupid-fast and light xXx. It’s powerful and nimble for fun rides, perhaps too much fun. I could see myself breaking it.

Where the Lynx shines is engineering for things more relevant to my interests: practicality, offering durability and distance. It hints at something more like “slow and steady” Dakar and much, much less at kids doing “endless burnouts in high school parking lots” or… *shudder*, white technocrats cruising Palo Alto.

Notably, the xXx has reliability issues with its motor cutting out without warning. That’s ok on fun rides, maybe. NOT acceptable for basically everything else. A dead 125lb bike at intersections or on trails… nope. Riding wheelies on the xXx and… ugh, why am I even looking at a bike marketed as xXx? Go away SEO bots.

When you’re ready for real life with responsibilities, the Lynx seems to be thinking about much more rational features for respectable long hauls (not the LOOOONG 200 mile haul of the new Buell but 63mi is plenty).

One nagging detail that kept me on the fence is regeneration of energy. Given the utility of eBikes for remote mountainous terrain (somehow I always end up on) a regen all the way down sounds great. Really great. Speaking of which, allegedly one of the reasons a xXx motor quits and requires reset is trying to regen over 90% causes thermal trouble. I’ll take a working engine over any regen one that abruptly quits, natch.

Even so, lack of any regen feels like oversight from QuietKat, especially given how they reference a Colorado mountain test environment and promote mountain this and that in their specs. Getting up to high elevation campsite is no bother if you know you have the option of charging back down.

As a final note, linking to a trailer seems like something Talaria doesn’t even think about, yet Lynx has a beefy cargo rack already setup behind the saddle and then offers options like their “Cargo Trailer”.

100lb capacity in a sizeable trailer is more than than enough for light Nextgen Anti-Tank Weapons. Source: QuietKat

If they spell cat with a K and they call a bike the Lynx, shouldn’t this be called something more creative like the “KatBox”? I’ll be here all week.

The cargo trailer doesn’t say it works well with NLAW mounts but you get the idea. QuietKat otherwise doesn’t hide the fact that they market towards “scout ahead” and the toughest “protect and serve” riders who “mount guns, bows, and more”. Remember their “Jeep” model? Maybe they should offer a decal set for riders to show how many helicopters downed or turrets popped? On a similar note their “Game Trailer” with the picture of a deer carcass doesn’t say it can be an ambulance gurney or extract wounded… but again, you get the idea.

Old side-car thinking ruins the anti-mine singletrack sensibilities of modern eBikes

All of this brings to mind military-grade engineering, regulated (in a good way) with long-term dependability for quiet professionals. The xXx however says race-to-the-bottom throwaway nuisance toy.

Between these two eBikes I might use an xXx for a few light-duty recreational trips, as a quick replacement for gas, but the Lynx seems far more likely to be the kind of infinitely useful bike I’d want to ride and ride and ride.