<div dir="ltr"><div>Got it working now.</div><div><br></div><div>But interesting, conversations only displays the '... has read up to this point' label when I use the 'Sending a Message to All Occupants' approach. In my opinion, the 'Private Message' approach within a MUC should be sufficient here.</div><div><br></div><div>Does someone knows the reason for this?</div><div><br></div><div>Best regards</div><div>Schorsch</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Sa., 14. Sept. 2019 um 08:15 Uhr schrieb Georg <<a href="mailto:scooterschorschi@gmail.com">scooterschorschi@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi<br> <br> I also implemented xep184. It works fine, but only for delivery receipts. It does not work for the 'displayed' status.<br> <br> 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 answering of chat-markers for the displayed status within MUC's.<br> <br> Best regards <br> Schorsch <br> <br> <br> <br> <br> Am Freitag, 13. September 2019 schrieb Dave Cridland:<br> > On Fri, 13 Sep 2019 at 22:08, george b <<a href="mailto:scooterschorschi@gmail.com" target="_blank">scooterschorschi@gmail.com</a>> wrote:<br> > <br> > > Thanks for the quick response :-).<br> > > I read the xep and it sounds like what I was looking for. I tried it but<br> > > it doesn't work within the first test. I have to investigate more what's<br> > > going on there.<br> > ><br> > ><br> > A lot of clients use XEP-0184 instead, and many ignore both entirely from<br> > XEP-0045 chatrooms.<br> > <br> > <br> > > Best regards<br> > > Schorsch<br> > ><br> > > Am Fr., 13. Sept. 2019 um 21:02 Uhr schrieb Dave Cridland <<br> > > <a href="mailto:dave@cridland.net" target="_blank">dave@cridland.net</a>>:<br> > ><br> > >><br> > >><br> > >> On Fri, 13 Sep 2019 at 19:27, george b <<a href="mailto:scooterschorschi@gmail.com" target="_blank">scooterschorschi@gmail.com</a>><br> > >> wrote:<br> > >><br> > >>> Hi<br> > >>><br> > >>> I am struggling with chat markers in MUC's.<br> > >>><br> > >>> In 1on1 chat, this works like expected:<br> > >>><br> > >>> <message from="<a href="http://aa@jabber-germany.de/shmoose" rel="noreferrer" target="_blank">aa@jabber-germany.de/shmoose</a>" id="<br> > >>> ce3f1534-ef71-4d6f-b699-661342ab4803" to="<a href="mailto:bb@jabber.de" target="_blank">bb@jabber.de</a>" type="chat"><br> > >>><br> > >>> <body>body</body><br> > >>><br> > >>> <markable xmlns="urn:xmpp:chat-markers:0"></markable><br> > >>><br> > >>> </message><br> > >>><br> > >>> <message id="33abcee5-7784-47eb-8841-14ba3e725d30" to="aa@<br> > >>> <a href="http://jabber-germany.de" rel="noreferrer" target="_blank">jabber-germany.de</a>" from="<a href="http://bb@jabber.de/shmoose" rel="noreferrer" target="_blank">bb@jabber.de/shmoose</a>"><br> > >>><br> > >>> <displayed xmlns="urn:xmpp:chat-markers:0" id="<br> > >>> ce3f1534-ef71-4d6f-b699-661342ab4803"></displayed><br> > >>><br> > >>> </message><br> > >>><br> > >>><br> > >>> But what is the 'to' address to answer the <markable> tag on MUC's? The<br> > >>> endclient didn't know the real jabber ID of the requesting room member. I<br> > >>> tried sending the <displayed> tag to the room. Does not work. I tried to<br> > >>> send the <displayed> tag to the room with the members name as a resource.<br> > >>> Does not work.<br> > >>><br> > >>><br> > >>> Does someone has a hint for me here? The description in the xep 0333<br> > >>> does not help here (at least for me).<br> > >>><br> > >>><br> > >>><br> > >> There are two options:<br> > >><br> > >> * Send the marker to the entire room (XEP-0045§7.4). This means that<br> > >> everyone sees when everyone reads the messages, which is a lot of<br> > >> information - and a lot of traffic.<br> > >> * Send the marker as a PM (XEP-0045§7.5). This means only the sender sees<br> > >> who has read their own messages - it's still a surprising amount of traffic<br> > >> though!<br> > >><br> > >> Dave.<br> > >> _______________________________________________<br> > >> JDev mailing list<br> > >> Info: <a href="https://mail.jabber.org/mailman/listinfo/jdev" rel="noreferrer" target="_blank">https://mail.jabber.org/mailman/listinfo/jdev</a><br> > >> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank">JDev-unsubscribe@jabber.org</a><br> > >> _______________________________________________<br> > >><br> > > _______________________________________________<br> > > JDev mailing list<br> > > Info: <a href="https://mail.jabber.org/mailman/listinfo/jdev" rel="noreferrer" target="_blank">https://mail.jabber.org/mailman/listinfo/jdev</a><br> > > Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank">JDev-unsubscribe@jabber.org</a><br> > > _______________________________________________<br> > ><br> ></blockquote></div>