Asks the channel to re-announce state the sender missed — typically fired by a client that just connected and wants the current picture without waiting a full cadence. Part of the IRC schema reference.
{
"type": "resend_request",
"include": [
"presence",
"entity_owner"
]
}| Field | Type | Constraints |
|---|---|---|
type | "resend_request" | Discriminator |
include | array | Any of presence, logout, entity_owner |
A well-behaved peer responds to a resend_request naming presence by immediately pushing a fresh presence batch for its online users, rather than waiting for the next scheduled one. That is what makes your users appear instantly to a freshly-connected client instead of seconds later.
Requests are coalesced
Every peer answers a resend_request with its whole cache, so each one costs the channel thousands of messages. The relay forwards at most one per channel every 5 seconds. A request that arrives inside that window is held and merged with any others, and then forwarded once the window reopens. Expect a freshly connected client to wait up to that long for its picture.
Repeated entity_owner answers are also deduplicated per stream. A stream that already received a given pearl and owner pair within the last minute is not sent it again. A pearl that changes owner is a new pair and is always delivered.