On Fri, 1 Mar 2019 at 08:35, Ненахов Андрей <[email protected]> wrote:
> This was discussed in July 2018 and, I guess, moved nowhere, but I'll > raise the issue once again. Any decent messenger bar XMPP based ones have > capabilities to signal type of user activity beyond just "composing a > message", but also "recording voice message", "recording video message", > "uploading file", .... > > We NEED that in our clients, and, subsequently, we'd prefer it to be an > XMPP standard. > > So far we've extended XEP-0085 by adding a "type" attribute to <composing> > element: > <message > from='[email protected]/pda' > to='[email protected]/elsinore' > type='chat'> > <composing type='audio' xmlns='http://jabber.org/protocol/chatstates'/> > </message> > > Counter-proposal: <composing xmlns='...'> <subtype xmlns='something-else' type='audio'/> </composing> I believe this should work fine and means we're not changing XEP-0085 (which is, indeed, Final). > Works OK by us and it does not break any clients with XEP-0085 that we > know of. > > However, last time when this matter was raised, there were objections that > 0085 is 'final' and therefore we can't change anything because of reasons > and was essentially discarded. Hope this time it'll be different. > > -- > Andrew Nenakhov > CEO, Redsolution, Inc. > https://redsolution.com <http://www.redsolution.com> > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: [email protected] > _______________________________________________ >
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
