5 ms·
If it's accessible on the public internet and asks for something as secure as API keys, that is when you should worry about security, not when it's "meant to be
by philwelch 14y ago
If it's accessible on the public internet and asks for something as secure as API keys, that is when you should worry about security, not when it's "meant to be picked up by HN".
- alyx 14y agoFair, but in any case, the ultimate responsibility still lies with the user's judgment. Maybe if there was a service promised but not rendered, could you place full blame on the developer(s).
- adgar2 14y agoExactly. When you go to provide your information to a website, you need to consider "what are all the possible outcomes of this?" We can't use the reputation of the providers of a service as a proxy and thus have zero information about what to expect. Since you almost never have the source code for the website you're giving your information to, using your logic, just never give your data out. Right?
- shardling 14y agoWhat exactly does "ultimate responsibility" even mean here?
- philwelch 14y agoIt's not a matter of assigning blame, it's a matter of not delivering a shitty service to your customers.