Erik Johnston
Erik Johnston
Hmm, this is deprecating `py_limited_api` option, so we should figure out how to migrate from that
Yup, currently the server creates the room then tries to invite the user. If the client retries then it will create more rooms
Though a regression test would be good
We should update the documentation to use `bool`
> [@erikjohnston](https://github.com/erikjohnston) thoughts on cleaning up `state_groups_pending_deletion` & `state_group_edges` tables? ^ Err, yes they should be cleaned up too
> > We probably do want to indicate which rooms are in which lists, but that can be added later. > > Whilst I appreciate wanting to break things up,...
> Element Web uses multiple lists and [different filters](https://github.com/element-hq/matrix-react-sdk/blob/be768525295c024eb9c1a29904ab59007ccccc31/src/stores/room-list/SlidingRoomListStore.ts#L36-L65). Do they use the list ops? Or will need to?
Worth noting those filters seem to pertain to information the client will see, so they can infer? Would be very interested in knowing if EW actually used the list ops...
I've reworked the MSC (fairly substantially) to a) include full API schemas, and b) clarify exact behaviour. Currently, this MSC describes the Synapse implementation. I wanted to start from there...
I've made a bunch of minor breaking changes, see the changelog at the bottom of hte MSC. I have tried to address most of the open comments in them.