-
Notifications
You must be signed in to change notification settings - Fork 72
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
Improve calculation of DM names & avatars #721
Conversation
Also: - fix DM metadata on startup - improve cleanup of DM when Matrix user leaves it - improve migration of DM when duplicate DM is created
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.
Looks good, I found a few nitpicks but nothing major.
I wonder if we need to do this metadata fixing on something else than bridge startup: maybe m.room.member events? Or will this name mismatch never happen organically, and the startup code is just there to fix the rooms that are currently broken, because they were created before this change went in?
My understanding is that it's the latter. |
Actually, there is more time we should do the fixup: on ghost profile info updates triggered by an inbound message. Otherwise, DM names/avatars can go out-of-sync with the name/avatar of the Slack user it's associated with. (This is the subject of my |
Also fix DM metadata on team syncing instead of bridge startup
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.
LGTM now!
Also: