California has 11.3% of America’s population — but bought 30% of America’s new zero-emission vehicles. That’s according to figures from the California Air Resources Board, which also reports 1 in 4 Californians have chosen a zero-emission car over a gas-powered one… for the last two years in a row.

But what about chargers? It turns out that California now has 48% more public and “shared” private EV chargers than the number of gasoline nozzles. (California has 178,000 public and “shared” private EV chargers, versus about 120,000 gas nozzles.) And beyond that public network, there’s more than 700,000 Level 2 chargers installed in single-family California homes, according to the California Energy Commission.

Of the 178,000 public/”shared” private chargers, “Over 162,000 are Level 2 chargers,” according to an announcement from the governor’s office, while nearly 17,000 are fast chargers. (A chart shows a 41% jump in 2024 — though the EV news site Electrek notes that of the 73,537 chargers added in 2024, nearly 38,000 are newly installed, while the other 35,554 were already plugged in before 2024 but just recently identified.)

California approved a $1.4 billion investment plan in December to expand zero-emission transportation infrastructure. The plan funds projects like the Fast Charge California Project, which has earmarked $55 million of funding to install DC fast chargers at businesses and publicly accessible locations.

Read more of this story at Slashdot.

QLED TV manufacturers have dug themselves into a hole.

After years of companies promising that their quantum dot light-emitting diode TVs use quantum dots (QDs) to boost color, some industry watchers and consumers have recently started questioning whether QLED TVs use QDs at all. Lawsuits have been filed, accusing companies like TCL of using misleading language about whether their QLED TVs actually use QDs.

In this article, we’ll break down why new conspiracy theories about QLED TVs are probably overblown. We’ll also explore why misleading marketing from TV brands is responsible for customer doubt and how it all sets a bad precedent for the future of high-end displays, including OLED TVs and monitors.

Read full article

Comments

The Certification Authority/Browser Forum “is a cross-industry group that works together to develop minimum requirements for TLS certificates,” writes Google’s Security blog. And earlier this month two proposals from Google’s forward-looking roadmap “became required practices in the CA/Browser Forum Baseline Requirements,” improving the security and agility of TLS connections…

Multi-Perspective Issuance Corroboration
Before issuing a certificate to a website, a Certification Authority (CA) must verify the requestor legitimately controls the domain whose name will be represented in the certificate. This process is referred to as “domain control validation” and there are several well-defined methods that can be used. For example, a CA can specify a random value to be placed on a website, and then perform a check to verify the value’s presence has been published by the certificate requestor.

Despite the existing domain control validation requirements defined by the CA/Browser Forum, peer-reviewed research authored by the Center for Information Technology Policy of Princeton University and others highlighted the risk of Border Gateway Protocol (BGP) attacks and prefix-hijacking resulting in fraudulently issued certificates. This risk was not merely theoretical, as it was demonstrated that attackers successfully exploited this vulnerability on numerous occasions, with just one of these attacks resulting in approximately $2 million dollars of direct losses.

The Chrome Root Program led a work team of ecosystem participants, which culminated in a CA/Browser Forum Ballot to require adoption of MPIC via Ballot SC-067. The ballot received unanimous support from organizations who participated in voting. Beginning March 15, 2025, CAs issuing publicly-trusted certificates must now rely on MPIC as part of their certificate issuance process. Some of these CAs are relying on the Open MPIC Project to ensure their implementations are robust and consistent with ecosystem expectations…

Linting

Linting refers to the automated process of analyzing X.509 certificates to detect and prevent errors, inconsistencies, and non-compliance with requirements and industry standards. Linting ensures certificates are well-formatted and include the necessary data for their intended use, such as website authentication. Linting can expose the use of weak or obsolete cryptographic algorithms and other known insecure practices, improving overall security… The ballot received unanimous support from organizations who participated in voting. Beginning March 15, 2025, CAs issuing publicly-trusted certificates must now rely on linting as part of their certificate issuance process.

Linting also improves interoperability, according to the blog post, and helps reduce the risk of non-compliance with standards that can result in certificates being “mis-issued”.

And coming up, weak domain control validation methods (currently permitted by the CA/Browser Forum TLS Baseline Requirements) will be prohibited beginning July 15, 2025.

“Looking forward, we’re excited to explore a reimagined Web PKI and Chrome Root Program with even stronger security assurances for the web as we navigate the transition to post-quantum cryptography.”

Read more of this story at Slashdot.

“The big set of open-source graphics driver updates for Linux 6.15 have been merged,” writes Phoronix, “but Linux creator Linus Torvalds isn’t particularly happy with the pull request.”

The new “hdrtest” code is for the Intel Xe kernel driver and is around trying to help ensure the Direct Rendering Manager header files are self-contained and pass kernel-doc tests — basic maintenance checks on the included DRM header files to ensure they are all in good shape.

But Torvalds accused the code of not only slowing down the full-kernel builds, but also leaving behind “random” files for dependencies “that then make the source tree nasty,” reports Tom’s Hardware:

