Skip to content
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

Deactivate user with erase: true does not delete user displayname in historical membership events as it is mentioned in the doc GDPR issue #15355

Closed
matrixbot opened this issue Dec 21, 2023 · 1 comment · Fixed by #17076

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 21, 2023

This issue has been migrated from #15355.


Description

Hello,

In the official documentation, erase : true should delete displayname BUT is not the case

I am still able to see the user display name when I query our room.

Screenshot 2023-03-30 at 17 58 37

Steps to reproduce

  1. Create a user with a displayname
  2. Deactivate a user with erase : true
  3. Query the room where the user was joined

Homeserver

my private server

Synapse Version

synapse version 1.79

Installation Method

Debian packages from packages.matrix.org

Database

postgres

Workers

Single process

Platform

All

Configuration

No response

Relevant log output

Please see the attached picture

Anything else that would be useful to know?

No response

@matrixbot matrixbot changed the title Dummy issue Deactivate user with erase: true does not delete user displayname in historical membership events as it is mentioned in the doc GDPR issue Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
@erikjohnston
Copy link
Member

Fixing this properly such that existing users see their display names, but new users join them don't, is going to be hard. This is due to the fact that Synapse doesn't have an easy way of answering the query of "who was in the room when this state event was 'live'".

I suggest as an easier fix we instead remove the display name for erased users for all members in the room. This does mean that people's historic view of the room changes (they'll no longer have display names or avatars), but they'll still have the user IDs so I think that is acceptable.

reivilibre pushed a commit that referenced this issue Apr 25, 2024
…ing (#17076)

Fixes #15355 by redacting all membership events before leaving rooms.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants