A mere reply... to a comment you made. Isn't it reasonable to expect that the commenter wants you to know?

In the line above, change "you" by just any Phabricator user, because users like Nemo_bis are not representative. :)

In T76993#824543, @Qgil wrote:

A mere reply... to a comment you made. Isn't it reasonable to expect that the commenter wants you to know?

Not when the quoted user has refused to follow the task.

In the line above, change "you" by just any Phabricator user, because users like Nemo_bis are not representative. :)

Most users don't follow notifications and/or don't remove self from subscribers, so I think the user story sufficiently restricted the target audience. :)

Should we merge this task and T78468 into a request not to CC users automatically when they are "just" quoted?

Should we merge this task and T78468 into a request not to CC users automatically when they are "just" quoted?

That would also work. Whatever is easiest to get implemented.

I don't myself have a problem with being re-added to the CC if I'm

@mention'd

in a late Comment (I would rather know that I've been quoted so I can re-enter the conversation to clarify if necessary). But If I've intentionally removed my

@handle

from the Description (if it was there in the first place) and I've un-CC'd myself, I don't want to be bothered with an email again until a new Comment is added where my

@handle``
 is explicitly included (or if someone re-adds it to the Description).

I don't myself have a problem with being re-added to the CC if I'm

@mention'd

in a later post. But If I've intentionally removed my

@handle

from the Description (if it was there in the first place) and I've un-CC'd myself, I don't want to be bothered again until a new Comment is added (or the Description is updated) where my

@handle

is explicitly included.

Over at https://secure.phabricator.com/T11471#190152, @epriestley writes:

If you don't like the @mention-implies-CC behavior, you can disable it by applying this patch to your install:

diff --git a/src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php b/src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php
index 1a3dd1c..16c08cd 100644
--- a/src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php
+++ b/src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php
@@ -1367,6 +1367,9 @@ abstract class PhabricatorApplicationTransactionEditor
     array $xactions,
     array $changes) {
 
+    // Do not subscribe @mention'd users.
+    return null;
+
     if (!($object instanceof PhabricatorSubscribableInterface)) {
       return null;
     }

We've only seen negative feedback about this behavior from one install, but use it frequently on this install and believe it is a useful feature overall, even if it isn't always perfect. As a general rule, we don't make upstream changes which only benefit one install. But if this feature is unusually disruptive on your install, the cost of maintaining that patch might be smaller than the cost of having the feature.

In T76993#824543, @Qgil wrote:

A mere reply... to a comment you made. Isn't it reasonable to expect that the commenter wants you to know?

No doubt. But if I unsubscribe myself, then it's reasonable to respect my desire NOT to be notified. Even if I'm mentioned.

Ideally there should be a config option: "Don't allow others to re-subscribe me." I've seen that on other systems.