[Standards] LAST CALL: XEP-0423 (XMPP Compliance Suites 2020)

Paul Schaub vanitasvitae at fsfe.org
Wed Oct 23 18:41:10 UTC 2019

I'm not quite happy with the fact that an advanced mobile client must support push. While I understand the rationale behind this (*cough* iOS *cough*), I dislike the fact that in order to be considered an advanced client, the client MUST depend on a centralized push service (for example Google GCM/Firebase/whatever it is called nowadays).
I can only speak for my own experiences, but I never had issues with battery life without Google services.

Wed Oct 23 17:07:41 GMT+02:00 2019 Jonas Schäfer (XSF Editor) <jonas at wielicki.name>:
> This message constitutes notice of a Last Call for comments on
> XEP-0423.
> Title: XMPP Compliance Suites 2020
> Abstract:
> This document defines XMPP application categories for different use
> cases (Core, Web, IM, and Mobile), and specifies the required XEPs
> that client and server software needs to implement for compliance with
> the use cases.
> URL: https://xmpp.org/extensions/xep-0423.html
> This Last Call begins today and shall end at the close of business on
> 2019-11-06.
> Please consider the following questions during this Last Call and send
> your feedback to the standards at xmpp.org discussion list:
> 1. Is this specification needed to fill gaps in the XMPP protocol
> stack or to clarify an existing protocol?
> 2. Does the specification solve the problem stated in the introduction
> and requirements?
> 3. Do you plan to implement this specification in your code? If not,
> why not?
> 4. Do you have any security concerns related to this specification?
> 5. Is the specification accurate and clearly written?
> Your feedback is appreciated!
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________

More information about the Standards mailing list