MSC2228 support should be reflected in `/_matrix/client/r0/capabilities`

[EdGeraghty]

Description:

Hey, I'm trying to implement a client-side implementation of synapse's limited MSC2228 support.

I feel that homeserver support for this functionality should be exposed under /_matrix/client/r0/capabilities (or at least somewhere) because the last thing I want to do in my implementation is completely mislead its users.

[anoadragon453]

Adding to to-discuss in order to figure out what the future of this feature looks like in Synapse.

[EdGeraghty]

Adding to to-discuss in order to figure out what the future of this feature looks like in Synapse.

Is there anything I can watch for the conversation? Just matrix-org/matrix-spec-proposals#2228?

[anoadragon453]

@EdGeraghty Issues that are added to the To-Discuss column of the board are discussed synchronously on a weekly-basis (team availability withstanding). We'll put the conclusion of that discussion here 🙂

[richvdh]

Unfortunately we wouldn't be happy to see this land in Synapse's mainline as things currently stand.

Exposing unstable features as a stop-gap to facilitate beta testing is one thing; however, as far as I'm aware there is no work currently being done to complete MSC2228, nor Synapse's implementation of it. Looking again at MSC2228, there's still a lot of unanswered questions - to the extent that if I were trying to write an implementation, I really wouldn't know where to begin; and I have no real idea how it relates to what was implemented in #6409. Indeed, as things currently stand we're considering reverting #6409 since it's clearly not ready for use.

If you or anyone else is interested in picking up MSC2228 and turning it into a finished proposal, that accurately reflects the implementation, then we'd be delighted. But without such a commitment, sorry, we can't support adding it to /capabilities (or /versions).