m.room.history_visibility does not appear in the backend at all.
It decides how much of a room a new member can read - shared, invited, joined, world_readable - and it is one of the few room settings with a privacy consequence rather than a cosmetic one. It is in Element's room settings, and a room created here takes whatever the server defaults to, unseen.
`m.room.history_visibility` does not appear in the backend at all.
It decides how much of a room a new member can read - `shared`, `invited`, `joined`, `world_readable` - and it is one of the few room settings with a privacy consequence rather than a cosmetic one. It is in Element's room settings, and a room created here takes whatever the server defaults to, unseen.
Read when it is asked for rather than cached: it changes rarely and is looked at rarely, and a value fetched as it is shown cannot be stale. A 404 is the ordinary answer rather than a failure — a room that has never set this does not carry the event, and shared is what that means.
The four values are labelled as sentences about people rather than as protocol words. "shared" and "invited" are the names of rules, not descriptions of them, and this is a setting somebody gets wrong once and cannot take back since it only ever applies from now on. world_readable says in as many words that it means anybody, account or no account.
moderation::can_send_state came out of this and is what every room setting has to ask before offering a control — the threshold is per event type and falls back to state_default, which is 50 rather than the 0 an ordinary message gets.
Finished.
Read when it is asked for rather than cached: it changes rarely and is looked at rarely, and a value fetched as it is shown cannot be stale. A 404 is the ordinary answer rather than a failure — a room that has never set this does not carry the event, and `shared` is what that means.
The four values are labelled as sentences about people rather than as protocol words. "shared" and "invited" are the names of rules, not descriptions of them, and this is a setting somebody gets wrong once and cannot take back since it only ever applies from now on. `world_readable` says in as many words that it means anybody, account or no account.
`moderation::can_send_state` came out of this and is what every room setting has to ask before offering a control — the threshold is per event type and falls back to `state_default`, which is 50 rather than the 0 an ordinary message gets.
[b7d42d8](https://git.salastil.com/Salastil/nobilis/commit/b7d42d8), [8900723](https://git.salastil.com/Salastil/moho/commit/8900723)
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.
m.room.history_visibilitydoes not appear in the backend at all.It decides how much of a room a new member can read -
shared,invited,joined,world_readable- and it is one of the few room settings with a privacy consequence rather than a cosmetic one. It is in Element's room settings, and a room created here takes whatever the server defaults to, unseen.Finished.
Read when it is asked for rather than cached: it changes rarely and is looked at rarely, and a value fetched as it is shown cannot be stale. A 404 is the ordinary answer rather than a failure — a room that has never set this does not carry the event, and
sharedis what that means.The four values are labelled as sentences about people rather than as protocol words. "shared" and "invited" are the names of rules, not descriptions of them, and this is a setting somebody gets wrong once and cannot take back since it only ever applies from now on.
world_readablesays in as many words that it means anybody, account or no account.moderation::can_send_statecame out of this and is what every room setting has to ask before offering a control — the threshold is per event type and falls back tostate_default, which is 50 rather than the 0 an ordinary message gets.b7d42d8, 8900723