4 ms·

That might look a bit weird on the outside, but this is how protocol design works in the XSF. First you make a proposal (which is marked as Experimental), then

by ge0rg 9y ago

That might look a bit weird on the outside, but this is how protocol design works in the XSF. First you make a proposal (which is marked as Experimental), then you implement it and wait for other people to implement it as well, and then you look how well it works and whether it has rough edges that need fixing. If it is considered good, it moves on to Draft and then to Final [0]. This process could be faster for sure, but that requires independent developers to work on implementations and to share their experience. [0] https://xmpp.org/extensions/xep-0001.html#approval-std https://xmpp.org/extensions/xep-0001.html#approval-std

detaro 9y ago
Is there a set of mobile and desktop clients that support all these things you said were "addressed" properly? People always parade Conversations, but if I want phone-only I already have to many messengers. Because if have to look through tables and bug trackers to figure out what client/server combination I can use (and have to pester my friends to use(!)) you can't count something as "addressed" IMHO. I still use only a very basic set of features with XMPP, because in my experience attempts to get anything advanced are way to time-intensive to be worth it for the few buddies still on XMPP, and I can't really push new people onto it that way.
dmitriid 9y ago
> WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft. Let me stress this: > production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft That's from XEP-0363: HTTP File Upload.

by ge0rg 9y ago

detaro 9y ago

Is there a set of mobile and desktop clients that support all these things you said were "addressed" properly? People always parade Conversations, but if I want phone-only I already have to many messengers. Because if have to look through tables and bug trackers to figure out what client/server combination I can use (and have to pester my friends to use(!)) you can't count something as "addressed" IMHO. I still use only a very basic set of features with XMPP, because in my experience attempts to get anything advanced are way to time-intensive to be worth it for the few buddies still on XMPP, and I can't really push new people onto it that way.

dmitriid 9y ago

> WARNING: This Standards-Track document is Experimental. Publication as an XMPP Extension Protocol does not imply approval of this proposal by the XMPP Standards Foundation. Implementation of the protocol described herein is encouraged in exploratory implementations, but production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft. Let me stress this: > production systems are advised to carefully consider whether it is appropriate to deploy implementations of this protocol before it advances to a status of Draft That's from XEP-0363: HTTP File Upload.