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

Desktop app should not tell user to use desktop app to search encrypted messages #17051

Closed
aaronraimist opened this issue Apr 23, 2021 · 7 comments · Fixed by matrix-org/matrix-react-sdk#6230
Assignees
Labels
A-Electron A-Indexing Indexing messages via Seshat A-Timeline-Search P1 S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@aaronraimist
Copy link
Collaborator

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.

@aaronraimist aaronraimist added the A-Indexing Indexing messages via Seshat label Apr 23, 2021
@jryans jryans added T-Defect P1 S-Minor Impairs non-critical functionality or suitable workarounds exist and removed P2 labels Apr 29, 2021
@delijati
Copy link

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:

Since this package is just the Electron wrapper for Element Web, it doesn't contain any of the Element Web code,

@t3chguy
Copy link
Member

t3chguy commented May 19, 2021

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

@delijati
Copy link

Yup found this #16483 (comment)

@hex-m
Copy link

hex-m commented Jun 16, 2021

For others who end up here: You can fix this in Security & Privacy -> Message search -> Reset

This issue is not about preventing message search from breaking.

But which one is? All linked issues are closed.

@aaronraimist
Copy link
Collaborator Author

@hex-m you can create one

@hex-m
Copy link

hex-m commented Jun 16, 2021

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.

@laurahetz
Copy link

I had the following error under

For others who end up here: You can fix this in Security & Privacy -> Message search -> Reset

This issue is not about preventing message search from breaking.

But which one is? All linked issues are closed.

This fixed the search issue for me.
The settings showed the following error, maybe this helps to reproduce/fix the issue in general

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Electron A-Indexing Indexing messages via Seshat A-Timeline-Search P1 S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

Successfully merging a pull request may close this issue.

8 participants