I have Debian on my servers for a decade or so, and on several workstations. My past experience doesn’t quite reflect that. The Debian guys and gals have always been pretty quick with patching the vulnerabilities. Like outstanding fast.

There is some merit to the bugfixing. But that’s kind of the point of Debian Stable(?!) Like in the meme picture of this post I don’t want updates each day. And I also don’t want the software on my servers to change too much on their own. I know my bugs and have already dealt with them and I’m happy that it now works seamlessly for 6 months or so…

And that’s also why I have Debian Testing on my computer. That gives me sort of an unofficial rolling distro. With lots of updates and bugfixes. I mean in the end you can’t have no updates and lots of updates at the same time. It’s either - or. And we can choose depending on the use-case. (I think the blame is on the admin if they choose a wrong tool for a task.)

Meh. No Flatpak, no worries. And no updates, no new software or security patches.

Well, the money wasn’t “seized” and having jewish members doen’t necessarily have anything to do with the business decision. It could, but we don’t know. Could also be the case this protest group filed the wrong paperwork / chose the wrong legal status for their organization and just breached contract. Also a single bank (despite being publicly owned) isn’t Germany.

So the words “Germany” and “Seizing” are wrong. “Jews” is speculation. I’m fine with the words “Is” “Money,” “again”.

10 points for the clickbaity title.

Going brrr since 1984?

Good call. I’ve added this as a feature request: https://github.com/TeamPiped/lemmy-piped-link-bot/issues/252

Hehe. Yeah I meant per default, everything is copyrighted. So it’d fall back to being restricted and thus “not allowing anything”… If the wording doesn’t hold up… I’m not really in the position to judge this. Could be very well the case that once somebody touches it, it’s not “this” product anymore and it’s no longer covered. Or taking just parts of it is also not “this product”. Or a copy. I can imagine that something like that is the reason why other licenses go on and on talking about modified versions and copies etc… But I’m really not a lawyer and you’re right with being creative with things. I did not intend to be too negative 🤗

I think it’s the other way around, however… You need to word it so your users can enforce it against you even if you yourself become malicious. Otherwise you’re not really allowing them anything. And for that you’d need to word it so it doesn’t depend on your interpretation, but on theirs. And it’d need to hold up in court for them. So the language needs to be specific and with well-defined words. Every bit of vagueness it the user’s problem and limits/restricts them.

I thought the main problem was that it’s debatable whether you can enforce it. So it harms users and distributions because they can’t really rely on it.

But the liability would definitely be another issue. I think the law is different here in Europe, so the liability might already be included for my hobby tinkering per default and I don’t need to worry.

And something else is: I’d include trademark… force people to choose a different name for their project if they take my code so there is no confusion and people can’t upload versions with advertisements on some software store.

Uh, just don’t mistake it for a license. It’s funny and I like to put my stuff under WTFPL. But in recent times I feel it’s appropriate to point out that you sometimes don’t do your users a favor by being silly (if it’s useful code.)

What’s the pun?

Let me scroll through your phone, see if there are some nice pictures or chats, the google search history, browser history… Uuh what’s that Lovense Buttplug App for? Do you have any medical conditions or mental health struggles? How do you approach people on Tinder? What’s your salary?