Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The average user will think they're about to get a virus or do irreversible damage to their computer, both of which are very, very far from the truth.

Very far from the truth, today, when this is a brand new beta that Devs are just getting their hands on.

But 6 months from now? A year? It's not going to be long before an unsigned binary probably is a trojan or similarly untrustworthy. It's not like Adium isn't going to be signed by the time Mountain Lion ships.

> tl;dr: Imagine if your grandma saw this error message. How would she react?

She'd freak out and throw it in the trash -- which is exactly what I want her to do with unsigned binaries.

There's really no analogy with the "An error occurred" dialog. We want to scare users away from blindly trusting binaries from the internet. "An error occurred" serves no similar purpose in training the user.



I doubt trojans will bother with unsigned binaries. I suspect they'll just do some sort of "social engineering" to get all the developer certificates they want.


Or maybe we'll see malware distributed in source form. That could be nasty if the development environment gets compromised. Probably more dangerous than a compromised website.


I'm commenting on this dialog, not some future hypothetical dialog that addresses Dustin's concerns.

As it stands it's far too aggressive and unfriendly. Aesthetically, the copy sucks monkey nuts (to put it politely).


I guess I simply disagree. I want the copy to be aggressive and unfriendly, and I'm happy there's no "Continue, and shoot myself in the foot" button for users to fixate on.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: