You'll notice
Useful3 Signal3
Your rate limit status now reaches a connected remote client right away.
What's wrong with this entry?
Anonymous. No account, no email.
What
Rate-limit state now reaches a connected remote client immediately. On bridge connect the current state is written to the peer, and later rate-limit events are written to the bridge channel as well as the local stream. Forwarding failures are logged, not thrown.
Details
- The connect-time send is skipped if a rejection window has already elapsed, and is recorded as
bridge_rate_limit_forward. - Both paths build the event through one shared helper.
- The connect-time send is also guarded by an internal predicate whose source of truth sits outside this code path.
Evidence
bridge_rate_limit_forward, rate_limit_event forward failed
Strings lifted out of the shipped bundle, so the claim above can be checked against them.