ntauthority

The 'fake error messages to thwart crackers' thing is pretty relatable - I think back in my day I went with 'early-exit trap (#23)' or the likes for this type of error condition. It does help that we didn't have any phone support - numbers would potentially be painful that way! Another common one I see is dictionary words though even something neutral like 'anteater' or 'weasel' or 'high-jig-south' can both be frustrating to see as a user as well as when trying to deal with support for the inevitable case an integrity check fails on real systems...

i like how this is a side effect of a bunch of assorted changes in a commit and PR solely described as "Fix path resolving" making it hard for anyone running Gitea to even know this is a security fix

warioware shows it can be fun though but i'd indeed not like to see that applied to safety-critical tasks

> because this policy only applies for non-security bugfixes, and almost all patches these days claim to just be security fixes, including the one which introduced this bug

There's numerous feature flags that seem to just be 'MSRC_[id]' (for the Microsoft Security Response Center), and anecdotally looking through Windows 11 a lot of actual bugfixes (various ReFS driver crashes, for example, have feature flag checks around their fixes) are feature-flagged as per usual with both global (for the whole batch of fixes) and per-feature flags, so this is a bit of an incorrect assumption.

Things breaking downlevel is pretty common anyway, and the emoji picker has been in a pretty bad state since the original picker IME (introduced I believe in RS3, ~2017) was replaced with 'Expressive Input' which also allowed adding GIFs and a few other things but relied on a new UI framework that I suspect was tied to an unrelated internal effort culminating in the '10X' product which only got canceled.. right before Windows 11 development started, and therefore pretty much bitrotted.

Windows 10 was left on a fairly 'bad' release, the 'Iron' semester which was used as a baseline for Server 2022 was still like 10 from a UX perspective (10X was only canceled between that and 'Cobalt', where the Sun Valley work which led to the Windows 11 product happened) but had a fair few bugfixes that didn't get backported to 10 'version 2004' ('Vibranium', I believe, as otherwise the codename would've been 'Chromium' which is bad).

The reserved memory would show up as 'dedicated' memory. Shared is just the amount of host memory that can be assigned to graphics resources, which usually equals the system memory or some amount derived from it.

If the full amount of system memory isn't showing on Windows that's likely an unrelated issue you're experiencing (for example with UEFI/BIOS memory mapping mismatching whatever else) and it working on Linux implies that either Linux gets fed different memory layouts or it parses this broken case fine unlike Windows.

If applications aren't using all the memory, and it's also not showing up as cached, that's odd as Windows usually tends to target around 80% of physical memory usage (unless you're really not using that many apps or there's another driver issue going on). Different OSes account for memory usage differently, and there's rarely one single 'memory used' indicator in modern operating systems.

Notably so, I believe Trillian was a paid product and Meebo was actually treated like a real tech startup. Interesting, indeed, how much the sentiment has shifted over the course of 10-15 years...

Qualcomm actually started offering LTS (long-term support) BSP (board support packages) to device manufacturers for a fee. This is why some vendors like Samsung and Microsoft started providing updates for phones with older SoCs for longer than usual: they're paying the additional per-product license fee for being allowed to ship updated firmware.

Many fiber ISPs here in Europe seem to share the backend infrastructure between DSL and FTTH subscribers and that sadly also involves PPPoE encapsulation.

I actually switched away from a UDM after finding out that I could only hit 500 Mbit/s uplink (out of ~930) due to a PPPoE performance bug as there's no hardware offloading and the old Cortex-A57 cores (in a SoC from a vendor now owned by Amazon, so extremely end-of-life) just couldn't handle that.

Now I'm running a Turris Omnia with the bundled OpenWRT fork for router tasks and that seems to work fine.

FYI: OpenWRT is just Linux and will run fine on x86 hardware as well.

> I don't have much choice - it's not like there would be five competing apps serving the same purpose (connecting to the people and communities on Facebook).

The same legislation that is requiring Apple to allow sideloading also requires other large players (like Meta) to open their communication platforms up to other service or application developers.

In this hypothetical case, there actually would be five competing apps, some even still distributed on the App Store.

It was introduced in Vista, deprecated for external use a bit later but the servicing system is still a heavy user of it.

Titanfall did work this way on the EA launcher. There was a tool that it'd run on first launch to decompress the compressed audio files.