Oh yeah, not saying that anybody using the word is a racist. Just ignorant, you shouldn’t use it if you are aware of its historical context.

Ah I see, yeah I guess something like that would be possible. On the other hand it would be trivial to prove this happened even in the future as long as the government keeps a unedited copy of this repo.

While true, a git history is also easily protected against fabrication. Require cryptographically signed commits and prevent contributors from force-pushing to the public repo and you should be good.

In Germany there is a legally recognised form of volunteering called Ehrenamt (honorary office), mostly used by non-profit organisations. It has benefits for taxes, gaining public funding, and such. E.g. if you are the primary caretaker of an elderly family member you can get unemployment benefits without having to look for work, since it is recognised as a public good.

The petition aims to recognise work on Open Source software as such an honorary office.

Thus using “race” is biologically ambiguous and “ethnic groups” should be preferred, however it is still very well socially defined.

“Ethnic group” is an anthropological category, not a biological one. The correct biological term is “subspecies”, which Wikipedia defines as “populations that live in different areas and vary in size, shape, or other physical characteristics (morphology), but that can successfully interbreed.”

Using “race” in a social context makes sense and is far from being racist.

Given the history of its usage in that context, I have to vehemently disagree. Plus it is so ill defined that it is a useless term anyway. From Wikipedia again: “[…] various definitions exist. Sometimes it is used to denote a level below that of subspecies, while at other times it is used as a synonym for subspecies.”

Using it invokes all the Social Darwinism and whatnot that the Nazis and others abused it for. So where is the sense in using it exactly?

Bash shell uses readline for this, which I would guess is the namesake of PSReadLine:

https://wiki.archlinux.org/title/Readline
https://man.archlinux.org/man/readline.3#DEFAULT_KEY_BINDINGS

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

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)

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.

There are rights and responsibilities associated with a proprietary model… and IMO you (and your permissive government) should not be overriding those rights for your own short-sighted benefit.

Kind of sounds like you misunderstood the initiative to be honest. This only affects games which have been abandoned by the developer, the proprietary model stays perfectly intact as long as you actually keep selling your games.

Ross is just doing PR basically, you can see the legal organisers of the petition here: https://citizens-initiative.europa.eu/initiatives/details/2024/000007_en

deleted by creator

Meh, essentially it’s just writing “Telecommunicationsourcesurveillance” as a single word without the spaces to indicate it’s a singular thing being referred to (in this case the concept of directly listening on the source device before encryption happens). Might seem weird I guess, but you get used to it pretty quickly.

https://de.wikipedia.org/wiki/Telekommunikationsüberwachung#Quellen-Telekommunikationsüberwachung

It means “telecommunication source surveillance”.

Well I for one (not GP) am actually quite glad that it is literally illegal to publicly display here in Germany, especially with the current political climate going on here and elsewhere. You want to just out yourself as a Nazi? Okay, off to prison you go. That’s good. AFAIK there are exemptions for temples and such, e.g. for artistic uses like Games, some Wolfenstein games replaced swastikas in the German release because nobody was sure if that’s legal.

I don’t think it is actually illegal to display in any country that has a lot of people using it religiously, but yeah it’s a sad fact that it still has to be illegal in so many places such a long time later.

I guess he means cruel as opposed to “accidental”. He’s trying to make clear that it happens deliberately.

This particular Russian attack seems to have been retaliatory in nature, because right before it Ukraine attacked Russian territory including Moscow with hundreds of drones at the same time.

Reported on here for example: https://www.youtube.com/watch?v=NBAIalMNCAA
And here: https://www.youtube.com/watch?v=5NbxXJJJNZk

I figure the logic of escalation here is something like “If Ukraine can already make massive strikes on Moscow with self produced drones there isn’t much sense in keeping up the range restrictions on NATO equipment anymore”.

Hmm, the thumbnail change doesn’t seem to have federated to lemmy.ml or other instances (so far at least), but it shows on lemmy.ca. Interesting. Thanks for updating it.