Is there any way to handle message histories that survive the XMPP server (ejabberd) being restarted?<p>At the moment all the MUC room histories vanish if I need to restart ejabberd which is a farce in a cloud world...<p>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&#x27;t actually log out of only a single one without pulling the plug on all connected devices.<p>Are these only ejabberd issues or issues in the XMPP specs?<p>BTW this is for realtime chat on for an app, nothing federated... I&#x27;m open to non-XMPP options too.