tredre3

> They recompiled it for EVERY kernel release of every supported distribution (they had never heard of DPMS apparently)

Neither have I, I think you goofed up on your acronyms? For a driver as embedded as crowdstrike you need to recompile, there's no other way around it. Linux doesn't provide anything stable to target and a shim won't cut it in this case.

> the service ran as root, it UPDATED ITS OWN BINARIES as root!

Would you prefer if Linux allowed local users to replace the kernel and/or its modules without root? What kind of faux-outrage is this?

That is a fun exercise! However the reality is that public IPv6 is always given out in 48 or 64 bits prefixes (minimum).

The math is a lot less impressive when you do it with 2^48 or 2^64.

In theory IPv6 solves the problem by putting all of this under a single prefix (fc00::/8) and asking nicely that implementation/admins add 40 random bits to form their prefix. Which is plenty to prevent (almost all) eventual conflicts.

The thing is, asking nicely doesn't always work. Sure, automated tools like docker/incus/wireguard/tailscale will respect it. But admins who don't want to be stuck typing long addresses? Not so much. I've lost count of how often I encounter a network admin that manually set their prefix to some fcXX::, when it's not outright fc00::.

Of course you can (and should) blame this on admins and not on IPv6, but then the same could be said of IPv4 where adding entropy to 10.X.X.0 is the usual recommended way of doing things.

What else would you use to power the configuration gui frontend? Allow me to eliminate some of the obvious and inevitable answers:

- Rust didn't exist at the time

- Go didn't exist at the time

- nodejs didn't exist at the time

- Java and Python likely used too much resources for a once-in-a-while used GUI

Irrational hatred aside, that's literally what PHP was designed for.

The baseline is: I want a burger and I don't want to cook it (or I enjoy this particular restaurant's recipe).

That's it. The comparison is indeed burger delivery vs drive-through/takeout. Cooking is irrelevant in the equation.

Unless they meant vaguely similar code (which I can't judge), the only mentions of mupdf are in the AI instructions:

    > **The Opportunity:** Capturing the high-growth enterprise AI engineering market by replacing bloated, slow Python extraction pipelines (`Unstructured.io`, `Docling`, `Marker`, `LlamaParse`, `PyMuPDF4LLM`) with a pure-Rust, sub-10ms, multi-format ingestion kernel.
    - This structure guarantees that if we ever swap the PDF engine to `pdfium` or `mupdf`, not a single line of business logic in `paperpilot-core` or CLI tools will need to be rewritten.
    > Directly captures the high-growth AI Engineering & RAG pipeline market (displacing bloated Python stacks like Docling, Marker, PyMuPDF4LLM, and Camelot) with sub-10ms, pure-Rust, on-device parsing.
    | A.2.5 | `MuPdfBackend` adapter (Future) | Use MuPDF for OCR-heavy workflows via FFI |

That is likely the point, but it's clearly phrased deliberately poorly to elicit a specific interpretation from viewers.

"The Dune books were all about islam, the movies are not; Today I will analyze what was lost in translation and why they did it!" doesn't have the same ring to it than "ISLAM IS BEING ERASED BY HOLLYWOOD!"

If only management was to blame, we wouldn't see the AI spam in the open-source world.

The fact that we do proves that ICs are equally to blame, because evidently the majority of them love using AI.

I disagree with your use of the word zealot but I agree, MS Office is objectively the best office suite. I no longer use it daily, but anybody arguing otherwise has: never used it, never tried the alternatives to see how bad it can be, doesn't do collaborative work, or doesn't need any features beyond bold/italic. For example I can do most of my coding in Notepad, but it's still a very inferior experience. I feel the same way about MS Office vs LibreOffice.

That being said let's keep in mind that the latest wave of moving-away-from-MS-Office is using OnlyOffice this time and I believe it might work. OnlyOffice actually wants to entice MS Office users. And thus it is more compatible, has a much closer/better UX, and despite being a web app it is somehow more responsive than LibreOffice.

> It's not easily defeated by the default setup. Quite the contrary, the default setups are great. Typical apache + mod_php is the easiest to exploit.

But apache + mod_php hasn't been the default setup for a very long time, that's what people are trying to tell you. Given your expertise, you must know that already. So I have to conclude that you're arguing in bad faith because it's the only setup you can break.

All webservers (apache, nginx, litespeed, caddy) have keep-alive enabled by default. All browsers also support it. Whether it's actually used/negotiated on most connections, I don't know, and if you want to be pedantic you're right that it can't be default by definition since you need the header to use it. But I suspect it actually is used for most connections nowadays.

Multiplexing is the default in HTTP/2 and 3. So you're still wrong.

Assuming your phone cannot be trivially unlocked by a thief, it likely is safer to bank on it than on a computer.

Because unless your desktop is dedicated to banking, there's always the chance that one of your other activities will install malware. If you don't use FDE (the majority of people) and you saved your banking password in the browser rather than a password manager (likely a scary amount of people), then theft is also an issue.

Neither of those things are really a problem on a mobile device.