Hi,

On the chat marker XEP, as far as I remember, it looked consistent to me when I 
implemented support for it in Jappix.
So, from an application developer perspective, the spec. is a good fit for what 
it says it does and I had no trouble w/ it, nor requirements not fulfilled.

Cheers,

--

Valerian Saliou
Crisp <https://crisp.im/> - Connect your customers to your team.

Looking for my contact details? <https://valeriansaliou.name/>
> On Jan 25, 2017, at 5:51 PM, Daniel Gultsch <[email protected]> wrote:
> 
> Hi,
> 
> 2017-01-18 17:36 GMT+01:00 Sam Whited <[email protected]>:
>> ## Move XEP-0153: vCard-Based Avatars to "Obsolete"
>> 
>> https://github.com/xsf/xeps/pull/357
>> 
>> - Tobias         -1
>> - SamWhited      +1
>> - Dave Cridland  -1
> 
> +1
> 
>> ## Accept Bind 2.0 as Experimental
>> 
>> https://xmpp.org/extensions/inbox/bind2.0.html
>> 
>> - SamWhited      +1
>> - Dave Cridland  +1
>> - Tobias         +1
> 
> +1
> 
> 
>> ## Consider advancing XEP-0333: Chat Markers to LC
>> 
>> - This is one of the XEPs that Sam deferred, but he thinks its widely used so
>>  maybe it's worth advancing.
>> - Tobias, Dev, and Dave question the assumption that it's widely used.
>> - Dave notes that this is what LC is for, if it's good enough to implement, 
>> and
>>  seems to be working, it should be LCed and people will respond if there are
>>  issues with it.
>> - Dave also notes that "widespread use" might matter for Draft->Final but not
>>  for Experimental->Draft
> 
> Jappix used to implement it IIRC.
> But in any case it does what it is supposed to. So I am in favor of
> advancing it.
> 
> cheers
> Daniel
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: [email protected]
> _______________________________________________

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to