Re: [Standards] NEW: XEP-0380 (Explicit Message Encryption)

2016-10-27 Thread Michal Piotrowski
The URL doesn't work for me. I get error 404. Best regards Michal Piotrowski michal.piotrow...@erlang-solutions.com On 26 October 2016 at 22:42, XMPP Extensions Editor wrote: > Version 0.1 of XEP-0380 (Explicit Message Encryption) has been released. > > Abstract: This

Re: [Standards] PubSub Item Publisher

2016-10-27 Thread Stefan Strigler
Yes, the PR now is just a small fix to what's inherently wrong. I'd love to see a discussion about a possible config option. Or maybe I should just create another PR as a proposal too? So far it seemed like nobody is interested at all. On Wed, Oct 26, 2016 at 4:13 PM Sergey Dobrov

Re: [Standards] UPDATED: XEP-0288 (Bidirectional Server-to-Server Connections)

2016-10-27 Thread Michal Piotrowski
The URL is still pointing to version 1.0 from 2013. Is this somehow connected with the error 404 I noticed for the new XEP 380 earlier today? Actually it looks like all the yesterday's updates are not reflected on the xmpp.org pages. Best regards Michal Piotrowski

Re: [Standards] Proposed XMPP Extension: OMEMO Encryption

2016-10-27 Thread Chris Ballinger
The URIs will already be super long so I don't think saving a few bytes to omit the sid is that important as far as overhead. Our db model for devices is currently keyed to JID + deviceId, because we normally don't know identityKey until the bundle is fetched. We could also prepend the 32-bit sid

Re: [Standards] Proposed XMPP Extension: OMEMO Encryption

2016-10-27 Thread Chris Ballinger
Hey, I'd like to propose an OMEMO addition to XMPP URIs so you can pre-share the identityKey for each of your devices through another channel. Currently OTR fingerprints in URIs are formatted like this: http://xmpp.org/extensions/xep-0364.html#sect-idp672480 xmpp:fe...@allfools.lit

Re: [Standards] Proposed XMPP Extension: OMEMO Encryption

2016-10-27 Thread Daniel Gultsch
Hi Chris, is there a reason you are including the SID in the URL? If not I would just propose doing xmpp:fe...@allfools.lit?omemo=070c42a11644a78b2f6f56213be4686374222895eb67b781abc44b860c47656c,e3898c2083b830a5fcb5e49632a3442837f8e8a24bea2f39e37d632807c82871 instead. Or maybe ?omemo=key=key2

Re: [Standards] UPDATED: XEP-0288 (Bidirectional Server-to-Server Connections)

2016-10-27 Thread Sam Whited
On Thu, Oct 27, 2016 at 11:07 AM, Michal Piotrowski wrote: > The URL is still pointing to version 1.0 from 2013. Is this somehow > connected with the error 404 I noticed for the new XEP 380 earlier today? > Actually it looks like all the yesterday's updates

Re: [Standards] PubSub Item Publisher

2016-10-27 Thread Sergey Dobrov
I was interested in it like 3 years ago, you may find such a discussion here, I also said about the issue at NA summit that year, I was said that it'll be fixed but we did not discuss any particular solutions. I'd be OK if it was just enabled by default and would be mandatory, but I'm not

Re: [Standards] NEW: XEP-0380 (Explicit Message Encryption)

2016-10-27 Thread Sam Whited
On Thu, Oct 27, 2016 at 2:21 AM, Michal Piotrowski wrote: > The URL doesn't work for me. I get error 404. Fixed, sorry for the trouble. —Sam -- Sam Whited pub 4096R/54083AE104EA7AD3 ___ Standards mailing

Re: [Standards] NEW: XEP-0380 (Explicit Message Encryption)

2016-10-27 Thread Michal Piotrowski
Thanks! Best regards Michal Piotrowski michal.piotrow...@erlang-solutions.com On 27 October 2016 at 16:08, Sam Whited wrote: > On Thu, Oct 27, 2016 at 2:21 AM, Michal Piotrowski > wrote: > > The URL doesn't work for me. I get error