This goes back to the days of AOL chat rooms, where they shut down forums for breast cancer survivors because they said “breast”.

https://www.chicagotribune.com/1995/12/02/america-online-admits-error-in-banning-word-breast/

Woo hoo!

Fascists lie.

As a reminder, Eich was turfed from Mozilla for joining an anti-LGBT hate campaign (and thus alienating a whole lot of developers, sponsors, and users); and his So Brave browser pushed NFTs and stole money via referral fraud.

Congratulations … you’ve trained a generation of junior product managers.

First step: Find a country with a navy competent to defend your undersea cables.

Case in point, Microsoft’s water use shot up from 6.4 million cubic meters in 2022 to 7.8 in 2023, in large part due to the “construction of more data centers.”

By way of comparison, the California almond industry uses 3.5 billion cubic meters of water per year. Describing datacenters as using “astronomical amounts of water” is a plain and simple lie.

Moreover, datacenters can be cooled with water that’s not suitable for most other uses. Google’s Finland datacenter is cooled with seawater, for example.

You’re currently a Trump supporter. If you don’t want to be one, you can stop.

A war crime occurred when Hamas put a military installation in a civilian hospital.

Once that happened, attacking the hospital to get at the military base is not itself a war crime.

You might wish it was, but that’s not what the law says.

Remember, streaming only has a business model as long as it has a better user experience than piracy. That’s why iTunes took off in the era of Napster. When a streaming service’s user experience drops below that of digging up pirate treasure off a shitty ad-ridden torrent site, that service is not long for the world.

Headphone jacks are not little. They take up a huge amount of board space on a device that people want to be small and light. They’re also fragile and they open up a big hole for crud to get in.

Since 2017 at least; and IIRC years before that; that’s just the earliest NIST publication on the subject I could find with a trivial Web search.

https://pages.nist.gov/800-63-3/sp800-63b.html

Verifiers SHOULD NOT impose other composition rules (e.g., requiring mixtures of different character types or prohibiting consecutively repeated characters) for memorized secrets. Verifiers SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically). However, verifiers SHALL force a change if there is evidence of compromise of the authenticator.

“Memorized secrets” means classic passwords, i.e. a one-factor authentication through a shared secret presumed to be known to only the right person.