OVERWATCH

leviathan/OVERWATCH

Fork 0

Commit Graph

Author	SHA1	Message	Date
KaraZajac	26c4248282	v0.5.0 — Waze police source via key-protected proxy Re-adds the WAZE detection source (removed in v0.1.5 when Waze reCAPTCHA-gated its live-map endpoint). Data comes from OpenWeb Ninja's hosted Waze feed, but the paid API key never ships in the app: a Caddy reverse proxy at api.blackflagintel.com injects the key server-side, and the app authenticates with a scoped X-App-Token entered in Settings and stored encrypted via the Android Keystore (SecureStore). No credential is baked into the APK. - scan/WazeClient.kt, scan/WazeScanner.kt: proxy client + 4-min poller, 200-alert page + client-side POLICE filter, 45-min freshness window. - data/settings/SecureStore.kt: Keystore AES/GCM at-rest store (no dependency). - Settings: encrypted wazeProxyToken + "Waze police feed" token field. - ConfidenceEngine.scoreWaze, SourceHealth/DetectionSource WAZE, service wiring. - Removes the BuildConfig/local.properties key baking entirely. versionCode 15 -> 16, versionName 0.4.0 -> 0.5.0. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015jgJnzMr2bdNuWcDX2xRUR	2026-07-13 00:26:07 -04:00
KaraZajac	3574970a5f	Add OVERWATCH v0.1.0 — full detection engine + polish Phase 1 (BLE), Phase 2 (WiFi BSSID/SSID), Phase 3 (DeFlock map proximity), Phase 4 (Waze live POLICE alerts), and Phase 5 polish all wired through one DetectionStore. Confidence engine scores 0-100; UI maps to 4-tier circle. Polish: - Stylized two-line app title: [DЯΣΛMMΛKΣЯ] // 0VΣЯW4TCH - Modal bottom sheet for source drill-down (tap circle) - Settings screen: per-source toggles, proximity sliders, theme select - SharedPreferences-backed Settings with StateFlow exposure - DetectionService respects per-source toggles at start time - Scanners read proximity overrides via supplier lambdas README documents all sources, architecture, build steps, permissions, and the legal disclaimer.	2026-04-28 21:10:57 -04:00

Author

SHA1

Message

Date

KaraZajac

26c4248282

v0.5.0 — Waze police source via key-protected proxy

Re-adds the WAZE detection source (removed in v0.1.5 when Waze reCAPTCHA-gated
its live-map endpoint). Data comes from OpenWeb Ninja's hosted Waze feed, but
the paid API key never ships in the app: a Caddy reverse proxy at
api.blackflagintel.com injects the key server-side, and the app authenticates
with a scoped X-App-Token entered in Settings and stored encrypted via the
Android Keystore (SecureStore). No credential is baked into the APK.

- scan/WazeClient.kt, scan/WazeScanner.kt: proxy client + 4-min poller,
  200-alert page + client-side POLICE filter, 45-min freshness window.
- data/settings/SecureStore.kt: Keystore AES/GCM at-rest store (no dependency).
- Settings: encrypted wazeProxyToken + "Waze police feed" token field.
- ConfidenceEngine.scoreWaze, SourceHealth/DetectionSource WAZE, service wiring.
- Removes the BuildConfig/local.properties key baking entirely.

versionCode 15 -> 16, versionName 0.4.0 -> 0.5.0.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015jgJnzMr2bdNuWcDX2xRUR

2026-07-13 00:26:07 -04:00

KaraZajac

3574970a5f

Add OVERWATCH v0.1.0 — full detection engine + polish

Phase 1 (BLE), Phase 2 (WiFi BSSID/SSID), Phase 3 (DeFlock map proximity),
Phase 4 (Waze live POLICE alerts), and Phase 5 polish all wired through one
DetectionStore. Confidence engine scores 0-100; UI maps to 4-tier circle.

Polish:
  - Stylized two-line app title: [DЯΣΛMMΛKΣЯ] // 0VΣЯW4TCH
  - Modal bottom sheet for source drill-down (tap circle)
  - Settings screen: per-source toggles, proximity sliders, theme select
  - SharedPreferences-backed Settings with StateFlow exposure
  - DetectionService respects per-source toggles at start time
  - Scanners read proximity overrides via supplier lambdas

README documents all sources, architecture, build steps, permissions, and
the legal disclaimer.

2026-04-28 21:10:57 -04:00

2 Commits