You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, delete from the HS is indeed the first step we take:
Delete from HS
Trigger email verification
User hopefully verifies email link and presses continue
Adjust discovery status
So, we could delay the delete step to avoid this... but rather than doing that, it would be a lot better to use the "re-add with different bind setting" flow from MSC2229.
At the moment though, MSC2229 work is deferred to phase 2.
If this issue is phase 1, should we try only re-ordering the delete (which will add complexity to Riot) or pull MSC2229 into phase 1?
Ah well, @anoadragon453 went ahead and implementedMSC2229 in Synapse just now... so I guess it's "basically free" to pull into phase 1 now, as clients can choose to use it.
Tested using:
riot.im/develop
the test homeserver andrew spun up
vector.im as the IS
The text was updated successfully, but these errors were encountered: