Yeah... thats the one I would like. But as I said, my current htpc is good enough to play steam games on.

edit: Nevermind... this is their handheld gaming device. I don't want one of those. I was thinking of the new livingroom gaming box..

I'd like to buy one, but not at that price.

I will wait for the price to come back down, and probably lose interest before it does -my current htpc does a good enough job of gaming for my needs.

I do not see those words in the summary above.

I did not say "evil" nor did I say it was illegal. I said it was abusive.
-If they do in fact upstream the fixes (as you assert) then it is not abusive.

These capabilities will be offered through commercial subscriptions, allowing enterprises to integrate secure patches directly into their existing software supply chains with enterprise-grade validation and lifecycle management.

Selling security patches as a subscription service instead of submitting them upstream to fix the problems for all users.

An abominable abuse of open source.

"Is it insider trading if the AI does it?"

Asking for a friend...

"It is better that a hundred guilty men escape than that one innocent suffer." -Blackstone
"Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety." -Franklin ...

Shall I go on, or do you get the concept?

Yes. Those are ALL gambling. Even the stock market. Owning stock is fractional ownership of a business; the stock market is gambling on the future value of a stock. Some gambling is legal, taxed and regulated.

Vulnerability. They keep using that word. I do not think it means what they think it means.

A real vulnerability can be exploited. Flaws in code, may be vulnerabilities, or they may not be. Until they are proven exploitable, they are lower priority. Still worth fixing... as time allows.

Delete? No. No one is freed from the system. Marked as a threat to national security, denied employment, travel, housing, banking, etc. But still tracked and logged. Even prisoners have IDs.

Draw on the stored energy from when the sun was shining and the wind was blowing. There are these things called "batteries" that you may have heard of....

or

Rely on "the grid" to transport power from where the sun is shining or the wind is blowing to where you need to consume it. The sun is always shing somewhere, and the wind is always blowing somewhere. Blows your mind eh? Witchcraft! Sorcery! Technology!

The "worst case scenario" was never likely. Neither was the "best case scenario" likely.

It was always going to be somewhere in the middle.

Life is gonna suck for a whole lot of the world. Humanity will survive. Life will go on. We can still choose just how bad we are going to make it. How many of us survive. How we live. How many other species survive. How many don't.

Google is feeding their AI-search the entered text. It is interpreting the "disregard" as an instruction to "disregard what I just said". So it aborts. With a polite response.

Ha ha. anyway...

It is not possible. The update happens instantly on the local node, but how long it will take to propagate to all systems is a guess.

Best practice would be to warn the user that updates may take time to propagate, but not to give a promised completion time for an uncertain process.

Propagation delays in an auth table did not cause the keys to leak.

The root cause remains the root cause, whether it is accidentally posting the keys on your github repository or a disgruntled former employee acting maliciously.

I once pushed a BGP update with an error in it. I caught it right away and pushed a correction. But thanks to propagation delays... it caused problems for hours. Lesson learned.