![](https://lemmy.world/pictrs/image/603e8cc2-aa23-4c50-9f24-24e8712ae87d.jpeg)
![](https://lemmy.world/pictrs/image/41e39366-cb91-4d4a-bc07-a47621cb7d5f.jpeg)
Well not with that headline but maybe, with a bit of effort, the same message can become oniony.
“Far-right decides to finally bite the bullet and just behead political rivals.”
Probably other ways too, I’m just lazy lol
Well not with that headline but maybe, with a bit of effort, the same message can become oniony.
“Far-right decides to finally bite the bullet and just behead political rivals.”
Probably other ways too, I’m just lazy lol
From what I understand you always want to keep accidentals as close to their note as you can to decrease chances to misread the notation.
Oh the joys of my apartment AC breaking
So you have a product that you’ve made into a system for getting answers. And then you couldn’t be bothered to try and sanitize training data enough to get your answer system’s new headline feature from spreading blatantly incorrect information? If it doesn’t work, maybe don’t ship it.
Not anymore! twitter.com
now redirects to x.com
. There’s nothing left.
Seen a concerningly large amount of companies calling things they don’t like “unconstitutional” lately.
Heyyyy I know about the Noid!
I’m not saying incomprehensible build scripts are good here, my mistake for making it seem that way. I’m not confident that hiding it elsewhere would have been strictly more obvious but it absolutely could have been.
I’ve done some pretty complex C projects and haven’t had build scripts nearly that large. This one seems particularly unwieldy and certainly helped the attacker.
I’m going to be honest, I’m getting a little tired of hearing everyone’s thoughts on the xz backdoor. It’s discouraging and sucks when every detail of the project which, keep in mind, was maintained by one person who fell victim to a social engineering attack, is scrutinized. It makes me concerned about anyone depending on any of my projects.
Especially the comments on things such as the build scripts, which this kind of article seems to gravitate towards. If the build scripts were tiny and checked then the attack vector would have just been different, I’m not even too sure the language mattered. The attack was social engineering, after that it was pretty much project agnostic. xz was targeted cause the maintainer was done working on it and it was heavily depended on.
Such a fucking vile thing to read while starting my morning