Re: XEP-0333 - Chat Markers for MUC's
george b <[email protected]> Tue, 17 Sep 2019 21:57:00 +0200
| Newsgroups | gmane.network.jabber.devel |
|---|---|
| Message-ID | <CAL30P+bsAp9R6a2AjfZbGSKZjC-d_bBhN47YyZ_u7=YFQTsc-w@mail.gmail.com> |
--===============0975739081== Content-Type: multipart/alternative; boundary="00000000000045a76b0592c520e3" --00000000000045a76b0592c520e3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Got it working now. 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. Does someone knows the reason for this? Best regards Schorsch Am Sa., 14. Sept. 2019 um 08:15 Uhr schrieb Georg < [email protected]>: > 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 la= st > remaining piece is the answering of chat-markers for the displayed status > within MUC's. > > Best regards > Schorsch > > > > > Am Freitag, 13. September 2019 schrieb Dave Cridland: > > On Fri, 13 Sep 2019 at 22:08, george b <[email protected]> > 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 many ignore both entirely fr= om > > XEP-0045 chatrooms. > > > > > > > Best regards > > > Schorsch > > > > > > Am Fr., 13. Sept. 2019 um 21:02 Uhr schrieb Dave Cridland < > > > [email protected]>: > > > > > >> > > >> > > >> On Fri, 13 Sep 2019 at 19:27, george b <[email protected]> > > >> wrote: > > >> > > >>> Hi > > >>> > > >>> I am struggling with chat markers in MUC's. > > >>> > > >>> In 1on1 chat, this works like expected: > > >>> > > >>> <message from=3D"[email protected]/shmoose" id=3D" > > >>> ce3f1534-ef71-4d6f-b699-661342ab4803" to=3D"[email protected]" type=3D"c= hat"> > > >>> > > >>> <body>body</body> > > >>> > > >>> <markable xmlns=3D"urn:xmpp:chat-markers:0"></markable> > > >>> > > >>> </message> > > >>> > > >>> <message id=3D"33abcee5-7784-47eb-8841-14ba3e725d30" to=3D"aa@ > > >>> jabber-germany.de" from=3D"[email protected]/shmoose"> > > >>> > > >>> <displayed xmlns=3D"urn:xmpp:chat-markers:0" id=3D" > > >>> ce3f1534-ef71-4d6f-b699-661342ab4803"></displayed> > > >>> > > >>> </message> > > >>> > > >>> > > >>> But what is the 'to' address to answer the <markable> tag on MUC's? > The > > >>> endclient didn't know the real jabber ID of the requesting room > member. I > > >>> tried sending the <displayed> tag to the room. Does not work. I > tried to > > >>> send the <displayed> tag to the room with the members name as a > resource. > > >>> Does not work. > > >>> > > >>> > > >>> Does someone has a hint for me here? The description in the xep 033= 3 > > >>> does not help here (at least for me). > > >>> > > >>> > > >>> > > >> There are two options: > > >> > > >> * Send the marker to the entire room (XEP-0045=C2=A77.4). This means= that > > >> everyone sees when everyone reads the messages, which is a lot of > > >> information - and a lot of traffic. > > >> * Send the marker as a PM (XEP-0045=C2=A77.5). This means only the s= ender > sees > > >> who has read their own messages - it's still a surprising amount of > traffic > > >> though! > > >> > > >> Dave. > > >> _______________________________________________ > > >> JDev mailing list > > >> Info: https://mail.jabber.org/mailman/listinfo/jdev > > >> Unsubscribe: [email protected] > > >> _______________________________________________ > > >> > > > _______________________________________________ > > > JDev mailing list > > > Info: https://mail.jabber.org/mailman/listinfo/jdev > > > Unsubscribe: [email protected] > > > _______________________________________________ > > > > > --00000000000045a76b0592c520e3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Got it working now.</div><div><br></div><div>But inte= resting, conversations only displays the '... has read up to this point= ' label when I use the 'Sending a Message to All Occupants' app= roach. In my opinion, the 'Private Message' approach within a MUC s= hould be sufficient here.</div><div><br></div><div>Does someone knows the r= eason for this?</div><div><br></div><div>Best regards</div><div>Schorsch</d= iv><div><br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla= ss=3D"gmail_attr">Am Sa., 14. Sept. 2019 um 08:15=C2=A0Uhr schrieb Georg &l= t;<a href=3D"mailto:[email protected]">[email protected]<= /a>>:<br></div><blockquote class=3D"gmail_quote" style=3D"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. I= t does not work for the 'displayed' status.<br> <br> I mostley test against conversations client. Shmoose is currently able to r= equest the chat-markers and process the answers, also from MUC's. The l= ast remaining piece is the answering of chat-markers for the displayed stat= us 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=3D"mailto:scootersc= [email protected]" target=3D"_blank">[email protected]</a>> wro= te:<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 f= rom<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=3D"mailto:[email protected]" target=3D"_blank">dave@cridl= and.net</a>>:<br> > ><br> > >><br> > >><br> > >> On Fri, 13 Sep 2019 at 19:27, george b <<a href=3D"mailto:= [email protected]" target=3D"_blank">[email protected]</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=3D"<a href=3D"http://aa@jabber-germ= any.de/shmoose" rel=3D"noreferrer" target=3D"_blank">[email protected]/s= hmoose</a>" id=3D"<br> > >>> ce3f1534-ef71-4d6f-b699-661342ab4803" to=3D"<a = href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>" type= =3D"chat"><br> > >>><br> > >>> <body>body</body><br> > >>><br> > >>> <markable xmlns=3D"urn:xmpp:chat-markers:0"&= gt;</markable><br> > >>><br> > >>> </message><br> > >>><br> > >>> <message id=3D"33abcee5-7784-47eb-8841-14ba3e725d= 30" to=3D"aa@<br> > >>> <a href=3D"http://jabber-germany.de" rel=3D"noreferrer" t= arget=3D"_blank">jabber-germany.de</a>" from=3D"<a href=3D"http:/= /[email protected]/shmoose" rel=3D"noreferrer" target=3D"_blank">[email protected]/sh= moose</a>"><br> > >>><br> > >>> <displayed xmlns=3D"urn:xmpp:chat-markers:0"= id=3D"<br> > >>> ce3f1534-ef71-4d6f-b699-661342ab4803"></displa= yed><br> > >>><br> > >>> </message><br> > >>><br> > >>><br> > >>> But what is the 'to' address to answer the <ma= rkable> tag on MUC's? The<br> > >>> endclient didn't know the real jabber ID of the reque= sting 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 membe= rs name as a resource.<br> > >>> Does not work.<br> > >>><br> > >>><br> > >>> Does someone has a hint for me here? The description in t= he 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=C2=A77.4). Thi= s means that<br> > >> everyone sees when everyone reads the messages, which is a lo= t of<br> > >> information - and a lot of traffic.<br> > >> * Send the marker as a PM (XEP-0045=C2=A77.5). This means onl= y 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=3D"https://mail.jabber.org/mailman/listinfo/jde= v" rel=3D"noreferrer" target=3D"_blank">https://mail.jabber.org/mailman/lis= tinfo/jdev</a><br> > >> Unsubscribe: <a href=3D"mailto:[email protected]" t= arget=3D"_blank">[email protected]</a><br> > >> _______________________________________________<br> > >><br> > > _______________________________________________<br> > > JDev mailing list<br> > > Info: <a href=3D"https://mail.jabber.org/mailman/listinfo/jdev" r= el=3D"noreferrer" target=3D"_blank">https://mail.jabber.org/mailman/listinf= o/jdev</a><br> > > Unsubscribe: <a href=3D"mailto:[email protected]" targe= t=3D"_blank">[email protected]</a><br> > > _______________________________________________<br> > ><br> ></blockquote></div> --00000000000045a76b0592c520e3-- --===============0975739081== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ JDev mailing list Info: https://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________ --===============0975739081==--