-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Setting up E2EE on a new login doesn't block initial sync #12953
Comments
I think this basically breaks self-verification, because the self-verif to-device msgs get blocked behind the explosion of initialsync traffic |
Hmm, I have definitely seen self-verif work fine, so perhaps it only "breaks" for large accounts then...? I am a bit worried we might rely on some client APIs that expect an operational sync to be running, so I am wary of changing this just before release... |
In #12981 (comment), we took a decision that we should gate on initial sync before complete security, so this may be resolved soonish. |
this is now resolved, i think? |
* Update browserslist * Increment version in user-agent string --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: R Midhun Suresh <[email protected]>
Resulting in the initial sync exploding in attempts to decrypt undecryptable messages, rather than just waiting until E2EE has been set up.
The text was updated successfully, but these errors were encountered: