ckastner

oh, I missed that. Brilliant!

This, exactly. For example, cheating is a strategy. If cheating gets an agent to the goal faster than the other strategies, what's so surprising about the agent picking that strategy?

The problem is indeed alignment.

> Are you saying people haven’t been throwing unneeded GPU capacity on the market? That is happening.

That, by itself, doesn't have to mean anything.

AWS is far more compute capacity than Amazon needs, but that's not because Amazon misjudged how much capacity they need. They built it out to sell it to others, leveraging know-how and economies of scale to do so very profitably.

Note that we are still in the discussion period, and more proposals can and will be added. Some might even be withdrawn.

The death knell was Elop announcing that Nokia would be exclusively Windows, at a time when Windows had low single-digit market share and where this exclusivity was a one-way street. Other major manufacturers continued to ship Windows phones, and they did that in parallel to their main Android line.

I never understood what the end game here was. If they had wanted market dominance based on someone else's OS, they could have just used the well-established Android. There was little to gain (their efforts of promoting Windows Phone would have also helped the competition's offerings) and all to lose.

> Isotopic dating shows that whale falls in this region have occurred since at least 5.3 million years ago

Anyone know why these wouldn't be covered under a thick layer of sediment?

> He’s the richest man on the planet and doesn’t have a track record of not paying for shit he buys.

My impression was the other way around. The shenanigans he pulled around the Twitter acquisition were just farcical, and at Twitter he repeatedly refused to pay owed rent, etc. (I assume as a ploy to renegotiate terms).

> They are not. They are best practices if you want reproducible builds.

Or if you're writing a test suite, and you want failing test results to be actionable.

Or you have any other type of behavior that you'd like to reproduce somehow.

One of the first things app developers ask for in bug/issue templates are the steps to reproduce something. I wonder why you'd think that they would suddenly be opposed to the concept when thinking of a build peocess.

I agree that compromised source dependencies are the bigger problem, but that doesn't mean a compromised build infrastructure isn't. Just this last week, we had two Linux kernel LPEs that could have been leveraged to implement just such an attack, for example.

Another thing to consider is that Debian has quite a few derivatives who may also rebuild packages from source, so you have a multiplier there.