mirror of
https://github.com/mikaela/mikaela.github.io/
synced 2024-12-26 13:12:34 +01:00
blog/{mppn,mcasbo}: simplify checking servers not supporting room version X
Ref: af5c8405ee
This commit is contained in:
parent
3ee7b95da8
commit
90c3887f4a
@ -84,8 +84,8 @@ and as your room is hosted on every homeserver that has users in your room,
|
||||
have a single homeserver that hasn't explicitly enabled it, or doesn't otherwise support it, and the room
|
||||
history never goes away. Executing `/upgraderoom {{site.matrixLatestRoomVersion}}` or any other version [will also remove the event](https://github.com/matrix-org/synapse/issues/11279).
|
||||
|
||||
***WARNING! Always before executing `/upgraderoom` check that everyone in your room has a recent Matrix server that supports your target room version. Otherwise you may lock your users out.*** For example `/invite @version:maunium.net` and once it joins, say
|
||||
`!servers` and once it finishes printing server versions you can `!servers match SOFTWARE < 1.0` to get list of servers running SOFTWARE older than 1.0. Once aware of what servers are being used, either check their changelogs/documentation/support_rooms/admins for their support to your target version e.g. {{site.matrixLatestRoomVersion}}.
|
||||
***WARNING! Always before executing `/upgraderoom` check that everyone in your room has a recent Matrix server that supports your target room version, otherwise you may lock some of your users out.*** For example `/invite @version:maunium.net` and once it joins, say
|
||||
`!servers upgrade {{site.matrixLatestRoomVersion}}` to get a list of servers that don't support room version {{site.matrixLatestRoomVersion}} yet.
|
||||
|
||||
In case there isn't enough confusion, retention shouldn't be confused with actual [self-destructing/disappearing messages](https://github.com/vector-im/element-meta/issues/82).
|
||||
|
||||
|
@ -25,13 +25,11 @@ smaller steps:
|
||||
labs)
|
||||
2. Create a space.
|
||||
3. Through developer mode `/upgraderoom {{ site.matrixLatestRoomVersion }}`.
|
||||
1. ***WARNING*** The room version number here is configured in Jekyll site
|
||||
variable, not one specific to this post.
|
||||
2. ***WARNING*** You should check [the Matrix spec](https://spec.matrix.org/latest/rooms/)
|
||||
for the latest stable room version. Or maybe the [unstable spec](https://spec.matrix.org/unstable/rooms/)?
|
||||
Or maybe you should just [search GitHub](https://github.com/matrix-org/matrix-spec-proposals/issues?q=room%20version)?
|
||||
3. ***WARNING! Always before executing `/upgraderoom` check that everyone in your room has a recent Matrix server that supports your target room version. Otherwise you may lock your users out.*** For example `/invite @version:maunium.net` and once it joins, say
|
||||
`!servers` and once it finishes printing server versions you can `!servers match SOFTWARE < 1.0` to get list of servers running SOFTWARE older than 1.0. Once aware of what servers are being used, either check their changelogs/documentation/support_rooms/admins for their support to your target version e.g. {{site.matrixLatestRoomVersion}}.
|
||||
3. ***WARNING! Always before executing `/upgraderoom` check that everyone in your room has a recent Matrix server that supports your target room version, otherwise you may lock some of your users out.*** For example `/invite @version:maunium.net` and once it joins, say
|
||||
`!servers upgrade {{site.matrixLatestRoomVersion}}` to get a list of servers that don't support room version {{site.matrixLatestRoomVersion}} yet.
|
||||
4. Clear cache and reload so the old space maybe disappears.
|
||||
5. See also [Element-web#19208: Allow upgrading spaces](https://github.com/vector-im/element-web/issues/19208)
|
||||
6. Now that there is a space, right click it to create a new room under it and
|
||||
|
Loading…
Reference in New Issue
Block a user