[Standards] Proposed XMPP Extension: OMEMO Media sharing

Ivan Vučica ivan at vucica.net
Tue Jun 5 20:07:23 UTC 2018


Typo: data:image/jpep

What can a client do to discover whether the new URL schema is supported? I
exchanged some messages with a friend yesterday and I used Gajim to send
pictures. He was surprised to see the aesgcm URL in, I believe, Chatsecure.

Leaking the anchor was raised as a problem. This paragraph mentions a
"server operator". As http server operator can be distinct from the xmpp
server operator, I assume the former is the problem?

Should aemgcs URI schema be registered with IANA?

On Tue, Jun 5, 2018, 16:18 Jonas Wielicki <jonas at wielicki.name> wrote:

> The XMPP Extensions Editor has received a proposal for a new XEP.
>
> Title: OMEMO Media sharing
> Abstract:
> An informal way of sharing media files despite limitations in the
> OMEMO encryption
>
> URL: https://xmpp.org/extensions/inbox/omemo-media-sharing.html
>
> The Council will decide in the next two weeks whether to accept this
> proposal as an official XEP.
> _______________________________________________
> 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/20180605/7ddcc1d0/attachment.html>


More information about the Standards mailing list