GranPC

That reminds me of the Richards Tip episode from Nathan for You, in which, in order to fulfill a legal requirement for a name change, they started printing a newspaper called The Diarrhea Times.

Flash didn't use JS, but rather ActionScript. Which was very much inspired by ECMAScript, especially AS3 -- but Flash's security holes were all of Adobe's doing. Good times.

Did you work on BB10?

It's more of a gut feeling than anything else. I don't know what the normalization rules are, but I think we mostly notice the normalizer when it mangles something [1], and not when it's just quietly humming along. Someone with more spare time could probably figure out a dataset of original to normalized titles and measure that.

[1]: Example from the frontpage right now: "How Big Are Factorials?" probably got normalized to "Big Are Factorials?" originally, based off other previous manglings I have seen previously.

In its (admittedly weak) defense, if the submitter edits the title back during the few-minute window after submitting where this is possible, the normalizer does not kick back in. But it is a bit opaque, in the sense that the poster needs to: realize that the title has been changed; know that they can edit the title (but not too slow!); and know that it won't be filtered through again.

I have no idea what the website would look like without it, but I have a feeling it does more good than harm.

I believe the "This" might have gotten swallowed by HN's title normalizer.

I am trying very hard to find an original version of this cipher with no luck. It almost sounds like this whole thing is a hallucination...? Can anyone point me to a PDF of the original Cyphral Distich as printed?

Couldn't you put !.gitignore et al in your global config file?

FWIW, the Original version looks misaligned on my Linux phone running Firefox. Fixed is, well, fixed.

It means they rebased all their changes on top of the new version. This is usually time-consuming because AOSP is not developed in the open, so you can't do this incrementally as things change -- you just get a massive drop sometime after release.

No, they got it booting on bare metal a few posts down.

Previously: https://news.ycombinator.com/item?id=9690703

You should probs edit out the spoiler, or encode it somehow for others who haven't watched it yet!

It was bundled with XP.

Wrong link. https://news.ycombinator.com/item?id=48039362

What does that have to do with Americans specifically?

Sorry for the off-topic, but I was curious about Affectable so I opened the website. I saw it's very thin and light and comfortable, but I struggled to find out what "it" is and what it does for me. It's kinda buried.

I was interested enough to click through the different links in the footer. And just as I reached the purchase page, I see that it requires "an iPhone running iOS". Unsure why it requires an iPhone; and no info on a timeline for iPhone-less customers. But that immediately rules me out as a customer.

I feel like the landing page would be a lot better if it started out focusing on what it is & how it can help me.

Apologies again for the unsolicited advice. Just wanted to share my impressions in case it's helpful.

Just for what it's worth, I just pushed an eBPF-based workaround for people who are running kernels in which AF_ALG is linked directly into the kernel and not as a module: https://github.com/Dabbleam/CVE-2026-31431-mitigation

I am running this in production right now and it mitigates the attack, with no unexpected side-effects as far as I can see.

I don't think RustDesk was hit by this. If you weren't able to access it two weeks ago, it was due to an outage on their end: https://github.com/rustdesk/uptime/issues/53

By Microsoft’s convention, that would be a way to run Windows 9x on Linux. It’s a bit confusing. Another example is “Windows Subsystem for Android”, which is what they use for running Android apps on Windows. I think the idea is that it’s not a “Windows Subsystem” for X, but rather a Windows “Subsystem for X”.

(Edited: mixed it up on the last sentence.)

No? WSL is Linux on Windows — so W9xSL is Linux on Windows 9x. I think… :)

I think this is it: https://reg.redsara.es/#login

Well, in that case, if they want full control and attestation yadda yadda, I'm fine with them shipping me a device they fully control exclusively for use of this stuff. But if we're talking about my smartphone that I paid for with my money that I worked for, I will do whatever I damn please with it. So I guess that means eIDAS will be inaccessible to me.

I didn’t know that, thanks for letting me know. I don’t think I logged out, unless maybe I accidentally triggered that in my pocket.

I figured it was worth posting because I get relatively uneasy when unexpected things happen, and if others were also affected then I could just justify it to myself as a server side thing. In fact, what you just told me about logout being global is already very helpful, so I guess it wasn’t for naught. :)

I hadn’t checked how long the cookie is set for yet. But since I got logged out from both devices on the same day, I figured it can’t be that. I haven’t had this tablet for too long, and I think I must have signed in just 2-3 months ago. Thanks for your response!

I think they meant employees from the hosting company. But that's a funny interpretation!

> The efficiency is a red herring - you will still use every CPU core for IO threads in ffmpeg, if you don't configure that away, which you do not. And it requires really annoying setup and premium features on stuff like Plex. It just makes no sense!

I would love to learn more about this! What can I do to fully optimize ffmpeg hardware encoding?

My use case is transcoding a massive media library to AV1 for the space gains. I am aware this comes with a slight drop in quality (which I would also be keen to learn about how to minimize), but so far, in my testing, GPU encoding has been the fastest/most efficient, especially with Nvidia cards.