3 ms·

Is there any way to handle message histories that survive the XMPP server (ejabberd) being restarted? At the moment all the MUC room histories vanish if I need

• goffi 11y ago
  > Is there any way to handle message histories that survive the XMPP server (ejabberd) being restarted? Message Archive Management (XEP-0313) is supposed to do that. > And message carbons work, but since ejabberd only seems to support a single auth token meaning that if users connect with multiple devices they can't actually log out of only a single one without pulling the plug on all connected devices. Not sure to understand: if you disconnect a device, all the other devices with the same jid are disconnected? If so, it's definitely not normal, and not a spec issue. I'm also surprised to see ejabberd having this behavior, you should talk to the dev team.
  • estefan 11y ago
    > Message Archive Management (XEP-0313) is supposed to do that. Thanks, I'll check that out. > if you disconnect a device, all the other devices with the same jid are disconnected? No, not on disconnection - I can't seem to find a way to tie multiple auth tokens to a single user (one per device) to allow them to log out on different devices individually. At the moment logging out one device would disconnect all clients.