forked from quentin/quentin.dufour.io
typo
This commit is contained in:
parent
9d5708f0e5
commit
503ac6ba9f
1 changed files with 9 additions and 8 deletions
|
@ -9,18 +9,19 @@ category: operation
|
|||
tags:
|
||||
---
|
||||
|
||||
Some time ago, the Matrix team was pushing hard E2EE and activated for all created rooms.
|
||||
Believing encryption was the future, we kept this default for all the rooms we created.
|
||||
But now that one of our room starts being popular, it appeares that E2EE does not work well with public rooms:
|
||||
Some time ago, the Matrix team was pushing hard E2EE and activated it for all created rooms.
|
||||
Believing encryption was the future, we kept this default for all of our rooms.
|
||||
But now that one of our room starts being popular, it appears that E2EE does not work well with public rooms:
|
||||
1. the history is not available to newcomers
|
||||
2. we can not search the history of an encrypted room (or at least, I never managed to make it work even with the desktop app)
|
||||
3. notifications options are limited on mobile
|
||||
3. notification options are more limited
|
||||
4. scaling issues
|
||||
5. and so on.
|
||||
5. many additional minor issues
|
||||
|
||||
It seems that Matrix developpers are aware of these problems as now, if you create a "public room", you will not be asked to encrypt it at all.
|
||||
But for existing rooms, we have a problem: for security reasons, you can't disable encryption in a room.
|
||||
It seems that Matrix developers are aware of these problems as if you create a "public room" now, you will not be proposed to encrypt it.
|
||||
But for existing rooms, we still have a problem: for security reasons, you can't disable encryption in a room.
|
||||
Our only option is to create a new room and to point the old one to the new one.
|
||||
|
||||
Thankfully, Matrix has a feature named **Tombstone** that helps redirecting users from one room to another.
|
||||
This feature is used for room version upgrade, but we can "abuse" it to redirect people to a completely different room.
|
||||
|
||||
|
@ -31,7 +32,7 @@ You can set a new alias for your old room and send a message containing it on yo
|
|||
|
||||
> Hi, this is the beginning of the history of this room. If you want to go back even more in time, check the old room: #myroom-old:example.tld
|
||||
|
||||
Finally, you need the identifier of your room. It starts with a `!`. For example: `!ARbIZeDKGloDOnjyyw:deuxfleurs.fr`.
|
||||
Finally, you need the identifier of your **new** room. It starts with a `!`. For example: `!ARbIZeDKGloDOnjyyw:deuxfleurs.fr`.
|
||||
Keep it somewhere accessible, and we are done configuring our new room.
|
||||
|
||||
We can now prepare the tombstone for the old room.
|
||||
|
|
Loading…
Reference in a new issue