MrDOS

Doubtful. Doom was fully software-rendered. Quake, maybe?

All the numbers were under 256. Surely they did.

Yes, as I understand it, this sort of problem is what “Name Constraints”[0] were designed to solve. (Well, really, they were intended to be used with corporate internal CAs[1], but there's no reason they wouldn't work more broadly, too.)

[0]: https://www.rfc-editor.org/info/rfc5280/#section-4.2.1.10 [1]: https://utcc.utoronto.ca/~cks/space/blog/tech/TLSInternalCAN...

I imagine, too, that as better encoders become available, we'll be able to losslessly recompress existing JXLs, much as mozjpeg's jpegtran can losslessly recompress existing JPEGs.

Right. Although the article demonstrates the changes by making requests of a public web server, I would imagine this change has been primarily motivated by a desire to reduce overhead and latency on internal communication between microservices, which very often uses unencrypted HTTP/1 traffic.

Once upon a time, AliExpress had a really bad reputation for missing packages. I imagine they ramped up the notifications to help repair their reputation.

Right. The “correct” way for a service to handle this is to disable password logins for any account that has enrolled a passkey. A few services do this, but boy howdy is it ever unfriendly to users (or at best, difficult for them to get their heads around).

And the frequent delivery status updates make sure that I am very aware how much time the parcel sits around waiting to clear customs, too.

Nah, it's Firefox, not the ad blocker. I run into similar problems all the time, and disabling my ad blocker never solves it. If you pop open the developer console and look for errors, it usually boils down to Firefox having stricter policies about cross-origin requests. Even major web properties simply don't bother testing for even the most superficial functionality on browser engines other than Blink any more.

I think it's extremely likely that all these major websites are built specifically to work with Google Chrome, and I would call that “broken”, yes.

> AMD designed Bulldozer with a very long pipeline, betting they could sacrifice efficiency per clock cycle in exchange for extraordinarily high clock speeds

It blows my mind that AMD watched Intel try to do basically the same thing only a few years prior with NetBurst, and fail so badly that they had to scrap that entire evolutionary branch and start over – and AMD still went and did it again themselves anyway.

> so I gave that all to Claude

Damn. I have really enjoyed reading Doug Brown's past reverse-engineering and repair work (e.g., Chumby resuscitation). Shame to see another one fall to brain offloading.

Parent is thinking iOS/iPadOS, not macOS. Older devices that are not capable of running iOS 26 are still receiving security updates for iOS 18, but any device supported by iOS 26 is not. It's a real hard push by Apple to get people to swallow Liquid Glass by withholding security updates.

I had one of those to charge a bicycle headlight. I gave it away with the bicycle, but in the span of time I had it, one visiting guest borrowed it to recharge a portable generic USB battery pack. So there you go, two product categories known to use that sort of cable!

Well, you can do 3.5 Mbps ADSL over wet string[0], which is about 5 channels of uncompressed 16-bit PCM at 44.1 KHz.

[0]: https://www.revk.uk/2017/12/its-official-adsl-works-over-wet...

“Terrible inefficient workflows”, like having to prompt Claude to change one or two words in a file rather than just manually editing it, because it gets confused when the file changes out from under it and will later overwrite the changes?

Are very many of them time travellers?

Technically, “unified memory” is where both the GPU and CPU have access to the RAM over the same bus, which is different from the older, reviled “shared memory”, where the RAM was always at least one bus hop away from the GPU. But yes, there is a certain amount of spin to it, isn't there? (“You have less total memory now, and that's a Good Thing!”)

And “donated money” here means “his donations amounted to 72% of the party's entire 2025 revenue”[0].

[0]: https://www.flamman.se/techprofil-ger-miljoner-till-orebropa...

For those who haven't made the connection, Cockos, the company who make REAPER, is run by Justin Frankel, previously the founder of Nullsoft, the company who made Winamp. REAPER very much carries the Winamp torch of robust, resource-efficient software, and in the 15 or so years I've used it as a hobbyist, I don't think I've ever lost any work due to the software's fault.

My understanding is that the Qt 6 build system is vastly easier to work with.

