pep/blog.bouah.net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Remove commas before parentheses

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-02-24 20:56:57 +00:00
parent 1b6dee1e36
commit 2db452c30f
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/posts/slixmpp-omemo-release.md
View file

@ -53,7 +53,7 @@ port of the original library implemented in Signal.
The only bits that prevent him for releasing his library under MIT is the
wireformat, that has to be the same as the original implementation as
specified in [XEP-0384][OMEMO]. Providing that we define another wireformat
for all OMEMO implementations to use, this restriction will go away, (still
for all OMEMO implementations to use, this restriction will go away (still
easier said than done.)
[python-axolotl]: https://pypi.org/project/python-axolotl/
@ -64,9 +64,9 @@ easier said than done.)
There is still lots of things to be improved in OMEMO, the specification.
I would personally like to see what is usually called _Full Stanza
Encryption_, (it's really only partial). Today, an OMEMO implementation will
Encryption_ (it's really only partial). Today, an OMEMO implementation will
only encrypt the plaintext part of messages you send, and either leak
everything else, (e.g., chatstates, receipts, corrections, xhtml-im), or
everything else (e.g., chatstates, receipts, corrections, xhtml-im), or
effectively disable them, for privacy-conscious implementations.
I would also like to drop _Forward Secrecy_, in the context of Instant