2 ms·
Slightly OT, but the "Nothing to Hide"/Privacy article is yet another example of "how not to write an abstract": >In this short essay, written for a symposium
by SilasX 14y ago
Slightly OT, but the "Nothing to Hide"/Privacy article is yet another example of "how not to write an abstract":
>In this short essay, written for a symposium in the San Diego Law Review, Professor Daniel Solove examines the nothing to hide argument. When asked about government surveillance and data mining, many people respond by declaring: "I've got nothing to hide." According to the nothing to hide argument, there is no threat to privacy unless the government uncovers unlawful activity, in which case a person has no legitimate justification to claim that it remain private. The nothing to hide argument and its variants are quite prevalent, and thus are worth addressing. In this essay, Solove critiques the nothing to hide argument and exposes its faulty underpinnings.
In other words, "there's a common argument out there, and I'm gonna refute it". Does that help me decide whether to read the paper? No, because it gives no hint about specific part of the argument it's going to refute, or what "underpinning" it's going to claim is "faulty".
This kind of crap is extremely prevalent in abstracts, and in people's ability to summarize and justify recommendations.