> So a human being, someone who works at Twitter dot com, looked at that video, looked back at the rule it was breaking, looked once again at the video, and went “Yeah, this all checks out.”

I am going to go out on a limb and assume that the people handling these appeals are expected to hit a certain number per day whether explicitly or not. And to paraphrase Charlie Munger, there's the incentive and this is the outcome.

I imagine someone sitting at a screen showing a queue of hundreds of thousands of posts awaiting review. Maybe there's even a leaderboard showing which employee has reviewed the most this month. Why waste their time watching the video in its entirety? Easier to just deny the appeal and move on to the next.

they have an arbitrary (and low) max on shortened urls. i believe it's 5000 :-(

i don't understand why they went through all this trouble of encrypting things client-side if they're just going to store the private key on their own servers! what actual benefit is there to this service? the fact that data is encrypted in-transit? i assume every backup provider does that via https/etc!

The private key can be encrypted by a password, presumably this encryption is done client-side.

This means the data is also secure in their datacentre at rest. That is, until you provide backblaze with your password to actually access your data.

Essentially, until you need the data that is backed-up, no-one can get to it.

My SSH keys are also protected by a passphrase, but you certainly won't find me uploading them to the Internet.

If it uses pbkdf2 with sufficient rounds and a decent password (say 5 words from diceware) it should be perfectly safe to upload the keys.

Better to keep them offline and keep ownership of the key as a second factor certainly, but encrypted keys can be a fully acceptable single factor.

The answer to just about every question posed on this thread is the same: "it's the government!"

"A simple `/ctcp $nick version` would be quite insightful to the tastes and possibly technical floor of the user."

insightful? it tells you if the person uses irc on a regular basis already (in which case they might have a native client) or whether they use something else usually (in which case they might use the simplest web-based client they can find on google).

After reading this I fired up Safari (on Yosemite). Never really tried Safari before - opened it once when I got my first Mac, wondered who moved my cheese, and downloaded Chrome. But the last half hour with it have been great actually!