Re: Omemo: confused by devicelist via pep
george b <[email protected]> Tue, 26 Jan 2021 22:20:41 +0100
| Newsgroups | gmane.network.jabber.devel |
|---|---|
| Message-ID | <CAL30P+Yd7i8oHRi5wAUfavWdguadK1qD8fgTL-R-QaQ1Mye85g@mail.gmail.com> |
--===============0174238790== Content-Type: multipart/alternative; boundary="000000000000b1366c05b9d43a64" --000000000000b1366c05b9d43a64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you for the quick reply. Indeed, this sounds like the source of the problem. After reading through the xeps, the generation of the verification string is somewhat complicated. Will try to implement this the next days :-). Am Di., 26. Jan. 2021 um 21:22 Uhr schrieb Kevin Smith < [email protected]>: > Hi, > > On 26 Jan 2021, at 19:36, george b <[email protected]> wrote: > According to omemo xep [3] 5.2: "Devices MUST subscribe to urn: > xmpp:omemo:1:devices via PEP". But pep state [4] 1.2: "because they are > subscribed to your presence, they automatically receive your events". I > would expect, as long as the users are subscribed to the others presence, > they will automatically receive the devicelist nodes and updates? That do= es > not work for me. > > > I suspect you=E2=80=99re missing the magic presence subscription mechanis= m PEP > uses. You automatically subscribe to PEP nodes that you indicate in your > caps that you want to using +notify features. > > Searching 163 for +notify will probably help here. > > /K > _______________________________________________ > JDev mailing list > Info: https://mail.jabber.org/mailman/listinfo/jdev > Unsubscribe: [email protected] > _______________________________________________ > --000000000000b1366c05b9d43a64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Thank you for the quick reply. Indeed, this sounds li= ke the source of the problem.</div><div>After reading through the xeps, the= generation of the verification string is somewhat complicated. Will try to= implement this the next days :-).<br></div></div><br><div class=3D"gmail_q= uote"><div dir=3D"ltr" class=3D"gmail_attr">Am Di., 26. Jan. 2021 um 21:22= =C2=A0Uhr schrieb Kevin Smith <<a href=3D"mailto:[email protected]">= [email protected]</a>>:<br></div><blockquote class=3D"gmail_quote" s= tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad= ding-left:1ex"><div style=3D"overflow-wrap: break-word;">Hi,<br><div><br><b= lockquote type=3D"cite"><div>On 26 Jan 2021, at 19:36, george b <<a href= =3D"mailto:[email protected]" target=3D"_blank">scooterschorschi@g= mail.com</a>> wrote:</div><div><div dir=3D"ltr"><div>According to omemo = xep [3] 5.2: "Devices MUST subscribe to <code>urn:<a>xmpp:omemo:1:devi= ces</a></code> via PEP". But pep state [4] 1.2: "because they are= subscribed to your presence, they automatically receive your events".= I would expect, as long as the users are subscribed to the others presence= , they will automatically receive the devicelist nodes and updates? That do= es not work for me. <br></div></div></div></blockquote><br></div><div>I sus= pect you=E2=80=99re missing the magic presence subscription mechanism PEP u= ses. You automatically subscribe to PEP nodes that you indicate in your cap= s that you want to using +notify features.</div><div><br></div><div>Searchi= ng 163 for +notify will probably help here.</div><br><div>/K</div></div>___= ____________________________________________<br> JDev mailing list<br> Info: <a href=3D"https://mail.jabber.org/mailman/listinfo/jdev" rel=3D"nore= ferrer" target=3D"_blank">https://mail.jabber.org/mailman/listinfo/jdev</a>= <br> Unsubscribe: <a href=3D"mailto:[email protected]" target=3D"_blan= k">[email protected]</a><br> _______________________________________________<br> </blockquote></div> --000000000000b1366c05b9d43a64-- --===============0174238790== 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] _______________________________________________ --===============0174238790==--