3 ms·
Not quite. I'd like to have lxgr@example.com hosted at xmpp.foo.com today, but if foo.com shuts down unexpectedly one day, I'd like to be able to redirect it to
by lxgr 2mo ago
Not quite. I'd like to have lxgr@example.com hosted at xmpp.foo.com today, but if foo.com shuts down unexpectedly one day, I'd like to be able to redirect it to xmpp.bar.com.
I might lose my chat history and maybe my contact list if I don't have a local backup of it, but people would still be able to reach me as lxgr@example.com. Ideally, I'd be able to upload my local, end-to-end encrypted backup to xmpp.bar.com and continue exactly where I left off.
AT proto's main innovation to me is decoupling the concerns of user identifier and data host at the protocol level, in the same way that DNS and my web or mail host are decoupled.
- goffi 2mo agoHey. I'm currently working on this: https://xmpp.org/extensions/xep-0516.html https://xmpp.org/extensions/xep-0516.html
- lxgr 2mo agoThis is awesome, thank you!
- rtpg 2mo agoI mean apart from the uploading of the backup xmpp already lets you do this right? That's my impression at least. Maybe I'm misunderstanding something. (The premise in my understanding is that you own example.com and control its DNS records right? And not "well I hosted on foo.com as name@foo.com but it went down and now I want to move")