From 3a39930f3d67b5b3acc7acef184f953f1c0a2027 Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Mon, 25 Apr 2022 21:00:05 +0200 Subject: [PATCH 1/5] Add files via upload --- ... room type of m.policy for policy rooms.md | 63 +++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 proposals/MSCXXXX Using room type of m.policy for policy rooms.md diff --git a/proposals/MSCXXXX Using room type of m.policy for policy rooms.md b/proposals/MSCXXXX Using room type of m.policy for policy rooms.md new file mode 100644 index 000000000..d35e565e6 --- /dev/null +++ b/proposals/MSCXXXX Using room type of m.policy for policy rooms.md @@ -0,0 +1,63 @@ +# MSCXXXX Using room type of m.policy for policy rooms + +## Introduction + +This simple MSC aims to make it easier for machines and people alike to be made instantly aware if a +room is a policy list. To facilitate this this MSC recommends using the already established `type` +attribute to flag rooms as policy rooms. This builds upon the precedent set by Spaces and their +`"type": "m.space"`. Adopting this for Policy rooms allows all stakeholders to instantly know if its +a Policy room or not for rooms covered by this proposal. + +For the purposes of this MSC policy lists can at times be called a policy room. This MSC does not intend +to change the name of the feature its just used to be very clear that we are talking about rooms with a +specific usecase. + +## Proposal + +This proposal is well quite simple. Allow for Policy rooms to be marked as such using the +`"type": "m.policy"`. The precedent for this comes from Spaces where they introduced this system in a +limited capacity. This proposal expands this system to help all stakeholders quickly identify +policy rooms in a machine compatible way that is computationally cheap. It has additional benefits like +allowing clients that are capable of editing policy to display editing tools for policy rooms when they +detect that a room is a policy room using this mechanic. For machine interaction with policy rooms this +proposal supplies a very fast way to tell if a room is definitively supposed to be a policy room or if +the user might have supplied a legacy room or typed in the wrong room ID / alias depending on how things +are configured. + +Legacy rooms in this proposal are defined as all rooms that predate this proposal and they are free to upgrade +if they desire to but they are also free to stay on their current room version and not upgrade their +room to include a type event in the creation event. All stakeholders are expected to gracefully support +interacting with legacy rooms until a future proposal changes this recommendation. + +The Author of this MSC believes that even with the problem of legacy rooms not being covered this MSC will +be useful in the future with more use of policy rooms. + + +## Potential issues + +As is covered in the proposal section this MSC has the potential issue relating to Legacy rooms. +The Author of this MSC thinks its that its an acceptable trade-off. + + +## Alternatives + +The alternative of using Peeking over fed to try to figure out if a room is a policy list has been +considered but considering that its currently considered at the time of writing to be a very in development +technology its deemed wholly unsuited for this application. The system this proposal recommends is the same +one that was used for spaces. Spaces have proven them self's in the real world and so has this system. + +## Security considerations + +None that the author is aware of at the time of writing due to the mostly informative nature of the data. +Due to that no client should trust that just because it says m.policy it is indeed a policy room the security +implications should be minimal. + +## Unstable prefix + +If you want to implement this MSC before its merged your free to use the unstable type of +`support.feline.policy.lists.msc.v1` please note that stakeholders are under no obligation to support this +unstable prefix after this MSC gets merged as of time of writing. + +## Dependencies + +The Author is not aware of any unstable MSC dependencies for this MSC. \ No newline at end of file From 32dca9f051250ec9ac2d91c27ab1bb7fb338ae83 Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Mon, 25 Apr 2022 21:00:59 +0200 Subject: [PATCH 2/5] Rename MSCXXXX Using room type of m.policy for policy rooms.md to XXXX-Using-room-type-of-m.policy-for-policy-rooms.md --- ....md => XXXX-Using-room-type-of-m.policy-for-policy-rooms.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename proposals/{MSCXXXX Using room type of m.policy for policy rooms.md => XXXX-Using-room-type-of-m.policy-for-policy-rooms.md} (98%) diff --git a/proposals/MSCXXXX Using room type of m.policy for policy rooms.md b/proposals/XXXX-Using-room-type-of-m.policy-for-policy-rooms.md similarity index 98% rename from proposals/MSCXXXX Using room type of m.policy for policy rooms.md rename to proposals/XXXX-Using-room-type-of-m.policy-for-policy-rooms.md index d35e565e6..1c7057326 100644 --- a/proposals/MSCXXXX Using room type of m.policy for policy rooms.md +++ b/proposals/XXXX-Using-room-type-of-m.policy-for-policy-rooms.md @@ -60,4 +60,4 @@ unstable prefix after this MSC gets merged as of time of writing. ## Dependencies -The Author is not aware of any unstable MSC dependencies for this MSC. \ No newline at end of file +The Author is not aware of any unstable MSC dependencies for this MSC. From 4e5c46c97141439c5a39e34ef34aa3ffe94cb4b5 Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Mon, 25 Apr 2022 21:01:22 +0200 Subject: [PATCH 3/5] Rename XXXX-Using-room-type-of-m.policy-for-policy-rooms.md to XXXX-using-room-type-of-m.policy-for-policy-rooms.md --- ...ms.md => XXXX-using-room-type-of-m.policy-for-policy-rooms.md} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename proposals/{XXXX-Using-room-type-of-m.policy-for-policy-rooms.md => XXXX-using-room-type-of-m.policy-for-policy-rooms.md} (100%) diff --git a/proposals/XXXX-Using-room-type-of-m.policy-for-policy-rooms.md b/proposals/XXXX-using-room-type-of-m.policy-for-policy-rooms.md similarity index 100% rename from proposals/XXXX-Using-room-type-of-m.policy-for-policy-rooms.md rename to proposals/XXXX-using-room-type-of-m.policy-for-policy-rooms.md From 8f3a8b4d53027f372ee5dd91b95dd2ff4487878d Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Mon, 25 Apr 2022 21:09:59 +0200 Subject: [PATCH 4/5] Update and rename XXXX-using-room-type-of-m.policy-for-policy-rooms.md to 3784-using-room-type-of-m.policy-for-policy-rooms.md --- ....md => 3784-using-room-type-of-m.policy-for-policy-rooms.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename proposals/{XXXX-using-room-type-of-m.policy-for-policy-rooms.md => 3784-using-room-type-of-m.policy-for-policy-rooms.md} (96%) diff --git a/proposals/XXXX-using-room-type-of-m.policy-for-policy-rooms.md b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md similarity index 96% rename from proposals/XXXX-using-room-type-of-m.policy-for-policy-rooms.md rename to proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md index 1c7057326..4640a08ea 100644 --- a/proposals/XXXX-using-room-type-of-m.policy-for-policy-rooms.md +++ b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md @@ -1,4 +1,4 @@ -# MSCXXXX Using room type of m.policy for policy rooms +# MSC3784 Using room type of m.policy for policy rooms ## Introduction From 8d99dcaa423e307ed7785fb1c9b624fb83854c12 Mon Sep 17 00:00:00 2001 From: Catalan Lover <48515417+FSG-Cat@users.noreply.github.com> Date: Sun, 24 Jul 2022 22:46:03 +0200 Subject: [PATCH 5/5] Improve Post merge information Added improved information about what to do after the MSC gets merged. --- .../3784-using-room-type-of-m.policy-for-policy-rooms.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md index 4640a08ea..5c292e2d7 100644 --- a/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md +++ b/proposals/3784-using-room-type-of-m.policy-for-policy-rooms.md @@ -55,8 +55,10 @@ implications should be minimal. ## Unstable prefix If you want to implement this MSC before its merged your free to use the unstable type of -`support.feline.policy.lists.msc.v1` please note that stakeholders are under no obligation to support this -unstable prefix after this MSC gets merged as of time of writing. +`support.feline.policy.lists.msc.v1`. + +After this MSC gets merged if a stakeholder has elected to remove its support for the unstable prefix if any +support existed or support never existed revert to Legacy room behavior for rooms that used the unstable prefix. ## Dependencies