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
I have setup mirage with an account that i also have setup with other clients, more specifically elements on Android and nheko on Linux. The mirage device (also running on Linux) appears as not verified but when clicking on verify either from nheko or elements both clients just wait from a response of mirage, but this never reacts.
I know I can verify the mirage session, from another mirage session comparing manually the session key, but even when I do that and it shows as verified under the second mirage session still nheko and element shows as unverified.
The text was updated successfully, but these errors were encountered:
That worked!
By the way, why is it called legacy? Is it meant to be removed in the future from the matrix specification? And will mirage eventually support responding to the verification requests by other clients?
Thank you!
It is called legacy in Element to make it clear that emoji verification should be preferred (because it's easier and more reliable). I doubt it will get removed, as long as there are clients that don't support emoji verification. Because then there would be no way to verify those clients!
I am unsure whether Mirage emoji verification has been discussed here on github. Personally I think Mirage is a more "hardcore" type of client, and might never get emoji verification
I have setup mirage with an account that i also have setup with other clients, more specifically elements on Android and nheko on Linux. The mirage device (also running on Linux) appears as not verified but when clicking on verify either from nheko or elements both clients just wait from a response of mirage, but this never reacts.
I know I can verify the mirage session, from another mirage session comparing manually the session key, but even when I do that and it shows as verified under the second mirage session still nheko and element shows as unverified.
The text was updated successfully, but these errors were encountered: