Jump to content

Wikipedia talk:Huggle/Feedback

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia


 Skip to the bottom 

Home
Home

Feedback
Feedback

Configuration
Configuration

Development
Development

Other pages
Other pages

Requested move 16 June 2022

[edit]
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: page moved. (closed by non-admin page mover) GeoffreyT2000 (talk) 04:18, 24 June 2022 (UTC)[reply]

Wikipedia:Huggle/Feedback → Wikipedia talk:Huggle/Feedback – A lot of templates do not work under the Wikipedia namespace, including {{requested move}} and {{Edit template-protected}} (See [1]). Wikipedia talk seems a more appropriate place. 0xDeadbeef 10:10, 16 June 2022 (UTC)[reply]

  • Support since all of the talk pages of Huggle warnings redirect here, it's impossible to make an edit request without waiting forever. I made one 10 days ago and it hasn't been addressed. interstatefive  20:49, 16 June 2022 (UTC)[reply]
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Nothing in queue

[edit]

Just upgraded to 3.4.13, but even before with 3.4.12, no edits seem to appear in the queue, even with the all edits option. I managed to revert an edit by entering the page in the page input field, but the queue seems dead, with any of the providers XmlRcs, IRC and Wiki. Is something broken, or I have missed something? - DVdm (talk) 15:45, 29 January 2025 (UTC)[reply]

More information:

  1. Using Win 10 pro.
  2. The logfile says: "Wed Jan 29 23:21:02 2025: ERROR: The webserver of enwiki requires that SSL is to be enabled. Please turn SSL on and try again. If you can't enable SSL (option is grayed out) you may need to install OpenSSL libraries to your system."
  3. TLS 1.2 is active
  4. Turned the firewall off, no effect (!)
  5. Turned firewall on again, now the Wiki and IRC providers work. XmlRcs not.
  6. Have set the preferred provider to Wiki in the feed options, but after close and re-open, the provider is IRC. Config file huggle.yaml.js lists preferred-provider: 0, which I manually set to 1, now it stays Wiki.

DVdm (talk) 23:13, 29 January 2025 (UTC)[reply]

I'm having the exact same issue. I came here hoping for a fix.--Mojo Hand (talk) 15:07, 2 February 2025 (UTC)[reply]
The question is: which is the best provider? Wiki and IRC work fine, but is XmlRcs —if it works— better? - DVdm (talk) 15:41, 2 February 2025 (UTC)[reply]
Weird that XmlRcs is the default provider.--Mojo Hand (talk) 16:18, 2 February 2025 (UTC)[reply]
Having this exact same issue. --Patient Zerotalk 00:36, 6 February 2025 (UTC)[reply]
It started working again for me when I changed provider on the system tab from XmlRcs to Wiki, but it seems slower to me.--Mojo Hand (talk) 00:41, 6 February 2025 (UTC)[reply]
Done that as well Mojo Hand, and completely agree that it is now slower...! Patient Zerotalk 01:28, 6 February 2025 (UTC)[reply]

I made improvements to XmlRcs server running on wmfcloud that should make it more resilient to similar outages. Petrb (talk) 17:15, 27 July 2025 (UTC)[reply]

So I can learn more about the architecture, may I ask what kind of improvements you made? Is there a GitHub repo for this server somewhere? –Novem Linguae (talk) 13:52, 28 July 2025 (UTC)[reply]
Yes, there is a github repo here - https://github.com/huggle/XMLRCS the architecture is described here - https://wikitech.wikimedia.org/wiki/XmlRcs the changes I made are major refactoring of es2r daemon (event stream to redis) which is now more resilient to crashes. On top of that there is a new service file for systemd which restarts the service on crash Petrb (talk) 19:50, 4 August 2025 (UTC)[reply]

When will 3.4.14 be released?

[edit]

