v0.5.0: bubble for Android 0.5.0 — text from the Rabbit's SIM on the desktop, and chat names and read status sync, through jai
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.
This commit is contained in:
@@ -22,10 +22,18 @@ Where his data lives:
|
||||
`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).
|
||||
|
||||
Reference in New Issue
Block a user