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

Better support for convos w/ multiple sessions #45

Open
arlolra opened this issue May 1, 2015 · 2 comments
Open

Better support for convos w/ multiple sessions #45

arlolra opened this issue May 1, 2015 · 2 comments

Comments

@arlolra
Copy link
Owner

arlolra commented May 1, 2015

"refreshed the private conversation" is a strange wording

cc/ @azadi @fqueze

@azadi
Copy link
Collaborator

azadi commented May 4, 2015

(Another related string is the Refresh private conversation label in the padlock options.)

I see in the OTR documentation the word "refresh" is used. Can we change it to perhaps "restart"? I am not sure but "restart" seems more easy to decipher than "refresh" for some reason.

And perhaps, we can remove this string altogether:

Attempting to refresh the private conversation with

And instead just say this directly:

The OTR conversation with X has been restarted.

And if it fails, complain accordingly, but don't say "attempting" first?

@arlolra arlolra added the ux label May 5, 2015
@arlolra
Copy link
Owner Author

arlolra commented May 5, 2015

So, the point of this refreshing thing is that some transport protocols allow you to login to the same account from multiple devices simultaneously. Refreshing lets you establish OTR sessions with each device individually (a necessity since they don't share short term ratcheting keys). It then uses instance tags to indicate the intended recipient and lets the other clients drop those messages.

The docs depict a UI element we're missing; selecting to which session to send.

In that light, "restart" doesn't seem like the right term. But "refresh" is also unclear. Hmm.

@arlolra arlolra changed the title "refreshed the private conversation" is a strange wording Better support for convos w/ multiple sessions May 7, 2015
@arlolra arlolra added enhancement and removed ux labels May 7, 2015
arlolra added a commit that referenced this issue Jun 23, 2015
 * Until #45 is resolved, avoid the potential for the UI to display
   the wrong trust state for the active session.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants