You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Displaynames from local server are properly fetched, unlike federation users. Local server doesn't provide information about federation users at endpoint https://server/_synapse/admin/v2/users/.
Synapse-admin shouldn't request federation users info on local homeserver, please check endpoints within https://github.com/element-hq/synapse/blob/develop/synapse/rest/admin/users.py
However Displayname field of local users is shown with correct value for a small moment and then all displaynames are changed to that red icon.
awesome-manuel
changed the title
Room members Displayname is not shown correctly
Room members information (e.g. displayname) should not be fetched for non-local users
Feb 8, 2024
However Displayname field of local users is shown with correct value for a small moment and then all displaynames are changed to that red icon.
Try to enable "Stop on exception", then first name of local user is visible. After excecution is complete, red icon is everywhere. I would expect, that local users have their displaynames, federated have red icon. It happens in the room with 5 local users and 1 federated.
It's not shown when some of members originate from different homeserver (matrix.org).
However
Displayname
field of local users is shown with correct value for a small moment and then all displaynames are changed to that red icon.Expected result is that only members from other homeservers shall have that red icon because of response 400
The text was updated successfully, but these errors were encountered: