> 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...
Anecdotal point of data: M247 seems to run a lot of bad-faith traffic as well - while a service I run tries to keep block lists minimal even for frequently abused endpoints (eg credential stuffing) their ASNs are a mainstay in there.
Piracy and such hoarding are inextricably intertwined. If you want a particularly uncommon variant of some pirate content (like an obscure movie in any quality, or a somewhat popular movie in original BD format), you better grab it when it's available, as further down the line getting the exact same such content may be more and more difficult.
Streaming services have a similar issue (re-encoding, bad rereleases due to licensing issues, delistings, crappy format choices in the first place) but generally a bit better SLA-like and a longer timeframe to watch certain content.