Idea
While driving with DeFlock open, use the phone's camera to capture periodic photos (or continuous video). When an RF detection fires, automatically tag the nearby frames for later review. This creates a visual record that can be used to locate and identify physical cameras.
This issue is a proposal/placeholder to gather community feedback, ideas, and suggestions — not a prescriptive spec.
Why
RF detections give an approximate location ("somewhere around here"), but a photo or video taken at the moment of detection can capture the physical camera. By automatically correlating RF detections with timestamped, GPS-tagged photos, users can later review exactly what was visible when a detection occurred — greatly increasing the chances of visually identifying the device.
How it might work
- User activates "capture mode" — phone camera starts taking photos at a configurable interval (e.g., every 2-5 seconds)
- Each photo is GPS-tagged and timestamped
- When the scanner detects a device, mark the photos within ±10 seconds (or a configurable window) as "near detection"
- User can later browse flagged photos to visually locate cameras
- All photos stored locally — nothing uploaded without explicit consent
Modes
- Photo interval mode — take a photo every N seconds while driving
- Video mode — continuous video recording, with timestamps marked at detection events
- Manual mode — user takes photos manually; app just correlates timestamps with detection log
Considerations
- Storage — continuous photo capture eats storage quickly; need configurable quality/interval and automatic cleanup options
- Battery — camera + GPS + scanner simultaneously is battery-intensive
- Phone mounting — works best with phone mounted on dashboard/windshield with camera facing forward
- Privacy — captured images may contain people, plates, private property. All storage is local, but should be clearly communicated to users
- Night driving — photos in low light may not be useful; could auto-disable or warn
- Background operation — ideally camera capture continues when screen is off or app is backgrounded
Future Extension
Captured frames could be fed into an on-device AI model for automated camera detection (see the AI-based camera detection issue).
Open Questions
- Photo mode vs video mode vs both?
- What's the right default capture interval?
- How to handle storage management — auto-delete after N days? User-configurable?
- Should non-flagged photos be kept or discarded automatically?
- How to handle multi-tasking — can the camera capture while the map is visible?
Effort Estimate
Large
Dependencies
Related
Idea
While driving with DeFlock open, use the phone's camera to capture periodic photos (or continuous video). When an RF detection fires, automatically tag the nearby frames for later review. This creates a visual record that can be used to locate and identify physical cameras.
This issue is a proposal/placeholder to gather community feedback, ideas, and suggestions — not a prescriptive spec.
Why
RF detections give an approximate location ("somewhere around here"), but a photo or video taken at the moment of detection can capture the physical camera. By automatically correlating RF detections with timestamped, GPS-tagged photos, users can later review exactly what was visible when a detection occurred — greatly increasing the chances of visually identifying the device.
How it might work
Modes
Considerations
Future Extension
Captured frames could be fed into an on-device AI model for automated camera detection (see the AI-based camera detection issue).
Open Questions
Effort Estimate
Large
Dependencies
Related