←back to thread

239 points sodality2 | 1 comments | | HN request time: 0s | 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
runtimepanic ◴[] No.46222218[source]
One thing this surfaces nicely is how scale changes the privacy model. Individually these look like “mere observation,” but once you can reconstruct routine movement patterns across counties, the data starts behaving more like long-term tracking than casual surveillance.
replies(1): >>46231470 #
1. wwweston ◴[] No.46231470[source]
Retention is one good line between enforcement and tracking.

If we wanted to solve this problem while retaining the benefits, what we'd do is have stiff penalties for warrantless retention and required yearly independent audits of systems.