-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Experiment with putting threads back behind a beta toggle #25676
Comments
Is this available in the latest Nightly? I couldn't find it in settings :) |
matrix-org/matrix-react-sdk#11151 is a draft PR → not available on nightly . But to test it you can use the PR deployment. |
@thibaultamartin had you noticed any other issues not already listed above on the deployment yesterday? |
A regular issue I face with threads and stuck notifications is that restarting Element (or rather: updating my Nightly) "re-sticks" notifications that were unstuck. For example the main channel I use has no notifications left (usually after being cleared with "Mark as unread"), and when I update it's back to ~20 unread notifications |
Do you mean you see that on normal / nightly Element? Or on the deployment with threads turned off? |
Oh my apologies I meant regular Nightly, I didn't have the time to try the experimental deployment yet! I will give it a go today |
Re-tested on the updated deployment today and, unfortunately, the two issues listed above still persist. |
Thank you for considering making the Threads feature optional (via a toggle). My intuition is that a lot of problems related to stuck notifications are caused by Threads. Is the current understanding of the dev team that disabling Threads doesn't / wouldn't help with stuck notifications? |
@johanricher last time we discussed it we concluded that a significant portion of stuck notification issues relate to threads, but not certain that turning them off would undo the damage and also were unable to get buy-in from the Product/Management teams to disable threads. |
Threads are one of the main drivers of #24392. Purely as an experiment, it would be helpful to compare the notification experience on Element Web with threads enabled to a state where threads are turned off and use the reply fallback when rendering.
This has been prototyped in matrix-org/matrix-react-sdk#11151.
Issues found on the deployment are tracked below.
Issues
The text was updated successfully, but these errors were encountered: