Re: [Standards] Disappearing timers for OMEMO proposal

I might be mistaken, but isn't there a message processing hint, that indicates that the message should not be stored in MAM? Or was it the other way round? -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Standards

Re: [Standards] Disappearing timers for OMEMO proposal

Am 10. Mai 2018 14:24:47 MESZ schrieb "Remko Tronçon" : >I don't see why a XEP for data retention hints needs to be tied to >other XEPs like >OMEMO, though. I'd also rather not tie it to OMEMO. The same principle of disappearing messages could also be applied with other

Re: [Standards] XEP-0394: too weak to replace XEP-0071

I would claim that a huge part of XMPP nowadays happens on mobile devices and I haven't seen a single rich text editor in any mobile application. Thats why I think that markdown is the way to go. Sending greeting cards in html sounds like an idea from the 90s to me (not saying that it isn't a

Re: [Standards] XEP-0393 and XEP-0394 naming

Also if we'd do that, we'd have "Message Markup" and "Message Markdown"... Am 8. März 2018 17:23:32 MEZ schrieb Sam Whited : >On Thu, Mar 8, 2018, at 10:18, Kozlov Konstantin wrote: >> For example we may rename XEP-0393 to "Markdown" 'cause its syntax >somewhat >> similar to

Re: [Standards] Proposal: Server selection for user-registration

Am 8. Januar 2018 23:57:20 MEZ schrieb Stefan >I see a problem with "choose server" right now, because: >- Not every client developer wants to setup and maintain a good xmpp >server by himself (ChatSecure for example). >- Not every XMPP server is a good choice for the user. So if someone

Re: [Standards] JET-OMEMO Encrypted Jingle Transports

Am 7. Oktober 2017 10:52:25 MESZ schrieb Jonas Wielicki : >I would go with the simplest solution. IANAC (I Am Not A >Cryptographer), but >AES-128-GCM-NoPadding sounds fine to me. There’s no need to add >complexity >where none is needed. So limiting ciphers to

Re: [Standards] Proposed XMPP Extension: Jingle Encrypted Transports

This means, that this XEP will specify the reusable stuff, while additional addon xeps will be created for different encryption methods. Greetings vv Am 20. September 2017 17:18:07 MESZ schrieb Sam Whited : >On Tue, Sep 12, 2017, at 07:21, Paul Schaub wrote: >> I just

Re: [Standards] OMEMO Key Agreement

implementation. Thats also the reason why OMEMO was (prematurely) specified based on Olm instead of libsignal. Would you rather suggest to put the efforts into a permissive XEdDSA implementation or what would be your advice? Greetings Vanitasvitae -- Diese Nachricht wurde von meinem Android

Re: [Standards] OMEMO and Olm

Regarding file transfer: I'll probably tackle that as part of my Google Summer of Code project, so we might get in contact later :) Vanitasvitae Am 18. Mai 2017 12:57:29 MESZ schrieb Andrey Gursky <andrey.gur...@e-mail.ua>: >Hi, > >On Wed, 17 May 2017 16:59:53 +0100 Dave

Re: [Standards] XEP-0384 (OMEMO Encryption) Questions/Remarks

>> The signed preKeys are used for authentication. >> > >I understand this is the idea, but where is this described in the >Olm/OMEMO >protocol? AFAICT, this is an X3DH thing, which Olm doesn't use. This is not stated in the current Version of the XEP. I guess it would be good to put this into

Re: [Standards] Proposed changes to OMEMO's use of PEP

OMEMO works perfectly fine without changes on the server side (apart from implementing PEP/PubSub of course), so I really don't get the reason of the discussion :/ Am 25. März 2017 18:43:59 MEZ schrieb Evgeny Khramtsov : >Sat, 25 Mar 2017 18:35:47 +0100 >Jonas Wielicki

Re: [Standards] Proposed changes to OMEMO's use of PEP

If you don't like the intention, then PGP is probably the way to go for you. MAM is used to sync messages in OMEMO. Its unorthodox, but still totally valid. Am 25. März 2017 12:49:21 MEZ schrieb Evgeny Khramtsov <xramt...@gmail.com>: >Sat, 25 Mar 2017 11:48:56 +0100 >VanitasVita

Re: [Standards] Proposed changes to OMEMO's use of PEP

You cannot search Messages server side, that's true. But that's intended and I guess there is no way to achieve this while preserving forward and future secrecy. If you want to search through your messages, the only way is to do it in your local archive. An interesting feature would be to

Re: [Standards] XEP-0384 (OMEMO Encryption) Questions/Remarks

the receiving device can simply try to decrypt with every matching keyId In the message. Also the signal protocol works just the same with mucs as it does with single user chats. You simply forward all the ratchets of all recipients. Kind regards Vanitasvitae Am 13. März 2017 09:32:29 MEZ schrieb "