We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Cut it down Seven pages of prose for a program you install by tapping a link. Merged the first-connection page into Installing, since they are one task, and shortened everything else to what someone actually needs to do. 848 lines to 391. The reasoning that survived is the kind that changes what you do — why the bridge should not run on the public host, why there is no way past a changed host key. The rest belongs in How it works or in the source.
Put the steps first and the reasoning behind a fold The pages read as essays with instructions buried in them. Someone trying to install this wants numbered commands; the reasoning matters but not on the critical path, so it moved into collapsed sections and into How it works. Troubleshooting is tables now — it is consulted, not read.
Document how to install, connect, and reach a server that is not on the LAN Written for someone who does not have this project's infrastructure: the bridge page covers Tailscale, WireGuard and no VPN at all, and Caddy as well as nginx, where the WebSocket upgrade headers are not automatic and a default read timeout cuts an idle session every minute. Most of the platform's failures produce no error message, so Troubleshooting is written as symptom to cause rather than as a feature list.