[DRAFT] feat: implement encrypted group conversation #509
Conversation
This file contains 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
ice-damocles
force-pushed
the
feature/origin/implement-encrypted-group-conversation
branch
from
64b5d95 to
1f2d2a1
Compare
ice-damocles
force-pushed
the
feature/origin/implement-encrypted-group-conversation
branch
from
1f2d2a1 to
ad54be5
Compare
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
To implement on-one-one EE2E chat @ice-kreios needs to send message with empty content to both participants (user himself and another participant), for some reason not all users pubkeys work properly, for example orion20 pubkey works fine, other users sometimes return
Unhandled Exception: public key is not on this curveWould be also nice to add expiration tag to the 1059 event service (wrap message) and define its duration in production
Type of Change