-
Notifications
You must be signed in to change notification settings - Fork 396
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
MSC3266: Room summary API #3266
Conversation
Signed-off-by: Nicolas Werner <[email protected]>
855306e
to
642f4e1
Compare
Signed-off-by: Nicolas Werner <[email protected]>
Signed-off-by: Nicolas Werner <[email protected]>
…est of the path separate Signed-off-by: Nicolas Werner <[email protected]>
That way the requesting server knows, if any user would have access to that room and it can forward the room to the user. Signed-off-by: Nicolas Werner <[email protected]>
@mscbot resolve should unauthenticated access be enabled by default? |
Co-authored-by: Johannes Marbach <[email protected]>
🔔 This is now entering its final comment period, as per the review above. 🔔 |
@KitsuneRal you have an outstanding request for changes (#3266 (review), I think). Could you dismiss your review, unless you still want to see changes here? |
As far as I can tell, this should have completed FCP weeks ago, but the bot seems to be stuck. |
considering FCP completed as-is. If there's edits to be made to the MSC, please put those up as a PR urgently. |
* Room summary proposal Signed-off-by: Nicolas Werner <[email protected]> * Remove alias resolution step from the federation API * Reference #688 in the alternatives section Signed-off-by: Nicolas Werner <[email protected]> * Remove `is_direct` from response Signed-off-by: Nicolas Werner <[email protected]> * Fix unstable prefixes for implementations which keep the prefix and rest of the path separate Signed-off-by: Nicolas Werner <[email protected]> * Add allowed_room_ids field That way the requesting server knows, if any user would have access to that room and it can forward the room to the user. Signed-off-by: Nicolas Werner <[email protected]> * Extend rationale for additional fields to reference MSC2946 Also explain that membership is already accessible information. Signed-off-by: Nicolas Werner <[email protected]> * Add bulk API as an alternative Signed-off-by: Nicolas Werner <[email protected]> * Remove federation API and address feedback - Add some additional rationale to some things. - Federation API now reuses MSC 2946 - roomid -> roomId - Move it out of /rooms, because it allows using an alias Signed-off-by: Nicolas Werner <[email protected]> * fix prefixes again * Remove extensions to federation API since that MSC is amended now Signed-off-by: Nicolas Werner <[email protected]> * Fix minor inaccuracy about the spaces sumary api * Add encryption field back * Add room version field Signed-off-by: Nicolas Werner <[email protected]> * Apply suggestions from code review Co-authored-by: Andrew Morgan <[email protected]> Co-authored-by: Alexey Rusakov <[email protected]> * Add a bit more reasoning * version -> room_version * Apply suggestions from code review Co-authored-by: Richard van der Hoff <[email protected]> * Try to address review comments Signed-off-by: Nicolas Werner <[email protected]> * Fix incorrect statement about encryption being a bool Signed-off-by: Nicolas Werner <[email protected]> * Apply suggestions from code review Co-authored-by: Richard van der Hoff <[email protected]> * Split up the big alternatives section * Collapse the same descriptions for publicRooms and hierarchy into one * Shorten the 'accessible' section again * Update proposals/3266-room-summary.md Co-authored-by: Richard van der Hoff <[email protected]> * Update proposals/3266-room-summary.md * Update proposals/3266-room-summary.md Co-authored-by: Alexey Rusakov <[email protected]> * Support knock_restricted rooms and rename to room_summary As well as a few smaller clarifications. * Be more explicit about authentication * Apply suggestions from code review Co-authored-by: Richard van der Hoff <[email protected]> Co-authored-by: Patrick Cloke <[email protected]> * Fix error codes and missing "Optional" * Also add allowed_room_ids to hierarchy API It suffers from the same knock_restricted issue. * Apply suggestions from code review Co-authored-by: Eric Eastwood <[email protected]> Co-authored-by: Patrick Cloke <[email protected]> * Update spec links * Clarify accessibility rules * Update proposals/3266-room-summary.md Co-authored-by: Richard van der Hoff <[email protected]> * Update proposals/3266-room-summary.md Co-authored-by: Johannes Marbach <[email protected]> * Unauthenticated access is impl-dependent * add to response * Clarify resposnse documentation. * Clarify situation for invited rooms * further clarification about unauth access * Update proposals/3266-room-summary.md Co-authored-by: Johannes Marbach <[email protected]> --------- Signed-off-by: Nicolas Werner <[email protected]> Co-authored-by: Andrew Morgan <[email protected]> Co-authored-by: Alexey Rusakov <[email protected]> Co-authored-by: Richard van der Hoff <[email protected]> Co-authored-by: Patrick Cloke <[email protected]> Co-authored-by: Eric Eastwood <[email protected]> Co-authored-by: Richard van der Hoff <[email protected]> Co-authored-by: Johannes Marbach <[email protected]>
|
||
For unauthenticated requests a response should only be returned if the room is | ||
publicly accessible; specifically, that means either: | ||
* the room has `join_rule: public` or `join_rule: knock`, or: |
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 suspect this is meant to include knock_restricted
?
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.
If the current implementation does so, yes. Otherwise it'll need a new MSC.
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.
Spec PR: matrix-org/matrix-spec#2125 |
Rendered.
Somewhat related to MSC2946 this provides an API to get a summary for a specific room either from the local server or over federation.
Useful for a few cases, where you need to show a summary for a room like matrix.to, traveler bots, showing spaces, lightweight clients, etc.
Open design questions looking for feedback: see this comment chain: #3266 (comment)resolved as of 2021/10/06Implementations:
allowed_room_ids
part is implemented here: deepbluev7/synapse@37f4253.Signed-off-by: Nicolas Werner [email protected]
SCT stuff:
Shepherd: @richvdh
FCP tickyboxes
Checklist: #3266 (comment)