Hence one should adapt one's own behaviour and act accordingly (that doesn't mean that you should get paranoid - just be more careful :).
Reduce risk and watch what you say from now on.
Hence one should adapt one's own behaviour and act accordingly (that doesn't mean that you should get paranoid - just be more careful :).
Reduce risk and watch what you say from now on.
There's no such thing as online privacy - privacy is dead.
It's better that the default for most things online is public since any privacy setting is just an illusion of security. Of course there are some notable exceptions to this (encrypted backup services that encrypt locally before backup), but for the most part if it's online and at least some other people can see it - everyone can see it.
http://www.faqs.org/patents/app/20120110469#b
It took me a loooong time to figure out how to do privacy and social networking at the same time, using only web technology. Actually it can't be provably private using web technology because you have to trust the server -- which is why we need this: http://news.ycombinator.com/item?id=2024164
Not necessarily easy for everyone, but much more satisfying in the long run.
Hence, in this case, if you assume everything is public, you reduce the harm that can come to you when the trust you have in a service fails you (as it may well do). Just like an investor - take on risk, minimise uncertainty and price catastrophe correctly. This gives you the best of both worlds - risk priced in proportion to reward. You can have your cake and eat it too - if you only take a slice and no more.
In code, "int errorType = 1;" would be a badly chosen variable :)
The expressions "false positive" and "false negative" reveal more semantics than "type 1" and "type 2", and are therefore much easier to remember.
I quickly forget that the "map" in my brain is about 10 times more detailed than the vector representation I detail in my answer - and it often lacks ideas that may be critical to understanding.
I will use false positive/negative terminology from now on - apologies for the dense language and propagating difficult to comprehend terms - I'll try to stop doing that :D.
Classical statistics suffers from the inference problem, where instead of "tested positive for presence" you have to say "tested negative for absence". So a type I error is a false negative as much as it is false positive, which can get confusing.
[1] www.businessinsider.com/warning-google-buzz-has-a-huge-privacy-flaw-2010-2