3 ms·
I strongly disagree with this reasoning. Yes, more people will burned by making these data more easily available to the public - but as a result of those peopl
by LyndsySimon 10y ago
I strongly disagree with this reasoning.
Yes, more people will burned by making these data more easily available to the public - but as a result of those people being burned, security for the community as a whole will be improved over time.
An example of this is what happened with Facebook. Prior to 2013, most users logged in to Facebook without using HTTPS. A Firefox-based tool was released that sniffed for Facebook traffic over WiFi and snagged the other users' cookie to allow for easy session hijacking (Firesheep). Shortly after Firesheep started getting press coverage Facebook enabled HTTPS-by-default[1].
I think it's perfectly valid to argue whether or not the short-term harm caused by this sort of thing is justified by the longer-term benefit, but I don't think it's quite fair to say that the only reason to offer it is to enable abuse.
[1]: https://www.facebook.com/notes/facebook-engineering/secure-browsing-by-default/10151590414803920 https://www.facebook.com/notes/facebook-engineering/secure-b...
- zensavona 10y agoWhy not just write a quick script to send them all an automated message/ticket a week before this is live and then run it on archived data? You can do both at the same time.