Re: Omemo: confused by devicelist via pep

--===============1393501451==
Content-Type: multipart/alternative; boundary="0000000000006c2a8105b9e77f7d"

--0000000000006c2a8105b9e77f7d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Perfect. Thank you, that did the trick :-).

Had to call
client->getDiscoManager()->setCapsNode ...
first. Without that, the caps will not be added to the presence stanza.


Am Mi., 27. Jan. 2021 um 11:39 Uhr schrieb Kevin Smith <
[email protected]>:

> On 26 Jan 2021, at 21:20, george b <[email protected]> wrote:
> >
> > 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
> :-).
>
> If you mean the string for caps, you shouldn=E2=80=99t have to do that yo=
urself,
> your XMPP library should do that for you. E.g. in Swiften it=E2=80=99ll d=
o it for
> you in the CapsInfoGenerator if you set the features you want in the
> ClientDiscoManager.
>
> /K
> _______________________________________________
> JDev mailing list
> Info: https://mail.jabber.org/mailman/listinfo/jdev
> Unsubscribe: [email protected]
> _______________________________________________
>

--0000000000006c2a8105b9e77f7d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Perfect. Thank you, that did the trick :-).</div><div=
><br></div><div>Had to call</div><div>client-&gt;getDiscoManager()-&gt;setC=
apsNode ...</div><div>first. Without that, the caps will not be added to th=
e presence stanza.<br></div><div></div><div><br></div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Am Mi., 27. Jan. 202=
1 um 11:39=C2=A0Uhr schrieb Kevin Smith &lt;<a href=3D"mailto:kevin.smith@i=
sode.com">[email protected]</a>&gt;:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">On 26 Jan 2021, at 21:20, george b &lt;<a href=3D"=
mailto:[email protected]" target=3D"_blank">scooterschorschi@gmail=
.com</a>&gt; wrote:<br>
&gt; <br>
&gt; Thank you for the quick reply. Indeed, this sounds like the source of =
the problem.<br>
&gt; After reading through the xeps, the generation of the verification str=
ing is somewhat complicated. Will try to implement this the next days :-).<=
br>
<br>
If you mean the string for caps, you shouldn=E2=80=99t have to do that your=
self, your XMPP library should do that for you. E.g. in Swiften it=E2=80=99=
ll do it for you in the CapsInfoGenerator if you set the features you want =
in the ClientDiscoManager.<br>
<br>
/K<br>
_______________________________________________<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>

--0000000000006c2a8105b9e77f7d--

--===============1393501451==
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]
_______________________________________________

--===============1393501451==--