Remix.run Logo
▲ dataflow 3 hours ago

> The software should only "ping" when there is a confident match with said license plate(s)

Are you suggesting the set of all license plates of interest should be stored on the device itself?

▲jmb99 2 hours ago | parent | next [-]

If there are, say, ten thousand license plates of interest at any given time (which seems high), that’s what, 10KB? Not really that hard to update that every 15 minutes (or hell, every minute).

I don’t really see any drawbacks with storing them on the device, they should already be quasi-public knowledge (from warrants/etc) so it’s not like there’s a privacy/security risk there

▲felixgallo 20 minutes ago | parent [-]

You could just store it in a bloom filter, which would be non-public but also give you tunable accuracy. For 1 in a million false positives, a bloom filter would cost 28.8 bits per plate.

▲ocdtrekkie 3 hours ago | parent | prev [-]

There is a meaningful value in catching stolen vehicles and child abductors. Not high enough to justify capturing every single plate, but there's a value.

Bear in mind this is not meaningfully different than previous mechanisms of issuing BOLOs. Law enforcement widely distributes information about plates of interest. In my area, those plates are often on digital billboards already.

▲qmr 2 hours ago | parent [-]

There's no difference between a BOLO and a panopticon dragnet of always on AI powered cameras?

▲ocdtrekkie 2 minutes ago | parent [-]

If they solely look for and record sightings of specific plates associated with active investigations? Not a lot, no.

The core problem with Flock is that it tracks innocent citizens on the off chance it helps catch a criminal, when it could be designed to only track already known wanted vehicles.