-
Notifications
You must be signed in to change notification settings - Fork 625
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
Matrix: use per-room nicknames #1541
Conversation
Code Climate has analyzed commit 23e785d and detected 0 issues on this pull request. View more on Code Climate. |
Not sure how this works? There's only one global displayname? Seems like the per-room displayname is still being worked on - element-hq/element-meta#499 / matrix-org/matrix-spec-proposals#3189 |
In element you can already update your per-room nick with the commande |
Sure, but the API call here is fetching the global nick |
Hmm yeah I'm not really sure, I guess this is fixed by getting the state when syncing:
I will have to check that it also works when display names are changed while matterbridge is stopped. |
So, from what I understand, a server send the update when a user changes its displayname (as per |
For the current code (and your PR) this means that there's a 10 minute delay before the nickname also changes in the other rooms because we remove the cache every 10 minutes. And we'll ask for the nickname again (using the matrix API call) matterbridge/bridge/matrix/helpers.go Lines 106 to 108 in 23e785d
So I don't think this fixes the issue ? |
Oh yeah, I haven't tried this patch over sessions running long enough to hit that case. You're right, I will have to rethink this code. I'm not sure yet this is simple to do in matterbridge because there is no data persistence across restarts. |
I'm not currently working on this, so I'm gonna close this for now. |
Fixes element-hq/element-web#1336