-
Notifications
You must be signed in to change notification settings - Fork 60
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
Question: How to verify matrix-commander: other client is waiting for "accept request" #93
Comments
It might be due to a missing |
I have re-tested that about 1 month ago multiple times with Element Android and Element Webapp in Firefox.
You can and you must start the emoji verification on the Element client (e.g. Element Webapp in Firefox). Find the emoji verification initiation in Element. There is another old issue here about the same subject. Search for "emoji" or "verification" in the issues and read those too, they might be helpful. But the key issue is that you must find and learn how to initiation the emoji verification in Element. |
This may or may not be relevent to the OP, but for me the issue was (I think) my slow internet connection. after waiting ~10 minutes (approx, since I was not activly watching terminal or the browser, but I know it took longer then five minutes) the emoji's popped up in the terminal and in the browser. After which point everything seems to work fine. I don't know if this is an issue with matrix-commander, my server instance, or with my slow internet, but I will say that verifying via element desktop or verifying in a new firefox profile does not take more then 5 minutes. so idk. |
My personal experience: I have done dozens of verification, maybe close to 100. It never took more than 1 min, in most cases I would say it had taken 1-5 seconds. Just my experience, your mileage may vary. I am very doubtful that the time it takes has to do with the matrix-commander app. Thanks @ahcheing for sharing your experience. |
As a tiny tiny side note, it works slightly "better" if you accept the verification first on Element, then then secondly on matrix-commander. But this is not crucial, it works either way, but event order is different and logging is "nicer" that way. |
I'm new to matrix and matrix-commander.
I have installed by pip matrix-commander 7.6.0 2023-10-16 only result in:
this warnig repeat forever. I use firefox 119 on fedora 38 and Web Element to verify. Notification is enabled. (all other app notification are poped up) There is a problem or am I doing some thing wrong? best regards, |
I am closing this issue, Pleas continue any "verify" or "verification" related issue in Issue #182. |
OS: Linux
Matrix Commander Version: 3.5.0
Server: dendrite 0.9.8
Other Clients: Element 1.11.3 and nheko 0.10.0
Problem:
After matrix-commander is logged in successfully I can not complete the verification process.
Verification is started by matrix-commander and on either Element or nheko when I press verify
matrix-commander does not react. The process also seems to slightly deviate from the description in help
since I can not start emoji verification directly from the client.
Element and nheko can verify each other just fine.
Also I can not send any messages with matrix-commander but I guess this is because it's not verified.(I can send messages after I joined a room)
Debug output (ids, user and domain redacted):
After this I don't get any further reply except when the client declines because of "timeout" or client user interaction
The text was updated successfully, but these errors were encountered: