←back to thread

239 points sodality2 | 1 comments | | HN request time: 2.579s | source

Built this over the last few days, based on a Rust codebase that parses the latest ALPR reports from OpenStreetMaps, calculates navigation statistics from every tagged residential building to nearby amenities, and tests each route for intersection with those ALPR cameras (Flock being the most widespread).

These have gotten more controversial in recent months, due to their indiscriminate large scale data collection, with 404 Media publishing many original pieces (https://www.404media.co/tag/flock/) about their adoption and (ab)use across the country. I wanted to use open source datasets to track the rapid expansion, especially per-county, as this data can be crucial for 'deflock' movements to petition counties and city governments to ban and remove them.

In some counties, the tracking becomes so widespread that most people can't go anywhere without being photographed. This includes possibly sensitive areas, like places of worship and medical facilities.

The argument for their legality rests upon the notion that these cameras are equivalent to 'mere observation', but the enormous scope and data sharing agreements in place to share and access millions of records without warrants blurs the lines of the fourth amendment.

Show context
genewitch ◴[] No.46226855[source]
How come any area that has enough homes in the data set and ALPR have Veterinarians as the most surveilled, then Hospitals, then Libraries, usually over everything else, including food and church?

The strange implication is that they're watching the vet office traffic to find people who are getting treated by vets instead of doctors?

also my parish reports 0.0% across the board, and all the parishes near me. you have to get on the coast to get above 25%.

replies(2): >>46226988 #>>46227126 #
sodality2 ◴[] No.46227126[source]
Vets/hospitals are far less common (and the former probably suffers from less tags as hospitals are more important) so the distance one must travel increases, so higher likelihood of crossing one. Especially compared to how common everything else is.

If you check deflock.me, would you say that 0.0% aligns with what you expect?

replies(1): >>46228005 #
genewitch ◴[] No.46228005[source]
i suppose that makes sense.

There's 6 cameras in the metro area per deflock.me, 3 at each Lowe's, and that's it. It's very easy to not get in range of those, at least on "my side" of the metro. How do we know that is all the ALPR in an area? Or rather, what's the confidence? I'd assume Home Depot would also have them, for example.

note: maybe i need to restart firefox, but deflock.me is the slowest "map" based site i've seen since keyhole in the late 90s

replies(2): >>46228107 #>>46232651 #
1. sodality2 ◴[] No.46228107[source]
The best thing you can do is keep an eye out and tag them manually. The second best is a FOIA to your county government - there's some good examples on deflock.me and templates on muckrack. But private ones are not going to be FOIA-able.

The quality of ALPR tagging does probably lag behind true counts - for example, Williamsburg, VA has 28 tagged on OSM, but 32 are listed in the transparency log (https://transparency.flocksafety.com/williamsburg-va-pd). Unfortunately not much can be done except spotting them out and about (or wardriving with a BLE beacon scanner: https://www.ryanohoro.com/post/spotting-flock-safety-s-falco...)