-
-
Notifications
You must be signed in to change notification settings - Fork 107
feat: Synchronize encrypted groups creation across devices (#7001) #7009
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
base: link2xt/ykltkokxntvk
Are you sure you want to change the base?
Conversation
af4c33a
to
2530a6c
Compare
2530a6c
to
e4fd633
Compare
e4fd633
to
fa5fda4
Compare
Thanks for fixing! Once member addition&removal works, this LGTM |
ab25c68
to
55bb249
Compare
55bb249
to
7904843
Compare
7904843
to
0fa0f14
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
But @link2xt said in #7111 (comment) to merge the PR here after #7116, so, merging this still has to wait a bit.
It's after #7116 not because of merge conflict, but because if we do this before removing protected groups, we need to synchronize whether the group is protected or not. So we first remove protected groups and then don't have to synchronize this status. |
Unencrypted groups don't have grpid since key-contacts were merged, so we don't sync them for now.
If we use modules (which are actually namespaces), we can use shorter names. Another approach is to only use modules for internal code incapsulation and use full names like deltachat-ffi does.
0fa0f14
to
be8d47a
Compare
Fix #7001
To be merged after #7116