[bravetraveler]

Let's not forget, that while he did kind of shrug and agree to remove everything... that was a problem in the packaging spec.

The package (Steam, if memory serves?) should not have had the other packages referenced as they were. The dependency/requirement resolution was faulty...

Then he didn't truly take in the message and this is the result we get.

There's plenty of "probably say no if you don't know what this means" in what he ignored. Fault is all over.

    - His distribution of choice [or] the repository supporting it
    - him for not reading and acting accordingly
    - sheer chance

Had he chosen another distribution at random, there's little chance that would have happened.

If he repeated it on the same one now, it wouldn't happen. When you choose a niche distribution, you get niche problems.

My entire family manages fine on 'bleeding edge' Fedora, yet it doesn't market itself this way. Packaging is specifically in their domain of expertise

This isn't to say Linux is for everyone, but I really wish for a more fair representation.

As the reporters they should have dug in a bit more. They become part of the problem, in a sense, by not clarifying where there truly be dragons.

[SAI_Peregrinus]

> There's plenty of "probably say no if you don't know what this means" in what he ignored.

Users will pretty much always click what they think will make the goal they're trying to accomplish work. Usually "yes" or whatever the default is.

[bravetraveler]

Indeed, and a tool that does what it's told is a good tool

The packaging snafu was unfortunate, but beyond preventing him from having the ability, I don't know how it could have improved

The spec shouldn't have been so egregiously incorrect. Pretending it didn't happen... how is something both powerful and safe?

I don't know how anything could be made to take arbitrary input and sort it out to meaningful work

Edit: Fedora does well to mark things as protected, this would likely help. But still, the operator should serve as a filter