-
Notifications
You must be signed in to change notification settings - Fork 382
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spec ignoring users #1142
Spec ignoring users #1142
Conversation
Adds matrix-org#528 Signed-off-by: Travis Ralston <travpc@gmail.com>
Signed-off-by: Travis Ralston <travpc@gmail.com>
dbd8d31
to
1daf6af
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
need to add the module to specification/targets.yaml!
A map of users which are considered ignored is kept in ``acount_data`` | ||
in an event type of ``m.ignored_user_list``. | ||
properties: | ||
content: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we've lost a layer of objects here. Shouldn't there be an ignored_users
property?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
.. See the License for the specific language governing permissions and | ||
.. limitations under the License. | ||
|
||
Ignore Users |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Ignoring users", possibly? "User ignore lists"?
should perform a fresh sync. The client may also un-hide any events it previously | ||
hid due to the user becoming ignored. | ||
|
||
Clients should be aware that split-brain |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this sentence seems to be split-brain
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My brain seemingly split while writing this... not sure where I was going with that.
Client behaviour | ||
---------------- | ||
To ignore a user, effectively blocking them, the client should add the target | ||
user to the ``m.ignored_user_list`` event in their account data. Once ignored, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be useful to link to the right API for this, as the "Direct Messaging" module does.
Server behaviour | ||
---------------- | ||
Following an update of the ``m.ignored_user_list``, the sync API for all clients | ||
will immediately start ignoring (or un-ignoring) the user. Clients are responsible |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/will/should/
changelogs/client_server.rst
Outdated
@@ -19,6 +19,8 @@ Unreleased changes | |||
(`#1106 <https://github.com/matrix-org/matrix-doc/pull/1106>`_). | |||
- Clarify default values for some fields on the /search API | |||
(`#1109 <https://github.com/matrix-org/matrix-doc/pull/1109>`_). | |||
- Add spec for ignoring users |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be under "Changes to the API which will be backwards-compatible for clients".
Signed-off-by: Travis Ralston <travpc@gmail.com>
* Fix the event schema to represent the real world * Add the module to the spec targets * Remove incomplete thought from the client behaviour * Link to the account data API * Minor word choice changes Signed-off-by: Travis Ralston <travpc@gmail.com>
title: "Ignored User" | ||
description: "An empty object for future enhancement" | ||
x-pattern: "$USER_ID" | ||
required: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be under properties.content
, not properties.content.properties
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that did it, thanks :D
Signed-off-by: Travis Ralston <travpc@gmail.com>
5176f0e
to
0835612
Compare
Adds #528