No, it's not about stuff, it's about respect.

Do you honestly believe these botnets are made up of thousands of otherwise diligent users who fell prey to a zero-day attack?
The millions of those who can't be bothered to update their systems have been bloody lucky not to get caught up in it then haven't they?

And just because somebody might get caught out by a zero day doesn't automatically absolve everybody from taking some responsibility for the security of their systems.

"unknowingly" being the operative word here.
How many of these infections are caused by the user not having up-to-date AV software and blindly clicking on links in random e-mails?
You have to take some responsibility.

Ok, yes, if the owner has left the keys in the ignition, the doors unlocked, and walked away leaving a big sign on the car saying "please steal me".

Or like saying a car driver should be responsible for the damage he causes if he crashes into another vehicle.

Oh.. wait..

Rotate, not shift.

http://www.kali.org/official-documentation/

It's a link on the top of the home page. I bet you couldn't find your arse with both hands and a mirror.

non-free porn ?

Why not xxx.[country_code] for porn? No need to add an extra level just for that.
I like the idea of a separate porn tld, makes it easy both for those who want to find it, and those who want to avoid it.

... the better it was.

Create three pages, one of which contains only links to the other two. Now "click" from one of the child pages to the other. On a more serious note - Google may well be a massive generator of links to other sites, but I fail to see its usefulness in being able to click through it to other sites - it does rely on textual input.

FTFY

That's not what the article says, in fact it specifically says

(Note that unlocking is different from "jailbreaking," which opens the phone up for running additional software and remains legal for smartphones.)

so I read it as referring to sim unlocking.

He should have pointed the university admin to RFC2142 then - abuse@[anywhere] shouldn't be available for anybody other than the network admins.

MAC flooding