Problem: Getting untagged from an active discussion

[aschrijver]

Please state the bug, support or feature request in terms of a problem to be solved.

It often happens that a discussion gets very active, heated, or lasts very long. On all replies the previously tagged people are copied automatically. If you no longer want to receive notifications the only way to do so is to toot and politely ask "Please, untag me". This however is often forgotten if the thread continues, or if a new reply is given to a toot that mentions your handle.

(Optional) Proposed solution:

There's multiple possible solutions..

1. Locally suppress notifications for just that particular thread. Relatively easy to implement since no federation msgs need to be sent. The issues is that for others you still appear to be part of the discussion and informed. They may direct their reply directly to you, and perceive your unresponsiveness as rude.

2. An 'untag me' action in the UI triggers sending of federated msg with some property that either a) leads to your handle be omitted from replies on clients that support this, or b) defaults to a "Please untag me" regular toot in clients that do not have this support yet.

---

Creating this issue after it popped up on fedi in a thread with @nicksellen where I forgot to untag: https://mastodon.social/@humanetech/108396073863288911

[weex]

I've had this experience as well and agree that more control over notifications on threads would be nice. On the solution side I like 1 more and wonder if the code has a single object that can be muted or if it's a test that'd need to be applied for any notification.

[aschrijver]

Adding link to a fedi discussion of this feature, but relating to Bonfire project. Interesting aspects discussed..

https://mastodon.social/@humanetech/108516565708310158

@sebilasse found this in AP repo: https://github.com/w3c/activitypub/issues/319

[sebilasse]

@weex We iterated through the issue in the January meeting. In the meeting all the projects talk about how to do it together because it comes all down to the state for replies. Following what Benjamin said in above issue, we can either send capabilities per person in the audience or we can manage a Collection with policies per thread. This is described in https://gist.github.com/sebilasse/8ef2c615399ce9799ca9cf8a0fefa1ba But the permissions are still not done cause another person is asking to remove something from a Collection. Which means theoretically the Collection is either owned by the audience Group or we need to specify an Action to untag. Especially re. this project inviting to come to the monthly meeting cause in federated worlds it does not make sense to specify own things. In this regard peertube, pixelfed, mobilizon, zot and bonfire handle it all differently except mobilizon has a pt. fallback and redaktor has mobilizon and pt. fallbacks. But it would be super desirable to specify a generic mechanism which anyone can use. Not only for short message things. Also for Q&A, Events, Books, Journalism, Projects and all the nice things in the fediverse. The same goes for querying where we also want to talk about in the next meeting … https://socialhub.activitypub.rocks/t/developers-meeting-7-a-standard-way-to-query-in-activitypub/2488

[aschrijver]

@Rysiek tooted something very similar. A request for "Mute Conversation" with the addition of "starting from this toot" or "mute replies to this toot":

"Mute conversation" is a great thing, but I would love a "mute conversation starting from this toot" or "mute replies to this toot" (same thing) too.

There are long-winded conversations I find super useful, but they often have a branch or two that I could really do without.

#Fediverse #FeatureRequest

[nicksellen]

When I originally complained about this issue on mastodon, I wasn't aware of the "mute conversation" feature that already existed. Which is the one Rysiek is talking about there.

It's a bit limited though:

• it's only available if you've posted in a given thread (as the option is only on the post menu for your own posts)
• I think it only stops notifications, but your timeline would still be clogged up (I didn't try it, but that's my recollection from reading somewhere, don't take my word for it)
• ... plus the point Rysiek made (which I think is so if there is a multi-headed-hydra thread, you can cut off just selected heads...)