matrix-appservice-discord
matrix-appservice-discord copied to clipboard
matrix-org
Excessive metadata messages (name changes) in the timeline
got this issue too. The bot even recognize people's name on different servers
(also look at the iam.someone changed their name, at the bottom)
metadata leaks
This is a reflection of cultural difference. On Discord, nickname changes are free and only leave a temporary trace in the audit log. On Matrix, nickname changes leave a permanent trace in the timeline.
The virtual account only need to change its name channel-specific, not changing the name globally. Broken implementation, maybe?
This looks like discord user name changes simply being reflected to matrix, which would be intended behavior. (If you don't want to see the name changes in the element client, there's a setting under "Settings > Preferences > Timeline" called "Show display name changes" that allows you to disable it) Otherwise, please describe the nature of the issue more in-depth, e.g. are any display names not consistent between discord and matrix?
@Vyquos Excessive nickname changes make it slow to load the room on the matrix side, even if collapsed. Not a concern on the discord side as name changes are effectively free there.
I see what you're getting at. I don't think the bridge is at fault here though - bridging all user name changes is exactly what it's supposed to do. Excessive user name changes may occur for non-bridged matrix users too though. I believe that matrix clients have to solve this problem of timeline loading efficiency rather than the bridge.
bridging all user name changes is exactly what it's supposed to do.
Disagree. Just do not create all these useless events. Noone needs them. Waste of compute.
At Matrix's current state you are going to get terrible lags and worst user experience ever out of it.
Like, you have to send one HTTP request for each message deletion.
Not sending these events would cause inconsistent usernames - do you have a proposal to handle this? Also, what do you mean by "you have to send one HTTP request for each message deletion"?
Like, you have to send one HTTP request for each message deletion.
Deletion expectations do not match. It is impossible to bridge discord-side cheap traceless deletions to matrix.
@Vyquos Matrix protocol requires one event for each deletion, whether they are sent with one POST request for each event I am not sure, but it seems so. When I delete a large number of messages it's just stuck. Absolutely hilarious.