You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 25, 2024. It is now read-only.
In order to reliably update the list of threads in a room and their contents, your homeserver needs to support threads via MSC3440. If your home server runs Synapse, this is available in version 1.55 and above. You can ask your homeserver administrator to upgrade your server to ensure that threads are supported.
If your homeserver doesn't support threads, you will still be able to read and contribute to threads, but the feature might be unreliable - you might not see all threads in a room, and some messages might be missing, especially older messages. For that reason, we strongly recommend to upgrade your homeserver.
But dendrite still does not (fully) support Threads via MSC3440 (and thread support via MSC2836 appears to be obsolete). I actually tried element-web-v1.11.51 with dendrite-0.13.4 and it is quite a mess when you use Threads, especially when users from synapse homeservers join in.
There are a lot of (Enterprise) features that I don't miss on my small (family) dendrite homeserver and my understanding is/was that dendrite (especially after ditching polylith) is especially targeted for this scenario. But I cannot even disable Threads in current element clients (or let dendrite/nginx tell the clients to please not use Threads, e. g. via .well-known/matrix/client) which pretty much means that matrix.org / element.io are pushing towards one and only one combination of server and client which is synapse + element.
... and I thought that was excatly not what was supposed to happen.