Hi
I also implemented xep184. It works fine, but only for delivery receipts. It
does not work for the 'displayed' status.
I mostley test against conversations client. Shmoose is currently able to
request the chat-markers and process the answers, also from MUC's. The last
remaining piece is the
On Fri, 13 Sep 2019 at 22:08, george b wrote:
> Thanks for the quick response :-).
> I read the xep and it sounds like what I was looking for. I tried it but
> it doesn't work within the first test. I have to investigate more what's
> going on there.
>
>
A lot of clients use XEP-0184 instead, and
Thanks for the quick response :-).
I read the xep and it sounds like what I was looking for. I tried it but it
doesn't work within the first test. I have to investigate more what's going
on there.
Best regards
Schorsch
Am Fr., 13. Sept. 2019 um 21:02 Uhr schrieb Dave Cridland :
>
>
> On Fri, 13
On Fri, 13 Sep 2019 at 19:27, george b wrote:
> Hi
>
> I am struggling with chat markers in MUC's.
>
> In 1on1 chat, this works like expected:
>
>
>
> body
>
>
>
>
>
>
>
>
>
>
>
>
> But what is the 'to' address to answer the tag on MUC's? The
> endclient didn't know the real jabber ID of t
Hi
I am struggling with chat markers in MUC's.
In 1on1 chat, this works like expected:
body
But what is the 'to' address to answer the tag on MUC's? The
endclient didn't know the real jabber ID of the requesting room member. I
tried sending the tag to the room. Does not work. I t
Hi
I am a new list member. So let me just quick introduce myself. I am the
main developer of shmoose [1], a xmpp client for Sailfish OS.
Sometimes I have some questions (and maybe answers) about descriptions in
xep's. Hope to get good discussions here.
Best regards
Schorsch
[1] https://github.c