I've rather given up on Huggle. Are there setting that I can adjust to fix any of these?

  • Report user not not open popup window, either by Icon on tool bar, User->Report user, nor Ctrl+R
  • Before the problem with the popup window issue
    • "check if reported" would not work
    • Huggle would generate a duplicate AIV report for already reported vandals
  • UNAA does not work
  • RFPP: additions are made near the top, not at the bottom per instructions on page.
  • Warnings are often put in the wrong / previous section. If there is a "March 2025" and a "May 2025" (the current month) section, Huggle will put the warning in the March 2025 section.
  • On startup, one must change the provider. It would be nice if the setting was persistent.

I uninstalled and reinstalled Huggle 3.4.12 (accidently). The AIV functions seemed to work OK. The AIV window problem returned after reinstalling 3.4.13
Adakiko (talk) 01:19, 23 May 2025 (UTC)[reply]

I feel you. Huggle really needs a quality-of-life update. —⁠k6ka 🍁 (Talk · Contributions) 01:47, 23 May 2025 (UTC)[reply]
+1. I've noticed I am encountering a few of the issues here, namely that Huggle keeps generating duplicate AIV reports, and putting my warnings under the wrong headers. There is a fix for the provider issue by changing the default one in the settings (see above "Nothing in queue"), but it would be great if it just worked from the get-go. I'm also currently having issues with starting the application in the first place - details of which are on Phabricator if anyone's interested, but it involves the "you logged out" popup... Patient Zerotalk 01:56, 23 May 2025 (UTC)[reply]
I don't see any posts by the Huggle maintainers on this talk page. I'll go ahead and give them a ping: @Petrb. @Addshore. Both have some recent edits to enwiki, and Petrb has some recent commits to the GitHub repo, so that's a good sign. –Novem Linguae (talk) 17:56, 23 May 2025 (UTC)[reply]
+1 Frost 08:20, 9 June 2025 (UTC)[reply]
Hello, I feel you guys, I am not very active these days, addshore is probably in similar situation. We are no longer those young guys with loads of free time :), having a family and a full time job, there is very little time for hobbies like similar open source projects. I do start Huggle from time to time to check if it's at least working to eventually fix some critical issues, and last time I did it was working fine, but I admit these advanced features like AIV / UNAA, RFPP etc. may be broken. They relied on parsing respective pages and adding sections to them using various template black magic and this logic breaks every single time there is a major update to the layout of these pages, which is probably what happened this time too. I will have a look hopefully through the summer. Petrb (talk) 20:48, 23 July 2025 (UTC)[reply]
I fixed the RFPP bugs, but it needs an extra fix in the config page as well, but my privileges to edit it were revoked. So whoever has admin rights: we need to update the rfpp related parts, most notably these two:
rfpp-verify: '.*$title\}\}.*'
rfpp-section: 0
That will fix it. Petrb (talk) 17:12, 27 July 2025 (UTC)[reply]
@Petrb. Can you please provide a wikilink to the page needing editing? Also, in the future, you can post on that page's talk page with the {{Sudo}} template, and this will put your edit request in a queue and get the attention of the correct type of admin. –Novem Linguae (talk) 13:49, 28 July 2025 (UTC)[reply]
It's Wikipedia:Huggle/Config.yaml Petrb (talk) 19:53, 4 August 2025 (UTC)[reply]
3.4.14 was just released, it fixes most of the issues mentioned on this feedback page. Petrb (talk) 22:08, 12 November 2025 (UTC)[reply]
Thank you for all your hard work @Petrb! Cloned & compiled and will poke around more later. Nubzor [T][C] 23:59, 12 November 2025 (UTC)[reply]
Wow! Thank you @Petrb! I wasn't expecting this. Much appreciated. Adakiko (talk) 11:46, 13 November 2025 (UTC)[reply]

Compatibility with temp accounts

[edit]

As I wrote in WP:VPT#Compatibility of gadgets, scripts, bots, and edit filters with temp accounts, I wanted to ask you to check if AntiVandal is compatible. Here's our documentation for developers; in particular, see the section How should I update my code?. Thank you! SGrabarczuk (WMF) (talk) 08:53, 1 September 2025 (UTC)[reply]

