Oh SNAP, and there’s the Devil

I don’t know how else to put it. I’m sorry. It’s bad. It’s bad in my opinion, not fact. My opinion, is my expectation, will only turn fact by the time it is too late to do anything about it.

It’s like, “why back-up anything?” — well, you’ll know when you’ve lost everything. In other words, when it is just slightly beyond way too fucking late.

It’s like, “what’s security?” — well, you’ll know what it is when you can wrap up your business and shut it all down — just slightly too fucking late.

It’s like, “why should I care about privacy? I have nothing to hide!” — no, indeed, you don’t have anything to hide. You’re a commodity among another 8 billion of the same exemplary type of ignorant human being that you are — and I am. Indeed. Just slightly, repeat after me, too fucking late.

In many ways, you can start an argument about Snap as follows;

Whatever delivery mechanism is a free-for-all aimed at all possible targets, …

… is called a cluster bomb. Easy. Reliable. Powerful. Entertaining. Plenty of non-CGI balls of flames. In real life. Visually appealing. Take a selfie.

Then walk away. On to the next selfie if you so must.

Nothing is more dangerous than allowing a user — from mouseover to a double-click, from ctrl+delete to drag’n’drop — to do whatever the user wants. Users are, as any developer, operator and helpdesk employee will tell you, the biggest bug. But in the case at hand, they’re one of the few largest security risks. Sometimes, it’s demonstratively insecure, as is the case with Snap. Sometimes, what is secure is dysfunctional and what is functional is insecure.

I need say no more.