From 3bab6bd9e1ec9287e84ef43ce745719719d33f8a Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 17 Jun 2021 14:21:45 -0400 Subject: [PATCH] Remove via field. --- proposals/3083-restricted-rooms.md | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index b13589cd..936470b9 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -21,13 +21,11 @@ would include the rooms to trust for membership. For example: "allow": [ { "type": "m.room_membership", - "room_id": "!mods:example.org", - "via": ["example.org"] + "room_id": "!mods:example.org" }, { "type": "m.room_membership", - "room_id": "!users:example.org", - "via": ["example.org"] + "room_id": "!users:example.org" } ], "authorised_servers": ["example.org"] @@ -46,7 +44,6 @@ following keys: * `type`: `"m.room_membership"` to describe that we are allowing access via room membership. Future MSCs may define other types. * `room_id`: The room ID to check the membership of. -* `via`: A list of servers which may be used to peek for membership of the room. Any entries in the list which do not match the expected format are ignored. Thus, if all entries are invalid, the list behaves as if empty and all users without