From 9f517f33cee2a555fa635b9291a2422b27ff7802 Mon Sep 17 00:00:00 2001 From: Neil Johnson Date: Mon, 28 Jan 2019 17:59:17 +0000 Subject: [PATCH 1/4] Create 1819-remove-presence-lists.md --- proposals/1819-remove-presence-lists.md | 26 +++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 proposals/1819-remove-presence-lists.md diff --git a/proposals/1819-remove-presence-lists.md b/proposals/1819-remove-presence-lists.md new file mode 100644 index 000000000..7595f5699 --- /dev/null +++ b/proposals/1819-remove-presence-lists.md @@ -0,0 +1,26 @@ +# Remove references to presence lists + +[Presence](https://matrix.org/docs/spec/client_server/r0.4.0.html#id388) lists allow a given user the ability to subscribe to other users and be alerted to their current presence status. + +While spec'd, no established client has implemented support and the only server side implementation raises privacy concerns. + +The proposal is to simply remove references to presence lists with a view to revisiting the same ideas in the future. + +This MSC addresses [#1810](https://github.com/matrix-org/matrix-doc/issues/1810) + +## Proposal + +Presence lists seem like a good fit for ['MSC1769: Extensible profiles as rooms'](https://github.com/matrix-org/matrix-doc/pull/1769) proposal, meaning that the current design will most likely be superceded. + +Additionally, no major client has implemented the behaviour to date and the only server implementation of presence lists (Synapse) auto-accepts invites leading to privacy concerns in the wild. + +With this in mind the most pragmatic solution is to remove presence lists ahead of the r0 release. + +## Tradeoffs + +Ideally this proposal would also come with an alternative design for this functionality. Out of pragmatism the proposal only covers removal of what is there today. + + +## Conclusions + +This is a common sense attempt to remove unused portions of the spec ahead of an r0 release. It does not suggest that the ability to subscribe to the presence of others is undesirable and assumes that this behvaiour will return again in some form. From 5151aa0aa7bfa6ee3b8ce9c2d43deb2d6305aec4 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff <1389908+richvdh@users.noreply.github.com> Date: Wed, 30 Jan 2019 10:44:15 +0000 Subject: [PATCH 2/4] Update proposals/1819-remove-presence-lists.md Co-Authored-By: neilisfragile --- proposals/1819-remove-presence-lists.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/proposals/1819-remove-presence-lists.md b/proposals/1819-remove-presence-lists.md index 7595f5699..e082f5fae 100644 --- a/proposals/1819-remove-presence-lists.md +++ b/proposals/1819-remove-presence-lists.md @@ -1,6 +1,6 @@ # Remove references to presence lists -[Presence](https://matrix.org/docs/spec/client_server/r0.4.0.html#id388) lists allow a given user the ability to subscribe to other users and be alerted to their current presence status. +[Presence](https://matrix.org/docs/spec/client_server/r0.4.0.html#id107) lists allow a given user the ability to subscribe to other users and be alerted to their current presence status. While spec'd, no established client has implemented support and the only server side implementation raises privacy concerns. From 4f13f5289e656813a43083bc84d81533241a5c8d Mon Sep 17 00:00:00 2001 From: Neil Johnson Date: Wed, 30 Jan 2019 11:20:38 +0000 Subject: [PATCH 3/4] Update 1819-remove-presence-lists.md Add references to exactly what this proposal would remove --- proposals/1819-remove-presence-lists.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/proposals/1819-remove-presence-lists.md b/proposals/1819-remove-presence-lists.md index e082f5fae..38c318835 100644 --- a/proposals/1819-remove-presence-lists.md +++ b/proposals/1819-remove-presence-lists.md @@ -16,6 +16,18 @@ Additionally, no major client has implemented the behaviour to date and the only With this in mind the most pragmatic solution is to remove presence lists ahead of the r0 release. +Specifically:- + +CS API: Remove +* [POST /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#post-matrix-client-r0-presence-list-userid) +* [GET /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#get-matrix-client-r0-presence-list-userid) + +SS API: Remove + * [m.presence_invite](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-invite-schema) + * [m.presence_accept](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-accept-schema) + * [m.presence_deny](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-deny-schema) + + ## Tradeoffs Ideally this proposal would also come with an alternative design for this functionality. Out of pragmatism the proposal only covers removal of what is there today. From 2eae933ed6e03247ee3387ad0db267c19bff9679 Mon Sep 17 00:00:00 2001 From: Neil Johnson Date: Wed, 30 Jan 2019 11:28:53 +0000 Subject: [PATCH 4/4] hard wrap to 80 chars --- proposals/1819-remove-presence-lists.md | 41 +++++++++++++++++-------- 1 file changed, 29 insertions(+), 12 deletions(-) diff --git a/proposals/1819-remove-presence-lists.md b/proposals/1819-remove-presence-lists.md index 38c318835..7c5425097 100644 --- a/proposals/1819-remove-presence-lists.md +++ b/proposals/1819-remove-presence-lists.md @@ -1,38 +1,55 @@ # Remove references to presence lists -[Presence](https://matrix.org/docs/spec/client_server/r0.4.0.html#id107) lists allow a given user the ability to subscribe to other users and be alerted to their current presence status. +[Presence](https://matrix.org/docs/spec/client_server/r0.4.0.html#id107) lists +allow a given user the ability to subscribe to other users and be alerted to +their current presence status. -While spec'd, no established client has implemented support and the only server side implementation raises privacy concerns. +While spec'd, no established client has implemented support and the only server +side implementation raises privacy concerns. -The proposal is to simply remove references to presence lists with a view to revisiting the same ideas in the future. +The proposal is to simply remove references to presence lists with a view to +revisiting the same ideas in the future. -This MSC addresses [#1810](https://github.com/matrix-org/matrix-doc/issues/1810) +This MSC addresses +[#1810](https://github.com/matrix-org/matrix-doc/issues/1810) ## Proposal -Presence lists seem like a good fit for ['MSC1769: Extensible profiles as rooms'](https://github.com/matrix-org/matrix-doc/pull/1769) proposal, meaning that the current design will most likely be superceded. +Presence lists seem like a good fit for ['MSC1769: Extensible profiles as +rooms'](https://github.com/matrix-org/matrix-doc/pull/1769) proposal, meaning +that the current design will most likely be superceded. -Additionally, no major client has implemented the behaviour to date and the only server implementation of presence lists (Synapse) auto-accepts invites leading to privacy concerns in the wild. +Additionally, no major client has implemented the behaviour to date and the +only server implementation of presence lists (Synapse) auto-accepts invites +leading to privacy concerns in the wild. -With this in mind the most pragmatic solution is to remove presence lists ahead of the r0 release. +With this in mind the most pragmatic solution is to remove presence lists ahead +of the r0 release. Specifically:- CS API: Remove -* [POST /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#post-matrix-client-r0-presence-list-userid) -* [GET /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#get-matrix-client-r0-presence-list-userid) +* [POST + /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#post-matrix-client-r0-presence-list-userid) +* [GET + /_matrix/client/r0/presence/list/{userId}](https://matrix.org/docs/spec/client_server/r0.4.0.html#get-matrix-client-r0-presence-list-userid) SS API: Remove * [m.presence_invite](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-invite-schema) * [m.presence_accept](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-accept-schema) * [m.presence_deny](https://matrix.org/docs/spec/server_server/unstable.html#m-presence-deny-schema) - + ## Tradeoffs -Ideally this proposal would also come with an alternative design for this functionality. Out of pragmatism the proposal only covers removal of what is there today. +Ideally this proposal would also come with an alternative design for this +functionality. Out of pragmatism the proposal only covers removal of what is +there today. ## Conclusions -This is a common sense attempt to remove unused portions of the spec ahead of an r0 release. It does not suggest that the ability to subscribe to the presence of others is undesirable and assumes that this behvaiour will return again in some form. +This is a common sense attempt to remove unused portions of the spec ahead of +an r0 release. It does not suggest that the ability to subscribe to the +presence of others is undesirable and assumes that this behvaiour will return +again in some form.