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:
@@ -87,5 +87,16 @@ Install/Sync buttons then target the dev app with the sandbox's made-up data.
|
||||
side, through `MmsFiles`. Long texts go as multipart SMS; photos, voice notes
|
||||
and group chats as MMS (needs mobile data on). The dev app's sandbox never
|
||||
uses the SIM.
|
||||
- Relay (`Relay`, `RelayJob`): the desktop's link through jai (its
|
||||
`src/main/relay.ts`, server `server/bubble_relay.py`). config.json's `relay`
|
||||
(address, token, AES-256-GCM key) comes from Sync to Rabbit. The SIM's
|
||||
messages go to the desktop, sends typed there go out here (each one at most
|
||||
once, and not after a day), chat names and read status go both ways, and
|
||||
older photos are sent when the desktop asks. For the battery it has no timer
|
||||
of its own: it rides along with `PollJob`'s checks, plus one network job a few
|
||||
seconds after something happens here (a text in, a send done, a swipe or
|
||||
rename), and a catch-up when the app is opened (at most once a minute). Plain
|
||||
http is allowed only to jai's tailscale address and localhost
|
||||
(`res/xml/network_security_config.xml`).
|
||||
- The scroll wheel is left alone: it stays the volume control (and volume
|
||||
down + the side button still takes a screenshot).
|
||||
|
||||
Reference in New Issue
Block a user