Re: [Standards] Extending XEP-0085 Chat State Notifications, again

[Ненахов Андрей]

Counter-proposal:
>
> 
>   
> 
>
> I believe this should work fine and means we're not changing XEP-0085
> (which is, indeed, Final).
>

I'm fine with this as a messaging standard. However, I'm not really into
adding yet another XEP with number in 400s, but if it's how things work, ok.

What's the next step? Following discussion on x...@muc.xmpp.org i'm not
really sure what to do to move things forward. Should I submit a xep with
, or who?

-- 
Andrew Nenakhov
CEO, Redsolution, Inc.
https://redsolution.com 
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Extending XEP-0085 Chat State Notifications, again

[Kevin Smith]

On 1 Mar 2019, at 09:18, Dave Cridland  wrote:
> 
> 
> 
> On Fri, 1 Mar 2019 at 08:35, Ненахов Андрей  > 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  
> element:
> from='berna...@shakespeare.lit /pda'
>to='franci...@shakespeare.lit /elsinore'
>type='chat'>
>  >
> 
> 
> 
> Counter-proposal:
> 
> 
>   
> 
> 
> I believe this should work fine and means we're not changing XEP-0085 (which 
> is, indeed, Final).


I don’t immediately see issues with this.

/K___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Extending XEP-0085 Chat State Notifications, again

[Dave Cridland]

On Fri, 1 Mar 2019 at 08:35, Ненахов Андрей 
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 
> element:
> from='berna...@shakespeare.lit/pda'
>to='franci...@shakespeare.lit/elsinore'
>type='chat'>
> 
> 
>
>
Counter-proposal:


  


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 
> ___
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Extending XEP-0085 Chat State Notifications, again

[Daniele Ricci]

FWIW, I second that. I'm using a custom extension for now, but I'd really
like to see this standardized. The type attribute is a nice idea.

On Fri, 1 Mar 2019, 09:50 Sergey Ilinykh,  wrote:

> I like the addition.
>
> Best Regards,
> Sergey
>
>
> пт, 1 мар. 2019 г. в 11:36, Ненахов Андрей  >:
>
>> 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
>>  element:
>> >from='berna...@shakespeare.lit/pda'
>>to='franci...@shakespeare.lit/elsinore'
>>type='chat'>
>> 
>> 
>>
>> 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 
>> ___
>> Standards mailing list
>> Info: https://mail.jabber.org/mailman/listinfo/standards
>> Unsubscribe: standards-unsubscr...@xmpp.org
>> ___
>>
> ___
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

Re: [Standards] Extending XEP-0085 Chat State Notifications, again

[Sergey Ilinykh]

I like the addition.

Best Regards,
Sergey


пт, 1 мар. 2019 г. в 11:36, Ненахов Андрей :

> 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 
> element:
> from='berna...@shakespeare.lit/pda'
>to='franci...@shakespeare.lit/elsinore'
>type='chat'>
> 
> 
>
> 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 
> ___
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: standards-unsubscr...@xmpp.org
> ___
>
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___

[Standards] Extending XEP-0085 Chat State Notifications, again

[Ненахов Андрей]

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 
element:




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 
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
___