While Torvalds was disturbed by the code that was impacting the latest Linux kernel, beginning his post with a “Grr,” he remained precise in his objections to it. “I did the pull, resolved the (trivial) conflicts, but I notice that this ended up containing the disgusting ‘hdrtest’ crap that (a) slows down the build because it’s done for a regular allmodconfig build rather than be some simple thing that you guys can run as needed (b) also leaves random ‘hdrtest’ turds around in the include directories,” he wrote.

Torvalds went on to state that he had previously complained about this issue, and inquired why the hdr testing is being done as a regular part of the build. Moreover, he highlighted that the resulting ‘turds’ were breaking filename completion. Torvalds underlined this point — and his disgust — by stating, “this thing needs to *die*.” In a shot of advice to fellow Linux developers, Torvalds said, “If you want to do that hdrtest thing, do it as part of your *own* checks. Don’t make everybody else see that disgusting thing….”
He then noted that he had decided to mark hdrtest as broken for now, to prevent its inclusion in regular builds.

As of Saturday, all of the DRM-Next code had made it into Linux 6.15 Git, notes Phoronix. “But Linus Torvalds is expecting all this ‘hdrtest’ mess to be cleaned up.”

Read more of this story at Slashdot.

“Microsoft built things. It broke things.”
That’s how the Seattle Times kicks off a series of articles celebrating Microsoft’s 50th anniversary — adding that Microsoft also gave some people “a lucrative retirement early in their lives, and their own stories to tell.”

What did they remember from Microsoft’s earliest days?

Scott Oki joined Microsoft as employee no. 121. The company was small; Gates was hands-on, and hard to please. “One of his favorite phrases was ‘that’s the stupidest thing I’ve ever heard,'” Oki says. “He didn’t use that on me, so I feel pretty good about that.”

Another, kinder phrase that pops to Oki’s mind when discussing the international division he founded at Microsoft is “bringing home the bacon.” An obsession with rapid revenue growth permeated Microsoft in those early days. Oki was about three weeks into the job as marketing manager when he presented a global expansion plan to Gates. “Had I done business internationally before? No,” Oki said. “Do I speak a language other than English? No.” But Gates gave Oki a $1 million budget to found the international division and sell Microsoft products overseas.

He established subsidiaries in the most important markets at the time: Japan, United Kingdom, Germany and France. And, because he had a few bucks left over, Australia. “Of the initial subsidiaries we started, every single one of them was profitable in its first year,” he says…

Oki left Microsoft on March 1, 1992, 10 years to the day after he was hired.

Other memories shared by early Microsoft employees:

One recent graudate remembered her parents in Spokane saying “I think that’s Mary and Bill Gates’ son’s company. If that kid is anything like those two, that is going to be a great company,'” She got her first job at Microsoft in 1992 — and 33 years later, she’s a senior director at Microsoft Philanthropies.

The Times also interviewed one of Microsoft’s first lawyers, who remembers that “The day the U.S. government sued Microsoft … that was a tough day for me. It kind of turned my world upside down for about the next eight years.”
Microsoft senior VP Brad Chase remembers negotiating with the Rolling Stones for the rights to their song “Start Me Up” for the Windows 95 ad campaign. (“Chase is quick to dispel any rumor that Mick Jagger called up Bill Gates and got $12 million. But he won’t say how much the company paid.”)

But Chase does tell the Times that Bill Gates “used to say all of the time, ‘We’re going to bet the company on Windows.’ That was a huge bet because Windows, frankly, was a lousy product in its early days.”

Read more of this story at Slashdot.

What happens when you ask Copilot to “write a program that can be run on an iPhone 16 to select 15 random photos from the phone, tint them to random colors, and display the photos on the phone”?

That’s what TouchDevelop did for the long-discontinued Windows Phone in a 2013 Microsoft Research ‘SmartSynth’ natural language code generation demo. (“Write scripts by tapping on the screen.”)

Long-time Slashdot reader theodp reports on what happens when, 14 years later, you pose the same question to Copilot:

“You’ll get lots of code and caveats from Copilot, but nothing that you can execute as is. (Compare that to the functioning 10 lines of code TouchDevelop program). It’s a good reminder that just because GenAI can generate code, it doesn’t necessarily mean it will generate the least amount of code, the most understandable or appropriate code for the requestor, or code that runs unchanged and produces the desired results.
theodp also reminds us that TouchDevelop “was (like BASIC) abandoned by Microsoft…”

Interestingly, a Microsoft Research video from CS Education Week 2011 shows enthusiastic Washington high school students participating in an hour-long TouchDevelop coding lesson and demonstrating the apps they created that tapped into music, photos, the Internet, and yes, even their phone’s functionality. This shows how lacking iPhone and Android still are today as far as easy programmability-for-the-masses goes. (When asked, Copilot replied that Apple’s Shortcuts app wasn’t up to the task).

Read more of this story at Slashdot.