Travis Ralston
Travis Ralston
Like polls and voice messages before it, this MSC doesn't feel as though it can make meaningful progress until extensible events is through its own FCP. @mscbot concern Blocked on...
This is blocked on extensible events, and I don't think it can make meaningful progress without that. Removing from the SCT's "look at this now" pile: @mscbot fcp cancel
There's lots of green: @mscbot fcp merge
honestly if the freenode bridge hits `/sync`, we've done something terribly wrong. Can we stop optimizing the proposal for a bridge that won't use sync?
There shouldn't be anything in the MSC/spec that says things should(n't) use a particular endpoint. I don't think it's realistic for us to solve operational problems in the spec. From...
One use case would be go-neb: it doesn't use appservice transactions but fits really nicely for reserving a namespace of users. Because the spec says that the `sender_localpart` is required...
so we've discussed this as a spec core team and have come to the conclusion that Matrix isn't quite ready for this change just yet. Appservices tend to have extremely...
@mscbot fcp postpone
@Zocker1999NET when you get the chance, please [Sign Off](https://github.com/matrix-org/matrix-spec-proposals/blob/main/CONTRIBUTING.md#sign-off) on your changes.
tentatively pushing this into the queue for a room version given initial steering of third party invite handling. Edit: this has now been pushed to MSC2212, so removing label.