If a user account has the bot right they should not trigger edit summary ping notifications.
Discussion in: T188960: Figure out which bots mention users in summaries, how often, and decide how 'Edit summary pings' should handle bots
If a user account has the bot right they should not trigger edit summary ping notifications.
Discussion in: T188960: Figure out which bots mention users in summaries, how often, and decide how 'Edit summary pings' should handle bots
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T125653 Create new types of notifications | |||
| Resolved | None | T32750 [Epic] Ping/notify user when username used in an edit summary | |||
| Resolved | MaxSem | T189040 Bot accounts should not trigger edit summary pings/mentions |
I think we should take this a step further and disable pings for any edit made via the API -- not just bot edits -- unless it's given the new "allow ping" parameter (T189041). Looking at the Twinkle code alone (which I can fix, if need be), there are going to be a lot of unwanted pings. I think a few of my other scripts are also vulnerable. There must be many more.
The other option is to maybe get our liaisons to post on Village Pumps, etc., advertising that user scripts, gadgets, etc., will be affected by this and may need to be updated. Then perhaps a one-week waiting period before deployment?
This would punch a hole through all our abstractions. Let's take a different look and identify all the problematic and widespread types of edit summaries.
I ran some queries on recent changes, and it looks like most of the Twinkle edits that mention users are speedy deletion requests of the userpage. In this case we need to link to it, since that's the actual page in question, but probably fine that it pings, too? Other examples are warnings about conflict of interest, and reporting to UAA. These all are because the user is doing something semi-bad-faith, so not terrible to ping, but we also are leaving a message on their talk page, and in the case of speedy deletion, tagging the user page and logging it on the patrollers specified log page. So up to three echo notifications!
Overall I don't think we need to worry too much. I'll work on updating Twinkle to minimize the spam. There probably aren't that many other scripts as popular as Twinkle that ping, at least on enwiki.
Quick question, does prefixing with a colon prevent it from pinging? Like [[:User:Foo]]? If not, would that be hard to implement?
Change 416881 had a related patch set uploaded (by MaxSem; owner: MaxSem):
[mediawiki/extensions/Echo@master] Disable pings from summary for bots
Change 416881 merged by jenkins-bot:
[mediawiki/extensions/Echo@master] Disable pings from summary for bots
Change 417330 had a related patch set uploaded (by MaxSem; owner: MaxSem):
[mediawiki/extensions/Echo@wmf/1.31.0-wmf.24] Disable pings from summary for bots
Change 417330 merged by jenkins-bot:
[mediawiki/extensions/Echo@wmf/1.31.0-wmf.24] Disable pings from summary for bots