v0.9.5: bubble for Android 0.7.8 — the relay is just a relay server: its address is a setting, and deploy-relay.sh reads scripts/relay.env
This commit is contained in:
@@ -1,8 +1,9 @@
|
||||
#!/usr/bin/env python3
|
||||
"""bubble-relay: a mailbox between the desktop app and the Rabbit R1. Runs on jai.
|
||||
"""bubble-relay: a mailbox between the desktop app and the Rabbit R1. Runs on a
|
||||
server of yours that both can reach (a tailscale address is the easy way).
|
||||
|
||||
It never sees a message: every blob is AES-256-GCM sealed by the apps with a
|
||||
key jai doesn't have (the desktop makes it and hands it to the Rabbit over
|
||||
key the server doesn't have (the desktop makes it and hands it to the Rabbit over
|
||||
USB). This only stores opaque base64 strings, hands each device what the
|
||||
other one posted, and forgets them once picked up (or after KEEP_DAYS).
|
||||
|
||||
@@ -19,7 +20,7 @@ to it, which the other side posted, so those are deleted. `more` = there's
|
||||
more than fits in one answer: call again with the new cursor. A cursor past
|
||||
anything this server ever issued (a wiped server) means "from the start".
|
||||
|
||||
python3 bubble_relay.py --host 100.69.139.40 --port 8080 --data DIR
|
||||
python3 bubble_relay.py --host <tailscale address> --port 8080 --data DIR
|
||||
"""
|
||||
|
||||
import argparse
|
||||
|
||||
Reference in New Issue
Block a user