Hi Standards, I had the opportunity to discuss with people interested in <moved/> at the 35C3.
The current state of <moved/> is not ideal, it is pretty much ephemeral, and I Ge0rG has been working on it, and we've been discussing it at the Düsseldorf sprint[0]. I'll keep this thread focused on my question though, this is to provide a bit of background. One question that came back was how to cope with servers going offline, or shutting down. When this is the case, a user has no way to prove their identity. What was suggested from a user at CCC (owl, for credit), was to be able to define "metacontacts". Not in the way of 209[1], where metacontacts are purely a client-side feature, but as something that a user would be able to declare for themselves. userAB has accountA and accountB, they tell their contacts that both accounts are their own. In the context of <moved/>, when serverA if offline, userAB wants to tell their contacts that they are moving their main account on accountB. AccountB now has the authority to do this, as accountA has agreed beforehand. This should probably get its own XEP and does not need to be linked to <moved/> specifically. This is also pretty much at the "thoughts" level at the moment, and there are lots of unanswered questions, like the obvious security concerns. Any strong arguments against this? There isn't much to bikeshed at the moment as there isn't anything specified. Are there any resources out there already that are worth looking into? Cheers, [0]: https://wiki.xmpp.org/web/Sprints/2018_November_Dusseldorf/Pad grep <moved/> [1]: https://xmpp.org/extensions/xep-0209.html Metacontacts -- Maxime “pep” Buquet
signature.asc
Description: PGP signature
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
