From 9fced9056282b5c5d574eb91580e39448dab9459 Mon Sep 17 00:00:00 2001 From: Ginger Date: Tue, 16 Sep 2025 14:44:15 -0400 Subject: [PATCH] Stop silently re-adding the `displayname` and `avatar` fields to leave and ban state events Signed-off-by: Ginger --- src/models/room-state.ts | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/src/models/room-state.ts b/src/models/room-state.ts index 25057a20af..010608a8e9 100644 --- a/src/models/room-state.ts +++ b/src/models/room-state.ts @@ -464,19 +464,6 @@ export class RoomState extends TypedEventEmitter if (event.getType() === EventType.RoomMember) { const userId = event.getStateKey()!; - - // leave events apparently elide the displayname or avatar_url, - // so let's fake one up so that we don't leak user ids - // into the timeline - if ( - event.getContent().membership === KnownMembership.Leave || - event.getContent().membership === KnownMembership.Ban - ) { - event.getContent().avatar_url = event.getContent().avatar_url || event.getPrevContent().avatar_url; - event.getContent().displayname = - event.getContent().displayname || event.getPrevContent().displayname; - } - const member = this.getOrCreateMember(userId, event); member.setMembershipEvent(event, this); this.updateMember(member);