-
singpolyma
I wonder if we could push csi info up to mucs so they don’t send presence for a bit and then send it again later when we have an active user again or the mic is sending a message. This way even when a message from something else comes in you don’t get that flood of presence from the muc until you actually want it
-
larma
Shouldn't CSI already be able to do that without pushing the state to the MUC? I think holding back presences until the client signals active is basically *the* example for CSI
-
larma
> Suppress presence updates until the client becomes active again. On becoming active, push the latest presence from each contact.
-
singpolyma
but when you get a message all stanzas come through, regardless of csi state
-
singpolyma
if the mic was holding you’d get just the message✎ -
singpolyma
if the muc was holding you’d get just the message ✏
-
Kev
If we follow the GC3 'you can opt in/out of presence/messages' then yes, that could happen.
-
singpolyma
yeah that’s what made me think of it, but I’m not sure I want to opt out so much as delay
-
Kev
That's mostly the same as opt-out, and then opt-in+catch-up, I think?
-
singpolyma
yeah I think so