ci / node (pull_request) Skipped
ci / version (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m27s
ci / stalwart (stalwartlabs/stalwart@sha256:baafeacd6cbde77acdd94af49972d41c6709e54a376df48e18a9fe3f445eb3d5, 1.0.0) (pull_request) Skipped
ci / stalwart (stalwartlabs/stalwart@sha256:c429b311c93db5606598abc1c68225a85a6953183848ae01bee9c6a98885836c, 0.16.27) (pull_request) Skipped
ci / docker-build (pull_request) Skipped
ci / publish (pull_request) Skipped
Since #72 the relay answers the browser before Stalwart has, so an open stream no longer proves anything: when Stalwart never answers, the dot would turn green while no updates arrive. The client now shows "connected" on the first ping or state event instead of on open, and resets its backoff there too, so a stream that opens and ends at once keeps backing off instead of retrying every second. Relayed tabs get Stalwart's own first ping. Fan-out has no upstream ping, so the server sends one when a tab joins fan-out, directly or by moving off the relay.