-
Notifications
You must be signed in to change notification settings - Fork 325
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
Notify remote backends when users join #1556
Conversation
b36c70d
to
577ade7
Compare
1f69b23
to
a24c00d
Compare
a24c00d
to
2dcb90a
Compare
f2a8c33
to
a7cdbb7
Compare
a7cdbb7
to
bdf3660
Compare
bdf3660
to
7708b88
Compare
Before this change, only backends of new users (including local ones) were notified of a conversation update.
$ others | ||
. nubOrd | ||
. map (unTagged . rmId) | ||
$ rmm <> rothers |
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.
If I am getting this right, this traversing rightfully notifies remote users. Is there an equivalent for local users?
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.
This doesn't directly notify users, but it calls the update-conversation-memberships
federation RPC, which will in turn notify users on its backend.
Notifications for local users are sent in the two statements that follow.
7708b88
to
8642c1e
Compare
…update-conv-membership
This makes a backend notify remote backends when users join a conversation.
Note: this includes commits from #1570. Rebase them away before merging.