On Sonntag, 13. Januar 2019 17:33:38 CET Ненахов Андрей wrote: > There is, however, a really big problem that no one seems to be > talking about - it's not the protocol, but accompanying behaviour. > Simple example: subscription request. It looks like very simple, but > it's not. It is more or less straightforward only if user has just one > device. But if it has more devices? > - Romeo has XMPP clients on phone and tablet > - Romeo has received subscription request from Juliet > - Romeo opened dialog on tablet, but switched to phone > - Romeo opened same dialog on phone and accepted subscription > - What should happen on tablet? Should it close this dialog? What > should tablet open after closing dialog? main screen, or user details?
Those are indeed important considerations, but not relevant to the current form of Compliance Suites. Note that the XSF is primarily a *XMPP Standards* Organisation, and as such focuses on the protocol. Still. The issues you raise are important. There are several people interested in doing similar things, and I suggest that you hang out in the xmpp:[email protected]?join or xmpp:[email protected]?join MUCs and/or contribute to the wiki (there are pages such as [1], [2], [3] which could use some contributions, with cases like the one you described). [1]: https://wiki.xmpp.org/web/XMPP_IM_Client_Design_Guidelines [2]: all in https://wiki.xmpp.org/web/Category:Easy_XMPP [3]: https://wiki.xmpp.org/web/Usability/Glossary
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
