[Standards] XEP-0163: Notify after directed presence

Dave Cridland dave at cridland.net
Wed Aug 28 09:04:56 UTC 2019


I can't remember who, but someone kept on pointing out this issue with PEP
for various cases.

Loosely, PEP only really works in the case where we have a mutual
subscription - so much so that some clients go out of their way to try an
enforce mutual subscriptions.

It would be nice to fix PEP so it works for one-way subscriptions and
ad-hoc contacts. I don't think key distribution should operate over PEP,
but that's somewhat irrelevant to this discussion.


On Sat, 24 Aug 2019 at 19:26, Maxime Buquet <pep at bouah.net> wrote:

> Hi standards,
> I found about this issue while working on the OMEMO implementation in
> poezio (that should be available soon(tm)), but I guess this can be
> applied to other things. The issue goes as follows:
> - Start encrypted chat with non-contact recipient.
>   At this point, my OMEMO code will fetch devicelist and bundles via
>   PEP.
> - Recipient then updates his OMEMO status (adds a device, removes a
>   devices from the devicelist)
> - ???
>   I am not aware of changes as I am not being notified through PEP
>   because of not being a contact. I continue encrypting same as I was
>   before the changes.
> One obvious answer is to add the recipient as contact, but this might
> not always fly.
> Asking quickly in jdev@ [0], I was suggested to use directed presences,
> and [even if it might not be specified yet?] it would make sense if I
> now received PEP notifications for items with an access_model of "open".
> Thoughts?
> Happy Hacking!
> [0]: https://logs.xmpp.org/jdev/2019-08-24#2019-08-24-bf845f259b5e8576
> --
> Maxime “pep” Buquet
> _______________________________________________
> Standards mailing list
> Info: https://mail.jabber.org/mailman/listinfo/standards
> Unsubscribe: Standards-unsubscribe at xmpp.org
> _______________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.jabber.org/pipermail/standards/attachments/20190828/0a95563d/attachment.html>

More information about the Standards mailing list