kevinday

The lack of unlocking really surprised me. We bought one for testing that some of our mobile software would run on it, so we got the no-contract version. Even if you pay full retail price, it's still locked to AT&T. That's just blatant foot-shooting. If someone's going to pay you full price, it shouldn't be locked.

(And yes we tried getting Amazon to give us the unlock code. They said their contract with AT&T didn't allow it.)

Hard drives store things with varying forms of ECC. Each sector has an ECC field, allowing it to detect many errors and automatically correct some.

This isn't a replacement for something better, it just allows simple bit errors to be corrected automatically by the drive. The problem is that it's not really obvious when it's happening, and you only notice when it can't fix something. Drives eventually throw a SMART error when it's had to do too many corrections though.

If you're looking at this and not seeing any difference between the "before" and "after" versions, it's because HTTPS Everywhere is redirecting all github urls to their SSL version, so http://jessepollak.github.io/card/ redirects to https://jessepollak.github.io/card/ then can't load any of it's javascript dependencies due to the http/https mismatch.

Bonus points for the form still working right through all of that.

I've had really good experiences with Amadi Systems as a Supermicro reseller. http://amadisystems.com/

I've stopped buying Dell/HP entirely now, because the price of Supermicro's stuff is so much better and you don't get into warranty arguments like you do with HP about running non-approved OSes.

Is this also why when I hover over the menubar icon I get a beachball until it's done animating? I didn't see in this in the old version, but with today's I couldn't access the menu bar at all until it was finished fading.

For the lazy: the interesting part is on line 630.

I know you say you're not storing the password on your end, but what prevents you (or a hacker who somehow gets access to your server) to suddenly start logging the passwords as they're sent to the server when someone logs in?

You've got what looks like a good approach to storing things in an encrypted way, but it's still requiring the user to trust that the server is actually doing what it says it's doing and no more.