This room version builds on version 5 while changing various authorization rules performed on events. Client considerations There are no client considerations introduced in this room version. Clients which implement the redaction algorithm locally should refer to the redactions section below for a full overview of the algorithm. Redactions [New in this version] All significant meaning for m.room.aliases has been removed from the redaction algorithm. The remaining rules are the same as past ro...| Matrix Specification
This room version builds on version 4 while enforcing signing key validity periods for events. Client considerations There are no client considerations introduced in this room version. Clients which implement the redaction algorithm locally should refer to the redactions section below for a full overview of the algorithm. Server implementation components The information contained in this section is strictly for server implementors. Applications which use the Client-Server API are generally un...| Matrix Specification
Rooms are central to how Matrix operates, and have strict rules for what is allowed to be contained within them. Rooms can also have various algorithms that handle different tasks, such as what to do when two or more events collide in the underlying DAG. To allow rooms to be improved upon through new algorithms or rules, “room versions” are employed to manage a set of expectations for each room. New room versions are assigned as needed.| Matrix Specification