Forgot your password?

typodupeerror

Comment: Dropbox's followup is no good (Score 3, Insightful) 185

by Wuhao (#36510928) Attached to: Dropbox Password Goof Let Any Password Work For 4 Hours

Not only was there a serious security issue here, but Dropbox customers are having to find out about this through blogs. Dropbox has yet to email its users about this issue. It claims on its blog that users who logged in during this time have been notified. I logged in during this time, and have received no notice.

I am now leaving Dropbox. I need to review Wuala and Spideroak to see if they meet my needs, but I can safely say that this event and Dropbox's earlier behavior has demonstrated to me that they do not take the security and privacy of their customers seriously.

Comment: Re:Linux was a derivative of UNIX (Score 1) 239

by Wuhao (#33006652) Attached to: The Scalability of Linus

Geez, Linux is not some revolutionary, unique software. It copies from other systems and OSes. As long as we know what and where, we can figure out why and how.

As for Linus: not scalable. He needs a break. and do you all really know he's the only one that commits? Really? It's just a git account, i.e. Linus could still be committing in 2310, if he gave someone his password of course... Conspiracies, conspiracies....

Come on, Darl, let it go. It's time to move on.

Comment: Re:Found this in SCO's code... (Score 3, Funny) 578

by Wuhao (#32872098) Attached to: Claimed Proof That UNIX Code Was Copied Into Linux

Dude, you ruined it. As written, you have a brilliant joke in C: the premise is bad (we're beating a dead horse), the plan is questionable (we're directly comparing a pointer and a string literal), and the execution is sloppy (thanks to the typo, we're testing the result of a non-zero assignment, so the horse is beat forever regardless of liveliness).

This is pretty much the story of SCO.

Comment: Re:Wrong or right (Score 1) 386

by Wuhao (#32526508) Attached to: For Normals, Jobs' "Retina Display" Claim May Be Fair After All

The difference here is that "blast processing" was a vague, nebulous term that was never really elaborated on, and this is a very specific technical specification (the iPhone 4's 326 ppi screen), and is being compared against a reasonably specific reference metric (the sensitivity of the human eye). The practical upshot of this is that once you have a display whose pixels are so small that at a normal viewing distance nearly all of the population will be unable to distinguish neighboring pixels from each other, there is very little use in further improving resolution without also increasing screen size.

Do the specs speak for themselves? No, they don't, because while 326ppi makes perfect sense to me, I don't know anything about the maximum sensitivity of the human eye, and I'm interested to hear where that bar is set, whether this display really exceeds that, and what caveats I should be aware of in taking this metric into consideration when selecting screens for my own use.

Whether or not the iPhone 4 in particular meets this goal only of mild interest; it's a case study of a device that literally claims to be designed to have a higher resolution than the eye can distinguish. If it doesn't hit the mark, there's going to be a display that will come closer soon, and I'd like to be able to talk more knowledgeably about what this means.

Promptness is its own reward, if one lives by the clock instead of the sword.

Working...