3 ms·
It wasn't the data itself that was questionable. Search history has been commonly used as evidence for a while now. The difference is that usually you identify
by paxys 3y ago
It wasn't the data itself that was questionable. Search history has been commonly used as evidence for a while now. The difference is that usually you identify a suspect and then pull up their history, while in this case it was the reverse.
I personally do think that "give me a list of everyone who searched for XYZ in this time frame" is a clear case of a search warrant being unconstitutionally broad, but then this is generally where surveillance is going so it's futile to think it won't just continue to get worse.
- DistractionRect 3y agoIt's not like they ask for all searches in this time frame. It's who searched for this specific address. That's pretty narrow, one can expect the only people to search that address did so because they had business there (or perhaps nearby, and someone messed up the street number). I suspect with geofencing and a adequate window, you can further narrow the scope of the warrant (likely people looking up this address years ago have nothing to do with the arson, but people looking it up last week/month are suspect). In my opinion, it was reasonable, and not broad at all. That it only returned 5 accounts and not 500+ speaks to how narrow it is given the volume of search queries Google handles.
- bsder 3y agoSo, 5 accounts and 3 teens. So a 40% miss rate? In what way did the 2 accounts that weren't guilty get harassed by the police?
- DistractionRect 3y agoYou're confusing accuracy and precision. You want search warrants to be precise, but the only way to guarantee accuracy is to know in advance the fruits of the search. You can have a solid foundation for a warrant against an individual, but find out they aren't responsible, a 100% miss rate! But that's the problem, you don't know what you dont know, which is why you need a search warrant (and justification for it) to begin with.
- PH95VuimJjqBqy 3y agoIf you're regularly getting warrants against innocent people, someone needs to be fired and/or jailed. If there's any part of your process that is regularly putting innocent people into the line of fire of police, something is wrong and needs to change. You're entirely too cavalier about the risks associated with this, which was the point of the previous posters 40% metric. IOW, No one is afraid of a gun until it's pointed at them or their loved ones. And that's being fair to your blaise attitude.
- DistractionRect 3y agoAgain, if you already know with 100% certainty the fruits the search, then there's no need to do it as you can already prove whatever case you're building. People are presumed innocent until proved guilty which is to say search warrants are practically always used against innocent people. And just because a search warrant comes up short does not mean the person is innocent. A person's rights are not absolute. There are limitations, exceptions, and cases where they are taken away. Search warrants are an exception where a persons right to privacy are infringed upon in service of a greater good. It's not done lightly, and it will never be perfectly accurate. Taken to an extreme, if we treat the right to privacy as an absolute, that would mean one could murder with impunity on private property so long as it's out of view. People could strongly suspect, but not prove, the murders without infringing on the right to privacy. On the other hand, a murder occurring doesn't give LE carte Blanche to search the houses and computers of everyone in the county. We have to compromise in between. It's a grey area, but I think in this instance it was perfectly reasonable and narrow. But it could be argued that this is to the left or the right of where the compromise ought to be.
- PH95VuimJjqBqy 3y agowarrants should not be given out like candy. If you are regularly giving warrants out for innocent people, it means the due diligence is lacking. What you're trying to say is that sometimes it's reasonable to be incorrect. __sometimes__, yes. That's not what your attitude suggests here.