MSC4370: Federation endpoint for retrieving current extremities #4370
Conversation
turt2live
changed the title
turt2live
added
proposal
There was a problem hiding this comment.
Implementation requirements:
- Server (calling)
- Server (serving)
There was a problem hiding this comment.
I'd recommend waiting to implement this MSC until it has a reasonably healthy amount of review given the security considerations.
This comment was marked as duplicate.
This comment was marked as duplicate.
| this may mean requesting state at each event and merging the results for a good enough representation | ||
| of current state - specific handling is left as an implementation detail. | ||
|
|
||
| ## Potential issues |
There was a problem hiding this comment.
This doesn't seem to consider v1 or v2 rooms, which have
prev_eventslaid out differently.
(please use threads to ensure comments are visible and can be replied to)
There was a problem hiding this comment.
in all honesty, I'm not concerned about v1 or v2 rooms at this point in our history. If a server really wants to support those room versions, it can call this endpoint then the GET /event/:eventId endpoint to get the hash, then wedge that tuple into whatever it needs to.
2 participants
Rendered
Disclosure: I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as a Trust & Safety team member allocated in full to the Foundation.