so, when someone's client leaves a MUC they go offline, right, and leave the MUC
eta
could you continue to send that client messages for the MUC and would they be stored in offline storage?
Ge0rG
eta: when a client goes offline, their server will normally respond with errors to all MUC messages, leading to a kick of the client
eta
awww
Ge0rG
eta: the most interesting idea so far was to register XEP-0357: Push Notifications on each MUC, so that the MUC would send a push when a given client leaves, causing the client to be woken up and to rejoin
Ge0rG
AFAIK it wasn't implemented yet
eta
Ge0rG: I'm mainly trying to avoid having to store messages for a transport
eta
or at least, trying to offload storage to user servers
Ge0rG
eta: that's a nice idea, but won't work because users' servers drop groupchat from MAM
eta
Ge0rG: and offline storage?
Ge0rG
eta: never stored groupchat, and is also rather deprecated
eta
ah
eta
Ge0rG: what's wrong with offline storage?
vallhas left
Ge0rG
eta: it will be depleted by the first client coming online, your second client won't see anything from it
eta
oh is it not per-resource?
Zash
I experimented with having everything sent from the users bare JID, instead of the full JID
eta
okay that's a bit garbage
eta
Zash: yeah, the minimix thing
Zash
Yeah, that
eta
but that doesn't solve the MAM issue
Zash
Maybe we've talked about it
eta
we have :)
Zash
eta: Not directly, but it can solve the MAM issue, with some trickery.
eta
Zash: i.e. get the MAM service to store groupchat messages too?
Zash
You'd have to have the minimix and MAM conspire together
Ge0rG
what we need is more trickery.
eta
(and intercept MAM queries for the room JID)
Zash
Hacks upon hacks upon hacks
eta
that's how protocols work, of course
eta
"layers are only added, never removed"
eta
Zash: surely this would solve all the problems though?
eta
I guess it'd impose a storage burden on the servers
Zash
ALL THE PROBLEMS
Ge0rG
what about just going forward with XMPP 2.0?
eta
Ge0rG: XMPP *what*
Ge0rG
eta: https://wiki.xmpp.org/web/XMPP_2.0
eta
Zash: yep, all the problems all fixed, no more work needed
eta
Ge0rG: oh, fancy
Жокирhas left
lovetoxhas left
vallhas joined
moparisthebesthas left
moparisthebesthas joined
debaclehas joined
lovetoxhas joined
vallhas left
Beherithas left
Beherithas joined
waqashas joined
Beherithas left
paulhas joined
Beherithas joined
larmahas left
larmahas joined
test2has joined
goffihas joined
Beherithas left
Beherithas joined
larmahas left
Beherithas left
Beherithas joined
Bartekhas joined
etahas left
etahas joined
etahas left
etahas joined
Bartekhas left
dropshas left
dropshas joined
Beherithas left
Beherithas joined
Beherithas left
larmahas joined
Beherithas joined
ralphmhas left
ralphmhas joined
Beherithas left
Beherithas joined
Beherithas left
Beherithas joined
lovetox
its assumed that a well maintained server, has pubsub persist items set to True by default on new nodes, or?
lovetox
im asking if i need to have code that reconfigures the node
lovetox
or if this is something i can tell users to bug the admin with