Hi,
While I was rereading XEP-0407 I discovered that it specifies custom
element within urn:xmpp:mix:misc:0 namespace. I'm now wondering why it uses
this custom solution instead of using element with namespace
urn:xmpp:message-retract:0 as specified in XEP-0424.
I suppose that XEP-0407 was c
> I have another question, maybe you know how to implement it. When I send a
> change for the allowed node, what's the notification the other members
> subscribed to that node receive: the complete list for allowed items or only
> the elements I sent to be published/retracted?
If I recall corr
Hi,
> I'm doing an implementation of the MIX (XEP-0369) and now, I was implementing
> some administrative tasks, like config and info modification, but I was
> questioning about some parts, because, i.e. Example 7 in XEP-0406 (MIX-ADMIN)
> is saying:
>
>
>
>
>
> I mean, it's
> Wiadomość napisana przez JC Brand w dniu 30.12.2020, o
> godz. 17:28:
>
>> In the proposed protoXEP element contains real bare JID of the
>> user affiliated with the room, which is available, if I'm correct, only in
>> non-anonymous rooms. In semi-anonymous it may not be available. Due to
Hi all,
> To enable this feature, I've opted for a configuration setting in the MUC.
>
> Apparently Tigase already has a similar feature to this protoXEP and relies
> on letting the user opt-in when registering a nickname with the MUC.
>
> Maybe someone from Tigase can comment on the particular
> I've started the implementation of XEP-0427 with a goal to use the collation
> of fastenings (and pseudo-fastenings) to reduce traffic related to MAM
> history synchronization.
>
>
> You're ahead of me; though the Mobile Lead at Pando is begging me to do the
> same.
>
> I should warn that
Hi everyone,
I'm sorry but this will be a long email.
I've started the implementation of XEP-0427 with a goal to use the collation of
fastenings (and pseudo-fastenings) to reduce traffic related to MAM history
synchronization.
I was thinking about using `collate` summarizing to retrieve delive
Hi,
> Wiadomość napisana przez Daniel Gultsch w dniu
> 08.04.2020, o godz. 12:15:
>
> Add a disco feature:
> Assuming that I have presence subscription with the person I want to
> call and I can see that they support Jingle I still might want to use
> JMI to have all of their devices ring. Howe
>> At the Summit, I've suggested to send all required data within Push
>> notification,
>> but for security reasons, encrypted by XMPP server initiating push
>> notification.
>> Here is a document which describes encryption process done by us at Tigase
>> https://tigase.github.io/tigase-xeps/doc
> Wiadomość napisana przez Florian Schmaus w dniu
> 07.04.2020, o godz. 09:45:
>
> On 4/7/20 8:17 AM, Daniel Gultsch wrote:
>> Am Di., 31. März 2020 um 20:42 Uhr schrieb Jonas Schäfer
>> :
>>> This message constitutes notice of a Last Call for comments on
>>> XEP-0357.
>>>
>>> Title: Push No
Hi,
> Wiadomość napisana przez Paul Schaub w dniu
> 28.02.2020, o godz. 14:01:
>
> Hi List!
>
> XEP-0369 (MIX-Core) section 7.1.2 about joining a channel states that
> when the users server sends a join request to the mix channel, the
> channel responds with an IQ of type result. Further it st
11 matches
Mail list logo