Right-wingers are so reliably sore winners. X is still comfortably the dominant microblogging platform on the internet, Facebook and Youtube happily boost and feed right-wing content and concerns. Tiktok has been brought to heel. ATproto hasn't found a way to encode communism - just like activitypub could be used for Truth Social - the ATmosphere will turn right once the ecosystem is in anyway relevant politically or commercially. But you could always start quatrechan while we wait
This is a misreading of the bug. It is from upstream stable kernels before 6.5 that include commit 91562895f803 but not 936e114a245b6[1].
In this case Debian's current process is good - it's kernels track kernel.org stable releases. This debian bug is responsibly flagging "for visibility" that a serious bug has been discussed and fixed upstream.
Linux Virtualization Based Security (LVBS) is an umbrella term under which we can offer various hypervisor backed kernel protection solutions. This is a common hypervisor agnostic extendable architecture in Linux kernel that can be used by any hypervisor to implement and extend Linux kernel protections. Different hypervisor frameworks (Hyper-V as an example of type-1 hypervisor and KVM as an example of type-2 hypervisor) can plug into the common layer to harden the Linux kernel.
Hypervisor-Enforced Kernel Integrity (Heki):
Heki is a proof-of-concept that implements new KVM features (extended page tracking, MBEC support, CR pinning) and defines a new API to protect guest VMs. It is designed to be merged with the mainline project. It is inspired from other private implementations currently in use (e.g. Windows's Virtual Secure Mode), but our approach is tailored to Linux specificities.
The example doesnt seem to support your argument. The rationale the developer gives here is reasonable and looks like good stewardship of a shared library - the patch added a new API that was tightly based on termites' needs and provided little benefit for other terminal programs. What the maintainer wanted was a more complete API for the feature. The termite dev said he did not want to implement this feature in the library. This is also reasonable. Its his code and his time. So we have two people who can't find/commit to a solution everyone is happy with. It doesn't really seem user hostile at all, just that something couldnt be worked out. Sure, its frustrating when its an app you really like, but sometimes interests wont align even when it seems from the outside like they should.
This misrepresents what happens if you use busybox in your product and don't comply with the license (posting a buildable version of your changes) - they first try and negotiate compliance before starting litigation. You won't get served papers until you refuse to comply with the license. This includes giving you time to fix the situation - https://sfconservancy.org/copyleft-compliance/principles.htm...
I mean this is basically all politics - who should suffer and how much to keep society running. I don't think you'll find a progressive monopoly on that