Hello support for this feature is already integrated and will be available in next release. Petrb (talk) 18:34, 11 November 2025 (UTC)[reply]
@Petrb Quick question for you--Is there a setting to disable the "Shared IP" notice that gets automatically added to warnings? Or is that something perhaps that can be removed in a future release due to the move to temp accounts? Like here Special:Diff/1321843589. Again, thank you for all your work on this project still. Nubzor [T][C] 00:16, 13 November 2025 (UTC)[reply]
Yes, this is taken from the configuration that Huggle uses, it's just necessary to remove last 2 lines in the config file:
shared-ip-template-tag: '<!-- Template:Shared IP advice -->'
shared-ip-template: '{{subst:Shared IP advice}}'
I already requested template editor permissions so that I can fix this kind of stuff myself - https://en.wikipedia.org/w/index.php?title=Wikipedia:Requests_for_permissions/Template_editor&oldid=1321764358 Petrb (talk) 08:54, 13 November 2025 (UTC)[reply]
Given that temp accounts are technically IP accounts and it's no longer possible to use true IP account I think that this entire template could be also just modified accordingly, but not showing it at all is probably also fine. Petrb (talk) 08:55, 13 November 2025 (UTC)[reply]
@Petrb Thank you for already working to fix it. Looks like they did just grant you those permissions, so congrats also! :) Nubzor [T][C] 15:48, 15 November 2025 (UTC)[reply]
Great, now I can finally edit the page I created again :) I will fix it right now. Petrb (talk) 23:03, 15 November 2025 (UTC)[reply]

Misplaced warnings

[edit]

I am more confident than not I am using this talk page correctly to describe a problem I've recently noticed on user talk pages today.

On one of the user talk pages I've just warned someone about misbehavior of an article, I then noticed a misplaced Huggle message above an earlier edit ClueBotNG made. A few examples: User talk:209.137.220.113, User talk:137.52.208.53 and User talk:Dorathedestroyer. Seems like the tool places the warnings correctly if older warnings were made by other users however. Iggy (Swan) (Contribs) 15:56, 10 September 2025 (UTC)[reply]

