-
Notifications
You must be signed in to change notification settings - Fork 59
Description
Currently, Jumble do not provide a way to block or mute an entire discussion thread. This has become a significant usability issue due to the increasing prevalence of so-called “hell threads” — threads where users tag large numbers of followers and followees.
After the creation of https://hellthread.shakespeare.wtf/, this behavior has become more frequent. As a result, users receive dozens or even hundreds of notifications whenever there are replies in these threads, even if they have no interest in participating.
Why existing filters do not help
In most cases, the participants in these threads are people the user actually follows and legitimate accounts with good reputation. Because of that:
- Web-of-Trust (WoT) filtering does not apply
- Score-based or reputation-based filtering does not apply
- Muting individual users is not a viable solution, as the issue is not user-specific but thread-specific
This makes thread-level control essential.
Proposed feature
Add support for blocking or muting an entire thread, based on the root event (or equivalent thread identifier), with the following expected behavior:
- Muting a thread suppresses all notifications related to replies in that thread
- The mute applies regardless of which users reply, including followed accounts
- The action should be reversible (unmute)
- The mute state should persist across sessions
Why this matters
- Hell threads are not spam in the traditional sense, but they create notification floods
- Without thread-level muting, users are forced to endure unwanted activity or unfollow legitimate accounts
- Thread-level blocking is a standard feature in other discussion platforms and is necessary for sustainable conversation scaling
Additional notes
- This can likely be implemented entirely client-side by tracking the root event ID
- UX could mirror “mute conversation” features found in email clients and mainstream social networks
Expected outcome
Improved usability, reduced notification overload, and better control over user attention without weakening trust models or social connections