3 ms·
Well, yeah. Did anyone honestly think the FBI intentionally (and perhaps even illegally) took data belonging to Instapaper to.. what? Build profiles on upper mi
by eli 15y ago
Well, yeah. Did anyone honestly think the FBI intentionally (and perhaps even illegally) took data belonging to Instapaper to.. what? Build profiles on upper middle class Americans' reading habits?
I'm definitely not an apologist for the post-9/11 police state, but that's a pretty silly conspiracy theory.
- wmf 15y agoNo, people thought the FBI accidentally took data belonging to Instapaper. You're right that the FBI wouldn't have looked at it anyway since their investigation is not about Instapaper. They can't even afford to investigate crimes that are reported, so they definitely don't have the resources for random Web 2.0 fishing expeditions.
- gojomo 15y agoMy concern would be that if the wrong disks get imaged (either by real bumbling, or erring on the side of over-collecting, or calculated-hoovering-that-could-be-portrayed-as-an-honest-mistake-later), the disk data could then wind up in some broader forensic analysis pipeline, or long-term evidence archive, and then be eventually misused. For example, if they think they may have imaged too much, do they promptly and irreversibly wipe the extra? Or keep it, just in case their assessment of its relation to the current investigation changes again? Could current or future automated criminal-activity-analysis engines be run against every old disk image in their possession, ignoring the details of how/why they were collected?
- wmf 15y agoCould current or future automated criminal-activity-analysis engines be run against every old disk image in their possession... As problematic as that is, it's a drop in the bucket compared to things like Echelon. I think people should be realistic about their paranoia.
- nknight 15y agoEchelon can be guarded against with in-transit crypto. Physical access to systems is far more problematic. Even if the data is nominally encrypted on-disk, the key must be in RAM to make use of the data, rendering it vulnerable at the time of seizure. (You can partially mitigate the risk, but you can't make it 100%, and it's very likely you'll have issues with cost, performance, and user-friendliness along the way.)