On Freitag, 2. November 2018 17:26:16 CET Timothée Jaussoin wrote:
> Le mardi 25 septembre 2018 à 19:49 +0200, Timothée Jaussoin a écrit :
> > I just reviewed the XEP-: MUC Avatars and I would like to discuss some
> > ideas about it before proposing adjustments.
> >
> > The core idea of this
Le mardi 25 septembre 2018 à 19:49 +0200, Timothée Jaussoin a écrit :
> I just reviewed the XEP-: MUC Avatars and I would like to discuss some
> ideas about it before proposing adjustments.
>
> The core idea of this XEP is to expose the Vcard hash in the bare MUC JID
> disco#info and notify
On Thu, 27 Sep 2018 at 13:09, Dave Cridland wrote:
> On Thu, 27 Sep 2018 at 12:56, Kim Alvefur wrote:
>>
>> Hi,
>>
>> On Tue, Sep 25, 2018 at 07:49:24PM +0200, Timothée Jaussoin wrote:
>> > What I'd like to propose is to generalize this XEP
>>
>> I am opposed to entrenching vcard-temp more.
>>
>
Hi,
On Tue, Sep 25, 2018 at 07:49:24PM +0200, Timothée Jaussoin wrote:
> What I'd like to propose is to generalize this XEP
I am opposed to entrenching vcard-temp more.
This MUC avatar XEP is as I understand it meant to define a slightly
less breaking way to do something that was already
On Tue, 25 Sep 2018 at 18:49, Timothée Jaussoin wrote:
> I just reviewed the XEP-: MUC Avatars and I would like to discuss some
> ideas about it before proposing adjustments.
>
> The core idea of this XEP is to expose the Vcard hash in the bare MUC JID
> disco#info and notify it using a
I just reviewed the XEP-: MUC Avatars and I would like to discuss some
ideas about it before proposing adjustments.
The core idea of this XEP is to expose the Vcard hash in the bare MUC JID
disco#info and notify it using a message 104.
This is a really specific use case that solves a really
