duskwuff

Another candidate would be the DOJ ending attempts at school desegregation:

https://www.nytimes.com/2026/09/24/us/politics/justice-depar...

Perl also has "until" as the inverse of "while".

(It'll also let you use "unless ... else ..." - but please don't.)

Most of those models were not sold concurrently. The Apple II, II+, and IIe each replaced the previous model; the same was true of the IIc and IIc Plus. "//e" was an alternate textual rendering of IIe, not a separate model.

The most Apple II models that were sold concurrently were the IIe Platinum, IIc Plus, and IIgs. (And this was around 1990, at which point there were far more models of Macintosh computers on the market.)

The chatbot sidebar seems to also be the only way of accessing certain Amazon features, like the price history. And it seems to be implemented in a particularly silly way - clicking the "price history" button prompts the chatbot to show you the price history, rather than just showing it.

Thank you. Yes - that's where I was going with this. It was certainly possible to use computers for long-form writing in the early 1980s, but it wasn't a particularly economical or practical way of going about it. Some people did, but they were in it more for the novelty than practicality.

Not even "most" of Europe - almost all European languages use diacritics to some extent or another. In the context of domain names, some words are comprehensible with the diacritics stripped, but there's some loss of precision. (For instance, an "ñ" is critical if you're trying to say "happy new year" in Spanish...)

... might sound like a reasonable solution until you start trying to write about languages. It is unreasonable for a sentence like "In Japanese, the word for 'hello' is こんにちは; in Korean, it's 안녕하세요." to be unrepresentable.

Neuromancer was written between 1981 and 1984. The personal computers that existed at that time were poorly suited to writing; using one to write a novel would have been a deliberate and rather unusual choice.

(Consider, for example, that the first chapter of Neuromancer alone would have exceeded the stock memory capacity of many personal computers at the time, at ~46 kB.)

Internally, sure. But the application that was (probably) compromised was an FTP client, so it would have received the plain text of those passwords from users as they logged in.

Reading the tea leaves: given that the outage started with "connectivity issues affecting the File Manager", which was an install of Monsta FTP [1] - a commercial PHP application - I suspect the file manager got popped by one of the recently published PHP vulnerabilities, and users' FTP credentials may have been exfiltrated.

[1]: https://www.monstaftp.com/

I don't think the DVI-A connector was ever widely used for analog video input. Devices which supported analog video input almost universally did so using a VGA connector.

The analog pins on the DVI connector were used on many video cards for output, but they were mostly there so that you could use a DVI-to-VGA adapter, not because there were many devices which could use it directly from that pinout.

And? Having boatloads of money doesn't make you any smarter or better at making business decisions.

And even when a fire truck responds to a house fire (for example), they may still potentially need to treat and/or evacuate people who have been injured in the fire. Cross-training firefighters so that they can do both makes sense.

Is it possible that these are real people who are unwell? I can imagine a situation where users who spend a lot of time (like, to an obsessive degree) viewing and commenting on regional content start getting recommendations for more similar posts, regardless of whether it's local to them not. If there's enough users like this - and I'm sure there are - Facebook might even start treating them as a demographic, effectively creating a sort of self-organizing trolling group.

Players of classic roguelike games? ;)

GPLv3 added language which specifically requires that GPLv3 software embedded in products be distributed with "Installation Information" explaining how modified versions of that software can be installed. It is not at all clear how this would apply to software in an immutable, signed system volume. This language was not present in GPLv2.

https://www.gnu.org/licenses/gpl-3.0.en.html#section6

(There are other issues with GPLv3 which make it a dubious choice for companies like Apple, but this one is particularly problematic.)

That's a bit of an exaggeration. Domain-validated certificates already existed, and were fairly commonplace, before Let's Encrypt. What was different about LE was that their certificates were free.

Most independent site owners couldn't obtain an EV certificate even if they wanted to - the process effectively requires that the applicant be a business.

Anyone who has done any work with hardware can confirm that neither of these things is ever true. :(

> Apple doesn’t want to distribute them

Apple can't distribute them - coreutils is GPLv3, which is incompatible with Apple's immutable system volume.

Probably not, then. The /pkg hierarchy on macOS doesn't look like that at all - there's no /pkg/bin, only /pkg/env/global/bin, where /pkg/env/global is a symlink to a subdirectory of /pkg/inv/envs.

Does pkgsrc use the env, etc, inv, and var subdirectories of /pkg seen here?

And the Public Suffix List didn't even attempt to handle .name.

https://github.com/publicsuffix/list/issues/2306

In domain registration parlance, that is the registry (e.g. Verisign for .com). A registrar is one of the companies which intermediates between the registry and the users who obtain domain registrations (e.g. GoDaddy).

> this one is close to my heart.

That sounds dangerous - you should probably see a doctor. ;)

It's left fairly ambiguous by Frank Herbert's books. The Jihad is implied to have taken place over ten thousand years before the beginning of Dune - it's ancient history to everyone involved*, so it's only natural that the details are a little hazy.

*: except Leto II, and he doesn't say much about it

> TLS 1.0’s CBC chaining made IVs predictable and enabled the BEAST attack. That’s a documented protocol weakness, allegedly put in there by US state actors on purpose.

This is errant nonsense. At the time SSL/TLS were designed, using CBC with block ciphers was generally considered best practice - it was not at all an unusual choice.

You did, in fact, read a different story. You're thinking of the story told in the books by Brian Herbert and KJA - which were a distinctly pulpier take on the Dune universe than Frank Herbert's.

That could be a valid suspicion if the RNG chosen was particularly obscure. drand48 isn't - it's part of the standard C library.

Doubly so if they were motorized toys, so when the motors kicked in, the battery voltage would droop and make the pitch shift even more...