#300 Client-side encrypted search (replaces server search) FIXED#311
Open
veloura-dev wants to merge 1 commit into
Open
Conversation
|
@veloura-dev Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Author
|
PLEASE REVIEW |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implements local E2EE message search over the decrypted message cache.
CLOSE #300
Since the server can no longer search ciphertext (#124), search now runs 100% client-side:
clicked-search.messages)useMessageHistory→useMessageSearchIndexMessageSearchUI component with ranking, snippet highlighting, and E2EE tradeoff disclosure/app/searchpage documenting the local-only scopesrc/lib/crypto/messageCrypto.ts– ready to swap in real X3DH/SignalMessages are indexed as they are decrypted on-device. Search is scoped to locally available / synced history only – this is clearly communicated in the UI.
Type of change
Checklist