-
Notifications
You must be signed in to change notification settings - Fork 385
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
Application service spec cleanup; Security definitions; r0 prep #1555
Conversation
@@ -254,6 +191,8 @@ paths: | |||
Retreive an array of third party network locations from a Matrix room |
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.
Retrieve
@@ -298,6 +237,8 @@ paths: | |||
description: |- | |||
Retreive an array of third party users from a Matrix User ID. |
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.
Retrieve
lgtm (modulo feedback in dependent PRs being solved) |
This commit has approval under matrix-org#1555 although is being included in this branch/PR so the build passes, permitting a merge.
This puts the scaffolding in place for an r0 release to happen, such as the changelog and version variables.
63d67ff
to
6f80db5
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.
A few things I'm unsure about, but it's mostly fine.
@@ -377,8 +392,6 @@ additional parameters on the ``/publicRooms`` client-server endpoint. | |||
Event fields | |||
~~~~~~~~~~~~ | |||
|
|||
.. TODO-TravisR: Fix this section to be a general "3rd party networks" section | |||
|
|||
We recommend that any events that originated from a remote network should | |||
include an ``external_url`` field in their content to provide a way for Matrix | |||
clients to link into the 'native' client from which the event originated. |
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.
Do we want to mention that client's using these should warn about them. From all the other issues raised in the spec, it looks like we are going for cautious?
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.
Oh, and do we have a suggested format?
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.
Would be good to clarify this section, yea. Will do that in a dedicated PR.
Edit: #1624
Application Services | ||
-------------------- | ||
Application services are passive and can only observe events from a given | ||
homeserver (HS). They can inject events into rooms they are participating in. |
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.
"from a given homeserver (HS)" I'm worried this might confuse people to believe appservices only work against events originating from one homeserver?
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.
sounds like we just need to remove "given"?
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.
Just the external_uri
and then you can merge :)
(reminded out of band that this is not an r0, just the prep for it - an r0 is a whole thing) |
Rendered: see 'docs' status check
This may be best to review commit by commit.
This is a PR for the few small tasks that need to be completed before an r0 can be cut:
unstable
)Blocked on: