despera

For that kind of scope we are not talking just "some" more than 5000 but hundreds of thousands of soldiers, thus full invasion to a country twice the size and population of Afghanistan.

A tool can very well be broken thought or simply useless for anything but the most lightweight job (despite all the PR nonsense)

They call it a tool and so people leave reviews like any other tool.

History is filled with workers of any kind standing up, speaking politics as part of their unions, taking action as one and having the black sheep marginalized.

No, we won't be making games together. We are not in this together. We will never be.

You people really making things up. I understand, fake news comes with the culture. Let's just say goodbyes and best wishes for that chad fork.

Polarization like... staying tf away from racists, homophobics, genocide supporters and in general toxic people? Yeah, i guess that's the kinda of polarization that i can support. Majority or not.

How do you know what the majority wants or that even matters?

Simply because some sociopaths have stopped seeing themselves as active members of the society, doesn't necessarily make them neither a majority nor a healthy group of people.

To honor basic human rights is "poisoning"? That's some strong projection.

Nobody threatened your very obscured sense of free expression. They didn't ban them from the platform (even that would be discussable), they simply stopped interacting with a bunch of very weird and intolerant people. It's their right to ignore toxic people.

I cannot verify that this guy is a contributor to Godot. Nothing shows up on his main github account relevant to godot. Only with that new fork.

Don't get me wrong, Godot did ban few accounts. Those totally weird hecklers who made issues and PR's trolling against basic human rights.

Again, if you have a proof of a ban campaign of ACTUAL contributors, please show it.

Do you have a proof for that?

Oh come on it's not such a big brain moment the fact that there are more quality elements involved for projects beyond a license that someone would take in account. I'm pretty sure you can think many just by yourself but elude you at this moment for "reasons" that have exactly to do with sympathizing with the main developer or contributors.

Now that the location of the supposed "attack by stalker" has been geolocated by someone affiliated to Bellingcat[1] and obviously that (if ever happened) had nothing to do with services or bots that share aviation public data; can we move past the, arguably naively made, smokescreen and ask what this supposed to disorient us from?

I mean, the hypocrisy of using a jet plane instead of driving for 40 minutes in your "environmental green" car is a thing[2], but shouldn't be enough to randomly ban journalists.

[1]https://twitter.com/EliotHiggins/status/1603454821700452365 [2]https://nypost.com/2022/08/22/elon-musk-planes-9-minute-35-m...

https://twitter.com/pragmaticml/status/1411113232048218119

So yeah, sorry for those who believe that it's going to return some "purely algorithmic" code and won't just randomly copying code.

Also, https://twitter.com/mitsuhiko/status/1410886329924194309

Wow, just wow... this has to be regulated FAST.

Image caption triggered my greek cheese-seller's nerves. Those are not "slabs of feta cheese" shown but mizithra or anthotyro.

https://en.wikipedia.org/wiki/Anthotyros

Now for the important part. Region locking is completely idiotic. If i was living abroad, i wouldn't dare to buy, for example, imported greek feta. White cheese is not the kind that matures. They are very delicate has to stay fresh. Surely there must be standards of HOW a certain kind of cheese is made but not where.

Sure, people beaten, imprisoned and murdered trying to improve working rights, eight hour work etc but let's trivialize all that to childish terminology (cringe) and argument (bad apple).

Because being "100% employee" and having no free time is SO MUCH FREEDOM and as it is already public knowledge, "work sets you free".

But, i know, those few dicks. Not. The. Company.

Right, such few damn dicks also happened to keep active relations with the Third Reich supporting the logistics of the concentration camps.

Never a company policy, just those few bad people giving it a bad name...

Since when parts of the kernel are governed differently than other parts? It is code _within_ the official kernel, not some module in a dark alley git server at IBM.

The real question is Linus OK with the project being separate feuds with different (corporate) rules instead of a single community

No, the manager obviously talking about "hobby" email and being 24h/day employee (slave) so this has nothing to do with the day work of the certain programmer.

Shameful and regressive corporate tactics. This is part of the main kernel source code, not some private module. This is obviously against any sense of openness and inclusive development process. If a certain person has something to offer that is technically correct, must be able to do so in any secure way he wants.

This is plain face control.

Oh no no i didn't mean that it's happening because of/for the immigration. Just saying that European Union is already in honeymoon with the far right so such policies are only to be expected.

Well, it has been only few months since when a ""study"" released, ordered by the EU parliament, where the authors were asking for a european firewall similar to the chinese one.

Between drowning refugees and immigrants in Mediterranean sea, shooting them at the borders and throwing whoever survive in concentration camps, it's only logical to go after the local dissidents too.

I do agree with the premises, i don't agree with your conclusion.

Yes only a part of patches would be marked as such. That, major or minor, part would simply mean that people won't have to reinvent the particular wheel, as happened in this case. People won't be missing critical _discovered_ changes, the vulnerability would be discussed, recognized in its totality (PoC, documentation etc) and proper patches will be offered. There have been cases where LTS backports were old revisions of bad patches.

I think that baking LTS kernels is unnecessarily closer to an artistic approach of doing things.

How is no marking better than some marking?

If there is a commit that refers to a "memory leak" why shouldn't be, at least superfluously, checked, identified and have distros informed? (e.g 2ca068be09bf8e285036603823696140026dcbe7)

If the crypto fix was assigned early as a vulnerability would have stayed unpatched for that long?

I understand that completely and i already know your thoughts on that and in some extend i do agree.

Still, i think we do have in hand a very characteristic issue that even without knowing the details, simply by searching commit messages for "crypto" "key" "buffer" etc it should alert somebody to give it a second and third look.

While RedHat's backporting might not be great, i believe that upstream would do good if they would change their mind about having or not a well defined vulnerability identification and notification system.

It's understandable that almost every piece of kernel code could potentially be a bad actor thus it would be tough to identify if every fix has security implications or not.

Still there must be a middle ground around common exploitation methods.

Of course it does involve frequency, "again" can either mean something that's happening very often OR something that stopped happening and started again.

It's a matter of corporate strategy and has nothing to do with each worker.

Considering that the browser choice UI first "neglected" and then removed from Windows we can safely call this another EU bubble.

"Again"? When did they stop? You mean that hypocritical "MS loves Linux" stuff while their partners are digging the grave for FOSS like in Munich?

Package maintainers have far, far worse problems to deal with than some shell scripts that are trivial most of the time for alternative init systems like openRC. Also, hopefully, no maintainer in his (security-wise) right mind use upstream provided system files as-is.