# 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't `run-as` into 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 --token` is 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.py` and `test/relay.test.ts` run a throwaway local server; `DEVICE=1 npm test -- test/relay.device.test.ts` drives the dev app on a plugged-in Rabbit through `adb reverse`. Never test against jai's. - Android: the dev app `me.teafry.voipmessages.dev` (`python3 android/build.py --dev --install`, then `python3 android/tools/push_sandbox.py` for made-up conversations).