| Lea_WMDE | |
| Sep 2 2016, 4:25 PM |
| F7862829: Screen Shot 2017-05-01 at 12.31.03 PM.png | |
| May 1 2017, 7:48 PM |
| F7798849: Screen Shot 2017-04-27 at 2.59.31 PM.png | |
| Apr 27 2017, 11:06 PM |
Since Flow mentions users explicitly, there is no need to have the success mention feature for it (see T139962).
However, it is not possible with Flow to realise when you hit the flow mention limit. In contrast to wikitext mentions, flow sends out the first 100 mentions and then stops.
Therefore, please
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T125653 Create new types of notifications | |||
| Resolved | thiemowmde | T139962 When saving, be informed about mentions you sent (#9) | |||
| Resolved | Lea_WMDE | T135717 Add mention failure notifications | |||
| Open | None | T108400 Flow mentions (tracking) | |||
| Resolved | SBisson | T144614 Inform Flow users when they hit the flow mention limit |
Change 308555 had a related patch set uploaded (by Addshore):
Add mention failure notifications to Flow
The summary of differences for mention notifications between wikitext and Flow pages (for testing after code review)
On wikitext pages
On Flow pages
Change 349251 had a related patch set uploaded (by Sbisson):
[mediawiki/extensions/Echo@master] MentionStatus: prefer failure-type
Change 349251 merged by jenkins-bot:
[mediawiki/extensions/Echo@master] MentionStatus: prefer failure-type
Change 308555 merged by jenkins-bot:
[mediawiki/extensions/Flow@master] Add mention failure notifications to Flow
Tested locally (could not make it work in betalabs):
(1) The following spec is not implemented:
The message should reflect that the first 100 mentions have been sent out, only the following ones have not
The notification does not list which ones were not sent.
(2) Strange counting issue: if "FlowMaxMentionCount" is set to 12, 'flow-mention-failure-too-many' notification will come if the number of mention is between 13 and 18. Above that (I tried 19, 20, 25, and 65) - the failure notification does not come.
re (1)
I'll rework the message. @jmatazzoni any suggestion about how to phrase the notification header? It is currently using the Echo message, it goes like this: Your mentions were not sent because they exceeded the limit of 100. It sort of implies that no mentions were sent but the reality is that your first 100 mentions were successfully sent but the other ones, say from 101 to 115, were not sent.
re (2)
It turns out this change from 2y8m ago cancels all mention attempts of more than 20 users thinking it must be spam.
$wgFlowMaxMentionCount, with its default value of 100, seem to have been introduced by this change about 3y7m ago.
I see no reason to keep the hard limit of 20. $wgFlowMaxMentionCount exist specifically so it can be tweaked to the right balance between functionality and protection.
But I have to agree that 100 is a very high value. I can't really imagine writing a Flow post and explicitly pinging 100 users by name because they are relevant to the conversation. Echo has a limit of 50. We could look in the db for mention-failure-too-many to see how often and in which context that limit is reached.
Change 350877 had a related patch set uploaded (by Sbisson; owner: Sbisson):
[mediawiki/extensions/Flow@master] Remove arbitrary limit of 20 mentions
How about this for language:
You tried to mention more than 100 users. All mentions above that limit were not sent.
That works for me. Do you think we should change it in Echo so it is used for this purpose in both Flow and Echo and leave the Echo one as-is and use this new version for Flow only?
It would be good to make the messaging and functionality consistent across these systems. If it's not too much effort...
It's actually less effort. I'll change it in Echo and let Flow use it as the default.
Change 350886 had a related patch set uploaded (by Sbisson; owner: Sbisson):
[mediawiki/extensions/Flow@master] Set max mention count to 50
Change 350887 had a related patch set uploaded (by Sbisson; owner: Sbisson):
[mediawiki/extensions/Echo@master] Rephrase notification-header-mention-failure-too-many
Change 350877 merged by jenkins-bot:
[mediawiki/extensions/Flow@master] Remove arbitrary limit of 20 mentions
Change 350886 merged by jenkins-bot:
[mediawiki/extensions/Flow@master] Set max mention count to 50
Change 350887 merged by jenkins-bot:
[mediawiki/extensions/Echo@master] Rephrase notification-header-mention-failure-too-many
Checked in betalabs
See https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Pinging_over_50
The new wording "All mentions above that limit were not sent" is still presented on the English wikipedia for Echo notifications, despite the fact that Echo sends none of the messages if the limit is exceeded. Different messages should be shown for Flow and Echo since the behavior is different ("Your mentions were not sent because they exceeded the limit of 50." for Echo, "You tried to mention more than 50 users. All mentions above that limit were not sent" for Flow).
I re-checked - Echo notifications (mention-failure-too-many) are not sent at all when the limit is reached (in betalabs the limit is above 100). Thus, the message "All mentions above that limit were not sent" is incorrect and that should be fixed.
The scope of this ticket was about flow-mention-failure-too-man notification functionality which was done.
The separate phab task - T199391: 'mention-failure-too-many' notification incorrectly says "All mentions above that limit were not sent" - was filed to address Echo notification for above the limit mention count.