Our Three Lawsuits Against Microsofters Are About to Become a Lot More Relevant to GNU/Linux
Microsoft 'kill switch' installed by Matthew J. Garrett - in the face of resistance from Linus Torvalds (whom Garrett would later defame a lot) - as explained a few hours ago (also in Microsoft's MSN):
To be clear, I never chose to do this. Nor did my wife. But they started it. We had to respond. It has now been exactly a week since we took on the dangerously violent Serial Strangler from Microsoft - almost a year after we had taken on his litigation buddy Garrett [1, 2] of "secure boot" infamy. I prepared a ~200-page document to illuminate how they work together with the exact same legal team, sending my wife and I over 5 kilograms of legal papers like drunken SLAPPers (the word "drunken" goes a long way and isn't just a metaphor). This week I separately spoke to two women at the Court. They work there. They were rather shocked to learn that violent Americans who attack women weaponised the dockets here in the UK to harass not only me but also my wife. They're attacking their own victims as well as reporters. Apparently SFC (in FOSSY 2025) deems such grotesque individuals "safe" enough for public events, which says a lot about SFC and FOSSY. The SFC connection was covered here before.
Regarding Garrett, around the time he needs to fly to the UK to defend himself in the UK High Court we expect that many GNU/Linux PCs will simply stop working. They won't boot [0]. That's timely, as it will help us present to the Judge examples of the global, widespread harms done by Garrett. The Master will easily understand why Garrett has been attacking me since 2012. I correctly predicted what Garrett's sabotage would lead to. So he kept defaming, stalking, harassing me, even 24/7 for a number of years. Yes, he stalked me 24/7 in my own network; that's a morbid obsession. He also did likely illegal things in IRC, set aside the motivations. He also lied to the Court already and showed disrespect for the process. I explained this to another Master last month - it was in the Hearing about the Serial Strangler from Microsoft. Their barrister loves to casually lie to judges about it. They try to cover up their own misconduct, knowing they are still under investigation by British authorities, which communicated to me about that yesterday.
I very much look forward to the trials. It'll help expose what those people did to us, then we can seek full compensation. We can pursue people "up the chain" (including Directors of phantom companies or friends who help fund the SLAPPs).
Regarding the proof of motivation, and quoting [0]: "A new key was issued in 2023, but it might not be well-supported ahead of the original key's expiration."
It's not an "oops"; it's a design decision.
In simple terms, millions of GNU/Linux user will be prevented from booting into GNU/Linux and that's because Microsoft remotely (and secretly) controls their machines. Thanks, Garrett! It's not like it didn't happen before. Microsoft embraced the mentality of drug dealers and now uses as catspaw anyone who is himself a drug fanatic, including the Ontario Criminal and the two people above. They may attempt - as they did before - to leverage their own insanity to disclaim responsibility, but that won't work in the UK High Court. British law isn't exactly lenient if you're an addict or autistic or cut your own body parts. It treats everyone equally, unlike this dreadful law firm that does not filter clients.
Microsoft is in a truly terrible shape right now, and that's not limited to Windows [1]. "It's difficult to work when you're looking at a graveyard" [2].
That Microsoft is sabotaging PCs of people who don't even use Windows is a scandal in the making or a ticking time bomb. I'll be more than happy to bring up this issue in the UK High Court; it'll be extremely relevant to the lawsuits we lodged last year. █
Related/contextual items from the news:
-
Microsoft's Secure Boot UEFI bootloader signing key expires in September, posing problems for Linux users
That leaves operating system distributors with a decision to make: omitting Secure Boot support entirely; expecting users to generate and sign their own keys; or finding a way to use the Microsoft-controlled db, dbx, and KEK to enable Secure Boot in their own systems. NetBSD, OpenBSD, and some of their more esoteric counterparts settled on the first option, while some Linux distributions and FreeBSD opted for the third by using a "shim" to build their Secure Boot support on top of Microsoft's infrastructure.
-
ZeniMax employees discuss chaos of Microsoft's "inhumane" mass layoffs in new report
ZeniMax employees have spoken out following Microsoft's mass layoffs impacting over 9000 employees at the company, calling the process - which reportedly saw "hundreds" of colleagues at the studio lose their jobs - "inhumane".
"It's not okay. It wasn't normal," senior QA tester Autumn Mitchell told Game Developer. "I don't care how many times [Microsoft lays off people] to try and make it seem normal - it's not. The way they do it is inhumane. I don't care how much they say that it's dignified or they want to do it in a respectful way - it's not."
This month's mass layoffs - which impacted numerous Xbox studios including Rare, Turn 10, The Initiative, and Raven Software - were accompanied by multiple project cancellations, and marked the third round of significant job cuts at the company since 2023.
-
ZeniMax staff lambast chaotic Xbox layoffs: 'It's difficult to work when you're looking at a graveyard'
It has been around three weeks since Microsoft laid off a reported 9,000 workers, including many within its video game division, and multiple employees at the company's ZeniMax Media subsidiary have spoken out to explain how that chaotic day unfolded and detail the struggles of adapting to a new normal after yet another debilitating round of cuts at the Xbox maker.
Microsoft's decision to force people out of the door hasn't just caused widespread upheaval and emotional distress—but, as some employees tell us, will also hamper the productivity of those left behind.
Correction: Sadly, as a typo or an unfortunate Freudian slip, I somehow managed to confuse SFLC with SFC. And perhaps that makes a key point: that's why the trademark lawsuit is warranted. SFC is piggybacking the good name of SFLC and its people try to convert this confusion into money ("FSFE" likewise). "Has SFLC gone bad?" one person asked. No, I meant to type SFC. It was an error. I thought of SFC and typed in the wrong acronym. The person said "annotation is probably needed in addition to correction in case people have already read the wrong version". I am now correcting it while also expanding the full acronym. Software Freedom Conservancy is the parasite, SFLC is the "real thing". Software Freedom Conservancy is associating with the serial harasser and serial defamer. It is trying to destabilising decent activism to the detriment of the FSF, sometimes to the benefit of GAFAM (Google is a top sponsor of FOSSY).