Hacker News new | past | comments | ask | show | jobs | submit login

Wait a second.

You're saying I shouldn't bash my employer on a public blog and then submit it to another public website?

OMG

Really you didn't dig deep enough. Googling my name pulls up an email with my current employer in it. I don't work for Amazon anymore.




It's reassuring to know that you wait until you're employed by somebody else before violating your previous employer's privacy policies.


Amazon is violating its own privacy policy by allowing users to interact with its site insecurely.

Two wrongs do not make a right, but when you can implement a technical measure to protect your users from rogue ex-employees, you should do it. A legal contract does not prevent data loss, it merely allows you to punish the person who stole the data. SSL prevents the data loss in the first place.


What? Unless he is still bound by some Amazon NDA or something, what difference does it make if he violates the policies of someone he no longer works for?




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

Search: