This room version builds on version 8 to add additional redaction rules that were unintentionally missed when incorporating v8. Client considerations See room version 8 for specific details regarding the addition of restricted rooms. Clients which implement the redaction algorithm locally should refer to the redactions section below for a full overview. Redactions [New in this version] m.room.member events now keep join_authorised_via_users_server in addition to other keys in content when bei...| Matrix Specification
This room version builds on version 7 to introduce a new join rule that allows members to join the room based on membership in another room. This room version is known to have issues relating to redactions of member join events. Room version 9 should be preferred over v8 when creating rooms. Client considerations Clients are encouraged to expose the option for the join rule in their user interface for supported room versions.| Matrix Specification
This room version builds on version 9 to enforce that power level values be integers, and to introduce a new knock_restricted join rule, allowing prospective members to more easily join such a room. Client considerations This room version adds a new knock_restricted join rule to allow prospective members of a room join either through knocking (introduced in room version 7) or through “join restrictions” (introduced in room version 8 and refined in room version 9).| 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