-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Desktop app should not tell user to use desktop app to search encrypted messages #17051
Desktop app should not tell user to use desktop app to search encrypted messages #17051
Comments
Maybe i'm overlook something, but why do I need the Desktop app at all to search in encrypted messages? The Desktop app is only a wrapper via Electron:
|
The Desktop app has an Element Web instance embedded, but it also includes Keytar and Seshat. Seshat is a secure message index, which is what powers encrypted message search. Browsers don't support anything like that and Seshat can't be used in a browser due to lack of encrypted-at-rest indexes/sqlite and threading |
Yup found this #16483 (comment) |
For others who end up here: You can fix this in
But which one is? All linked issues are closed. |
@hex-m you can create one |
I don't have the problem anymore (and don't know how to reproduce it) but if it comes back I'll create an issue with logs. |
I had the following error under
This fixed the search issue for me. |
Related: #16721 #16636 #14229 #16568
Not #15715
matrix-org/matrix-react-sdk#5806 which was part of the fix for #14229 didn't actually fix the whole issue. In Settings there is now a better error message telling you that something broke which is great but most people are not looking at Settings to see if something went wrong.
Most people are just trying to search for a message and they see the same confusing message that has always been there "Use the Desktop app to search encrypted messages". There is no hint that the problem isn't the app you are using but rather a problem with the message searching feature.
This issue is not about preventing message search from breaking. This issue is about giving a better error message when it does break.
The text was updated successfully, but these errors were encountered: