Re: [Standards] XEP-0333: meaning of 'acknowledged'

I think, user have to explicitely acknowledge. So, it should be something like "Ack" button for this. Acknowledge by other user action is not a good idea, I think. 21 мая 2020 г. 19:45:00 GMT+05:00, Matthew Wild пишет: >Hi folks, > >XEP-0333 defines the state: > >> acknowledged -- the message

Re: [Standards] XEP-0393 and XEP-0394 naming

Hello!8 марта 2018 г. 21:26 пользователь VanitasVitae написал:Also if we'd do that, we'd have "Message Markup" and "Message Markdown"...Yeah, but it will be really funny. Just like "more" and "less" viewers Linux! :-)With my best

Re: [Standards] 2017-11-08 XSF Council Minutes

It's too bad you didn't use your veto against that awful proto.It don't even worth to waste XEP number for things like this one.___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe:

Re: [Standards] LAST CALL: XEP-0313 (Message Archive Management)

Hello!17 нояб. 2017 г. 20:22 пользователь Matthew Wild написал:On 15 November 2017 at 17:32, Kozlov Konstantin wrote: > That's nice! > This XEP is still too raw. Just out of curiosity, care to share your thoughts on what needs polish? I don't disagree

Re: [Standards] XEP-0167: How to?

Hello! 20 июня 2016 г. 0:02 пользователь Philipp Hancke написал: > > Am 19.06.2016 um 09:12 schrieb Kozlov Konstantin: > > Hello! > > > > typically that is done by looking at the payload type of the rtp > packets. You could have multiple 'codecs' like rtx after all

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Kevin Smith wrote: On Thu, Jun 17, 2010 at 2:29 PM, Konstantin Kozlov yag...@yandex.ru wrote: For me, knowing, that user on the other side read the message is very useful. 'cause if I got received / confirmation from the other side, but getting no read / confirmation from the other side

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Waqas Hussain пишет: On Fri, Jun 18, 2010 at 5:00 PM, Konstantin Kozlov yag...@yandex.ru wrote: Well. According to my experience, based on knowledge of my behavior and behavior of my friends, the fact that my message is not new anymore on the other side is enough to assume that user

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Yann Leboulanger пишет: On 06/18/2010 08:20 PM, Konstantin Kozlov wrote: Waqas Hussain пишет: See XEP-0085: Chat State Notifications. That nicely solves the problem of determining if the other side is paying attention to the conversation. No. We don't know how messages represented

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Waqas Hussain wrote: On Fri, Jun 18, 2010 at 11:20 PM, Konstantin Kozlov yag...@yandex.ru wrote: No. We don't know how messages represented on the other side. It could be chat windows, pop-ups or whatever author of the application can imagine. So, in some implementations some (or all) chat

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Kevin Smith wrote: On Wed, Jun 16, 2010 at 8:10 PM, Konstantin Kozlov yag...@yandex.ru wrote: Yes. Let's sort out what means received, displayed and read to decide which of them are needed and which are not. Yes. So: What's the use case for needing to know when the user's client

Re: [Standards] XEP-0184: received/ vs. displayed/ vs. read/

Kevin Smith wrote: On Wed, Jun 16, 2010 at 7:43 PM, Kozlov Konstantin yag...@yandex.ru wrote: On 06/16/2010 08:27 PM, Kevin Smith wrote: The log, attached to the first message clearly says that even author of XEP-0184 do not agree with you, Kevin. So, why do you argue? Well,