Page MenuHomePhabricator
Create Task
Maniphest T234082

Different definitions of "recently warned" for IP editors and registered editors are required
Open, MediumPublicBUG REPORT
Actions

Description

Seen on enwiki: Huggle automatically reports users to WP:AIV. This only happens if the user has recently received a final warning, but the definition of "recent" needs to be differentiated.

  • Registered users who have received a "final warning" for repeated vandalism can probably even be reported if they resume their activity months later.
  • IP editors may not be the same person and usually need to have received a very recent final warning (say, not older than 12 hours, to be on the safe side).

Automatic reports seem to have been implemented in a "report if in doubt" way. I'd argue that this is possibly the wrong philosophy, and that Huggle should restrict automatic reporting to clear cases, which WP:AIV is for.

Related Objects
Search...

Event Timeline

ToBeFree created this task.Sep 27 2019, 6:10 PM
DannyS712 removed a project: Tracking-Neverending.Sep 27 2019, 6:13 PM
ToBeFree added a comment.Sep 27 2019, 6:14 PM

Is the definition of "recent" currently hardcoded, or an undocumented configuration option like "report-auto-summary" which I had to manually look up in src/huggle_core/projectconfiguration.cpp?

ToBeFree added a comment.Sep 27 2019, 6:27 PM

Example report that should perhaps ideally not have happened:

This talk page state https://en.wikipedia.org/wiki/Special:PermanentLink/916174648
resulted in this report https://en.wikipedia.org/wiki/Special:Diff/918240249

ToBeFree updated the task description. (Show Details)Sep 27 2019, 6:48 PM
Amorymeltzer subscribed.Sep 28 2019, 10:25 AM

Is the definition of "recent" currently hardcoded, or an undocumented configuration option...

Without commenting on (or thinking about) anything else here, I believe the setting is TemplateAge, which defaults to 30 days (see https://github.com/huggle/huggle3-qt-lx/blob/master/src/huggle_core/configuration.cpp#L187 and https://github.com/huggle/huggle3-qt-lx/blob/master/src/huggle_core/projectconfiguration.hpp#L172) but template-age can be set otherwise (see https://en.wikipedia.org/wiki/Wikipedia:Huggle/Config#Warning). Not sure what CBNG does.

ToBeFree added a comment.Oct 1 2019, 5:03 AM

Ah! This default may have caused a change of behavior when Huggle moved to the .yaml configuration. That would explain it.

ToBeFree added a comment.Oct 1 2019, 5:57 AM

Makeshift fix implemented: Prevent bad reports for IP editors: https://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config.yaml&diff=918980316&oldid=918243346

The point of this task is now to provide a way to increase the value for registered users, perhaps back to 30 days.

Petrb triaged this task as Medium priority.Mar 27 2020, 9:20 PM
Petrb added a comment.EditedMar 27 2020, 9:23 PM

Sorry to be late to the party - regarding "undocumented options", we keep documentation for options on place that not every one is probably aware of, here: https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml and even the options you claim to be undocumented, are in fact there ;)

# Text appended to automatic AIV reports
#report-auto-summary: 'This user was automatically reported by Huggle due to reverted vandalism after a final warning. Please verify their contributions carefully, it may be a false positive'

# Define how old templates are considered valid in days, older templates are ignored
# By default templates older than 30 days are ignored
# template-age: -30

It's all documented ;)

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL · Credits