Re: [Standards] LAST CALL: XEP-0443 (XMPP Compliance Suites 2021)
Dear all, I would like to also have XEP-0425: Message Moderation [1] added to the XMPP Compliance Suites 2021 as spam messages to MUCs are happening more often. Would you consider adding it to advanced client and advanced server? Best regards, Martin [1] https://xmpp.org/extensions/xep-0425.html signature.asc Description: PGP signature ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] LAST CALL: XEP-0443 (XMPP Compliance Suites 2021)
This message constitutes notice of a Last Call for comments on XEP-0443. Title: XMPP Compliance Suites 2021 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-0443.html This Last Call begins today and shall end at the close of business on 2020-11-03. Please consider the following questions during this Last Call and send your feedback to the standards@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-unsubscr...@xmpp.org ___
Re: [Standards] LAST CALL: XEP-0443 (XMPP Compliance Suites 2021)
Hi, > 1. Is this specification needed to fill gaps in the XMPP protocol > stack or to clarify an existing protocol? Yes > > 2. Does the specification solve the problem stated in the introduction > and requirements? Yes > 3. Do you plan to implement this specification in your code? If not, > why not? Yes. My client has some, if not all the compliance. > 4. Do you have any security concerns related to this specification? No > 5. Is the specification accurate and clearly written? Yes I would like to suggest to ~include~ mention message styling in the document. Not as a requirement for base or advanced clients but as a bit of a hand wave-y "If you are planning on implementing some kind of mark down ish text formatting anyway; feel free to take a look at &xep393;. You don’t have to implement it to be compliant. If you want some light mark down anyway please consider using a standardized syntax" cheers Daniel ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] LAST CALL: XEP-0443 (XMPP Compliance Suites 2021)
This message constitutes notice of a Last Call for comments on XEP-0443. Title: XMPP Compliance Suites 2021 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-0443.html This Last Call begins today and shall end at the close of business on 2020-11-03. Please consider the following questions during this Last Call and send your feedback to the standards@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-unsubscr...@xmpp.org ___
