Wikipedia talk:Huggle/Config.yaml

Latest comment: 11 months ago by Josve05a in topic Whitelist requirements

Improvement LIVE - here are the new features: edit

Any further suggestions should probably go to Wikipedia:Huggle/Feedback instead! ~ ToBeFree (talk) 22:45, 13 May 2018 (UTC)Reply

Overview, Features edit

There has been a renovation of the warning-types and welcome-messages menu. Features:

  • Alphabetical sorting of the warnings / revert reasons
  • Renaming the warning descriptions to look good in an alphabetical list:
id new name revert summary old identifier
00000 Attack: Personal attack against editor personal attack toward another user attack
00100 Disruptive editing nonconstructive edits disruptive
00200 Errors: Factual errors factual errors error
00300 Joke edit (improper humor in articles) using improper humor in articles (WP:NPOV, WP:V) joke
00400 Manual of style not adhering to manual of style mos
00500 NPOV: Biased content not adhering to neutral point of view npov
00600 NPOV: Fringe theories NPOV: WP:FRINGE fringe
00700 NPOV: Genre change change of genre genre
00800 Removal of content: Blanking whole page unexplained page blanking blank
00900 Removal of content: Unexplained deletion unexplained content removal delete
01000 Removal of template: AFD unexplained AFD template removal afd
01100 Removal of template: Speedy deletion unexplained speedy deletion template removal speedy
01200 Spam: Advertising / Promotion using Wikipedia for advertising/promotion advert
01300 Spam: External links addition of unnecessary/inappropriate external links spam
01400 Talk page used as forum/chat using talk page as forum chat
01500 Talking in article please use the talk page (WP:TPHELP) or be bold and fix the problem talkinarticle
01600 Test: Editing tests editing tests test
01700 Test: Editing tests, self-reverted incompletely self-reverted editing tests selfrevert
01800 Unsourced: Biography of living person addition of unsourced content to a biographical article bio
01900 Unsourced: No verifiable reliable source not providing a reliable source (WP:CITE, WP:RS) unsor
02000 Unsourced: Original research / incorrect synthesis original research nor
02100 Vandalism nonconstructive edits warning
  • Adding support for new warning sequences:
  • "Promotion / Advertising" as opposed to the old "SPAM" button which only refers to external links:
  • Improving the automatical edit summaries to match the guidelines and actual usage:

Contentious material about living persons (or, in some cases, recently deceased) that is unsourced or poorly sourced—whether the material is negative, positive, neutral, or just questionable—should be removed immediately and without waiting for discussion.[1] Users who persistently or egregiously violate this policy may be blocked from editing.

(emphasis changed by me!)
  • 'Welcome: standard': '{{subst:Welcome}} ~~~~'
  • 'Welcome: short': '{{subst:Welcome-short}} ~~~~'
  • 'Welcome: personal (cookies)': '{{subst:Welcome-personal}} ~~~~'
  • 'Welcome: graphical': '{{subst:Welcome-graphical}}'
  • 'Welcome: with menu': '{{subst:WelcomeMenu}}'
  • 'Welcome: screen': '{{subst:Welcome-screen}}'
  • 'Welcome: Welcome to Wikipedia': '{{subst:Welcome to Wikipedia}}'
  • 'Welcome: Unregistered': '{{subst:Welcome-anon}} ~~~~'
  • 'Welcome: Unregistered: constructive': '{{subst:Welcome-anon-constructive}}'
  • 'Welcome: Unregistered: unconstructive': '{{subst:Welcome-anon-unconstructive}}'
  • 'Welcome: Problematic: list of rules': '{{subst:Welcomelaws}} ~~~~'
  • 'Welcome: Problematic: first article': '{{subst:First article}}'
  • 'Welcome: Problematic: test edits': '{{subst:Welcometest}} ~~~~'
  • 'Welcome: Problematic: neutral point of view': '{{subst:Welcomenpov}} ~~~~'
  • 'Welcome: Problematic: conflict of interest': '{{subst:Welcome-COI}} ~~~~'
  • 'Welcome: Problematic: images / image links': '{{subst:Welcome-image}}'
  • Shared IP advice is now automatically being added to IP talk pages. (Thanks to OhKayeSierra for the suggestion!)

Complete list of changes edit

  Special:Diff/841072943/prev


Known problems edit

  • Keyboard shortcuts assigned to current warnings will be cleared on update. To minimize negative impact and annoyance, this means:
  • The config change will be made in the moment when a new Huggle release comes out, to emphasize the connection between config and source code update.
  • The configuration update needs to be well-tested, and there should be no need for a quick bugfix which would clear the shortcuts once again.

We thank YOU! for testing the beta configuration! edit

 
Thank you!

We need YOU! to test the beta configuration

(removed obsolete beta testing instructions) ~ ToBeFree (talk) 22:21, 13 May 2018 (UTC)Reply

Feedback / Feature requests edit

Please add your ideas and comments here. If you like the proposed changes, indicating your support here would also be helpful. Thank you.   ~ ToBeFree (talk) 04:10, 12 April 2018 (UTC)Reply

Any further suggestions should probably go to Wikipedia:Huggle/Feedback instead! ~ ToBeFree (talk) 22:45, 13 May 2018 (UTC)Reply

