mirror of
https://github.com/FoggedLens/deflock.git
synced 2026-08-18 00:17:13 +02:00
update gh actions, move kb dir
This commit is contained in:
Will Freeman
@@ -0,0 +1,19 @@
|
||||
# kb/
|
||||
|
||||
Knowledge base grounding content for the AI contact-screening classifier in `api/`
|
||||
(`api/services/AiScreeningClient.ts`, `api/services/KnowledgeBase.ts`).
|
||||
|
||||
## Convention
|
||||
|
||||
- One topic per `.md` file. Plain markdown, no required frontmatter — write it as canonical
|
||||
Q&A/policy content a human would also want to read.
|
||||
- The filename *is* the citable reference: the classifier's `kb_reference` output field is
|
||||
constrained to exactly the set of `.md` filenames present here (plus `"none"`), so the model
|
||||
can only ever cite a document that actually exists — never a hallucinated one.
|
||||
- Only some classification categories are instructed to ground their answers here rather than
|
||||
answer freely — currently `donation`, `api_data`, `other`, and
|
||||
`camera_correction` (see `api/prompts/contact-screening.md` for the exact list). For
|
||||
those categories, if nothing here covers the question, the classifier is instructed to defer
|
||||
to a human (`kb-gap` tag) instead of inventing policy.
|
||||
- Files are loaded once when the `api/` process starts. Adding or editing a file here requires
|
||||
restarting the API server to take effect.
|
||||
@@ -0,0 +1,5 @@
|
||||
Q: Why does DeFlock recommend/use AI for things like public records requests? I don't think you should use AI.
|
||||
A: Our reason for recommending AI as a tool is to help ordinary people make use of existing transparency laws. Public records requests are a legal accountability mechanism, but many people don't know how to draft effective requests or navigate bureaucratic processes — AI can help lower that barrier and make government oversight more accessible. AI has real drawbacks and isn't the best solution in every case, but in our view it's a useful way to lower the barrier to entry for people who wouldn't otherwise engage. Nobody on our end thinks these concerns are unreasonable — we've had internal discussions about this ourselves, since plenty of us have our own reservations about AI. Using AI is never required; you're welcome to skip it entirely. We appreciate you raising it and would love to support whatever action you want to take in your own community.
|
||||
|
||||
Q: Why is DeFlock using AI-generated art/imagery? I don't think you should use AI for that either.
|
||||
A: We understand AI-generated imagery is a contentious topic, and plenty of us have mixed feelings about it too — these aren't unreasonable concerns, and we've had internal discussions about the tradeoffs. Our community is made up mostly of technical contributors rather than artists, so while AI imagery isn't a perfect solution, it's helped us produce visual assets for projects that otherwise would have had none at all. If you'd rather see non-AI artwork, we'd genuinely welcome community contributions, and we're happy to support anyone interested in creating or organizing an alternative artwork effort. We appreciate you raising this — conversations like this help us make better decisions as a community, even when we don't all land in the same place, and we'd be glad to support other initiatives you want to pursue too.
|
||||
@@ -0,0 +1,48 @@
|
||||
Q: What can I do to help?
|
||||
A: Depends on your skillset and what you're comfortable with — we're happy to support whatever you want to pursue in your own community:
|
||||
- Don't mind paperwork? Filing public records requests and sending them our way is genuinely useful.
|
||||
- Have free time? You can submit cameras to the app.
|
||||
- Design-inclined? Contribute to (or use) designs from the DeFlock Store.
|
||||
- Comfortable with public speaking? Speaking to city council is very effective.
|
||||
- Interested in organizing your town/area? We'd love to talk you through starting a local group.
|
||||
|
||||
Reach out on Signal if you want guidance on any of this — we're here to help: https://signal.me/#eu/nJAAGCq9X29CQQRW4DD1e8M0wGHRI3mkBtqt-XfltzDQ1n2V2nZBKKgA7pRTLIRD
|
||||
|
||||
Q: I'm having trouble finding cameras near me — what do you know about wardriving?
|
||||
A: Join the Discord: https://discord.gg/aV7v4R3sKT — the #mapping-discussion and #wardriving channels are good places to ask. People there are generally friendly and willing to share skills, tools, and resources, and you may be able to find like-minded folks in your own state.
|
||||
|
||||
Heads up: there are probably law enforcement and Flock employees lurking in that Discord, so keep that in mind.
|
||||
|
||||
Q: Are there any petitions I can sign?
|
||||
A: There are likely several petitions active in your area. Easiest way to find them: search "[your area/nearest major city] ALPR petition" (or "Flock petition" / "DeFlock petition"), swapping in the terms most relevant to you. Many are hosted on Change.org.
|
||||
|
||||
Q: How do I actually get cameras removed from my city?
|
||||
A: It's genuinely complicated and varies a lot by city and situation, but roughly, for a city that's still deciding whether to adopt cameras and has a vote/discussion scheduled:
|
||||
1. Gather a group of motivated people to help.
|
||||
2. Inform the public about ALPRs and encourage people to attend the council meeting.
|
||||
3. Try to get private meetings with individual council members to gauge and build support.
|
||||
4. Get as many people as possible to actually show up and speak at the public meeting.
|
||||
5. Hope they listen.
|
||||
|
||||
More info here: https://github.com/DeflockYourCity/flock-alpr-toolkit
|
||||
|
||||
We'd like to support you if you want to start a local group or run a campaign in your area — happy to set up a call to help evaluate what you need and connect you with others in your state working on the same thing. Reach out on Signal to set up a time: https://signal.me/#eu/nJAAGCq9X29CQQRW4DD1e8M0wGHRI3mkBtqt-XfltzDQ1n2V2nZBKKgA7pRTLIRD
|
||||
|
||||
Q: I'm speaking with city council and need help preparing — what resources do you have?
|
||||
A: We'd love to help. Some resources that tend to help:
|
||||
- https://deflock.org/council — our guide to speaking with city councils
|
||||
- https://github.com/DeflockYourCity/flock-alpr-toolkit — a toolkit built to help with this
|
||||
- https://library.kansas.watch/ — a library of documented ALPR abuse incidents
|
||||
- https://eyesoffcr.org/blog/blog-8.html — a whitepaper on critical security vulnerabilities
|
||||
- https://deflockwoodland.org/senator-wyden-investigation-flocks-security-notoriously-insecure/ — background on Flock logins found on the dark web
|
||||
- https://consumerrights.wiki/w/Common_Questions,_Arguments,_%26_Responses_when_discussing_Flock_Surveillance — a list of talking points
|
||||
|
||||
Practical tips: consider requesting private meetings with council members beforehand (or asking friends/supporters to do the same — calls and emails count too), and get as many people as possible to attend the public meeting even if they don't plan to speak. Make sure it's clear the concern is with ALPR surveillance broadly, not just one vendor.
|
||||
|
||||
We may also be able to connect you with others in your area willing to show up in support — let us know the time and address of the meeting if you'd like us to help spread the word.
|
||||
|
||||
Q: A city near me got rid of its Flock cameras — what should I do with that info?
|
||||
A: That's great news — let us know the details and we'll get it queued up to be reflected wherever we track that. Keep us updated on anything else that develops!
|
||||
|
||||
Q: Following up with someone who previously expressed interest in starting a local group
|
||||
A: (Outreach template, not a reply to an inbound question.) "Hey, are you still interested in organizing a group in your area?"
|
||||
@@ -0,0 +1,19 @@
|
||||
Q: How do I get/download the underlying map data?
|
||||
A: DeFlock uses OpenStreetMap (OSM) as our backend/database — think "Wikipedia for maps" if you're not familiar. OSM has been around for 20+ years and there's a ton of (often free and open source) tooling for interacting with its data.
|
||||
|
||||
Until downloads are built directly into the website, a good place to start is Overpass Turbo: https://overpass-turbo.eu/s/2cMH (or https://overpass-turbo.eu/s/2liK). Overpass Turbo lets you search and export OSM data to GeoJSON, GPX, and KML. The linked queries have comments with instructions for filtering by country, state, or getting worldwide data.
|
||||
|
||||
Note that query includes all ALPRs, not just Flock ones. To filter to Flock specifically, replace the `node[...]` line with:
|
||||
```
|
||||
(
|
||||
node["manufacturer"="Flock Safety"];
|
||||
node["brand"="Flock Safety"];
|
||||
);
|
||||
```
|
||||
|
||||
Q: I'm in Canada (or another country) — can I map ALPRs there too?
|
||||
A: Yes, the app isn't geographically bound. Canada (and most non-US countries) just has far fewer known ALPRs mapped so far, and the ones that exist haven't drawn as much public attention yet, so fewer people have been mapping them. We're not sure what brands/capabilities are common outside the US — that's somewhat unmapped territory (pun intended).
|
||||
|
||||
Technical context: DeFlock doesn't run its own database — we show a limited set of what's on OpenStreetMap. OSM's database is full of "nodes" tagged with key=value pairs. Our app ships with a few built-in "profiles" (just a set of tags describing a type of thing), but you may need to create or modify a custom profile in Settings > Profiles to correctly map whatever devices exist in your area. As an example of how flexible this is: you could map a park bench with a custom profile of just `amenity=bench`, or a tree with `natural=tree`. Look at the built-in profiles for a sense of the pattern.
|
||||
|
||||
We're also working on a larger update to deflock.org/identify with more vendors and non-ALPR device types, each with an importable app profile, to make this easier going forward.
|
||||
@@ -0,0 +1,20 @@
|
||||
Q: Does the camera data get sold?
|
||||
A: Flock states that they do not sell the information they capture. What they do instead is capture it, then sell access to the software that contains it. DeFlock (like you) has reasonable questions and concerns about this, given Flock's integration with data brokers and their rapidly changing terms and conditions around data policy. You can read more here: https://haveibeenflocked.com/news/terms-feb2026
|
||||
|
||||
Q: I think you're Flock (or a Flock affiliate) — you're the ones running these cameras / collecting data on me or my car / please delete my data.
|
||||
A: We are DeFlock, a privacy-advocacy project pushing back against these cameras — we're not Flock, and we're not affiliated with them. DeFlock doesn't operate any cameras and doesn't collect, store, process, or access any information about you or your vehicle (or anyone else's). We don't even run our own user registry or database for the map; everything comes from crowdsourced OpenStreetMap data. The company that actually operates these cameras and holds that data is Flock Safety: https://www.flocksafety.com. If you specifically want your data deleted, we can't guarantee they'll honor the request, but you could try support@flocksafety.com or privacy@flocksafety.com.
|
||||
|
||||
Q: How do I keep from being tracked by these cameras?
|
||||
A: Unfortunately, physical plate covers and films are illegal in most jurisdictions. Flock also uses vehicle fingerprinting (make, model, stickers, dents) to identify your car, so obscuring just your plate doesn't help much anyway. IR blocking/reflection is similarly ineffective and can actually make your vehicle *more* identifiable, since instead of being identified by plate you light up distinctly in the camera's IR image.
|
||||
|
||||
The most effective legal countermeasures are civic action and route avoidance: use the free DeFlock app to see camera locations and plan alternate routes, or push at city council meetings for restrictions on data sharing and retention. Happy to help with the app or with getting involved if you want to push back on this locally.
|
||||
|
||||
Q: A camera looks deactivated/covered — can I trust that it's actually off?
|
||||
A: Worth checking: is it black-bagged or covered in some way? There have been cases of Flock reinstalling and reactivating cameras without notifying the city/contract holder:
|
||||
- https://www.yahoo.com/news/articles/cities-fighting-back-against-law-011500912.html
|
||||
- https://lookouteugene-springfield.com/story/latest-news/2025/12/09/flock-activated-camera-during-pause-chief-says-pushing-city-to-axe-contract/
|
||||
|
||||
If a camera really is non-functional, asking the city/property owner to physically cover it can help make that verifiable.
|
||||
|
||||
Q: When did this camera physically get installed?
|
||||
A: We're unfortunately not able to say with certainty when a specific camera was physically installed — only that it was probably before the date it was submitted to OSM. (See the "reporting and fixing map entries" doc if you're looking for the date it was *logged* on the map, which we can pull up.)
|
||||
@@ -0,0 +1,26 @@
|
||||
Q: I found a camera — can you add it to the map for me?
|
||||
A: Thanks for the report :) You can use our DeFlock.me mobile app! See: https://deflock.org/report — you'll need an account with OpenStreetMap.org (aka OSM — if you're not familiar, think "Wikipedia for maps," they operate the backend database we use to inform our map) to make edits. We have some documentation at https://deflock.org/app/docs but it's a work in progress; happy to answer any questions.
|
||||
|
||||
Q: I found something on the map that isn't actually a Flock/ALPR (or is otherwise wrong) — how do I get it fixed?
|
||||
A: Thanks for the report! A little technical background — our map shows a subset of the OpenStreetMap database; you can directly make edits yourself by signing up for an account with them. Our mobile app is a focused OSM client intended to make the process as easy as possible, but you can use any client/editor you like, including OSM's official web editor called "iD." See https://deflock.org/report for instructions on both that and our app. Beyond that, it's often a good idea to reach out to the original submitter via OSM direct message to politely correct their mistake so it hopefully doesn't continue happening. Thanks for keeping an eye out and helping us clean up the map — that's a very important part of maintaining any collaborative dataset, and we sincerely appreciate it.
|
||||
|
||||
Q: Can I add a non-ALPR device, or a mobile/temporary installation, to the map?
|
||||
A: They ARE mappable, but as you noted, they're not in the default profile list. The most recent app update lets us provide "import app profile" links right on our Identify page: deflock.org/identify — we're working to add more things there, including sneaky/uncommon setups. You can also create custom profiles yourself under Settings > Profiles; figuring out the right tags is the fun part.
|
||||
|
||||
DeFlock uses OpenStreetMap data, and OSM has standards and conventions that should be followed. One of those: generally do NOT map temporary installations like trailers or traffic cones. That said, if you're willing to take personal responsibility for keeping the map updated as things change, the accepted way to mark such an object is with the tag `temporary=yes`: https://wiki.openstreetmap.org/wiki/Key:temporary
|
||||
|
||||
Q: A camera, manufacturer, or other "thing" isn't listed on the website or in the app — can you add it?
|
||||
A: Yes! We have a backlog of things to add to the Identify page; we'll make sure it's on the list. The app can import profiles directly from the website now, but we've avoided including everything by default to keep the built-in list from getting too long.
|
||||
|
||||
Q: When was a specific camera/entry added to the map or website (logged date, not physical install date)?
|
||||
A: You can get the date it was logged using our site:
|
||||
1. Go to your area on our map: https://maps.deflock.org
|
||||
2. Click the blue camera icon to bring up info on a specific camera
|
||||
3. Click "View OSM" to open the detailed information panel
|
||||
4. Click "Download XML"
|
||||
5. Look for the field tagged "Timestamp"
|
||||
|
||||
Feel free to reach out if you need help with this.
|
||||
|
||||
Q: Why do I have to give OpenStreetMap my email address just to make an edit?
|
||||
A: Sadly, some means of tracking and blocking bad actors (and reverting their edits) is required due to spam and vandalism. For context: DeFlock doesn't run our own database — our map pulls from OpenStreetMap, which has been solving the problems of collaborative mapping for over 20 years (think "Wikipedia for maps" if you're not familiar). All OSM asks for is an email address, and you're welcome to sign up with a throwaway over a VPN if you prefer. Our mobile app is just a focused client for OSM tailored to this task — you can use any editor you like, including the online "iD" editor at openstreetmap.org.
|
||||
@@ -0,0 +1,13 @@
|
||||
Q: Someone put a DeFlock/anti-ALPR sign on my property (or I got a "you need a permit" complaint about signage) — can you get it removed?
|
||||
A: Sorry to hear that's happening. For context, DeFlock is a website, some technical information and tooling, and a small organic community of people around the country — we don't print or post signage ourselves, and we don't encourage people to do so without checking and following local laws. People do print and share signage designs, almost always without consulting us first, and we have no hand in the methods or locations they choose. We're not aware of anyone specifically posting signs in [their city], so we may not be able to get this message to the right person directly — but we can post a notice in our community's [their state] channel asking whoever's been posting signs there to stop and get in touch with us. It's helpful if the reporter can share an exact location or a photo of one of the signs, so whoever posted it can recognize the message is about them.
|
||||
|
||||
Q: I want to print and hang up a bunch of signs — is that okay?
|
||||
A: Go for it! Feel free to download any of the printables we have at https://deflock.org/store (or upload your own designs so others can use them too). Keep us in the loop on how it goes and let us know if there's any way we can support you.
|
||||
|
||||
Q: Isn't damaging/vandalizing the cameras a valid way to fight back?
|
||||
A: We believe the cameras should be removed, and we understand the anger people feel about being surveilled this way. But property damage isn't a good route to that — it can create legal consequences for the person doing it, and it tends to shift public attention away from the actual concerns being raised. Calling your representatives (https://deflock.org/council) or putting up posters (https://deflock.org/store) to raise awareness is more productive toward our actual goal. Happy to help with either of those if you want it.
|
||||
|
||||
Q: Can DeFlock push city council to require warning signs on all the cameras?
|
||||
A: We get the instinct, but in practice we're not planning to spend our limited bandwidth lobbying cities to add camera-warning signs, since our actual goal is getting the cameras removed, not better-labeled. There's a strategic concern too: asking a council to add signage can unintentionally validate the cameras as acceptable "so long as they're marked," which shifts the conversation from whether they should exist at all to how they're implemented — not a compromise we want to make.
|
||||
|
||||
There's also a practical issue: most camera locations are far enough from approaching traffic that a camera-specific sign wouldn't be safely readable by a driver anyway, so it wouldn't function as a real-time warning. The signage we do support is aimed at building general public awareness (especially among pedestrians), not warning drivers in the moment. We've already made signs and educational materials for that purpose — people are welcome to print, share, and use them: https://deflock.org/store
|
||||
@@ -0,0 +1,19 @@
|
||||
Q: What the heck are these things? What is an ALPR?
|
||||
A: Automatic License Plate Readers are cameras that private businesses and local municipalities install that capture and analyze images of all passing vehicles, storing details like your car's location, date, and time. They also capture your car's make, model, color, and identifying features such as dents, roof racks, and bumper stickers. These images are turned into data points for a searchable database that law enforcement does not need a warrant to access.
|
||||
|
||||
Q: I think I've misidentified a traffic cam / red light cam as a Flock/ALPR — how can I tell the difference?
|
||||
A: The ones you see at intersections are (almost always) strictly for changing the traffic lights. They're mostly really poor quality image sensors, and the systems they connect to are mostly offline. Easy rule of thumb is that if it's facing the front of your car, it's probably traffic monitoring; if it's looking at the back, it's probably a privacy issue (an ALPR). Not always true, but probably 95%.
|
||||
|
||||
That said, traffic cams are totally mappable — you'd just need to create a custom tag profile in the DeFlock app for that. Something along the lines of:
|
||||
```
|
||||
Name: "unknown traffic cam"
|
||||
man_made=monitoring_station
|
||||
monitoring:traffic=yes
|
||||
camera:type=fixed
|
||||
camera:mount=pole
|
||||
```
|
||||
You can add `manufacturer=` if you know it. Generally the FOV should be left blank unless it's a 360 or PTZ camera.
|
||||
|
||||
Because these aren't ALPRs, they won't appear on the deflock.org website. But if you have a profile for it, your app will show them.
|
||||
|
||||
Side note: OpenStreetMap maps just about everything. DeFlock is just a focused, limited client tailored to ALPR mapping. Nothing stops you from mapping park benches, utility poles, or fire hydrants in OSM directly — you'd probably want to use a fuller OSM client like JOSM, StreetComplete, or GoMap for that, but it's all the same OSM data on the backend.
|
||||
Reference in New Issue
Block a user