element-hq / element-hq/synapse
Implement MSC4023: Thread ID for 2nd order-relation in Synapse
- Dominant language
- Python
- Stars
- 4.6k
- Forks
- 600
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 51
Description
This issue has been migrated from [#15701](https://github.com/matrix-org/synapse/issues/15701).
---
The proposal https://github.com/matrix-org/matrix-spec-proposals/pull/4023 requires an implementation in Synapse.
This issue is part of the ongoing effort to fix [stuck notifications](https://github.com/vector-im/element-web/issues/24392) in Element Web. As mentioned in @neilisfragile's engineering newsletter this week, we had to skip the last Element Web release because [one](https://github.com/matrix-org/matrix-react-sdk/pull/10864) of our client-side fixes has unhidden a larger battery of other issues that we have since been working on.
The biggest remaining issue we've narrowed things down onto this week is https://github.com/vector-im/element-web/issues/25450. We've put in a [client-side fix](https://github.com/matrix-org/matrix-js-sdk/pull/3427) for this but the excess requests to fetch the unknown events have a performance impact. The size of the latter is hard to gauge but in our tests it was as bad as 5x in extreme cases.
After testing on today's nightly, we believe the general experience is good enough to unblock our release but preferably we'd like to limit the time window where performance is negatively impacted by leveraging server-side support through [MSC4023](https://github.com/matrix-org/matrix-spec-proposals/pull/4023).
Contributor guide
Assessment
This issue has not been assessed yet.