Page MenuHomePhabricator

Echo shouldn't send pings on bot edits
Open, Needs TriagePublic

Description

The issue on T128617 showed that when a bot posts a message, it still triggers notifications on echo like pinging mentioned users. As a bot-bit is used to not have for example talkpage edit notification, and in general don't bother people about the edit (hide from recent changes and such), it makes sense to also suppress the ping notification.

Event Timeline

Akoopal created this task.Mar 2 2016, 10:10 PM
Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptMar 2 2016, 10:10 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
MusikAnimal added a subscriber: MusikAnimal.EditedMar 2 2016, 10:15 PM

Can't the bots just be programmed to use direct links rather than wikilinks? E.g. on enwiki you could use {{no ping|MusikAnimal}} and it would appear the same as [[User:MusikAnimal]] but not actually trigger an echo notification.

The ability for a bot to ping is desirable in some cases. We've had talks about implementing such tasks before, but I don't have any live examples to point to.

Addendum: Actually Cyberbot on enwiki pings users when malformed reports are made at WP:RFPP. example here.

I suppose with such a use case we could set the bot flag to false when making the edit to enforce pinging, but at the consequence of unwanted edits showing up in recent changes and watchlists.

Problem in the specific case is that the same bot does two tasks and that it archives a notification it has done himself. On the first you might want a ping, on the second not, and rewriting a message you archive is also not nice.

For your example, I think if a message is important enough it should trigger notification, it is also important enough to show up on watchlists and recent changes.

Problem in the specific case is that the same bot does two tasks and that it archives a notification it has done himself. On the first you might want a ping, on the second not, and rewriting a message you archive is also not nice.

You could:

  1. Not use the blacklist.
  2. Use noping for the notification to the user talk page. They would still be notified since it's a user talk edit.

When it's archived, the noping would still be in effect.

The first ping is to the nominator who has done the nomination, not the author of the article. It is debatable if that ping is wanted, but that should be discussed on the other ticket. I opened this ticket for the general discussion where I expected a bot-bit to disable notifications.

The first ping is to the nominator who has done the nomination, not the author of the article. It is debatable if that ping is wanted, but that should be discussed on the other ticket. I opened this ticket for the general discussion where I expected a bot-bit to disable notifications.

I think that if a bot marks their edit as minor, then they will not trigger the user-talk-edit notification. (This is based purely on archivebot actions not notifying me on Enwiki. I don't know how that works technically, or whether it would also suppress mention notifications.)

As for changing the default, I not sure if it would be good to prevent all bots from making mention notifications. I'll have to look/ask around to determine whether it is purposefully done anywhere.

Having the edits only suppressed on minor edits would be a solution. The bot that triggered this is also an archiving bot, who is also doing minor edits.

Restricted Application added a project: Growth-Team. · View Herald TranscriptSep 27 2018, 12:16 PM
APerson renamed this task from Echo shouldn't send pings on bot-edits. to Echo shouldn't send pings on bot edits.Sep 28 2018, 10:34 PM

In general, it's important for bots to be able to ping editors. On ENWP, I plan to have a bot ping users from a centralized talk page to reduce spam.