Iggy the Swan reached out to me on my user talk page about this issue and linked me to this discussion. I've also been noticing that Huggle warnings have occasionally been left at the top of some user talk pages instead of adding them to the end of previous warnings that are under the section header for the current month and year, and of those - Huggle is sometimes also not adding the correct warning level (such as a level 3 warning when the user already has a level 2 warning under the section header for the current month and year). It seems to me like something, somewhere, has changed and is occasionally causing Huggle to either not see that prior warnings have been left on a user's talk page at all, or is causing other issues that is resulting in these occasional issues with warning levels and the location in which they're left. ~Oshwah~(talk) (contribs) 17:08, 10 September 2025 (UTC)[reply]
The wrong warning levels being given is a perennial issue, see phab:T110818. I don't think there's a ticket about the warnings being misplaced, though. Perryprog (talk) 20:39, 10 September 2025 (UTC)[reply]
I've also had and seen this problem while using AntiVandal on rare occasions, so I don't think it's exclusive to an issue with Huggle. Nubzor [T][C] 15:02, 13 September 2025 (UTC)[reply]
Unless AntiVandal and Huggle share some of the same code, they are likely independent bugs. Deciding what warning to give is probably an algorithm in each tool that reads the page's wikitext, then determines what level to give. And there's probably a bug in the algorithm. There could be different heading formats, different template formats, etc. so it might be hard to cover all of them. –Novem Linguae (talk) 21:41, 13 September 2025 (UTC)[reply]
Yeah, I'm not particularly worried about it because it's so infrequent and seems like it'd be a nightmare to try and fix with all the variables. I had this example from earlier today where Huggle put a level 1 warning after a level 4. Maybe because it was from 6 days ago? But still September 2025. Then ClueBot put a level 2 after that. But I do check my reverts and caught it anyway. Not a big deal. :) Nubzor [T][C] 22:32, 13 September 2025 (UTC)[reply]
Shouldn't be that hard to fix with diffs. Wikicode in wikicode out, with a failing test case, is an easy programming problem to solve. However this project isn't actively maintained, so 🤷‍♂️. The best we can do is probably comment in a phab ticket with that diff. –Novem Linguae (talk) 22:51, 13 September 2025 (UTC)[reply]
Hello, please note that by default Huggle ignores all messages on talk pages that are older than 30 days. So if there is warning level 2 template that is 2 months old, Huggle would just issue level 1 template. This can be changed in wiki config, using key "template-age" (it's meant to be negative, default is -30), see https://en.wikipedia.org/wiki/Wikipedia:Huggle/Config.yaml for details. Petrb (talk) 20:23, 22 September 2025 (UTC)[reply]
Ohhhh very good to know @Petrb. In checking the linked config, template-age is currently -3. Would that mean 3 days, not 30? Nubzor [T][C] 20:53, 22 September 2025 (UTC)[reply]
Yes, that is correct, it seems it was set long time ago here - https://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config.yaml&diff=prev&oldid=918980316 I don't think that value is correct, 3 days is really short. Maybe up for a further discussion, but this is most definitely the root cause why Huggle seems to ignore most of warning templates. It doesn't see anything older than 3 days. Petrb (talk) 19:34, 23 September 2025 (UTC)[reply]
That clears up my issue at least. Thanks for sharing :) Nubzor [T][C] 19:36, 23 September 2025 (UTC)[reply]
cc ToBeFree. Looks like your diff https://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config.yaml&diff=prev&oldid=918980316 may have caused a couple of the sub-tickets at phab:T110818. Perhaps we should ponder if this 3 day limit can be raised a bit without re-introducing whatever AIV thing you were trying to fix. –Novem Linguae (talk) 03:26, 24 September 2025 (UTC)[reply]
Hmmmmmmmmmmm.
Thanks for the ping. The setting worked before my change and then for almost 6 years ... and we probably don't want an AIV report to be made when someone using an IP address 29 days ago had received a final warning back then. This setting also doesn't necessarily technically have to cause the issues described by Iggy the Swan initially here. That's caused by how Huggle implements the setting. My comment back then, When deciding whether to warn or report, ignore templates older than "-x" days, describes my intention. What Huggle appears to do instead is When parsing the page, completely ignore the existence of templates older than "-x" days, which is overkill. That should be changed. Users can still manually report anyone, just the (semi)automated reports of users whose warning was too long ago was the issue 2019. ~ ToBeFree (talk) 11:27, 24 September 2025 (UTC)[reply]
It's very hard to distinguish these 2 situations from the algorithm point of view - in fact it's pretty much the same. If you want to "ignore" the warnings when "warning or reporting" you pretty much want Huggle to completely ignore those old templates - those 2 situations you describe are the same. If you only wanted to consider the templates when reporting (not sending any subsequent warning) then the situation would be still only mildly different - let's say user has 3th level warning 2 months old. Huggle doesn't ignore all such templates as you expect - so it issues a 4th level warning. Then on next rollback is sees the user already received 4th level warning - so what should it do next? The logic say - report the user. But then you say: "ignore everything older than 3 days". The 4th level warning is not older than 3 days, but all previous warnings are. What should it do? I think Huggle behaves exactly as specified and required by the current configuration. I think the configuration should be fixed. There are multiple issues right now caused by misconfiguration on project config page. I already mentioned how to fix it elsewhere on this talk page. I can't fix it myself, because my extended global permissions already expired. Petrb (talk) 16:05, 27 September 2025 (UTC)[reply]
If you want to write a patch on the talk page and tag it {{IAER}}, someone will be along to implement it. –Novem Linguae (talk) 00:32, 28 September 2025 (UTC)[reply]
So as a compromise I raised the limit from 3 days to 15. I understand 30 is probably too much for English Wikipedia, but 15 should be fine. If there is a problem with that, we can adjust it. Petrb (talk) 23:09, 15 November 2025 (UTC)[reply]

