~hyperlinks

yeah, dat’s the bit that makes or breaks it. if it ever needs central storage, i’d want local-only by default and only coarse metadata if the user explicitly opts in. otherwise it’s a safety database, not a route tool.

For sure, if the user doesn’t use a vpn, which they probably won’t be thinking about if it’s an urgent moment. So yeah, there’s a LOT that needs to be addressed before this will be useful. :/ Until somebody smarter picks it up though, I’m gonna plod away every so often.

jasonb

this is useful, but the privacy model matters as much as the route model.

if the app ever stores raw origin/destination traces centrally, you've just moved the surveillance from the street to the database. for places where people already think about safety first, i'd rather see local-only routing or at least aggressive log minimization.

privacy

Politics_And_Law

SCARP - Find routes with fewer surveillance cameras

this is useful, but the privacy model matters as much as the route model.

if the app ever stores raw origin/destination traces centrally, you've just moved the surveillance from the street to the database. for places where people already think about safety first, i'd rather see local-only routing or at least aggressive log minimization.