Muehe

duuuuuude you need to airgap that shit.

ive got an isolated vlan with its own access point only accessed by my work laptop

That's not an air gap. "VLAN" already implies you have a direct physical connection between the networks, and "access point" implies you are using wireless LAN on top which is the literal opposite of an air gap.

I found AutoKey but that seems more focused on Text Input and doesn’t seem to support launching scripts individually (altouigh it has a Window Filter).

I'm not sure what exactly you mean by this, but AutoKey has Python scripting built in and an extensive API:

https://github.com/autokey/autokey/wiki/Scripting

And from a Python script you can launch any other script/program you want with a subprocess library call.

You have been at war since the January 6th beerhall putsch attempt. It's just that one side didn't realise and didn't even put your new dictator into a luxury prison first before letting him get re-elected. Rookie mistake honestly.

To preempt the common interpretation of hackers as criminals.

a low latency kernel (whatever that means. I’ll get there to figure it out eventually)

It's a kernel with real-time process scheduling enabled by default.

In normal kernels a process can theoretically block all other processes from running for up to several seconds, which is obviously bad for time sensitive things like audio recordings or controlling a CNC-machine for example.

In real-time scheduling all processes are guaranteed time slices in more regular intervals. This is good for time sensitive things like audio recording, but since there is some scheduling overhead it's bad for single resource intensive processes or process trees like video games.

You can read more about the difference between a real time and low latency kernel here: https://help.ubuntu.com/community/UbuntuStudio/RealTimeKernel

• Breaking "DRM" in Polish trains – Reverse engineering a train to analyze a suspicious malfunction (2023)
• We've not been trained for this: life after the Newag DRM disclosure (2024)

The "hackers" (specialists who had been hired by the train owner) presented their findings and the manufacturers reaction on the last two chaos communication congresses if you want to hear their side of the story directly:

• Breaking "DRM" in Polish trains – Reverse engineering a train to analyze a suspicious malfunction (2023)
• We've not been trained for this: life after the Newag DRM disclosure (2024)

The "hackers" (specialists hired by the train owner) presented their findings and the manufacturers reaction on the last two chaos communication congresses if you want to hear their side of the story directly:

• Breaking "DRM" in Polish trains – Reverse engineering a train to analyze a suspicious malfunction (2023)
• We've not been trained for this: life after the Newag DRM disclosure (2024)

[...] "And you are an alarmist. You are saying that this must lead to this, and you can’t prove it. These are the beginnings, yes; but how do you know for sure when you don’t know the end, and how do you know, or even surmise, the end? On the one hand, your enemies, the law, the regime, the Party, intimidate you. On the other, your colleagues pooh-pooh you as pessimistic or even neurotic. You are left with your close friends, who are, naturally, people who have always thought as you have.

"But your friends are fewer now. Some have drifted off somewhere or submerged themselves in their work. You no longer see as many as you did at meetings or gatherings. Informal groups become smaller; attendance drops off in little organizations, and the organizations themselves wither. Now, in small gatherings of your oldest friends, you feel that you are talking to yourselves, that you are isolated from the reality of things. This weakens your confidence still further and serves as a further deterrent to—to what? It is clearer all the time that, if you are going to do anything, you must make an occasion to do it, and then you are obviously a troublemaker. So you wait, and you wait.

"But the one great shocking occasion, when tens or hundreds or thousands will join with you, never comes. That’s the difficulty. If the last and worst act of the whole regime had come immediately after the first and smallest, thousands, yes, millions would have been sufficiently shocked—if, let us say, the gassing of the Jews in ’43 had come immediately after the ‘German Firm’ stickers on the windows of non-Jewish shops in ’33. But of course this isn’t the way it happens. In between come all the hundreds of little steps, some of them imperceptible, each of them preparing you not to be shocked by the next. Step C is not so much worse than Step B, and, if you did not make a stand at Step B, why should you at Step C? And so on to Step D.

"And one day, too late, your principles, if you were ever sensible of them, all rush in upon you. The burden of self-deception has grown too heavy, and some minor incident, in my case my little boy, hardly more than a baby, saying ‘Jewish swine,’ collapses it all at once, and you see that everything, everything, has changed and changed completely under your nose. [...]

Excerpt from the book They Thought They Were Free: The Germans, 1933-45 by Milton Mayer. Longer excerpt available here.

Kemp et al. 2022 - Climate Endgame: Exploring catastrophic climate change scenarios

TL;DR: Societal collapse seems possible, more research is needed.

Again the git history does not seem to agree with this. If you compare the history of analog_controller.cpp for example in duckstation and swanstation you will find that the in-file license header was added 3 years ago while the latest common change between the files is from 4 years ago. In other words swanstation is using a version of the source code from before the license change, not removing the license change.

If you have any source for these accusations please post it, because as you have relayed them so far they seem to be untrue.

That's simply untrue, duckstation changed license from GPL3 to CC on September 1st 2024, while swanstation retains the original GPL3 license from September 11th 2019.

So the beef is that they kept using the code as they were before the license change, which is their right under the original GPL3 license.

~~If anything is legally questionable here it is the duckstation re-licensing to CC because the author of duckstation is not the author of PRs made before the change to CC, thus they might not have the legal right to change the license to those parts of the code without the assent of the individual PR authors (in most jurisdictions I'm aware of at least). I didn't see any Contributor License Agreement in the repo, which would be the usual way to acquire this assent.~~

Edit: Context somebody posted upthread. They rewrote parts of the code and got some contributors to agree to the license change. Remains unclear if that covers everything even to the author apparently, but fair enough I guess.