Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/218

Not really sure if there is much that can be done, you can't take back a notification once it's been sent...

You could suppress notifications if the transcluded page is over a certain number of bytes, or contains more than a certain number of usernames. (I think that last one might be done already?) Getting the cut-off point right would be hard, though.

I for one would prefer transclusion not to cause notifications at all, but suspect that someone may well come up with a valid explanation of why that would be throwing the baby out with the bathwater.

(In reply to Scott Martin from comment #4)

I for one would prefer transclusion not to cause notifications at all, but
suspect that someone may well come up with a valid explanation of why that
would be throwing the baby out with the bathwater.

If we did that, things like {{ping}} would stop working.

See, I knew there would be a good reason. :)

There's just something about how it currently works that doesn't sit well with me - it's either ping everyone or don't substitute at all.

The mention notification threshold was reduced from 300 to 100 in bug 48882. Could we simply lower the limit even further, to something like 10/20/30? (Limits of 10 and 20 were suggested in 48882).

The limit was lowered from 100 to 20, in https://gerrit.wikimedia.org/r/#/c/159804/

A few of the devs are discussing overhauling the Echo Mention system to not require a signature, but no decisions/directions yet, afaik.

Nope. My mistake. That fix was Flow-specific. I've filed https://trello.com/c/cRjNZzdF/ to do the same in Echo. Sorry :/

Change 159800 had a related patch set uploaded by EBernhardson:
Limit Echo mentions to 20 users

https://gerrit.wikimedia.org/r/159800

Change 159800 merged by jenkins-bot:
Limit Echo mentions to 20 users

https://gerrit.wikimedia.org/r/159800

All patches mentioned in this report were merged - is there more work left to do here (if yes: please reset the bug report status to NEW or ASSIGNED), or can you close this ticket as RESOLVED FIXED?