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:
2026-11-06 17:35:00 -08:00
parent e1bceb06a3
commit 96c368dfd1
39 changed files with 1638 additions and 53 deletions
+4
View File
@@ -22,6 +22,10 @@ const api: Api = {
rabbitInstall: (mode) => ipcRenderer.invoke('rabbitInstall', mode),
rabbitSync: () => ipcRenderer.invoke('rabbitSync'),
onRabbitProgress: (cb) => on('rabbitProgress', cb),
relayStatus: () => ipcRenderer.invoke('relayStatus'),
relayConnect: (url, token) => ipcRenderer.invoke('relayConnect', url, token),
relayDisconnect: () => ipcRenderer.invoke('relayDisconnect'),
onRelayStatus: (cb) => on('relayStatus', cb),
listContacts: () => ipcRenderer.invoke('listContacts'),
listAddressBooks: () => ipcRenderer.invoke('listAddressBooks'),