Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OMEMO implementation state/tracking #5

Open
COM8 opened this Issue Nov 2, 2017 · 8 comments

Comments

3 participants
@COM8
Copy link
Collaborator

COM8 commented Nov 2, 2017

This issue tracks the state of the OMEMO implementation.

  • Prerequisites
  • Key announcement
    • Single chat
    • MUC
  • Building a session
    • Single chat
    • MUC
  • Encrypt messages
    • Single chat
    • MUC
  • Decrypt messages
    • Single chat
    • MUC
  • UI stuff (requires #50)
    • Display own fingerprint as text
    • Display own fingerprint as QR-Code
    • Display own devices
    • Display contact devices
    • Display contact fingerprint as text
    • Display contact fingerprint as QR-Code
    • Un-/trust other devices

@COM8 COM8 self-assigned this Nov 2, 2017

@COM8 COM8 added the WIP label Nov 2, 2017

@COM8 COM8 closed this Nov 2, 2017

@COM8 COM8 reopened this Nov 2, 2017

@COM8 COM8 added this to In Progress in XMPP Client Nov 2, 2017

@COM8 COM8 moved this from In Progress to To do in XMPP Client Jan 2, 2018

@COM8 COM8 added the feature label Mar 9, 2018

@COM8 COM8 moved this from To do to In Progress in XMPP Client Apr 2, 2018

@COM8 COM8 changed the title OMEMO implementation state OMEMO implementation state/tracking Aug 15, 2018

@COM8 COM8 added this to the Beta milestone Aug 17, 2018

@Echolon

This comment has been minimized.

Copy link

Echolon commented Nov 25, 2018

As I suggested to other clients already, encryption should be treated simple for users.

Meaning:

  • Show a lock symbol in the chat window

  • Be clear about choices: Offer choices as 'Unencrypted' (dont use the plaintext terminology) or 'Encrypted (OMEMO)' (don't use the encryption name only)

Users can neither differ nor decide on whats right. They only know the states on and off. Everything else (like OTR or OpenPGP) is advanced and only for very advanced users in comparision to most common windows users.

So just a suggestion to do things right from the beginning

@COM8

This comment has been minimized.

Copy link
Collaborator Author

COM8 commented Nov 26, 2018

Yes, good point!
Have to remember myself to keep it simple :D

@COM8

This comment has been minimized.

Copy link
Collaborator Author

COM8 commented Nov 26, 2018

That's the current state. Is this simple enough, what do you think?

img

@Echolon

This comment has been minimized.

Copy link

Echolon commented Nov 26, 2018

Hey - cool - I like it! Yes, now the user directly understands what it about. You should add the selection 'Unencrypted', too. Maybe a toggle thing is nice too.

And of course the lock symbol, but I guess it's work in progress.

(by Lock symbol I mean, you should offer those choices from this symbol, like in Dino or Conversations for example. But - sure - support choices with symbols, too!)

🙌

@COM8 COM8 referenced this issue Dec 13, 2018

Open

UI Overhaul #50

53 of 91 tasks complete

@COM8 COM8 pinned this issue Dec 27, 2018

@Supded

This comment has been minimized.

Copy link

Supded commented Jan 31, 2019

Fix fingerprint representation, it must be conversation capable.

@Supded

This comment has been minimized.

Copy link

Supded commented Jan 31, 2019

31 01 2019_13 05 43 7972 2
31 01 2019_13 07 59 0300

@COM8

This comment has been minimized.

Copy link
Collaborator Author

COM8 commented Jan 31, 2019

Yes. I know what's going wrong and a fix will be published with the UI overhaul.

COM8 added a commit that referenced this issue Feb 10, 2019

COM8 added a commit that referenced this issue Feb 12, 2019

COM8 added a commit that referenced this issue Mar 5, 2019

@COM8

This comment has been minimized.

Copy link
Collaborator Author

COM8 commented Mar 5, 2019

31 01 2019_13 05 43 7972 2
31 01 2019_13 07 59 0300

40d7a8b fixes it. Finally!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.