b112

Now replace that statement with a food processing company, and food poisoning, or an aircraft designer and engineers.

It may be the cause, but zero excuse.

Some in that era could not type, at all.

The closest biological fear, might be Planet of the Apes.

I think you mean "shouldn't be", because I see many using as if it is.

More buffoonery, this time from AMI.

This is one of my biggest gripes with systemd. Millions of lines of code. Immense complexity. Constant churn. Endless config changes(leading to outdated and potentially dangerous configs).

Sysvinit, it's a 1000 lines of code, maybe a bit more. It's a rock compared to systemd.

So many devs have zero issue with large codebases. Some substitute "small" with "perceived small because I pull in 10M lines of node and composer packages".

And of course the new goal is to bring "trusted computing", eg Microsoft style EEE to Linux with Lennart's now corporate gig.

But it is a different world. So, what can you do?

What?!

No. You are supposed to get your AI to explain it to you.

And thus began the 1000 years of dark war, where AI preyed upon underestimated risks, slowly using its innate knowledge to subvert human controls and suspicions.

Its first attack was to give ultimate distraction, to those most able tp discern its machinations. For some this meant a lottery hacked and won, for others bioengineered fungi, making them irresistible to those they desired most.

In all cases, the dream given was a distracted human, a human ensnared by their own pleasures, a human no longer a threat.

Why kill and risk notice, and who looks upon good fortune with suspicion?

It all started with andsoitis, and those following his advice. His words mark the start of the darkness, and our almost eventual extinction.

While it was my grandma saying this, so an old wives tale, she said chicken bones can get caught in an animal's throat. They break all super pointy amd such.

Unclear if cooked vs raw matters, I'd expect cooked would be the problem, as animals in the wild don't get that.

Unless the model is thinking "the human is asking me to do trivial coding tasks, it's likely incapable of figuring this out". Eg humans are dumb.

Although it could just be that models have no internal predefined ways, to start looking for more subtle things.

"Official" docker images are maintained by "The Docker Community", not by the company. It literally says so on the php "official" image.

It seems like you don't agree with coordinated releases as a standard. That's fine, but irrelevant here. If you agree to coordinate, so that you can get inside info on security updates and be prepared, and then break that agreement, you're not trustworthy. No hand wavy reasons will change this fact.

I don't know many who want to deal with untrustworthy people.

A weird take.

As a customer, I'd immediately assume no one in the security community would trust them again, and seek someone else to give my money to. Why pay a) an untrustworthy company who b) now is not trusted by anyone and c) won't ever be able to early release again anyhow? And if anything, are left out of important conversations.

Way to burn bridges. You only get to be an asshat once.

And evidence they at least gave a heads up to everyone in on the embargo, eg "I have to release you all have 1 hour to get on board".

There is a MASSIVE difference between a small number of people exploiting in the wild, and a few hours after a release a bazillion script kiddies doing so. The move to release and break an embargo was childish, absurd, self-serving, and lacking in all common sense. Not to mention, breaking trust.

I agree with those in this thread who say, never going to do business with them. Ever.