Document pairing through Funnel and other HTTPS proxies
Document relay mode, and correct what 0.8.0 makes wrong
Connecting opened with "there is no account, no pairing code and no QR step",
which this release turns into three false statements in one sentence. Security
said the app has "no tokens, no cookies, no TLS, no pairing" as a flat fact
rather than as a description of one of the two modes it now has. Both are the
kind of wrong that sends a reader looking for a fault that is not there.
New Relay page covers setup, the two pairing routes and why they do not prove
the same thing, discovery, and the three 403s the relay answers for reasons only
the client can tell apart. Troubleshooting gains those three, keyed on the exact
strings the app shows, as the rest of that page is.
Two corrections that predate this release and were found while editing:
- The compatibility matrix stopped at 0.3.1 and rc.5. It now runs to 0.8.0, and
says outright that the baseline records what was tested rather than gating
anything.
- Connecting claimed the app compares the harness version and warns on a
mismatch. It has never done that, and docs/COMPATIBILITY.md says so — it
degrades on shape instead.
Release notes gain rows for 0.4.0 through 0.8.0 and a section for 0.8.0. The
four earlier releases get a line each rather than invented prose; the changelog
is the canonical account of those.