A relay on jai (server/bubble_relay.py, stdlib + SQLite, tailscale address only, bearer token) carries sealed blobs between the desktop and the Rabbit: AES-256-GCM with a key the desktop makes and hands over USB (Sync to Rabbit), so jai can neither read nor forge anything. It deletes what's been picked up, and anything after 14 days. - Desktop (src/main/relay.ts): "Rabbit SIM" is a number to text from, groups included; the SIM's history and new texts arrive; older photos are fetched when shown; names and read/unread/archived go both ways. Settings → Rabbit relay connects it. - Rabbit (Relay.java, RelayJob): no timer of its own for the battery; it rides along with the background checks, plus one network job after a text, a send or a swipe. Each send from the desktop goes out at most once and not after a day. Plain http only to jai and localhost (network_security_config). - scripts/deploy-jai.sh; tests: server unit tests, an end-to-end relay test, and DEVICE=1 relay.device.test.ts against the dev app.
1.9 KiB
1.9 KiB
bubble (voip.ms Messages)
Desktop SMS client (Electron, src/) plus its Rabbit R1 companion app
(plain Java, android/, see android/README.md).
trav's data is off limits
Never read trav's messages, contacts, accounts or anything the apps keep
about him, and never screenshot the real app showing them. Standard:
~/Documents/shared-resources/privacy.html. If reading it seems necessary,
ask trav first, every time (what and why); one yes covers one look. No
exceptions granted so far.
Where his data lives:
- Desktop:
~/.config/voip.ms Messages/(Electron userData: the message database, settings, secrets, photo cache, ui-state.json). - Rabbit R1: the private storage of
me.teafry.voipmessages(files/messages.db,files/config.json,files/media/,files/state*.json). Don'trun-asinto it, and don't screenshot that app. - Rabbit R1 SIM texts: Android's shared message store (
content://sms,content://mms, the telephony provider), which bubble reads and writes as the default SMS app. Don't query it over adb, and don't make an app the default SMS app yourself (it hands that app his texts). - jai:
~/Documents/bubble-server/data/(the relay's mailbox and token). Everything in relay.db is sealed, but it's still his messages: don't read it, and never print the token (scripts/deploy-jai.sh --tokenis for trav). The desktop keeps the relay's address, token and key in~/.config/voip.ms Messages/relay.bin.
Test with fake data only:
- Desktop:
VOIPMS_SANDBOX=/tmp/x npm run dev. - Relay:
server/test_bubble_relay.pyandtest/relay.test.tsrun a throwaway local server;DEVICE=1 npm test -- test/relay.device.test.tsdrives the dev app on a plugged-in Rabbit throughadb reverse. Never test against jai's. - Android: the dev app
me.teafry.voipmessages.dev(python3 android/build.py --dev --install, thenpython3 android/tools/push_sandbox.pyfor made-up conversations).