3 ms·

Just for the record, we are also working on a next-gen XMPP client, with decentralized blogging, file sharing, end 2 end encryption and all, and planing to do a

by goffi 11y ago

Just for the record, we are also working on a next-gen XMPP client, with decentralized blogging, file sharing, end 2 end encryption and all, and planing to do an Android port. Other projects like Movim also do similar things too, XMPP is definitely very alive these days. Sending message to other devices is managed by message carbons which is in last call for being a standard XEP, and support is becoming more and more common. XMPP is all but deprecated, very active, working well, with a large ecosystem. But is really badly known by most of people(I have by the way started a series of article to explain it: http://www.goffi.org/tag/talk_xmpp http://www.goffi.org/tag/talk_xmpp). It's really difficult to be heard these days, but there is a new wave in XMPP world (check our project: http://salut-a-toi.org http://salut-a-toi.org or movim: http://movim.eu http://movim.eu).

estefan 11y ago
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 to restart ejabberd which is a farce in a cloud world... 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. Are these only ejabberd issues or issues in the XMPP specs? BTW this is for realtime chat on for an app, nothing federated... I'm open to non-XMPP options too.
- 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.
jessaustin 11y ago
XMPP is all but deprecated... Just a short English usage note: "all but" means something like "almost". Judging by the rest of your post, you probably mean "XMPP is far from deprecated" here.
- goffi 11y ago
  yes indeed, I'm not a native speaker as you can guess. Thanks for the correction :)
  - kbenson 11y ago
    I usually read "X is all but Y" as "X is Y in all but name", but there are subtle distinctions that could be hard for a non-native speakers[1] to grasp without knowing about them. 1: http://english.stackexchange.com/questions/9967/all-but-idiom-has-two-meanings http://english.stackexchange.com/questions/9967/all-but-idio...

by goffi 11y ago

estefan 11y ago

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 to restart ejabberd which is a farce in a cloud world... 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. Are these only ejabberd issues or issues in the XMPP specs? BTW this is for realtime chat on for an app, nothing federated... I'm open to non-XMPP options too.

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.

jessaustin 11y ago

XMPP is all but deprecated... Just a short English usage note: "all but" means something like "almost". Judging by the rest of your post, you probably mean "XMPP is far from deprecated" here.

goffi 11y ago
yes indeed, I'm not a native speaker as you can guess. Thanks for the correction :)
- kbenson 11y ago
  I usually read "X is all but Y" as "X is Y in all but name", but there are subtle distinctions that could be hard for a non-native speakers[1] to grasp without knowing about them. 1: http://english.stackexchange.com/questions/9967/all-but-idiom-has-two-meanings http://english.stackexchange.com/questions/9967/all-but-idio...