aboutsummaryrefslogtreecommitdiffstats
path: root/android/app/src/webview/java/io
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-09-12 16:59:10 -0700
committerAdam Soltys <[email protected]>2026-09-12 16:59:10 -0700
commit8fe3d0d28d5f15643c1737809c5f1773cb8f9f94 (patch)
tree2241df66a3115b3261d6671dd0a7fbcf6d12d236 /android/app/src/webview/java/io
parent7fcad2ddfbaae862d150430b27674606ebca299e (diff)
downloadcoinosv3-8fe3d0d28d5f15643c1737809c5f1773cb8f9f94.tar.gz
coinosv3-8fe3d0d28d5f15643c1737809c5f1773cb8f9f94.zip
Don't trust the first distributor on the phone — three were installed.
ntfy went onto a real phone and the handshake ran: our app broadcast REGISTER, ntfy answered with an endpoint (https://ntfy.sh/up…), the app stored it, and the web app took it off the launch URL and kept it. That was the link I'd said was unproven. It also turned up something the sandbox never would. The phone had THREE apps answering the distributor action — Element's and Yakihonne's internal ones alongside ntfy — and both of those exist to serve their own app, not anyone else's. Picking the first would have registered with a distributor that will never hand us an endpoint, and there'd be nothing to show for it. The spec's answer is to let the user choose, and this app has no settings screen to choose in, so it works through them instead: ask one, and if no endpoint has arrived by the next launch, ask the next. A refusal moves on immediately. Whoever answers is remembered for good. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_019mrt228Upn9nNCwGixzSLx
Diffstat (limited to 'android/app/src/webview/java/io')
0 files changed, 0 insertions, 0 deletions