Yeah, but still - the elephant.

The Tarot of the Bohemians.

I think it’s fairly parochial, and sounds quite infantile to me. Growing up (uk) we just used clockwise to tighten.

“I love life on Earth… but I love capitalism more.”

That was my, admittedly bitter, point, yes. You do have to wonder what the hell weretcollectively playing at.

We live in a world of plenty where we still produce enough food that nobody need go hungry.

It does make me wonder about quantum suicide.

The Sixth Sense.

Thank-you.

And 51 feels prime. Someone sgould write a letter.

It’s “revelation,” singular. Like trivial pursuit.

So you’re a practiced expert and cannot understand how those who are not practiced experts can have trouble?

I think unqualified freedom to say anything can lead to negative utility, pragmatically speaking. Malicious lies bring less than nothing to discourse.

I’m concerned that the libel system can be abused, of course; and I don’t approve of arresting octogenerians under the Prevention of Terrorism Act for shouting “nonsense!” at Jack Straw. But I don’t see there being a need to draw a distinction between online and in person speech, and I think that incitement to riot isn’t something I’d typically defend.

Having said that: I hope the woman in question (who has a history of being a deniable pot-stirrer) gets a trial rather than copping a plea, because the bounds of these things are worth testing.

In which case, perhaps unqualified “freedom of speech” isn’t all it’s cracked up to be.

(I appreciate that Chomsky’s opinion resonates more with 1968 than now.)

Have you seen pictures of the sub? What makes you think the wiring was all hidden?

You joke, but watch this:

https://archive.org/details/take-me-to-titanic

from 29 minutes in. A last-minute adjustment before launch plugged in a thruster backwards; no protocol to check the behaviour prelaunch. They doscovered it when they got to the bottom.

…unless it’s running software that uses signed 32-bit timestamps, or stores data using that format.

The point about the “millennium bug” was that it was a category of problems that required (hundreds of) thousands of fixes. It didn’t matter if your OS was immune, because the OS isn’t where the value is.

Fab, cheers.

Dare I ask what the adjective “hella” means in this context?

The test case purported to be bad data, which you presumably want to test the correct behaviour of your dearchiver against.

Nothing this did looks to involve memory safety. It uses features like ifunc to hook behaviour.

The notion of reproducible CI is interesting, but there’s nothing preventing this setup from repeatedly producing the same output in (say) a debian package build environment.

There are many signatures here that look “obvious” with hindsight, but ultimately this comes down to establishing trust. Technical sophistication aside, this was a very successful attack against that teust foundation.

It’s definitely the case that the stack of C tooling for builds (CMakeLists.txt, autotools) makes obfuscating content easier. You might point at modern build tooling like cargo as an alternative - however, build.rs and proc macros are not typically sandboxed at present. I think it’d be possible to replicate the effects of this attack using that tooling.