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

[Story] Adjust message history disclaimer on EX key reset #2542

Open
2 of 3 tasks
mxandreas opened this issue Sep 27, 2024 · 7 comments
Open
2 of 3 tasks

[Story] Adjust message history disclaimer on EX key reset #2542

mxandreas opened this issue Sep 27, 2024 · 7 comments

Comments

@mxandreas
Copy link

mxandreas commented Sep 27, 2024

Description

We have gotten feedback that while users are migrating to EX, but haven't got any existing & verified devices and also have forgotten their recovery key, are hesitating to do the identity reset because we have the following statement in there:

You will lose your existing message history.

Screenshot 2024-09-27 at 13 53 58

This statement was intentional and is still valid - because: while we're not going to explicitly delete their history on their other existing devices, we also have no knowledge on what is exactly on those devices and the average user has also no idea what has a specific client downloaded / cached in the device or not. Thus, overall we have to account for the worst case scenario and be straightforward in our statements.

However, after a cautious debate how to prevent users from also making the conclusions in the other direction (like we were to delete what's already on their existing devices), it was agreed to adjust the wording of the statement as follows:

You will lose your existing message history unless it is stored on another device.

The updated designs are here: iOS and Android.

Since this is a subtle difference, and directed towards existing power-users, I propose not to change any translations but only the English text.

My understanding is that EW is out of scope here, but correct me if I am wrong.

Android

  1. T-Task
    bmarty

iOS

  1. T-Task

Rust

No tasks being tracked yet.

MAS

Sign-off

Android

  • Design sign-off on completion
  • QA sign-off on completion
  • Product sign-off on completion

iOS

  • Design sign-off on completion
  • QA sign-off on completion
  • Product sign-off on completion
@americanrefugee
Copy link

@mxandreas Updates made to iOS and Android

@americanrefugee
Copy link

Are any changes needed for the Settings version of "reset identity"?

@mxandreas
Copy link
Author

Are any changes needed for the Settings version of "reset identity"?

I think not because we are fine-tuning for the experience of migrating to EX, specifically. Just in case @pmaier1 .

@pmaier1
Copy link
Contributor

pmaier1 commented Oct 1, 2024

Are any changes needed for the Settings version of "reset identity"?

No. This part anyway needs more thinking. It will likely not use the same primitives as the identity reset during sign-in and has a different use case ("I think I have been compromised and want to change my secrets therefore").

Regarding the suggested wording, I'm fine with it.

@mxandreas
Copy link
Author

@pmaier1 Are you creating a subtask/ticket to do the update in MAS?

@pmaier1
Copy link
Contributor

pmaier1 commented Oct 1, 2024

@bmarty
Copy link
Member

bmarty commented Oct 1, 2024

String updated on Localazy: https://localazy.com/p/element/source-language/_a7281790744829274158#versions
Technically there is nothing else to do, the string will be synced during the next Localazy sync (which occurs in Monday mornings).

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

4 participants