One line under the room name in Room Settings → General, no new controls: e.g. "Encrypted · Invite only · History visible to members since they joined" derived from m.room.encryption, m.room.join_rules, m.room.history_visibility. Existing chips (encryption/join-rule) already exist on the room preview card — reuse their wording so it's consistent.
Jared: "maybe — must not be bloat". Decide on the mock-up; if it adds a card or icons, drop it.
One line under the room name in Room Settings → General, no new controls: e.g. **"Encrypted · Invite only · History visible to members since they joined"** derived from `m.room.encryption`, `m.room.join_rules`, `m.room.history_visibility`. Existing chips (encryption/join-rule) already exist on the room preview card — reuse their wording so it's consistent.
Jared: "maybe — must not be bloat". Decide on the mock-up; if it adds a card or icons, drop it.
jared
added this to the Features 2026-Q4 milestone 2026-09-17 16:10:05 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One line under the room name in Room Settings → General, no new controls: e.g. "Encrypted · Invite only · History visible to members since they joined" derived from
m.room.encryption,m.room.join_rules,m.room.history_visibility. Existing chips (encryption/join-rule) already exist on the room preview card — reuse their wording so it's consistent.Jared: "maybe — must not be bloat". Decide on the mock-up; if it adds a card or icons, drop it.