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

Share keys for historical messages when inviting users to encrypted rooms #5763

Merged
merged 4 commits into from Mar 26, 2021

Conversation

uhoreg
Copy link
Member

@uhoreg uhoreg commented Mar 16, 2021

@uhoreg uhoreg marked this pull request as ready for review March 17, 2021 01:47
@uhoreg uhoreg requested a review from a team March 17, 2021 01:47
Copy link
Member

@dbkr dbkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

otherwise lgtm

src/components/views/dialogs/InviteDialog.tsx Outdated Show resolved Hide resolved
src/components/views/dialogs/InviteDialog.tsx Outdated Show resolved Hide resolved
@uhoreg uhoreg requested a review from a team March 19, 2021 20:58
@jryans jryans changed the title share keys for historical messages when inviting users to encrypted rooms Share keys for historical messages when inviting users to encrypted rooms Mar 23, 2021
@jryans
Copy link
Collaborator

jryans commented Mar 25, 2021

I'm looking over the JS SDK changes today, but just wanted to highlight here that the Design review could potentially be skipped if we need to move faster, since this is disabled behind a feature flag.

@niquewoodhouse
Copy link
Contributor

Hi @uhoreg

Some design feedback from me: It could be a bit alarming for non-technical users - the way its presented makes it feel like you should note this before inviting people (which might be by design), but the words themselves are potentially scary (decryption keys - what are they, what am I sharing with people) and could just stop some people from inviting anyone.

I've just got some suggested redesigns below. I don't have great context on what the problem you're solving is, and these are a bit rushed, so these might not feel right to you but I'm happy to discuss.

1

I think the text is just saying people will be able to read old messages - do we have to say decryption keys?

229

2

Same idea really - but without an info icon

231

And these ideas are if we have to say decryption keys - but I would personally say that could be alarming for people.

3

If we have to say decryption keys (I genuinely think its a scary thing to say, for people who don't know what it means, like me)

232

4

If we absolutely have to say decryption keys, softening it with a tooltip

233

5

Have a learn more link that just expands a bit of in-page content.

234
235

@uhoreg
Copy link
Member Author

uhoreg commented Mar 25, 2021

New design:

image

Copy link
Contributor

@niquewoodhouse niquewoodhouse left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, will test when shipped to suggest tweaks if required (eg does icon make sense in practice). Thnaks

@uhoreg uhoreg merged commit e23583d into matrix-org:develop Mar 26, 2021
jryans added a commit that referenced this pull request Apr 9, 2021
After discussion with Product, we're ready to enable this key sharing work from
#5763 (based on
matrix-org/matrix-spec-proposals#3061).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants