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
There are clients that leave old versions of rooms when user follows tombstone (e.g. FluffyChat#880 & element-hq/element-web#10380 (:white_check_mark:)) and history visibility isn't connected to access to the room. Thus it's possible to have public history in rooms that no one in power can join anymore and cause privacy leak, especially with projects such as matrix-static or matrix-public-archive that to my knowledge don't care about tombstones.
I think there was also a related suggestion somewhere to make the old room allow joining by being a member of the new room automatically (adding the new room to upgraded room's restricted or knock_restricted join rule or doing that automatically), but I am unable to locate it from this repository and it may also have been only suggested in chat and not raised at a issue tracker.
The text was updated successfully, but these errors were encountered:
Suggestion
There are clients that leave old versions of rooms when user follows tombstone (e.g. FluffyChat#880 & element-hq/element-web#10380 (:white_check_mark:)) and history visibility isn't connected to access to the room. Thus it's possible to have public history in rooms that no one in power can join anymore and cause privacy leak, especially with projects such as matrix-static or matrix-public-archive that to my knowledge don't care about tombstones.
Originally raised at matrix-org/matrix-viewer#47 (comment) by me.
I think there was also a related suggestion somewhere to make the old room allow joining by being a member of the new room automatically (adding the new room to upgraded room's
restricted
orknock_restricted
join rule or doing that automatically), but I am unable to locate it from this repository and it may also have been only suggested in chat and not raised at a issue tracker.The text was updated successfully, but these errors were encountered: