On 02.06.2018 14:47, Kevin Smith wrote:
> On 2 Jun 2018, at 13:01, Florian Schmaus wrote:
>>
>> On 02.06.2018 13:46, Kevin Smith wrote:
On 2 Jun 2018, at 11:44, Florian Schmaus wrote:
I think I'm currently in the
- messages from channel@service/nick
- IQs to/from and presence
On 2 Jun 2018, at 13:01, Florian Schmaus wrote:
>
> On 02.06.2018 13:46, Kevin Smith wrote:
>>> On 2 Jun 2018, at 11:44, Florian Schmaus wrote:
>>> I think I'm currently in the
>>> - messages from channel@service/nick
>>> - IQs to/from and presence from channel@service/nick/client-id
>>> (where
On 02.06.2018 13:46, Kevin Smith wrote:
>> On 2 Jun 2018, at 11:44, Florian Schmaus wrote:
>> I think I'm currently in the
>> - messages from channel@service/nick
>> - IQs to/from and presence from channel@service/nick/client-id
>> (where client-id is a random unique string not containing '/')
On 2 Jun 2018, at 09:25, Steve Kille wrote:
>
> We've been talking about a number of variants to deal with the problem of
> encoding four pieces of information in a JID structure that only allows
> encoding of three.
>
> Here is an approach to avoid the problem.
>
> These JIDs are mostly
> On 2 Jun 2018, at 11:44, Florian Schmaus wrote:
>
> On 02.06.2018 10:25, Steve Kille wrote:
>> We've been talking about a number of variants to deal with the problem of
>> encoding four pieces of information in a JID structure that only allows
>> encoding of three.
>>
>> Here is an approach
On 2 Jun 2018, at 10:22, Steve Kille wrote:
>
>>> The only problem to address is when in a JID Hidden channel, the recipient
>>> wants to address a specific client (PM or vCard lookup). A solution here is
>>> to is to use the channel@domain/stable-participant-id addressing to the
>>> channel,
On 2 Jun 2018, at 09:25, Steve Kille wrote:
>
> We've been talking about a number of variants to deal with the problem of
> encoding four pieces of information in a JID structure that only allows
> encoding of three.
>
> Here is an approach to avoid the problem.
>
> These JIDs are mostly
On 02.06.2018 10:25, Steve Kille wrote:
> We've been talking about a number of variants to deal with the problem of
> encoding four pieces of information in a JID structure that only allows
> encoding of three.
>
> Here is an approach to avoid the problem.
>
> These JIDs are mostly (exceptions
The only problem to address is when in a JID Hidden channel, the recipient
wants to address a specific client (PM or vCard lookup). A solution here is
to is to use the channel@domain/stable-participant-id addressing to the
channel, and include the anoymized resource as an extension
On 2 June 2018 at 09:25, Steve Kille wrote:
> We've been talking about a number of variants to deal with the problem of
> encoding four pieces of information in a JID structure that only allows
> encoding of three.
>
> Here is an approach to avoid the problem.
>
> These JIDs are mostly
We've been talking about a number of variants to deal with the problem of
encoding four pieces of information in a JID structure that only allows
encoding of three.
Here is an approach to avoid the problem.
These JIDs are mostly (exceptions discussed below) used in the "from" of
stanzas coming
11 matches
Mail list logo