Looking forward to testing out the new config. Not sure if this would be the appropriate place to suggest this, but would it be possible to integrate {{subst:Shared IP advice}} for warnings to anonymous users, similar to what Twinkle already does? OhKayeSierra (talk) 09:02, 28 April 2018 (UTC)Reply
Yay, first feedback :D -- Interestingly, the old Huggle 2 config has the following lines:
  • shared-ip-template-tag:<!-- Template:Shared IP advice -->
  • shared-ip-template:{{subst:Shared IP advice}}
I wonder what happens when I copy them to the beta config! ~ ToBeFree (talk) 02:54, 5 May 2018 (UTC)Reply
@OhKayeSierra: Haha, it works! https://en.wikipedia.org/w/index.php?title=User_talk:178.202.191.79&oldid=839696657 -- this was easier than expected! Thank you very much for the suggestion! ~ ToBeFree (talk) 02:59, 5 May 2018 (UTC)Reply
  • This is working just fine! - DVdm (talk) 06:51, 9 May 2018 (UTC)Reply
Hey   I saw you two trying it and am very happy to see your edits! This is awesome; I am unsure how long we should keep testing it before letting the changes go live. I will definitely wait for at least one administrator to try it out, but I am afraid that those who already know about the beta test are not willing to lose their keyboard shortcuts for this experiment.   ~ ToBeFree (talk) 19:14, 9 May 2018 (UTC)Reply
Hm, I don't use keyboard shortcuts, so even if this never goes live, I'll just keep using this beta. Nice! - DVdm (talk) 19:38, 9 May 2018 (UTC)Reply
The new configuration has been released. Testing is nice, but there was no reason to keep the test running forever.   ~ ToBeFree (talk) 22:26, 13 May 2018 (UTC)Reply

Any further suggestions should probably go to Wikipedia:Huggle/Feedback instead! ~ ToBeFree (talk) 22:45, 13 May 2018 (UTC)Reply

References edit

  1. ^ Jimmy Wales. WikiEN-l: "Zero information is preferred to misleading or false information", May 16, 2006, and May 19, 2006; Jimmy Wales. Keynote speech, Wikimania, August 2006.

Protected edit request on 6 March 2021 edit

ToBeFree, At: 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', can a period be added at the end for proper grammar? Steve M (talk) 15:34, 6 March 2021 (UTC)Reply

Thanks,   Done ~ ToBeFree (talk) 21:12, 8 March 2021 (UTC)Reply

A way to increase the effectiveness of Huggle edit

Will it ever be possible to make Huggle draw feed from edit filter logs that were not disallowed? This will speed up the cleaning of vandalism and would be a huge step up for Huggle. Thoughts on whether this is a good idea and how this can be implemented? aeschylus (talk) 17:32, 1 June 2021 (UTC)Reply

Hello, this is probably technically doable, but can you elaborate on how should that be done? Where is such a log available (in machine friendly format)? Petrb (talk) 19:23, 9 June 2021 (UTC)Reply
There is Special:AbuseLog, but it shows all edit filter trips, including disallows. Jackattack1597 (talk) 13:38, 15 June 2021 (UTC)Reply
@Jackattack1597, there is an "impact" parameter that you can set to "saved changes only" if you want to filter out disallows. aeschylus (talk) 02:23, 24 June 2021 (UTC)Reply
@Petrb, what is a "machine-friendly format"? aeschylus (talk) 02:17, 24 June 2021 (UTC)Reply
Sorry for late reply, I am too busy these days, I think that such edits should be tagged, are they not? Huggle can already adjust score based on edit tags, see config page:
# This is a list of all edit tags that affect the score somehow, available since Huggle 3.1.17
score-tags:
    bad external: 100
    Huggle: -2000
    Twinkle: -2000
    Possible vandalism: 800
As you can see there are already tags "Possible vandalism" which should be added to all edits that are triggering abuse filter rules but are passed. Petrb (talk) 10:35, 29 June 2021 (UTC)Reply
@Petrb, for start, there is the tag "possible vandalism" with the lowercase p in the beginning, which is a different anti-vandal filter. I made a list of useful tags
  • possible vandalism
  • possible conflict of interest
  • RedWarn (make it -2000)
  • SWViewer [1.4] (make it -2000)
  • reverting anti-vandal bot
  • shouting
aeschylus (talk) 20:20, 26 July 2021 (UTC)Reply

Protected edit request on 26 July 2021 edit

Add the tags to the tag list to improve Huggle. See

  • possible vandalism (lowercase "p" is a different tag)
  • possible conflict of interest
  • RedWarn (make it -2000)
  • SWViewer [1.4] (make it -2000)
  • reverting anti-vandal bot
  • shouting aeschylus (talk) 21:08, 26 July 2021 (UTC)Reply
@Aeschylus: Done Petrb (talk) 18:15, 17 August 2021 (UTC)Reply

Whitelist requirements edit

@Petrb: Could we see if we can increase what is needed to be included on the whitelist, from -2000 to perhaps -3000? Right now HG added Yila30127 and Martiansalad. Neither should have been added in my opinion. Or perhaps add a requirement that the account needs to be at least a couple of days old. Jonatan Svensson Glad (talk) 01:54, 25 May 2023 (UTC)Reply