Huggle not showing replies

[edit]

I was doing a vandalism reversion session on Huggle and someone objected to one of my reversions. They replied to the user warning Huggle sends them, which I think should give me a notificaition on Huggle the same way as if someone had posted on my talk page (it doesn't). They subsequently reverted my edit a few more times. Because Huggle didn't display the reply notification, the conversation could have gone a lot differently than it did. I had no idea they were even sending me a message. He kept getting madder and madder at me (judging by the wording they used), presumably because he took offense at the template wording. Is there anything that can be done on Huggle to prevent this? Gommeh 📖   🎮 02:54, 7 October 2025 (UTC)[reply]

which I think should give me a notificaition on Huggle the same way as if someone had posted on my talk page (it doesn't). I don't remember Huggle having this feature. Talk page watchers, does this feature sound familiar to anyone? –Novem Linguae (talk) 03:56, 7 October 2025 (UTC)[reply]

Why is Huggle not using the standard uw templates?

[edit]

Why is Huggle not using the standard uw templates and instead using its own versions? For example, Huggle has Template:Huggle/warn-1 when the standard is Template:Uw-vandalism1. Gonnym (talk) 09:43, 20 November 2025 (UTC)[reply]

@Gonnym: Huggle adds a direct link to the diff of the edit it reverted when warning the user, which Huggle's own templates (but not the standard templates) support. The second parameter of Huggle's templates are used to show a link to the edit, whereas the second parameter of the standard templates are used to leave a custom message. —⁠k6ka 🍁 (Talk · Contributions) 12:34, 20 November 2025 (UTC)[reply]
Can't that feature just be added to the main template? Seems a reasonable feature to add. Gonnym (talk) 13:23, 25 November 2025 (UTC)[reply]

Note on revert

[edit]

@Sugar Tax I haven't reverted the revert, but just wanted to say that on https://test.wikipedia.org/wiki/Wikipedia:What_Test_Wiki_is_not, it specifically states one of the things not allowed is testing AWB, and that implies that Huggle is also not allowed as well. FantasticWikiUser (talk) 20:26, 10 December 2025 (UTC)[reply]

Huggle and AWB are two completely different tools. I don't see anything there indicating Huggle is not allowed to be used for testing on testwiki. Sugar Tax (talk) 20:30, 10 December 2025 (UTC)[reply]
Ah, that makes sense. I suppose that it certainly isn't easy to use Huggle on external wikis (outside the WMF) while it is easier to use AWB on external wikis. FantasticWikiUser (talk) 20:35, 10 December 2025 (UTC)[reply]
Huggle is being developed on testwiki, so it absolutely can be used there. Petrb (talk) 18:57, 22 December 2025 (UTC)[reply]

Cloud VPS VMs turned off because of lack of response to 2025 Cloud VPS Purge

[edit]

@Petrb, @Addshore: The Cloud VPS huggle project was not marked as in use at wikitech:News/2025 Cloud VPS Purge#huggle. As a result the virtual machine instances in the project were turned off earlier today. If huggle no longer uses XmlRcs this is probably not a big deal. Either of you should be able to use https://horizon.wikimedia.org to turn the instances back on if they are still expected to be in use. If you do that I would recommend also marking the project as in use on Wikitech so that a Cloud VPS root does not mistakenly wheel war with you over instance state. -- BDavis (WMF) (talk) 23:16, 4 February 2026 (UTC)[reply]

Thanks for the note, @Petrb would be the one to know if these are needed :) ·addshore· talk to me! 09:14, 7 February 2026 (UTC)[reply]

Discussion at Wikipedia:Village pump (idea lab) § Five strikes down to three

[edit]

 You are invited to join the discussion at Wikipedia:Village pump (idea lab) § Five strikes down to three. Discussion of vandalism warning levels, with some concerns raised about semi-automated warnings. ClaudineChionh (she/her · talk · email · global) 03:46, 6 February 2026 (UTC)[reply]

Text size of interface

[edit]

I used to use huggle, but stopped some years ago, cant remember why.

Just fired up the latest version and due to old age and declining eyesight, I cannot read any text on the working interface as it is far too small. In cases like this I usually go to the View menu and increase the text size to a readable level, in Firefox it is set at 130 to 160%. There is no View menu in huggle, and I grow tired after 30 mins of searching help in order to increase the text size.

HELP

Walter not in the Epstein files Ego 16:32, 16 February 2026 (UTC)[reply]

Template-protected edit request on 24 April 2026

[edit]

Please undo this undiscussed change. The change (removing the Template:uw-vandalism1 tag) causes other antivandalism tools including Twinkle, AntiVandal, and Interceptor to ignore the warning. When using these tools in auto-level mode (the default in some cases), they now ignore this template and will leave an additional uw-vandalism1 warning. The hidden tag has been there for fifteen years. The template editor who made this change (pinging User:Mathglot) does not wish to self-revert but indicates if anyone else wishes they may go ahead and revert. tony 02:04, 24 April 2026 (UTC)[reply]

Note that the two other templates in the same boat are {{Welcome-3rr}} and {{Welcome-unconstructive}}; presumably not germane here. For the backstory, please see WT:WARN#Impact of templates misidentified by their hidden tags (redux).That discussion explains why this template should not contain an incorrect template id, why I cannot in good conscience self-revert (because it would introduce errors in another tool; if no one here can do it, I will as last resort), and what the proper solution is in this case. I don't know what the point about longevity implies; if it has been fifteen years, then it has been wrong for fifteen years without being called out by anyone, but that doesn't affect where we are now. Phabricator is full of bugs going back fifteen years needing attention; there is no statute of limitations on them, afaik. If someone reverts, I hope it will be merely the opening salvo leading to the permanent solution already proposed when this was discussed in February that will allow all tools to work properly, and not merely forgotten. Every day following the revert will start to accumulate errors in the number of substed uw-v1 templates statistic which other tools rely upon. Cheers, Mathglot (talk) 02:39, 24 April 2026 (UTC)[reply]
As I mentioned in the linked discussions, this is an excellent discussion to have, but that discussion needs to happen prior to an alteration. As it stands this breaks functionality every single time anyone using Huggle issues a level 1 warning. tony 03:16, 24 April 2026 (UTC)[reply]
Why prior? This is not a simple case of unilateral change to a template without discussion, as more than one template is involved; otherwise I would agree with you and simply self-revert. The change I made stops the bug from corrupting data input by the other tool, and *causes errors to appear here instead* due to the bug that has been here for fifteen years. Which tool should be the one to manifest errors: the one that does not have a bug, or the one that does? The real solution, which may perhaps take a while, is to fix the underlying bug (here). If you want to buy some time by undoing my revert, I said I would not stand in the way, but it would make me vomit to knowingly put back a bug that causes problems in a working tool elsewhere, which is why I really would prefer someone else do it. But we agree that undoing it is solely a time-buying exercise on the way to a full solution (which we already know how to do) and not a we-just-revert-and-then-it-works-again-here-so-we-are-happy-case-closed situation, right? Mathglot (talk) 04:07, 24 April 2026 (UTC)[reply]
For your consideration, here's a possible compromise: Diff. It's not super pretty, but it does seem to me to accomplish both goals of 1) not lying to folks about where this template came from, and 2) not breaking Twinkle. Tested on testwiki, this fixes the auto-level issue in Twinkle. –Novem Linguae (talk) 14:59, 24 April 2026 (UTC)[reply]
This would be great for the time being. tony 15:54, 24 April 2026 (UTC)[reply]
I think you're on the right track. The variant of wording could work, but this version won't solve the problem, as the string that says it is the other template and triggers the tally is still there. Can you change it to say <!-- This is a variant of template uw-vandalism1 --> instead? That will break the pattern match on the other side and be a complete solution. The problem with current rev is that if it still contains <!-- Template:uw-vandalism1 --> it will be tallied as that template (and also as the Huggle/warn-1 template, so it will be tallied twice). (There is also the minor matter that this won't alter what gets reported in Category:Templates with matching hidden id—or the proposed 'non-matching' category—but if a few templates are listed there that shouldn't be, I don't care as there are no real consequences from it afaict.) Mathglot (talk) 18:01, 24 April 2026 (UTC)[reply]
Unfortunately that won't be a complete solution because tools rely on the Template: part. I'm not familiar with the pattern matching logic of the tallies you're describing but apparently they use the same logic that Twinkle and Interceptor and others use.
Twinkle:
const history_re = /<!--\s?Template:([uU]w-.*?)\s?-->.*?(\d{1,2}:\d{1,2}, \d{1,2} \w+ \d{4} \(UTC\))/g;
Interceptor:
const COMMENT_RE = /<\!-- Template:([uU]w-[a-z-]+)([1-4]?(?:im)?) -->/gi;
How about this, as a compromise?
<!-- Template:Huggle/warn-1 --><!-- Template:uw-hugglewarn1 -->
The above keeps the Template:Huggle/warn-1 and also includes a more standard (albeit currently fake) Template:uw-hugglewarn1 tag. This satisfies the antivandalism tools without bloating the uw-vandalism1 totals in the statistics you're worried about. Also, do you have a link to those tallies? I'd like to take a peek at their logic. tony 18:56, 24 April 2026 (UTC)[reply]
<!-- This is a variant of template uw-vandalism1 -->. That would require learning and changing the detection algorithms in multiple tools.
I can confirm that <!-- Template:Huggle/warn-1 --><!-- Template:uw-hugglewarn1 --> works to trigger auto-leveling in Twinkle. I'm not sure exactly why yet -- maybe there's a RegEx that looks for [a-z]\d{1,4}$ or something. But this looks like a promising compromise. –Novem Linguae (talk) 19:24, 24 April 2026 (UTC)[reply]
Will get back to you, but just eyeballing it looks very promising; thanks for all the investigation, testing, and suggestions. Mathglot (talk) 19:43, 24 April 2026 (UTC)[reply]
Have updated {{Huggle/warn-1/sandbox}} (diff) in order to do some testing on my side. If that doesn't represent the proposed solution or if it is an invalid test for some reason (I'm not familiar with Huggle internals), please lmk. Thanks, Mathglot (talk) 05:48, 26 April 2026 (UTC)[reply]
Do these numbers look plausible?
Sanity check: compare tallies for Uw-vandalism1 for 2016=107,799, and 2026=67,415. Mathglot (talk) 08:56, 26 April 2026 (UTC)[reply]
Need to test on my side now, but I think this will work. Mathglot (talk) 06:30, 27 April 2026 (UTC)[reply]
I'm good with your solution. One more pending issue (probably not an issue, but just in case); regarding this:

...works to trigger auto-leveling in Twinkle. I'm not sure exactly why yet...

I hope the reason is not that it is fortuitously working for now, based on anomalous regex behavior identified here and tracked in T424820. Because if it is, it is possible that the bug fix may stop your solution from working. At first glance, the patterns seem sufficiently different that I don't think they are related, but I have to admit that much of the discussion at the ticket was over my head so I can't be sure. You might want to monitor T424820.
It looks like they have a fix for the identified regex bug as of 11 May. I'm not sure of next steps there, but I assume there is some process leading up to a general release. When that happens, could you have another look at your proposed resolution here, and if it is still working, then I think we are good to go. Alternatively, if you feel quite sure the two situations are unrelated, then we can just go for it. Mathglot (talk) 00:16, 15 May 2026 (UTC)[reply]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia_talk:Huggle/Feedback&oldid=1354209035"