That sounds like the kind of work the CIA is supposed to do.

Some of newegg's return policies are garbage.

Shortly thereafter, toasters will be designed to quietly burn anything that doesn't have a cryptographically signed RFID tag...

... ugh. please excuse those terrible spelling errors.

Because stock browsers don't come with something like flashblock, noscript, or uBlock.

The best you get is a big on/off switch which is far too course to be of practical use.

One of the most annoying safety features to have come out in quite a while.

I've lost track of the number of times I'd had to buckle my -backback- in because my car thought there was a person sitting there :/

Mine is the symmetry-defying highway entry points. I tried for an hour and I can't figure out how to attach to them at the start in a way that doesn't look... well, really damn stupid.

That also means a git repo can get a bit bloaty, should a repository be very old and/or active.

There's pros and cons to each approach.

It's not that simple...

The metal contracts as it cools. You have to scale up the model to compensate, and that takes knowledge you don't generally get without working with casting a LOT.

To make things interesting, the amount of scaling that's required changes based on the metal/alloy being used, and the -shape- of the object at that given area.

Damn, that was well written.

I think it's a bit funny (and appropriate?) that the Japanese song sounds (to my ear) so much like a Vocaloid. That said, to someone that doesn't speak the language a well-written bit of singing from one of those sounds pretty damn good.

Keep in mind a file with 755 will be examined and run based on the magic number at the front of the file.

Even shell scripts. #! is actually a 16-bit magic number, that also happens to be a comment in almost every scripting language.

Go ahead - chmod +x a random non-executable file and try to run it. You'll probably get something enligthening: "invalid file (bad magic number): Exec format error"

Because a proper user is going to run iterm2 after logging in and never touch finder again...

That's the fault of your file browser.

In all of these cases that's true - it's not Windows or OSX doing it, but Explorer or Finder (or thunar or whatever you're using on Mint)

You could theoretically do some packet inspection on the handshake and send a spoofed RST if you see something during the exchange you don't like.

I've only ever dug into the certificate exchange portion of the handshake. I'm assuming the cipher negotiation is also in the clear.

Sure, if there's a competitive reason to do so.

After all, they do the same for power/data/audio connectors too. (or at least they did.. *cough*nokia*cough* )