One example use-case for Quick Response is the memberbot, which asks yes/no multiple times during membership voting. Memberbot does not use a form to ask for yes/no, but a plaintext message. The idea of Quick Response is to enable memberbot to tell clients that "yes" and "no" are possible answers, so that clients can offer convenient UI to quickly select one of these possibilities. I think forms would be helplessly overkill here.
--
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
Gesendet: Dienstag, 21. April 2020 um 13:46 Uhr
Von: "Andrew Nenakhov" <[email protected]>
An: "XMPP Standards" <[email protected]>
Betreff: Re: [Standards] Proposed XMPP Extension: Quick Response
Von: "Andrew Nenakhov" <[email protected]>
An: "XMPP Standards" <[email protected]>
Betreff: Re: [Standards] Proposed XMPP Extension: Quick Response
вт, 21 апр. 2020 г. в 16:29, <[email protected]>:
Why would you use a form to send a plaintext message?
Because they already exist and are capable of doint what this XEP intends to do. It might be convenient for a recepient to select one of several options, but it is not convenient for the asking entity to send such requests and review answers for them, so such feature will likely used only by bots. And for bot it is eaiser to process a form than a text message.
--
Andrew Nenakhov
CEO, redsolution, OÜ
https://redsolution.com
https://redsolution.com
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