Also, Audacity is not the first major FOSS project to successfully migrate from wxWidgets to Qt: Dolphin, the GameCube/Wii emulator, made a similar migration several years ago[0][1][2][3].

[0]: https://dolphin-emu.org/blog/2017/06/03/dolphin-progress-rep...

[1]: https://dolphin-emu.org/blog/2018/02/03/dolphin-progress-rep...

[2]: https://dolphin-emu.org/blog/2018/05/02/legend-dolphin-lens-...

[3]: https://dolphin-emu.org/blog/2018/07/06/dolphin-progress-rep...

> plain old epubs

Kobo devices ship two different rendering engines: the obsolete, appallingly bad Adobe Reader Mobile SDK (RMSDK), and their own, bespoke, WebKit-based renderer. By default, files with an .epub extension are rendered with RMSDK. Consequently, you'll get all sorts of weird issues. Some of the ones I've encountered: I've had cover images not displaying in the library, misbehaving internal links (footnotes), inability to override typefaces/text size.

Easy fix: rename the file to .kepub.epub[0].

Slightly more involved fix: run the file through Kepubify[1] first. This tool makes further tweaks to the books to enable a few other features, like remaining read time estimation.

[0]: https://github.com/kobolabs/epub-spec#sideloading-for-testin...

[1]: https://pgaskin.net/kepubify/

As a broke teenager, I came to have a G400 much later on in its lifecycle (c. 2007-2008). It did indeed have amazing analogue output quality (kids these days think VGA is inherently blurry, but it can be pretty much indistinguishable from DVI/HDMI if your graphics adapter has a good RAMDAC and you connect the monitor with a high-quality cable). However, my experience with the 3D drivers was pretty consistently terrible. I suspect the card was getting much less QA attention by that point, because one driver release would have broken OpenGL support, the next would break Direct3D, and so on. Very obviously not consumer-focused cards. I remember it extremely fondly nonetheless! Multi-monitor support was not common then, and that card was extremely formative to my lifelong thirst for desktop real estate.

> 8 character alpha

Good thing “xn--zp9h” fits, then.

> the battery drained too fast

I think this problem was unique to the 12 mini. I remember hearing a lot of people complain about it at the time, and I haven't experienced anything like it with my 13 mini (which I upgraded to from a six-year-old 1st-gen SE, so clearly my usage is not typical; YMMV).

Thank you, that forum post carries all the explanation I was looking for.

Handy for those four people left who want to author DVDs, but this is extremely light on details.

How does it compare to the venerable HCenc[0]?

Why does the VideoLAN x262 project page[1], the source for which hasn't moved since 2015, also link to a 404 wiki page in this Git repository?

It looks like perhaps this is an old repo which has recently been rebased onto a newer (but still not particularly new) revision of x264. It is very unfortunate that whoever did the rebase did not retain the original author dates (perhaps even having gone out of their way to --reset-author-date).

0: http://hank315.nl/

1: https://www.videolan.org/developers/x262.html

Historically, in a world of analogue phone lines, spoofed phone numbers were a legitimate feature: if my business has more than one phone line, each of those lines is going to have its own distinct number; but I'm going to want outgoing calls from any of those lines to appear to originate from the same number (the one that I put on my promotional material, invoices, etc.).

Much the same as e-mail, identity within the phone system was, historically, entirely built on trust (because only Ma Bell could make configuration changes, and they could verify that what their customer was asking them to do was legit). Those assumptions were carried through deregulation, and are very deeply entrenched in the technical design of the network. Changing them will hopefully become easier over the next few years as analogue service is turned off entirely (e.g., BT/OR in the UK are set to turn off all analogue phone service by the end of January 2027).

Ah, interesting. Searching the dataset for my local area, this seems to include some restaurants, but omits hotels entirely. That's skewing the numbers downward tremendously.

> the messages are confusing > while being frankly obnoxious

Try reading some time. It's pretty great.

> the Ctrl+C handling is just utterly broken

That's your terminal, not parallel.

> and all of the delays

Your terminal is adding the delay, not parallel. parallel is just warning you about your broken terminal. You're shooting the messenger here.