Travis Ralston

MSCs proposed for Final Comment Period (FCP) should meet the requirements outlined in the [checklist](https://github.com/matrix-org/matrix-spec-proposals/blob/main/MSC_CHECKLIST.md) prior to being accepted into the spec. This checklist is a bit long, but aims...

I'm still a bit unsure about whether this needs to be fixed in the spec, or on the sending client's side, but not enough to block progress. @mscbot fcp merge

For the overall changelog: this had a bunch of discussion amongst T&S developers from the community, resulting in the above changes. Namely: variables are now called arguments. Arguments have types...

MSCs proposed for Final Comment Period (FCP) should meet the requirements outlined in the [checklist](https://github.com/matrix-org/matrix-spec-proposals/blob/main/MSC_CHECKLIST.md) prior to being accepted into the spec. This checklist is a bit long, but aims...

@mscbot concern checklist incomplete (any SCT member can resolve this)

@mscbot resolve checklist incomplete

MSCs proposed for Final Comment Period (FCP) should meet the requirements outlined in the [checklist](https://github.com/matrix-org/matrix-spec-proposals/blob/main/MSC_CHECKLIST.md) prior to being accepted into the spec. This checklist is a bit long, but aims...

@mscbot fcp merge @mscbot concern Clarify the endpoint which allows for a start time of "now" on sticky events @mscbot concern Clarify if the sync API returns sticky events on...

@mscbot resolve History visibility semantics need clarification/specification @mscbot resolve Clarify if the sync API returns sticky events on subsequent requests @mscbot resolve Clarify the endpoint which allows for a start...

@mscbot resolve Unclear if addendum is normative for spec process purposes