Under the hood
Useful1 Signal2
A reconnect backoff and heartbeat schedule appears, with no identifiable consumer.
Retry constants exist; which connection uses them is not visible.
What's wrong with this entry?
Anonymous. No account, no email.
What
A new set of connection-retry constants appears: retries start at 1s and double up to a 30s cap, a connection must stay up 60s to count as healthy, 10 consecutive failures stop retrying, and a presence heartbeat goes out every 15s. Which connection uses these is not identifiable from the build.
Evidence
maxConsecutiveFailures
Strings lifted out of the shipped bundle, so the claim above can be checked against them.