Spec for MSC4277: Harmonizing the reporting endpoints#2311
Spec for MSC4277: Harmonizing the reporting endpoints#2311Johennes wants to merge 3 commits intomatrix-org:mainfrom
Conversation
Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
Johennes
force-pushed
the
johannes/msc4277
branch
from
02b5785 to
60f4e5d
Compare
| This endpoint now requires the user to be joined to the room. | ||
| 1.18: | | ||
| The `score` request parameter was removed. Additionally, servers | ||
| may deny event ID enumeration by using the 200 response |
There was a problem hiding this comment.
| may deny event ID enumeration by using the 200 response | |
| may prevent event ID enumeration by using the 200 response |
(The word 'deny' sounds a bit more active -- like the server should actively monitor for clients that are enumerating event IDs and return a 4xx or something. 'Prevent' reads a bit more passive.)
There was a problem hiding this comment.
The MSC isn't explicit about it, but can servers apply the same logic to non-existent room IDs?
There was a problem hiding this comment.
Hm, yeah, I guess by extension of the same argument, that would make a lot of sense. I hadn't thought of that before.
How do we deal with the MSC missing this?
There was a problem hiding this comment.
the MSC just says "MAY respond with 200 and no content regardless of whether the reported subject exists". I think we can squint at that "reported subject" and claim that it allows non-existent room IDs here.
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
2 participants
Pull Request Checklist
Preview: https://pr2311--matrix-spec-previews.netlify.app