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

Getting verified by other clients (Element, nheko,...) #278

Closed
cquike opened this issue Jan 20, 2022 · 3 comments
Closed

Getting verified by other clients (Element, nheko,...) #278

cquike opened this issue Jan 20, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@cquike
Copy link

cquike commented Jan 20, 2022

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.

@cquike cquike added the enhancement New feature or request label Jan 20, 2022
@MRAAGH
Copy link
Contributor

MRAAGH commented Jan 20, 2022

Use the legacy text verification feature in other clients. For example, in Element:
Screenshot_20220120-130907_Qc2N8
Screenshot_20220120-131207_j6tsK
Screenshot_20220120-131320_ghnV5
Screenshot_20220120-131333_2bhTw
Screenshot_20220120-131343_8hQzD

@cquike
Copy link
Author

cquike commented Jan 21, 2022

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!

@MRAAGH
Copy link
Contributor

MRAAGH commented Jan 22, 2022

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

PS: please close this issue if it is resolved ^^

@cquike cquike closed this as completed Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants