thoughtsync

Unlink was local-only. It cleared the server URL, token and cursor from the
device, and left the bearer token valid on the server indefinitely — so someone
who unlinked because the laptop was being sold or handed on believed they had
revoked access when they hadn't.

The blocker was identification, not intent: a token pasted from the web app
never carried a device id, and /api/auth/me describes the user, not the device
row, so DELETE /devices/<id> could only ever have worked for one of the two ways
this app can be linked. DELETE /api/auth/devices/self keys off the token in the
Authorization header instead, which the caller always holds — one route that
works for both paths, owner-scoped like the rest, and no local schema change.

Unlinking is never blocked on the network. Wanting to stop syncing is a local
decision, so the revoke is attempted first, its outcome carried back, and the
link cleared either way. When the token survives — server unreachable, or older
than the route — the Sync screen says so in place, with where to revoke it. A
toast would have been the wrong shape for that: it disappears, and this is
exactly what someone returns to the screen to check.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-16 10:31:06 -04:00

conftest.py

config: fix media path at /var/thoughtsync (no env knob)

2026-07-20 20:07:15 -04:00

test_acl.py

M0: backend skeleton — Quart factory, async DB, auth, ACL spine, migrations

2026-07-19 13:09:37 -04:00

test_admin.py

M1.5 backend: admin role + DB-backed settings, DB-URL-only install

2026-07-19 18:25:04 -04:00

test_app.py

M0: backend skeleton — Quart factory, async DB, auth, ACL spine, migrations