User:Traituwrait/Sandbox/Archive

 Skip to the bottom

Archives: /Archive index/, /Archive 1/, /Archive 2/, /Archive 3/, /Archive 4/, /Archive 5/, /Archive 6/, /Archive 7/, /Archive 8/, /Archive 9/, /Archive 10/, /Archive 11/, /Archive 12/

__NEWSECTIONLINK__ = Feedback =

Huggle @ zhwiki
Can I use Huggle on Chinese Wikipedia? I have the rollbacker permission there, but unfortunately, I can't find zh.wikipedia in drop-down box Project. Anyhow, I can help locallize this if needed. Thanks.--Jimmy xu wrk (talk) 12:47, 29 May 2009 (UTC)
 * One more question, when I forced to add  into config.txt and select zh.wikipedia in login window, it kept saying " ", but both in huggle and in Firefox I was logged in (at least able to log in). Anyone knows what to do? Thanks.--Jimmy xu wrk (talk) 12:56, 29 May 2009 (UTC)


 * If the project isn't in the drop-down list, you can't currently use it there. Sorry. Calvin 1998 (t·c) 13:29, 29 May 2009 (UTC)
 * So if I want to test it on another wiki, such as vi.wiki, how can I do? Do I have to download all the source code and make changes there? Vinhtantran (talk) 02:33, 30 May 2009 (UTC)


 * Currently, localization is done at the source code level, so yes, you would have to modify the source code itself. Calvin 1998 (t·c) 18:03, 30 May 2009 (UTC)


 * Same question. Maybe I can help do some localization job on zhwiki. Can we make new project into the drop-down list? Or just as it says after nlwiki, at a test period? Thanks a lot.--Jimmy xu wrk (talk) 14:51, 30 May 2009 (UTC)
 * I've found it, make edit to Huggle/Config to include your project, and make sure the configuration is set on your wiki and account. Vinhtantran (talk) 19:10, 30 May 2009 (UTC)


 * That actually works? Last time I checked, it didn't... Calvin 1998 (t·c) 15:40, 31 May 2009 (UTC)


 * So, that means I should copy Huggle/Config as a whole to zhwiki and make some changes to it? But I'm quite weird since many configuration lines in that page didn't actually appear in Huggle/Configuration... Anyone knows how to maintenance it? And, since the source is written in VB (.NET?), I think if possible, I am able to make a localized version... Thanks.--Jimmy xu wrk (talk) 13:47, 1 June 2009 (UTC)

Some regex failed, maybe?
I have downloaded the source code of Huggle 9.0.1 to run from code level and test for vi.wiki project. It seems to have problem when the program can't parse IRC recent change feed for vi.wikipedia (at channel #vi.wikipedia). In the application, it rarely show edits in queue, just some edits by bot accounts. In the source code, when I debug it, it passed every Match case when the input is a change in edit. The regex you put into source code is quite complicated so I can't really understand what is wrong. Maybe with the Unicode font? Can you test again with your regex and #vi.wikipedia feed? Besides, API is working well for vi.wiki. Vinhtantran (talk) 04:02, 2 June 2009 (UTC)

Localized month name
I think you should pull the month name out of source code to make it available in localization text file. There are only English and Spanish month name in code, and it's weird to warn the user in different languages with "June 2009" in the title. Vinhtantran (talk) 04:04, 2 June 2009 (UTC)


 * As far as I'm aware those are the only projects that put month headings above warnings as standard. On other projects the headings are meant to be disabled in config. Gurch (talk) 06:25, 2 June 2009 (UTC)
 * I see,, isn't it? Vinhtantran (talk) 13:15, 2 June 2009 (UTC)

Can't log in
I put my username and password into Huggle, and it gave me "huggle is not enabled for your account, check user configuration page". I have rollback rights, so what's the big issue? 10metreh (talk) 17:25, 3 June 2009 (UTC)


 * Read the first sentence on Huggle/Download. Gurch (talk) 17:30, 3 June 2009 (UTC)

not warning users
When I revert and warn (Q) most of the time the log reads Did not warn 'Example', user has not edited since their latest warning. In most cases, I know that statement is untrue, so I have to use Twinkle to warn them. Is this a bug? Griffinofwales (talk) 17:38, 4 June 2009 (UTC) Another problem. Sometimes when I revert the log reads Did not revert 'Article Name': The content of the target revision is identical to that of the current revision. I think that means that the revision has already been reverted, but usually it reads Did not revert 'Article name': The revision you tried to rollback was already rolled back. Could someone explain the difference? Griffinofwales (talk) 23:43, 4 June 2009 (UTC)
 * Ive been having the exact same problems as well and would like to know too! (I usually find it creeps up after running for about 20 minuts so i usually close and reopen) thanks to whoever knows whats going onOttawa4ever (talk) 23:47, 5 June 2009 (UTC)
 * To any of the techies that patrol this page, this problem isn't solved and I am waiting for a reply. I don't consider the above fix to be a proper fix for this. Griffinofwales (talk) 03:44, 19 June 2009 (UTC)

Regarding your second question, the first log entry simply means that the revision being rolled back to is identical to the current revision. The second specifically specifies that the edit in question was already rolled back. The former is more general. On the first question - it may be a bug (the only person who could really confirm that would be Gurch), or it could just be an odd combination of circumstances. Calvin 1998 (t·c) 04:16, 19 June 2009 (UTC)


 * 1. Why is this message >Did not revert 'Article Name': The content of the target revision is identical to that of the current revision.< used, or in what circumstances is it used? 2. Should I notify Gurch about the possible bug?Griffinofwales (talk) 23:40, 19 June 2009 (UTC)


 * It's still going on, so could Gurch give an explanation please. Griffinofwales (talk) 02:23, 2 July 2009 (UTC)


 * It means what it says. You can't edit a page and save exactly the same text as was there before, it doesn't record a revision in the page history. So if you try to revert to a revision identical to the current revision, no edit will take place. The message appears so that you know why it didn't. Gurch (talk) 21:54, 4 July 2009 (UTC)


 * 1. Thanks for the response, but how would a situation like that ever occur?, and 2. What about my other question? It's more important than the other one. Griffinofwales (talk) 22:27, 4 July 2009 (UTC)


 * "Already rolled back" = someone already rolled it back.
 * "Identical to that of the current revision" = someone has manually changed it back. – iride  scent  22:31, 4 July 2009 (UTC)
 * Thanks for the explanation. Griffinofwales (talk) 22:42, 4 July 2009 (UTC)

Can Non-admins or Non-rollbackers use it?
Airplaneman (talk) 02:57, 7 June 2009 (UTC)

All users that have the rollback tool can use it. That means all administrators & rollbackers. Twinklerollback doesn't count. Griffinofwales (talk) 03:12, 7 June 2009 (UTC)
 * Thanks; I have neither, having only edited about 1,000 times. I guess I'll have to step it up :-) --Airplaneman (talk) 03:19, 7 June 2009 (UTC)
 * 1000 is a lot more than me, and I have this feature. You should go and apply here. Mod .torrent realm 10:58, 9 June 2009 (UTC)

Just wondering
I reverted this edit with the "revert/warn" button. The resulting warning was an "only warning before blocking" template. Do I need to be more careful with the auto warnings? I don't necessarily have a problem with the warning level in this instance, but I abhor a bitey approach. I'm looking for guidance/feedback. Thanks  Tide  rolls  02:53, 13 June 2009 (UTC)


 * You selected "Blatant vandalism", which gives that warning. Gurch (talk) 11:46, 13 June 2009 (UTC)

Small query
I can run the main version of huggle just fine, but when I use the 'lite' version it crashes just after i put in my password. Has anyone encountered this problem?., Is there a fix? Im using a vista system if that helps any. Thanks Ottawa4ever (talk) 17:07, 13 June 2009 (UTC)

Not able to login with either version
I am experiencing a problem... both versions say they are unable to load the project configuration file. Until It Sleeps Wake me 11:29, 15 June 2009 (UTC)
 * same here. I cant login to Huggle in de.wp or en.wp --Krawi talk 11:37, 15 June 2009 (UTC)
 * I took the time of trying to log into each project on the list, and no luck. I can already feel my editcount slipping away this is a very annoying little problem we have here... Until It Sleeps Wake me 11:50, 15 June 2009 (UTC)

Guess the MediaWiki update broke something. Which I guess is to be expected with them leaving it so long between updates Gurch (talk) 11:51, 15 June 2009 (UTC)
 * When was that, within the last few hours? I used it last night without any problems... Until It Sleeps Wake me 11:53, 15 June 2009 (UTC)


 * 4 hours ago Gurch (talk) 11:54, 15 June 2009 (UTC)
 * during the last 4 hours and still ongoing. --Krawi talk 12:08, 15 June 2009 (UTC)


 * We're having the same problem at Wiki-pt, does somebody know what is going on? --Darwinius (talk) 13:18, 15 June 2009 (UTC)
 * MediaWiki has been updated. Huggle is temporarily broken. That's about it. A le_Jrb talk  13:22, 15 June 2009 (UTC)

Should we put this information on the main huggle page? Until It Sleeps Wake me 13:35, 15 June 2009 (UTC)


 * No, it will now force update and work again so it shouldn't matter Gurch (talk) 13:42, 15 June 2009 (UTC)
 * works again with 0.9.1. Thanks! --Krawi talk 14:05, 15 June 2009 (UTC)
 * No lite version? :( Oh well...  UntilItSleeps Public PC   14:23, 15 June 2009 (UTC)
 * So is the lite version gonna be update/recreated from scratch to conform to the MediaWiki changes? <font face="Segoe Print"> UntilItSleeps <sup style="color:green;">Public PC   14:56, 15 June 2009 (UTC)

I am also experiencing problems with logging into Huggle today. It says there is an update available, but when I click "Update" it gives me a 404 error. - Eugene Krabs (talk) 21:45, 15 June 2009 (UTC)

Hello? Any news about the lite version? I can haz lite version pl0x? Kthnxbai. <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 03:53, 16 June 2009 (UTC)

I'm having the same problem with Huggle Lite. --Ixfd64 (talk) 20:45, 16 June 2009 (UTC)

Archive
Good gosh, are we gonna archive this page anytime soon? It's really quite annoying to have to wade through topics to find a certain one... <font face="Segoe Print"> UntilItSleeps <sup style="color:green;">Public PC   16:19, 15 June 2009 (UTC)

Request for new feature
Hi guys, I just wondered if automatic reports to w:es:WP:VEC (AIV here) could be possible to set in -es. It will be really helpful to our fellow patrollers to save time and speed-up anti-vandalism fighting :). Many thanks in advance and thanks for your work. we, admins, are still experiencing troubles with the block feature Best regards, —df | 16:38, 15 June 2009 (UTC)
 * I join to the request made by Dferg, this application would really facilitate things with a link that automatically reported the vandalism to w:es:WP:VEC (AIV here). Thanks in advance. Best regards Saloca (talk) 17:15, 15 June 2009 (UTC)
 * Can somebody at least tell us if this will be possible to do or not?. Thank you. —df| 16:32, 28 July 2009 (UTC)

Rollback and Setting it up?
Hello, I have decided to start helping fight vandalisim and I got a message that said "Use of huggle on this project requires rollback!" I have a question on what rollback is and how to set it up?

-Thanks —Preceding unsigned comment added by Shamismcgillin (talk • contribs) 02:32, 16 June 2009 (UTC)


 * In order to use Huggle you need to request rollback rights for your account. However, given that you only have 8 edits at the time of this posting, it is highly unlikely that they would grant you rollback rights. You should try doing some patrolling down at Special:RecentChanges, and get rid of vandalism there for a while, and do some other edits, before you request rollback. <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 19:07, 16 June 2009 (UTC)

Version bump
Is there a reason to force min usable version to 0.9.1 ? Only the lite version 0.9.0 was useful for me on linux, and you forcebumped min version to 0.9.1 on meta. Is there a reason for forbidding 0.9.0 version? -- m:drini 16:18, 16 June 2009 (UTC)
 * Yes. A recent MediaWiki update broke both versions of Huggle, so Gurch was forced to push out 0.9.1... 0.9.0, full and lite, no longer work on any wiki. Not too sure atm what on Earth is gonna happen with the lite version, whether they are gonna update that, or scrap it altogether... <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 19:03, 16 June 2009 (UTC)
 * Kind of sad, as lite version was the only one fast enough to run under wine+linux to be useful to me. -- m:drini 21:42, 16 June 2009 (UTC)

IRC feed.
Huggle seems like it's not parsing the IRC feed correctly. It connects for sure, and it does enter the channel, (If Huggle is having problems, I enter in chatzilla to see if it's actually entering in the first place), and the RC bot is running, but it just isn't parsing the feed. I'm forced to use the API queries in order to get a queue. <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 19:51, 16 June 2009 (UTC)


 * 18:37 Fred: irc.wikimedia.org is back in service. Channel list is growing. Everything seems to be working as expected.
 * 18:02 Fred: upgrading irc.wikimedia.org. Server will be offline for a couple of minutes.


 * Gurch (talk) 23:37, 16 June 2009 (UTC)
 * Ah, so they updated the IRC as well, and that broke a part of Huggle too? <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 00:46, 17 June 2009 (UTC)

I'm having some trouble with IRC as well. I can't use Huggle until I tell it not to connect. – Zntrip 23:38, 17 June 2009 (UTC)
 * No problem using it against nowiki, but against enwiki I needed to disable system-options-Use IRC feed for recent changes if possible. Nsaa (talk) 15:12, 18 June 2009 (UTC)

There should be no reason it only works for one language, the RC feed is the exact same for all sites. Q T C 00:14, 28 June 2009 (UTC)

Ye old crashing problem
I was using the new version for a few minutes, and it seems to work fine and fast. But the problem of everything crashing when you try to cancel a revert still seems to be there. I forgot all about this and pressed the escape button... :P Anyway is there any way to disable this function at least until it can be fixed? <font color="#000080">C h<font color="#0000FF">a <font color="#4169E1">m <font color="#1E90FF">a <font color="#87CEEB">l  talk 01:52, 17 June 2009 (UTC)

History
Hi fellow Huggle users, I'm having a few problems loading the history of articles in the bar at the top. When I click the button it just doesn't seem to do anything. Is anybody else having the same issue? Is there a fix I can try? -- Noosentaal ·talk· 11:49, 17 June 2009 (UTC)


 * I get this too. I dunno what causes it. Q  T C 08:35, 2 July 2009 (UTC)

Fatal error
I got this fatal error message:

NullReferenceException: Object reference not set to an instance of an object. at Huggle.Misc.FindString(String Source, String From, String To) at Huggle.Processing.ProcessRc(String Result) at Huggle.Requests.RcApiRequest.Done at Huggle.Requests.Request.ThreadDone at Huggle.Misc.CallbackInvoke(Object TargetObject)

I'm not too sure if this is where I report stuff like this. :| – Zntrip 23:40, 17 June 2009 (UTC)


 * Reporting this stuff here is just fine :) - it just won't get fixed anytime soon :/ (although I thought I fixed this problem earlier...) Calvin 1998 (t·c) 03:56, 18 June 2009 (UTC)

Can't work with empty queue
I just downloaded version 0.9.1 and started it. The logs at the bottom part of my window tells me about a successful connection to the IRC channels, but I can't see anything at the queue. Alexius08 (talk) 23:12, 18 June 2009 (UTC)


 * I think the IRC update changed the format of the IRC entries... which means you're going to have to use the API recent-changes feed (so go to the options and disable IRC). Calvin 1998 (t·c) 01:09, 19 June 2009 (UTC)


 * Yeah, me too. A fix for me was to go System -> Options then uncheck to connect to the IRC feed. <font color="528B8B">Weeliljimmy  <font color="7A8B8B">talk 23:43, 21 June 2009 (UTC)

Error report
NullReferenceException: Object reference not set to an instance of an object. at Huggle.Misc.FindString(String Source, String From, String To) at Huggle.Processing.ProcessRc(String Result) at Huggle.Requests.RcApiRequest.Done at Huggle.Requests.Request.ThreadDone at Huggle.Misc.CallbackInvoke(Object TargetObject)

-- Just James  <font color="#0047AB">T /<font color="#0047AB"> C 05:37, 19 June 2009 (UTC)
 * This exact message is two sections above this one... A le_Jrb <sup style="color:blue;">talk  12:05, 19 June 2009 (UTC)
 * Ok...-- Just James  <font color="#0047AB">T /<font color="#0047AB"> C 12:51, 19 June 2009 (UTC)
 * Just thought I'd point it out - you could have saved yourself the effort of copying it! =) A le_Jrb <sup style="color:blue;">talk  15:38, 19 June 2009 (UTC)
 * Lol, I did notice it, but I figured I should start a new section, otherwise it may have gone unnoticed.-- Just James  <font color="#0047AB">T /<font color="#0047AB"> C 05:46, 20 June 2009 (UTC)
 * FYI, this error has appeared for a second time now.-- Just James  <font color="#0047AB">T /<font color="#0047AB"> C 08:09, 20 June 2009 (UTC)
 * I received the same error, crashed the program. :-\ Vicenarian  <sup style="font-family:Georgia;">(T · C) 03:45, 21 June 2009 (UTC)

Ok, it has happened for a third and fourth time. I'm able to edit on Huggle for about 10-20 minutes, then it crashes after showing that error message.-- Just James  <font color="#0047AB">T /<font color="#0047AB"> C 15:15, 22 June 2009 (UTC)

Binary installer?
I was wondering if there could be a binary installer. --Sushiflinger (Goldblattster) (talk!) 18:39, 21 June 2009 (UTC)


 * Why? The download consists of precisely 1 executable file, and all configuration files are created automatically on startup if they do not exist. So there would be nothing for an installer to do. Gurch (talk) 20:18, 21 June 2009 (UTC)


 * I suppose so. I just thought some people might like to have one, but maybe not if you say so. --Sushiflinger (Goldblattster) (talk!) 20:41, 21 June 2009 (UTC)


 * Most applications are not a single executable, but multiple libraries, executables, data files and configuration files organized in various subfolders. They also like to fiddle with the registry, make themselves run on startup, put an icon in your notification area, add themselves to your desktop, program menu and quick launch area, and possibly poke around with system files if they think they might need them. Huggle does not do these thngs and is intentionally distributed as a single file to avoid the need for an installer. Gurch (talk) 00:40, 22 June 2009 (UTC)

PS: "So there would be nothing for an installer to do." That is part incorrect, as the extracting installer can compress the files it contains. --Sushiflinger (Goldblattster) (talk!) 23:09, 21 June 2009 (UTC)


 * If that's all you wanted it could just be uploaded as a zip file. If downloading a 1Mb file takes any noticeable amount of time, though, your connection is going to be too slow to use Huggle anyway. Gurch (talk) 00:37, 22 June 2009 (UTC)

If you want n installer why not just make one? NSIS (Nullsoft Scriptable Install System) can make an installer for you, I guess it might be useful to have an installer with options to add it to the quick launch bar, start menu or desktop. I'll make one if someone will tell me if I'm allowed. <font style="color:#000080;">Hintswen <font style="background:#000080;"> <font style="color:#FFFFFF"> Talk | <font style="color:#FFFFFF"> Contribs 06:29, 23 June 2009 (UTC)
 * But why? It's a self-contained app and a small one at that, I'd understand if it did anything that required it to be installed but it doesn't do much else than create a handful of files in a folder where the app is and off it goes. It's redundant, doesn't need any special place to run from and even if it did need sidecar files I'd still take an archive over any installer for something so lightweight. Shortcuts are your own lookout. treelo  <sub style="color:#D2CDC6;">radda  08:59, 23 June 2009 (UTC)
 * I also prefer an archive over an installer but some people do prefer installers, saves them from creating shortcuts manually. <font style="color:#000080;">Hintswen <font style="background:#000080;"> <font style="color:#FFFFFF"> Talk | <font style="color:#FFFFFF"> Contribs 04:13, 24 June 2009 (UTC)
 * "If you want n installer why not just make one?" Fine, I just made one with Inno.--Sushiflinger (Goldblattster) (talk!) 15:56, 25 June 2009 (UTC)


 * If you just wanted shortcuts created automatically then that's not really enough to merit a separate installer. Adding an option to create shortcuts has a few problems though: it's not portable, it's not even possible using only .NET, and the application name changes with each version, breaking any shortcuts. It could feasibly be implemented as an option on Windows only if the updater were changed so that, rather than simply downloading the new version, launching it and then terminating, it downloaded it to a temporary file name, launched it with a commandline parameter that told it to delete the old version, copy itself to the old version's name, then launch the copy with a commandline parameter that told it to delete the temporary version. Gurch (talk) 20:06, 30 June 2009 (UTC)


 * Also that would mean the application would always keep the name of the previous version, which would be incorrect because the name includes the version number. This could be addressed either by having the latest version always named without the version suffix on the download server, or by having the application rename and re-launch itself if it is named anything other than a predetermined name, to which shortcuts would point. Both of these have drawbacks however. Gurch (talk) 20:37, 30 June 2009 (UTC)

Flagged Revisions
Hi, I'm from the german wikipedia, where flagged revisions are active. Huggle is used by some of our recent changes patrollers (yay to Huggle :-)). Therefore it would be really great if you could include interaction with flagged revisions as an option. Reverts are completely fine and will be flagged automatically, the feature we would like to have is the possibility to flag good edits as sighted from the Huggle interface. As it is now, all the checking of good edits has to be done twice if the RC-patroller uses huggle. The other supported project that uses flagged revisions is the ru.WP, so they would be happy as well. Any chance? Best, --P. Birken (talk) 15:29, 10 December 2008 (UTC)
 * I do believe there's a button for sighting revisions in version 0.8.3 (the latest released version). Calvin 1998 (t·c)03:05, 13 December 2008 (UTC)


 * Oh really? I havent found any button for sighting revisions in 0.8.3 yet. Any hint? --Krawi talk 08:31, 15 December 2008 (UTC)

Happy new year to everyone. I just wanted to ask how things are going now that 16278 is fixed? Best, --P. Birken (talk) 13:22, 3 January 2009 (UTC)


 * They aren't. Nobody is working on Huggle at the moment. -- Gurch (talk) 19:58, 3 January 2009 (UTC)
 * Mh, that's sad, there are quite a few people who use it. Hope that at sometime, you feel like working on Huggle again. All the best, --P. Birken (talk) 11:13, 4 January 2009 (UTC)
 * There are several issues using Huggle on DE (see).Avant-garde a clue- hexa Chord <sup style="color:#FFFF00;">2  11:45, 4 January 2009 (UTC)

So 16896 and 16278 are now in place. This means that in theory, Flagging from Huggle could be possible using the API and furthermore, that Huggles usability could profit from flagged revisions by removing sighted edits from the list of edits to check. And of course, also profit from other vandal fighting tools having a similar feature. For example, http://toolserver.org/~apper/ipp/ uses this already, the VF-people are on it. It would be great if somebody could implement this for Huggle. --P. Birken (talk) 18:10, 28 February 2009 (UTC)

Supporting "flagged revisions" is not as simple as just adding a "flag this" button next to the revert button, as you seem to think.

If there are unreviewed revisions between the last reviewed revision and the previous revision to the page, they won't be visible when viewing a diff of the latest revision, so there would have to be some way to fetch a diff of all changes since the last reviewed revision, then check that, then review it. Simply loading a diff of all changessince the last reviewed revision every time would not only be much slower than currently, but would also lead to problems when dealing with vandalism; people would hit the revert button on seeing vandalism and possibly revert unreviewed good revisions in the process.

More importantly, there are issues with the way "flagged revisions" work that mean reviewing an edit based only on a diff is a very bad idea. The extension freezes "stable" pages in the state they were when last revised, including any transcluded templates and images. Normally, checking a diff for vandalism and leaving the edit if not is OK, because while it misses vandalism to templates on the page, provided changes to those templates are also reviewed the vandalism will be reverted and when it is, the template will display properly again on pages that transclude it. If you review a revision using "flagged revisions" based on a diff that shows a good revision, but at the same time somebody just happened to vandalise a template transcluded in that page, the extension will freeze the page in the vandalised state. Reverting the vandalism to the template will not remove it from the page, in fact nothing will short of un-reviewing the revision and re-reviewing a different one. So revisions can only be reviewed after reading the whole text of the revision through in its entirety, including bits that were not changed. This is a stupid system and I have no idea why it was thought up; as well as being stupidly slow, it means reviewing has to be a completely separate process from recent changes patrolling, unless recent changes patrollers are expected to read entire revisions through for one-word changes rather than looking at diffs, which is also stupid. Gurch (talk) 22:43, 23 June 2009 (UTC)
 * Heyho Gurch, happy to see your details to Huggle flagged ;) . I'm not sure if I understand everything you wrote, but showing a Diff to the last reviewed revision seems for me a good (ok, more slow) first step to optimize the review process. You are right, the diffs between are also interessting and could have interessting, right content people can't see in the diff between the revisions perhaps.


 * The special case, that the diff between the last revision and the last flagged revision ist the same should be no problem. My thinkings:
 * Diff displayed in huggle, if pressed the button "not stable", next diff in queue comes to display (former showed diff is not reviewed), if pressed the next key or a new revision on the left side in the queue, version become flagged stable... If there are more changes between the last reviewed diff, people could decide to view the steps and use a special review button. If user changed to the next diff in queue left side (other article) revision becomes not automaticalle reviewed.
 * Where do you see problems in this process (sorry if that is told in the upper text :) )? What do I forget?
 * Happy for Huggle, thank you, Conny (talk) 04:42, 10 August 2009 (UTC).

Serious bug... Huggle is reverting a user who has already reverted a vandal...
Read the header... Here's the edits that Huggle has reverted a reverting user:, , and ...

This is becoming very annoying, both to me, and to the person I reverted, which in all 3 instances happens to be the same person. There needs to be something in Huggle that checks for something like this, so that it can revert itself if this happens. <font face="Segoe Print"> UntilItSleeps <sup style="color:green;">Public PC   14:45, 24 June 2009 (UTC)


 * The vandal made two edits. You seem to have instructed Huggle to revert just one of them at the same time as he tried to revert both; the result was that he reverted both, and then when Huggle came to revert the page it had to revert him and one of the vandal's edits to get the page into the state that you wanted it. It should be prompting for confirmation if you revert to a previous version by the same user, unless you've turned the prompt off, so the problem is you ignoring the prompt. Either that, or you have it set to automatically show new edits to the page, in which case you were viewing a diff of the second of the vandal's edits, then the revert was made, but you clicked "revert" anyway. Since the revert button is greyed out until the diff of the revert is loaded, I'm not sure how you're managing to do that without realising, furthermore Philip Trueman is on the whitelist so if it was the second of these that happened you would also have been prompted that you were reverting an ignored user, unless you turned that prompt off. Gurch (talk) 16:02, 24 June 2009 (UTC)
 * It's set with the prompts off, but it always reverts all edits by the user back to one by a different user. In this case, it seems that even though someone else reverted it, Huggle still thinks it's reverting 2 edits by the same user, so it reverts back 2 edits anyways, one by the IP, and one by the ignored user. That results in what happens here...

As for Huggle reverting a whitelisted user, I see no such option in the Options dialog... <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 19:34, 24 June 2009 (UTC)


 * But it doesn't always revert all edits by a user back to one by a different user. It only does that automatically if it's the last revision to the page, for reasons of efficiency (because this allows it to use rollback). When it's going to do otherwise, it prompts you, except you turned that prompt off. And there is no option in the options dialog to disable the prompt when reverting a whitelisted user, because I didn't want people turning it off, though it can still be done by manually editing the configuration page. Gurch (talk) 22:05, 24 June 2009 (UTC)

Config changes
I'm new to Huggle, but I'm having unpredictable behavior with config changes. I am unable to add the irc:0 option to my config file (I add it, and upon launching it is ignored and removed from the config file).

HG also seems to change my settings for whitelists, watchlisting, and some other minor modifications, and it also seems to modify my userspace huggle.css file everytime I launch it. What am I doing wrong here? Shadowjams (talk) 04:16, 25 June 2009 (UTC)


 * Using Huggle. Gurch (talk) 11:30, 25 June 2009 (UTC)
 * heh. So this is a common issue, and not unique to me then? Shadowjams (talk) 20:17, 25 June 2009 (UTC)


 * No, it's just that I don't have the time or desire to fix any of the issues on this page or its archives, of which there are about eleventy billion, and you're all better off implementing Flagged Revisions and stagnating the project so I don't have to worry about it any more. Gurch (talk) 22:40, 25 June 2009 (UTC)

Huggle Freezes Laptop
Ive installed Huggle on my HP pavillion laptop. However when I try to open it on my laptop nothing happens and after a few seconds my laptop is frozen. I let my laptop run to see if after a while it would unfreeze and after 4 hours I shut it off.

I then installed Huggle on my friends desktop, a Dell XPS, and it worked flawlessly. My laptop is almost three years old and I am buying a new one in August but until then I would really like to get Huggle running on my machine.

Does anyone have an idea of what might be causing the problem and any possible soultions? Thanks. Sweetness46 (talk) 05:33, 25 June 2009 (UTC)


 * It's probably HP's fault. Actually it probably isn't, but that way it doesn't involve me. Gurch (talk) 22:42, 25 June 2009 (UTC)
 * How fast is your laptop anyways? How much ram does it have, etc... I have a laptop that has a 2.4 GHZ P4 CPU... but it has only 512 MB of ram, and Huggle was rather iffy on that... On my tower though, which has a 1.8 64-bit dual core AMD in it... and it has 3 gigabytes of ram, and Huggle runs perfectly on that, save for the errors with disconnecting, and the freezing if I try to cancel a pending edit... <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 22:04, 26 June 2009 (UTC)

Revert all edits by a user?
Is there an easy way to do this? I'm asking because I just reverted some 20+ spam link insertions by an IP and was wondering if there was an easy way to do this. I remember back in vandal proof, there was a "view all contributions" buttom. I hit the "Contribs" button right next to the user textbox up top, but that doesnt do anything Corpx (talk) 06:59, 26 June 2009 (UTC)
 * That button, along with the History button, hasn't been working with the latest version... Sorry to tell you this. To tell you the truth it is very annoying that it doesn't work, but at least I can click on the IP's link in the diff box that leads to the contributions. <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 21:50, 26 June 2009 (UTC)
 * Which link are you referring to? I cant find any way to pull up an IP's other edits Corpx (talk) 06:55, 27 June 2009 (UTC)

welcoming
WP:TWINKLE has been modified so that if it creates a user talk page, it automatically adds a welcome template along with whatever warning or other notice is being sent, I was wondering if it would be possible for Huggle to do this as well, as it avoids biting the newcomers and making them feel unwelcome. Beeblebrox (talk) 22:19, 26 June 2009 (UTC)
 * Actually it only does that if it's a csd message, but I think it would be a good idea if both tools added a welcome whenever creating a user talk page. Beeblebrox (talk) 22:28, 26 June 2009 (UTC)
 * Because we don't want to welcome people who replace the contents of a page with obscenities directed at other contributors. Gurch (talk) 22:34, 26 June 2009 (UTC)
 * I realize Huggle is a vandalism fighting tool, but have you ever heard of the idea that you catch more flies with honey than with vinegar? In other words, despite their vandalism, we should try to get these users to understand Wikipedia and maybe decide to make useful contribs. Beeblebrox (talk) 22:43, 26 June 2009 (UTC)
 * I agree, that is the spirit ...  Nu&beta;i&alpha;&tau;&epsilon;ch  Talk/contrib 11:44, 27 June 2009 (UTC)


 * No, it isn't. These users are never going to make useful contributions. Gurch (talk) 14:10, 27 June 2009 (UTC)
 * May I ask, as the creator of this tool, do you feel you have total control over it and will not modify it if you don't like the suggestions? I'm honestly just asking, I don't know what the protocol is in these situations. I do see your point about obvious socks and retuning banned users and so forth, maybe it could be done as an option, where you uncheck a box if you don't wish to leave a welcome message, or vice versa. Beeblebrox (talk) 21:36, 27 June 2009 (UTC)
 * Or, if you feel a welcome message is needed, why not just add one? A program's features are down to the program's creators and maintainers. If you really need an anti-vandalism tool that adds a welcome at the same time as a warning, consider creating your own - no one is stopping you. Your post seems to suggest you feel that someone is under an obligation to modify their tool to perform an action they don't agree with, which strikes me as an odd opinion to have. A le_Jrb <sup style="color:blue;">talk  22:12, 27 June 2009 (UTC)
 * I don't have the slightest idea how to go about creating such a thing, and if you WP:AGF as you read my remarks you will see that I very plainly stated that I really don't know whether asking such a thing is inappropriate or not. There's already hundreds if not thousands of people using this tool and I thought I saw a way it could be improved to make it less WP:BITE-ey. I also said maybe it should just be an option to make it more discretionary. Beeblebrox (talk) 23:52, 27 June 2009 (UTC)
 * I am assuming good faith - I didn't state that you did believe that, only that it could be read in that way. It isn't inappropriate to ask, not at all, but you've pretty much already got an answer (though it could change, who knows?) :) A le_Jrb <sup style="color:blue;">talk  10:18, 28 June 2009 (UTC)
 * There is already an option to add a welcome. The aforementioned users are the reason it isn't included in the default warning, as that would make it compulsory. Gurch (talk) 16:23, 30 June 2009 (UTC)


 * All of the level 1 warning templates already include a short welcome, so the welcome you are requesting would be superfluous.   — Jeff G. (talk&#124;contribs) 04:47, 29 June 2009 (UTC)

Xfd ?
The manual states that huggle supports Xfd, but I don't see how tp tag an article for AfD.--Work permit (talk) 05:02, 27 June 2009 (UTC)
 * In the topmost text menu of the Huggle UI, see "Page | Request Deletion | xyz options" Newportm (talk) 00:13, 28 June 2009 (UTC)


 * I see and have used the options for CSD and PROD but I don't see an option for AFD--Work permit (talk) 05:17, 29 June 2009 (UTC)

Save settings?
How can I make huggle save my preferences? For example, every time I load up the program, I have to go into the settings to disable the IRC feed. Corpx (talk) 06:59, 27 June 2009 (UTC)

Michigan J. Frog
Michigan J. Frog contains the sentence, "while being interviewed by a writer named Jay Cocks." That was reverted by an editor using Twinkle to "Jay Cox." The anon IP editor reverted to Jay Cocks, whereupon I came across this edit in Huggle, which flagged "Cocks" as well. To the uninformed, it looks like blatant vandalism. Guess what...that is actually his name; there is even a live article about him. In the Huggle interface, I have not figured out how to tell the difference between a live wikilink and a red wikilink...especially when the filter tags the word in red. Any tips or suggestions? The other automated editor already suggested to the anon IP user that he get a free user account to minimize these hassles. Newportm (talk) 19:53, 27 June 2009 (UTC)


 * Just remember that accuracy is more important than speed. Calvin 1998 (t·c) 02:39, 28 June 2009 (UTC)


 * Noted; well said. Newportm (talk) 05:07, 28 June 2009 (UTC)


 * Huggle did not "flag" Cocks. It doesn't "flag" anything. It does not have a "filter" that "flags words in red". The red text is the text that was changed by the edit, this is no different to any other diff generated by MediaWiki. Huggle tries to sort all edits in approximate order of their likelihood of being vandalism. It doesn't use the revision text at any point in determining this, because it is not feasible to fetch it for every edit. Almost all of the edits it shows you are not vandalism, even ones near the top of the queue. You should assume an edit is not vandalism unless you are sure that it is. Gurch (talk) 14:55, 28 June 2009 (UTC)


 * Thanks, Gurch. Newportm (talk) 15:03, 28 June 2009 (UTC)

IRC Feed Fixed
I know what's wrong with the IRC Feed parsing, I threw together a fixed 0.9.2 release here until somebody can fix it upstream. Q T C 00:57, 28 June 2009 (UTC)


 * Do you feel like telling anyone what it is you know that's wrong, or do I have to go and find out myself? Gurch (talk) 14:58, 28 June 2009 (UTC)


 * OK, I see the problem. For some reason, whoever reconfigured the IRC feed last time it was reconfigured decided to change something, which they doubtless thought was purely internal, such that the user the feeds come from is no longer "rc@localhost" but "rc@I.still.hate.packets". Huggle was checking for precisely "rc!~rc@localhost", and so broke when this was changed. Gurch (talk) 15:14, 28 June 2009 (UTC)


 * fixed in 0.9.2 -- Gurch (talk) 15:44, 28 June 2009 (UTC)


 * Yea sorry, was going to send a mail, but I got stuck out all day. Q  T C 18:39, 28 June 2009 (UTC)

Errors when using the IRC feed
I keep getting "Failed to retrieve..." errors which show up in the log... quite annoying in fact... Here's a part of a log that I recently saved: <pre style="overflow: auto"> 2009-06-28 7:41:46 PM (+-6:00) -- Failed to retrieve 'title=User talk:68.46.132.194&diff=cur&oldid=prev&...': Unknown error 2009-06-28 7:41:14 PM (+-6:00) -- Failed to retrieve 'title=User talk:TM Ray&diff=cur&oldid=prev&uselang...': Unknown error 2009-06-28 7:40:09 PM (+-6:00) -- Failed to retrieve 'title=User talk:173.119.129.98&diff=cur&oldid=prev...': Unknown error 2009-06-28 7:40:08 PM (+-6:00) -- Failed to retrieve 'title=User talk:V8A2N6&diff=cur&oldid=prev&uselang...': Unknown error 2009-06-28 7:39:25 PM (+-6:00) -- Edited 'User talk:89.203.12.1': Level 2 warning re. Cradle of Filth (HG) 2009-06-28 7:39:23 PM (+-6:00) -- Edited 'Cradle of Filth': Reverted 3 edits by 89.203.14.241 and 89.203.12.1 to last revision by Magnius (HG)

Sometimes they start popping up, sometimes they don't. I never got these when I was using the API queries in 9.1... so why does it only get them in 9.2? <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 01:44, 29 June 2009 (UTC)
 * I'm getting blank pages, so I can't revert anything and stuff. - Eugene Krabs (talk) 00:38, 30 June 2009 (UTC)


 * For me, the IRC feed, while connected, is not giving me any updates, while the API is giving me updates. :(    — Jeff G. (talk&#124;contribs) 14:10, 30 June 2009 (UTC)

Interestingly, the "failed to retrieve" errors appear to be caused by r464, which I added to fix this issue. Hmm... Calvin 1998 (t·c) 01:21, 1 July 2009 (UTC)


 * Yeah, it seems to have been changed to fail the request on any web error, including transient ones that might go away, rather than retrying on all but timeouts. And while they always seem to give them when you least want them, I don't think the Wikimedia servers can be coerced into serving HTTP 500s on demand, making this stuff harder to test. Time to learn Apache configuration I guess... *sigh*. Interestingly I found it is possible to get the teal screen of death on demand, just pass a URL string longer than the maximum length. Having some problems finding the "Wikipedia has a problem" one; I want the source of it so I can test for it and throw a more useful error, but I can't find any way to force it to come up, nor have I been able to break my MediaWiki installation in the right way to make it appear (is it even part of MediaWiki at that point?) -- Gurch (talk) 16:51, 1 July 2009 (UTC)


 * Um... if you want HTTP 500s on demand for testing, just use PHP... and if you want to get your MediaWiki installation to fail and give the error message, I would assume all one would have to do is abort the accompanying MySQL server... Calvin 1998 (t·c) 02:04, 2 July 2009 (UTC)


 * Never mind, it seems the current SVN version of MediaWiki is broken in precisely the right way to give that message. Nice work devs (bug is 19447 if anyone cares) Gurch (talk) 17:28, 2 July 2009 (UTC)

Administrators' noticeboard/Edit warring Bug?
It appears that Huggle adds 3RR reports to the top of the page (diff), when the admins who work the page request that reports be added to the bottom. This may be a recent change in policy on this board or a one-time glitch, but thought I would report. Thanks! Vicenarian <sup style="font-family:Georgia;">(T · C) 03:14, 30 June 2009 (UTC)


 * Looking at that edit, I think it's broken anyway. Must rewrite it to use an XML parser at some point. Except on page text of course... Gurch (talk) 16:11, 30 June 2009 (UTC)


 * This diff looks even worse. :(   — Jeff G. (talk&#124;contribs) 03:16, 2 July 2009 (UTC)


 * Hm. Encoding problems. Not sure how it worked in the first place if that is the issue. Guess I'll have to turn off that feature. Gurch (talk) 17:31, 2 July 2009 (UTC)

Suggestion
I think it would be a good idea if Huggle pops up the article that you've recently reverted vandalism in when another edit is made to it, ahead of all others. Similarly, it should pop up the article where the warned user makes his next edit (and only the next edit, so it doesn't become policing or targeting). It would help keep track of repetitive vandalism much faster. It would also prevent a vandal from escaping the "Huggle highway" and vandalize more low-key articles that are lost in the flow, since you can chase a specific vandal or keep an eye on a specific article (like about schools, where the "alumni" like to post all kinds of garbage. I've noticed a lot of inbred vandalism that escaped RC patrollers). <font color="orange" face="Verdana">Shiva <font color="blue" face="cursive">(Visnu)  01:16, 2 July 2009 (UTC)


 * It's an excellent idea, but it would involve keeping track of all pages and users you've reverted, and comparing each and every page/user combination against that... shouldn't the current number-flag system (where edits by a user with 2 warnings has a 2 blob, etc) be enough? Calvin 1998 (t·c) 02:11, 2 July 2009 (UTC)


 * Huggle does keep track of all pages and all users you've reverted. That's how the queue ordering works. Gurch (talk) 16:17, 2 July 2009 (UTC)


 * I think using Special:Contributions/ would be the best way to keep track of the pages uve reverted and users uve warned - to make things easier, say Huggle will go only as far back as the last 50 edits.


 * My desire is to keep track of specific article(s) where the vandal strikes again within seconds/minutes. Its hard for me to stay watching an article I've just reverted vandalism on, waiting for the next strike that may/not come that quickly. So I want Huggle to do the watching and pop up the next edit the moment it happens. If the vandal so speedily ignores your warning, then it obvious you have a problem that's most likely not going away with a 2nd or 3rd warning. It helps to be directly informed the very second an edit is made, so you can pay attention to that article you've just worked on and don't have to rely on a fellow RC patroller who may or may not be there in time. I mention articles on schools, days of the year, etc., because those are where the inbred vandalism is most prevalent; even ClueBot is unable to keep up with a second strike that may happen just after it reverts the first. Such a pop-up can help if the school's "alumni" decide to try and dodge the patrollers by creating a vandalism-only account or playing with their IPs. <font color="orange" face="Verdana">Shiva  <font color="blue" face="cursive">(Visnu)  03:56, 2 July 2009 (UTC)


 * Have a look at Special:Contributions/S h i v a (Visnu) where I had to reverted vandalism that happened within seconds at List of characters from Total Drama Island and What About Bob?, and from user talk:Mightyaxon, who had something against lawyers to the extent that he was running wild on any legal article he could find - but in all cases, I had to lie in wait and only because I suspected that it would repeat. It would be easier for me to chase these people without sacrificing my time on writing and patrolling other articles if such a feature was enabled. <font color="orange" face="Verdana">Shiva <font color="blue" face="cursive">(Visnu)  04:00, 2 July 2009 (UTC)


 * Once you've given them one warning, any subsequent edits should be at or near the top of the queue with a "1" icon next to them, and so easily locatable. If this is not happening, let me know. Gurch (talk) 16:19, 2 July 2009 (UTC)


 * Plus, I don't want to give an impression that this is just about striking down the vandals. If I see that a user is repeatedly ignoring warnings at a fast pace, then it helps me to try and engage him/her directly and try to convince him/her to stop by reason. If you know this is a continuing problem, you can talk to those people and "try" to knock some sense without auto-warnings and blockings. If you're flying down the highway, you can but shoot-at-sight. There might be complicated situations afoot, like edit wars, etc. <font color="orange" face="Verdana">Shiva <font color="blue" face="cursive">(Visnu)  04:03, 2 July 2009 (UTC)
 * Once you've reverted someone once, they are warned, will have a warning, and thus appear above everyone else anyway. How is your system different from the current one? A le_Jrb <sup style="color:blue;">talk  13:14, 2 July 2009 (UTC)

Edits to pages that you have reverted during the current session are given more weight when ordering them in the queue, so they will appear near the top. The same goes for users whose edits you have reverted. If you find an edit war, that is not a situation which Huggle is designed to handle, because such situations do not generally benefit from editing assistance. Any responses to such situations should be done manually (though you can of course use Huggle to do so) Gurch (talk) 16:15, 2 July 2009 (UTC)

Huggle reports problem and closes on self-revert of a warning
I've noticed that Huggle reports problem and closes on self-revert of a warning for quite a while now. Wtmitchell (talk) (earlier Boracay Bill) 04:36, 5 July 2009 (UTC)

fullurl
It would be nice if the Wikipedia links that Huggle posts to Wikipedia (like links to diffs included in ) would use so that those of us using the secure server aren't needlessly redirected to the non-secure server. I know very little about Huggle, so I don't know if I'm being clear enough. Thanks.&mdash;C45207 | Talk 00:04, 7 July 2009 (UTC)


 * The recipients of the messages are very unlikely to be using the secure server. Gurch (talk) 13:42, 7 July 2009 (UTC)


 * Though other editors may be. Consider: User A makes a change, User B uses Huggle to revert it and posts a note at User Talk:User A. User C, using the secure server, notices another edit of User A's, reverts it, goes to the talk page, and wants to look at the diff that User B included. At this point, User C is taken to the non-secure server.


 * Also, using won't unconditionally take everyone to the secure server. It will keep those on the secure server on the secure server and those on the non-secure server on the non-secure server. (A and B would stay on the non-secure server, and C would stay on the secure server.) It has the added benefit of make page diffs slightly smaller to. Thanks for taking the time to respond.&mdash;C45207 | Talk 15:32, 7 July 2009 (UTC)


 * Remind me again of the point of a secure server for a website anyone can edit? Gurch (talk) 19:45, 7 July 2009 (UTC)


 * Security and privacy, as with all secure websites. Calvin 1998 (t·c) 02:52, 8 July 2009 (UTC)
 * My issue is more with the unintended, unneeded switch between sites. It has the potential to throw users off. One page has them logged in, the other doesn't, just by clicking on a diff link. Also, there's nothing wrong with encryption or making it easier for those who wish to remain (relatively) anonymous to do so. Though, the user experience detraction is more the issue for me. I can try to submit a diff, but I can't seem to find the section in the code. Any pointers?&mdash;C45207 | Talk 05:03, 8 July 2009 (UTC)


 * Anonymity? You are C45207, we can all see that, we can't see your IP address, but the server and checkusers can. None of that is any different with or without the secure server. Gurch (talk) 12:10, 9 July 2009 (UTC)


 * With the secure server, your ISP/government can't easily tell what pages you're requesting. Pseudomonas(talk) 10:37, 18 July 2009 (UTC)

I feel as though we've drifted a bit from the original suggestion... A few questions: Thanks. &mdash;C45207 | Talk 17:09, 18 July 2009 (UTC)
 * Does Huggle insert the and related warnings itself, or does an editor add them manually?
 * If Huggle automates the insertion, where is that code? I can't seem to find any references to "uw-huggle" in the source.

Huggle randomly freezing up for no explainable reason.
Huggle lately just freezes for no apparent reason. It can be reverting something, going to the next diff, or if someone else reverts an edit it's been known to freeze up loading the next version. It has never done this before until the last couple days. Half the time it recovers and I am able to use it again, but sometimes it just irrecoverably locks up and I have to kill it via the task manager. Could someone please look into this? Thanks. <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 17:44, 7 July 2009 (UTC)

Invalid token errors
When attempting some reverts with Huggle 0.9.2, I'm getting a message from Huggle about an invalid token. The revert fails. If I try again, the same message comes up (in the log pane at the bottom of the screen), and the revert fails once more. This seems intermittent—sometimes, things work just fine. Any explanation for the meaning and cause of this error?

This apparently came up before (Huggle/Feedback/Archive 10), but the meaning or cause of an invalid token message wasn't explained. <b style="font-family:Constantia; font-size:medium; color:#0077bb;">TheFeds</b> 00:41, 8 July 2009 (UTC)


 * I think invalid token errors mean you've been logged out (perhaps your session expired). Restarting huggle should fix it. Calvin 1998 (t·c) 02:46, 8 July 2009 (UTC)


 * Is there any other possible cause? It's happened immediately after beginning a Huggle session (first attempted revert). Other times, it just happens unexpectedly during use. Incidentally, restarting Huggle solves the problem temporarily (until it happens again...).<b style="font-family:Constantia; font-size:medium; color:#0077bb;">TheFeds</b> 05:00, 8 July 2009 (UTC)


 * I don't know of any other possible reasons, although Gurch probably does. Calvin 1998 (t·c) 06:25, 8 July 2009 (UTC)


 * When that happens to me, I just open the diff up in a browser, and click the rollback link... Surprisingly virtually every time that this happens to me nobody has reverted it yet, so it would seem that multiple people are experiencing the problem on the same page... <b style="font-family:Segoe Print; color:blue;">Until It Sleeps</b> <sup style="font-family:Segoe Print; color:green;">Wake me 11:55, 8 July 2009 (UTC)


 * Probably the same reason people keep getting errors about their session data being wrong when it isn't (when editing in the normal way) Gurch (talk) 12:11, 9 July 2009 (UTC)

Another error
I got this error message, I could still edit and use the program though,

NullReferenceException: Object reference not set to an instance of an object. at Huggle.Misc.FindString(String Source, String From, String To) at Huggle.Processing.ProcessRc(String Result) at Huggle.Requests.RcApiRequest.Done at Huggle.Requests.Request.ThreadDone at Huggle.Misc.CallbackInvoke(Object TargetObject) – Zntrip 06:23, 8 July 2009 (UTC)


 * Grr... I've tried to fix this exact problem about three different times. But it always comes back... Calvin 1998 (t·c) 06:26, 8 July 2009 (UTC)

Problem report
I received the following message at User talk:Wtmitchell:

"I have undone your edits because WP:SSP has been merged with WP:RFCU into WP:SPI. Since you performed that addition using Huggle, you should inform the tool maintainer for this bug. <b style='color:#0000FF;'>OhanaUnited</b><b style='color:green;'>Talk page</b> 20:03, 11 July 2009 (UTC)" Wtmitchell (talk) (earlier Boracay Bill) 21:52, 11 July 2009 (UTC)


 * I've disabled the sock-report feature until Gurch can sort this out and make sure it'll work. Calvin 1998 (t·c) 22:30, 11 July 2009 (UTC)


 * Ah, pointless page renames. where would we be without them Gurch (talk) 22:38, 12 July 2009 (UTC)

Crashing
Huggle is crashing on its second start up on every version whenever it loads the message files. Any ideas? —Preceding unsigned comment added by Ipatrol (talk • contribs)


 * yeah, stop using it. use that abuse filter that you all love so much Gurch (talk) 19:58, 14 July 2009 (UTC)

Not... helpful. If you want to stop paying attention to Huggle, go ahead. We'll just keep on working.--Ipatrol (talk) 14:13, 17 July 2009 (UTC)

Overwriting Twinkle edits?
In the past day or so, I've come across 2 instances of Huggle performing the same action as me immediately after I did so. In both cases, my edit was overwritten by the Huggle edit. In the first case, it was reporting a vandal to AIV. The second case is me warning a vandal, then the user immediately vandalizing again and being reverted by a huggle user. In both cases, Huggle overwrote what I did. Although it makes little difference as far as the action itself is concerned, it might be a problem if Huggle overwrites an edit with a different intention than the Huggle edit. It might be caused by the server lag we're experiencing, though. &mdash; Ledgend  Gamer  02:56, 15 July 2009 (UTC)


 * yeah, this used to not happen, but now it does. Things would indeed be a lot easier if it wasn't for lag of various varieties, but they would still go wrong sometimes Gurch (talk) 14:36, 16 July 2009 (UTC)

SSP
I received the following notification: "I have undone your edits because WP:SSP has been merged with WP:RFCU into WP:SPI. Since you performed that addition using Huggle, you should inform the tool maintainer for this bug. <b style='color:#0000FF;'>OhanaUnited</b><b style='color:green;'>Talk page</b> 20:03, 11 July 2009 (UTC)" Wtmitchell (talk) (earlier Boracay Bill) 03:49, 15 July 2009 (UTC)
 * You posted this exact same thing 4 days ago, 2 sections above... A le_Jrb <sup style="color:blue;">talk  08:40, 15 July 2009 (UTC
 * And again right below it on the same day which I removed because it seemed accidental but not so much now. In case you did miss it, Calvin 1998 disabled the sock reporting abilities until Gurch gets a fix done. treelo  <sub style="color:#D2CDC6;">radda  08:45, 15 July 2009 (UTC)


 * Ah. My mistake. Something, probably Huggle and/or a notification while I was going through my watchlist must have notified me of a new talk page message and I must have, somehow mistakenly gone to that SSP section of my talk page. I'll try to keep this in mind in case that happens again. Wtmitchell (talk) (earlier Boracay Bill) 00:02, 16 July 2009 (UTC)

Updating Warnings
Would it be possible to include more of the warning templates in future releases? I would particularly like to see "Addition of unsourced or improperly cited material" available as an option to use. Thanks. HarlandQPitt (talk) 20:19, 18 July 2009 (UTC)


 * I requested the same here back in March, and was ignored. :(   — Jeff G. (talk&#124;contribs) 16:09, 19 July 2009 (UTC)


 * If you click the pull-down arrow next to the revert/warn button (that leftmost/topmost button with exclamation point in triangular frame), then click "Advanced," a very similar warning is available from the "Revert summary" pull-down menu. It is, "Reverted addition of dubious unsourced content."  To have that be available as a top-level choice would make it more accessible, which speaks to your point. Newportm (talk) 18:21, 19 July 2009 (UTC)

Not working
When I logged in, the interface came up, but no recent changes were being shown, so I switched to API. With API, recently changed pages are appearing in the queue, but not on the screen. Is this happening to anyone else? If so, has anyone found a way to fix it yet?  Intelligent  sium  15:26, 20 July 2009 (UTC)
 * I have to ask, did you try a single click on the blue "next article in queue" button? Newportm (talk) 20:13, 20 July 2009 (UTC)

Huggle struggling with some talk pages
Sometimes when trying to send a message to a user I get "object reference not set to an instance of an object". I've been trying to detect a pattern so as to give a more helpful report, but I don't recognise one yet. Let me know if you need more information. --bodnotbod (talk) 15:02, 29 July 2009 (UTC)


 * Yeah, if you get an error report, post the entire thing up here. Calvin 1998 (t·c) 02:02, 30 July 2009 (UTC)


 * I've seen this numerous times. I've presumed, and I think have observed in several instances, that the reference was to a nonexistant article (e.g., one which had been deleted during my Huggle session). Wtmitchell (talk) (earlier Boracay Bill) 07:31, 31 July 2009 (UTC)


 * Generally, yes. But occasionally it's a hiccup somewhere else in the system. Either way the problem needs to be addressed. Calvin 1998 (t·c) 03:54, 5 August 2009 (UTC)

Preview not working
The last few times I've tried editing a page and then clicking the preview tab the preview does not appear. The window displays as blank. --bodnotbod (talk) 15:02, 29 July 2009 (UTC)

Error
NullReferenceException: Object reference not set to an instance of an object. at Huggle.Processing.ProcessContribs(String Result, User User) at Huggle.Requests.ContribsRequest.Done at Huggle.Requests.Request.ThreadDone at Huggle.Misc.CallbackInvoke(Object TargetObject)

Got this today; not sure what page I was on when it happened, though. Closed HG. Matt Deres (talk) 17:46, 2 August 2009 (UTC)
 * I believe this is a known issue. <font face="Segoe Print"> UntilItSleeps <sup style="color:green;">Public PC   14:45, 3 August 2009 (UTC)


 * Indeed. Grr... Calvin 1998 (t·c) 18:26, 3 August 2009 (UTC)

Request: Getting it to stay out of talk pages
The owner of the talk should be able to remove the text without it butting in.--IceHunter (talk) 19:24, 4 August 2009 (UTC)


 * You should be able to set the namespaces listed in the preferences. If that doesn't work... well, that's a whole new can of worms... Calvin 1998 (t·c) 19:56, 4 August 2009 (UTC)

Edit summaries
Please forgive me if this has been raised before or I am missing something glaringly obvious, but I personally dislike the standard edit summary for vandalism reverts. Wouldn't it make more sense that the summary should indicate that the edit was vandalism? Maybe I'm missing information on how to customize this. --    bsmithme    00:37, 5 August 2009 (UTC)


 * Everyone who uses Huggle on English Wikipedia has to have rollback enabled (be a member of the "rollbacker" group). Huggle's simple vandalism reverts use the rollback functionality of Mediawiki software to make the revert happen.  Also, all use of rollback is supposed to be on vandalism.  This is consistent with WP:RBI.    — Jeff G. (talk&#124;contribs) 00:50, 5 August 2009 (UTC)


 * Understood, thanks. Actually the more I think about it the more I realized my logic was non-sequitur because when identifying vandals, editors who don't issue notices to vandals won't be looking at revert reasons in the first place. --     bsmithme    00:56, 5 August 2009 (UTC)


 * Jeff, that's not true, huggle uses the API and supplies its own summary, however, I don't believe you can change it in preferences. You are right, though, in that reverts are assumed to be on vandalism unless otherwise stated (in accordance with the rollback policy). Calvin 1998 (t·c) 03:48, 5 August 2009 (UTC)

Error with warning
This edit attempted to substitute a non-existent template. The correct template should be "huggle/unsor-3", not "huggle/unsor3". 2help (message me) 17:30, 11 August 2009 (UTC)


 * ✅ (fixed) via this edit.   — Jeff G. (talk&#124;contribs) 14:27, 12 August 2009 (UTC)

Nonexistent template?
Eh, what's going on here (also happened here)? - sesu <font color="#b22222">PRIME  02:23, 15 August 2009 (UTC)


 * Per these logs, Template:Huggle/warn-unsor-1 and Template:Huggle/warn-unsor-2 were deleted by . It would be great if they were restored.    — Jeff G. (talk&#124;contribs) 03:48, 15 August 2009 (UTC)
 * Hmm I deleted the redirects, Not quite sure how i managed to also delete the pages i had just created, Now restored. Thanks for the heads up.  ·Add§hore·  <sup style="color:black;">T alk T o M e ! 09:23, 15 August 2009 (UTC)

New template
Is it okay if we add another template for final warning for removal of content?

It could be like this:

This is your last warning. You will be blocked from editing the next time you remove content from pages, as you did with [ this edit] to :.

Chevy  Impala   2009  01:03, 18 August 2009 (UTC)

Not Warning Users Error
I can revert pages, but quite often the user doesn't receive a warning.--Katieh5584 (talk) 10:52, 19 August 2009 (UTC)

I have tried uninstalling and reinstalling Huggle, but it makes no difference.--Katieh5584 (talk) 20:01, 23 August 2009 (UTC)

Bug
Huggle just overwrote my AIV submission, which I submitted with Twinkle. I don't know if this is just a one-time bug or what. Ten Pound Hammer, his otters and a clue-bat • (Many otters • One bat • One hammer) 00:17, 20 August 2009 (UTC)
 * Looks like both reports came in at the same time, which should explain it. – Juliancolton  &#124; Talk 00:26, 20 August 2009 (UTC)
 * See . SUL (talk) 11:46, 20 August 2009 (UTC)

Feature request: hotkey for Revert&Warn(Advanced)
I'd quite like a hotkey to bring up the box for revert-and-warn with custom warning levels and edit summary. If I could pre-define edit summary-and-warning combos (there are a bunch that I keep wanting, like "removing speedy deletion notifications"-and-"vandalism-n", or "Please don't name this person's children-see WP:BLPNAME"-and-"blp-n") and assign hotkeys to them, that'd be even more wonderful, but I can see that'd be more work to implement. Pseudomonas(talk) 12:00, 20 August 2009 (UTC)

Ignored pages list.
A user applies for and is granted roll back rights. The first thing he does is type some test text into Wikipedia:New admin school/Deleting/delete. What with the page apparently not being on the ignore list, and the user not white listed, the page pops up in my huggle session. Seeing that it is gibberish, I immediately revert it before looking at the page title and warn the user. How silly of me. Can we add pages like this to the ignored pages list? (btw user is now white listed). Martin 4 5 1  (talk) 00:21, 21 August 2009 (UTC)
 * Done. Next time you can just do it yourself. Calvin 1998 (t·c) 01:06, 21 August 2009 (UTC)

Failed to retrieve diff
I'm getting loads of "Failed to retrieve diff of ' ' messages. There seem to be two reasons given: "no response" and "request timed out". Sure enough, hardly any edits are showing up on screen. Any ideas? 10metreh (talk) 18:16, 26 August 2009 (UTC)

Blocking Weirdness
I'm getting some unexpected and undesirable side effects when blocking users using Huggle. I got the block prompt shown at this URL:

http://www.imagebam.com/image/1d1e6946953409

My understanding of the wording "Block editing of talk page by this user" would be that by leaving it blank, the user would still be able to edit their talk page, which is the normal procedure. However, accepting those very same parameters resulted in this block:

http://en.wikipedia.org/w/index.php?title=Special:Log&type=block&page=User%3A62.149.141.55

This has been going on silently for some time, it was only when User:C.Fred brought it to my attention that I became aware of it however. Am I the only one getting this behaviour, or am I making a monumental misunderstanding somewhere? Lankiveil (speak to me) 06:23, 28 August 2009 (UTC).


 * Note that I also blocked a user and checked that box on, and this was the result. Seems broken no matter what I do.  I've turned the functionality off for the time being to avoid any further errors, until this can be explained.  Lankiveil (speak to me) 22:20, 28 August 2009 (UTC).


 * No, you're not the only one experiencing it. It's an old bug; usually people revert vandalism with huggle but block using TW. -- Menti  fisto  09:33, 1 September 2009 (UTC)

Cannot download Huggle
I cannot download Huggle properly on Internet Explorer. Professor M. Fiendish, Esq. 02:47, 30 August 2009 (UTC)
 * You can't use it anyways. What are you worried about? Griffinofwales (talk) 03:00, 30 August 2009 (UTC)
 * I've tried to download it and the link is red. Why can't we use it? It doesn't mention anything about being a sysop-only tool (except on the Dutch Wikipedia site).  Dr Dec  ( Talk )    08:41, 1 September 2009 (UTC)
 * This doesn't work? -- Menti  fisto  09:25, 1 September 2009 (UTC)
 * I think the problem is that I need Roleback. Is that right?  Dr Dec  ( Talk )    09:28, 1 September 2009 (UTC)
 * Ah, yes, if that's the specific error. I've assigned it... try to see if it works now. -- Menti  fisto  09:33, 1 September 2009 (UTC)
 * Fantastic! It's working. I'll take some time to read the manual. Thanks Menti  fisto !   Dr Dec  ( Talk )    09:45, 1 September 2009 (UTC)

Reporting users/IPs glitch?
If me or someone else has already reported a user/IP, and I revert said user's/IP's edits again, instead if saying "Extending report for..." like it should, it keeps saying "The user has already been reported". Is this a bug? - Zhang He (talk) 04:26, 30 August 2009 (UTC)

Confusion over revisions
I attempted to revert at this edit with Huggle and was incorrectly warned that it would revert to a version by user 94.194.183.112 who had been "permanently warned" or some similar wording. I rolled the edit back with WP:Twinkle. Wtmitchell (talk) (earlier Boracay Bill) 01:23, 31 August 2009 (UTC)


 * In cases like this it is best to look at the previous edit as well, and in this case it was also a vandal edit. Click on the "Previous version [Z]" button, and then you can revert both in one go. If I find vandalism by more than one editor like this, I often check back until I see some good edits, or bring the page history up in a browser and use popups. Martin 4 5 1  (talk) 09:43, 1 September 2009 (UTC)

Notice of Non-maintainer update.
I've posted a patch on Issue 167 fixing the problems related to blocking users and other API options such as watching protected pages and so on. I've compiled a binary version here with these fixes that I have versioned 0.9.3. I'll give ample time for the maintainers to accept/reject my patch before posting my version and bumping the required versions. Q T C 09:44, 1 September 2009 (UTC)

Not enough tagging
I feel that HG needs more user notification options. Using improper humor (uw-joke), not adhering to mos (uw-mos). Also, some option needs to be added for notability. Manish <i style="color:green;">Earth</i>Talk • Stalk 13:58, 1 September 2009 (UTC)


 * I agree. Don't get me wrong; Huggle is far better than Twinkle, but it does lack the depth of warning topics that TW has. I find myself simply reverting in HG, then copying-and-pasting the article name in my web-browser so I can search the edit history for the user name of the editor of the edit I've undone, so that I can use a Twinkle warning on his page. All anti-vandalism tags should be included.  Dr Dec  ( Talk )    20:54, 1 September 2009 (UTC)


 * Gurch has talked about this before somewhere. He said that Huggle is only for real vandalism since it uses the rollback feature, and not for stuff like MOS. Twinkle is different since anybody can use it, and so there is more leniency. Griffinofwales (talk) 21:12, 1 September 2009 (UTC)


 * Yeah, there are also some warnings Twinkle has that Huggle doesn't, such as "Not signing posts" and "Erasing sandbox header" warnings. - Zhang He (talk) 21:36, 1 September 2009 (UTC)


 * But if you add the rollback usage of HG to the tagging coverage of TW then you'd have the mother of all anti-vandal programs. I'm sure that it wouldn't take much to add the warnings. Surely rollbackers should be given more features, and not less?  Dr Dec  ( Talk )    21:56, 1 September 2009 (UTC)


 * No no no no no. Rollback is to be used to "revert edits that are clearly unproductive, such as vandalism; to revert content in your own user space; or to revert edits by banned users" and nothing else. If you use Huggle to revert for "Using improper humor" or "not adhering to mos" you're at best going to find yourself stripped of rollback, and quite possibly explaining your case via an unblock template. – iride  scent  22:10, 1 September 2009 (UTC)


 * Okay, good point!  Dr Dec  ( Talk )    17:29, 3 September 2009 (UTC)


 * This is a bad idea... The last thing Huggle needs is more bloat to slow it down...  Until It Sleeps  <sup style="color:green;">alternate   01:11, 2 September 2009 (UTC)
 * Another thing (This DOES follow the rules for rollback), HG needs support for the 4im templates (just a few). This won't bloat HG as its just one more menu item for vand-4im. Manish <i style="color:green;">Earth</i>Talk • Stalk 02:23, 3 September 2009 (UTC)
 * Select "Blatant vandalism" rather than just "Vandalism" to issue a final warning straight away. Gurch (talk) 11:08, 3 September 2009 (UTC)
 * Can't find it. Where is it? Manish <i style="color:green;">Earth</i>Talk • Stalk 12:23, 4 September 2009 (UTC)

New page edit conflict resulted in overwrite
See this edit. Huggle apparently overwrote a new-page edit with its own new page. (Minor issue in the context of a great tool.) -- Tcncv (talk) 23:44, 1 September 2009 (UTC)


 * Here is another example of a Huggle edit conflict and overwrite – this one not involving a new page. (Note: Wikipedia servers were intermittently showing 10-30 second delays, which may be a factor.)  -- Tcncv (talk) 01:21, 2 September 2009 (UTC)


 * Huggle removed one warning and replaced it with a new one tonight. Here.  Ron h jones (Talk) 00:09, 8 September 2009 (UTC)


 * It appears that, during race conditions, unlike editing by web browsers, editing with huggle does not result in an edit conflict, but rather it results in huggle failing to notice the previous edit. If huggle could detect edit conflicts as is done with editing by web browsers, that would IMHO be more user-friendly all-around.


 * It would also be more user-friendly if huggle were to keep retrying failed communication attempts with Wikimedia (including loading of user whitelist and message files) and Freenode systems (perhaps with exponential backoff and performance metrics).   — Jeff G. (talk&#124;contribs) 01:49, 9 September 2009 (UTC)


 * I took a look at the source code and it appears that the problem may be due to the way that the edit token is used in the PostEdit method. If I understand the code correctly, the talk page content is retrieved and edited elsewhere and PostEdit is called to save the updated talk page content.  PostEdit retrieves an edit token and then uses that edit token save the update.  The problem may be that since the edit token is not one that was retrieved with the original page content, mediawiki has no way to detect the edit conflict.


 * I think it would be better to retrieve the edit token at the time the original talk page content is retrieved, and later use that same edit token for the update in PostEdit. If an edit conflict is detected, it might be necessary to restart the entire warning process – retrieving a fresh copy of the talk page (and a new edit token), reevaluating all the conditions for posting a warning (last warning level, time of last warning, etc.), and selecting a possibly different course of action based on the changed circumstances.  Or..., you could simply notify the operator that no warning was posted due to an edit conflict.  -- Tcncv (talk) 03:47, 11 September 2009 (UTC)


 * Yes, Huggle does not check for edit conflicts. Edit conflicts arise when someone saves a page while someone else is editing it. Unlike normal edits, Huggle does not spend any time "editing" the page but merely submits the new content. It thus doesn't check for edit conflicts, and this was never a problem until about eight months ago, when it started doing this all the time. The cause of this is on the server side. There is not just one server back there containing the wiki's state. There is one server containing the definitive version of the wiki's state and dozens more containing copies of it. Any data Huggle asks for is provided by one of these copies. All the copies are out-of-date slightly; it used to be that "slightly" was mere milliseconds, and so if you asked what the most recent edit to a page was, it would tell you. Nowadays the data it returns is often several seconds old and the delay can be much higher than that. You could say "well just make it check for edit conflicts" but the problem is a lot deeper than that; if the server cannot be relied upon to give the right information about the wiki's state then pretty much everything else Huggle works from goes out the window too. I came across this problem again when I tried to convert Huggle to use the API for diffs, but it's just impossible – a revision comes through the recent changes IRC feed, which is updated as part of saving the edit and so is always up to date, Huggle asks the API for a diff of that revision, and the API goes "huh? what revision?" because as far as it's concerned, the revision doesn't exist. Ask it ten seconds later, and it will exist, but meanwhile the Huggle user is irate that their diff hasn't shown up and goes and moans here that "new versions of Huggle are too slow". Ask for a diff through the UI and, as far as I can see, if it can't find it on the server that's handling the request it'll go to the master server for it. So if it tells you the diff doesn't exist, it really doesn't, not just it might do but we don't know. So Huggle continues to do that, and I have to do fugly screen-scraping instead of using the API. Gurch (talk) 16:32, 11 September 2009 (UTC)

"Huggle needs to close"
I sometimes look back at prior edits by a vandalizer by working my way along the items in the Contribs box from right to left. Often, on clicking a box at some point in the list, I'm told that Huggle has encountered a problem and needs to close. Wtmitchell (talk) (earlier Boracay Bill) 07:45, 2 September 2009 (UTC)
 * happens to me too. If I revert an edit made by a user at say 5:00, and then try to revert ans edit made to a different page byerror report. Manish <i style="color:green;">Earth</i>Talk • Stalk 12:55, 2 September 2009 (UTC)the same user at 4:45, HG gives an r

Watchlisting problem
Huggle is automatically watchlisting user talk pages where I have issued warnings. This is the first time I came across this, and I don't have this watchlisting enabled in my options either. Any idea what is causing this, and how to fix it? ≈ Chamal talk ¤ 11:45, 2 September 2009 (UTC)
 * I've been presuming that this happens if "Add pages I edit to my watchlist" is enabled in the User edit preferences. Wtmitchell (talk) (earlier Boracay Bill) 02:14, 3 September 2009 (UTC)
 * I haven't got that enabled in my preferences, and watchlisting is not enabled in my huggle options either. ≈ Chamal talk ¤ 11:39, 3 September 2009 (UTC)
 * Are they all new pages? I have that problem because I have 'Add pages I create to my watchlist' checked in my preferences, so every time I create a new talk page, it shows up on my watchlist. If they aren't all new pages, then I have no idea what's wrong. <font style="font-variant:small-caps;"> Little Mountain  5   15:36, 5 September 2009 (UTC)

Default browser problem
Firefox reports that it is my default browser. I typically use huggle with a firefox window logged in to WP. When I right-click on an article link in the huggle window and open it in a new window, it opens with IE (and not logged in to WP). Wtmitchell (talk) (earlier Boracay Bill) 03:22, 3 September 2009 (UTC)
 * Doesn't happen to me. I use CHrome as default and it works fine.
 * I changed the default to google Chrome, shutting down and restarting Huggle after the change, and still see the problem. I only see the problem if I right-click, etc. as described above. If I left-click the window icon on the Huggle toolbar it uses the default browser I have selected. I'm using Huggle 0.9.2. 210.1.78.160 Wtmitchell (talk) (earlier Boracay Bill) 05:03, 3 September 2009 (UTC)
 * Probably just weirdness with how Windows handles the link. If that is the case, we can't do anything about it (sorry). Calvin 1998 (t·c) 05:29, 3 September 2009 (UTC)
 * The internal browser element in Visual Basic uses the Internet Explorer rendering engine - if you right click there, you are using IE and new links will open in IE. You can't change this. A le_Jrb <sup style="color:blue;">talk  11:06, 3 September 2009 (UTC)

Error! Error!
Hello! I'm putting this here because it happened to me...


 * Hmmm...Similar error, but I can directly trace it to viewing my a dynamic list "Category:Tennis". (Notice Result instead of FindString) -- Also, this is version 0.9.2.

-- Mjquin_id (talk) 15:49, 19 September 2009 (UTC)

Revert and warn
If I click the revert and warn button (NOT the menu--I click the red dot with an exclamation), HG reverts, but does not warn. Could this be fixed? Manish <i style="color:green;">Earth</i>Talk • Stalk 04:02, 3 September 2009 (UTC)


 * Some questions to clarify the issue - (1) Does this happen all the time, or are there particular cases in which it happens? (2) Is there some sort of error message in the log? Does it say the user was warned? Does it say anything at all about warning? Thanks. Calvin 1998 (t·c) 04:06, 3 September 2009 (UTC)


 * Yeah, Huggle won't warn if the editor hasn't edited since their last warning, has been warned less than 10 seconds ago, or if they've already been warned for the same act of vandalism. (I leant this from the auto-generated comments in the bottom left corner). This is because two or more of us might be trying to revert and warn at the same time and a user shouldn't get multiple warnings for one act of vandalism. Also, I notice that sometimes (usually level 1 warnings) that I don't get a "user has been warned" type message, but when I go to the user's user page I find a signed warning.  Dr Dec  ( Talk )    17:22, 3 September 2009 (UTC)
 * It happens all the time, and the red entry in the bottom list doesn't appear. No error message appears. It took me a while to notice this, and I noticed it when i saw that my contribs consisted of reverts but no warnings. Manish <i style="color:green;">Earth</i>Talk •  Stalk 12:19, 4 September 2009 (UTC)

Does Huggle really use Roll-back?
Maybe I'm using it wrong, but when I revert and warn Huggle seems to only go back to the last version. When the same user has made several consecutive acts of vandalism against a page I find myself "rolling back" to the penultimate act of vandalism. The edit history, often quite embarrassingly, credits me with adding an uncouth line or other (sometimes the vandal replaces his rubbish with more rubbish and I end up restoring the last lot of rubbish). Roll-back, when used on its own, takes back all of the edits by that editor. Shouldn't Huggle? Or am I, quite probably since I'm new to this, making a silly mistake? Dr Dec ( Talk )    17:16, 3 September 2009 (UTC)


 * Do you have an example in mind? Link? A le_Jrb <sup style="color:blue;">talk  21:13, 3 September 2009 (UTC)


 * No, I don't have any links at hand. My question was directed towards someone that wouldn't need links, i.e. someone understanding the inner workings of Huggle and thus someone that might be able to answer my question outright.  Dr Dec  ( Talk )    21:45, 3 September 2009 (UTC)


 * Whey - that was some pretty speedy re-editing. I had an excellent, cutting sarcastic remark planned that I now don't need. :) huggle will use the built-in rollback if it can, which is virtually always. It won't if you're not viewing the latest change, if you've been browsing through the history or a user's contribs for example. If you come up with a specific example where it did it wrong, and think the above wasn't true, I would be able to give you more advice - thus my original remark. I'm not sure what it was about that comment that implied I knew nothing about the program. Perhaps I have to work on my clarity. A le_Jrb <sup style="color:blue;">talk  22:03, 3 September 2009 (UTC)


 * It seems that I need to use the red arrows to go back to the first case of vandalism and then undo it. Huggle will rollback from the current version to the version that's in the window. It was only going back one edit because I only had the last two edit histories on my screen. If I click the red arrows a few times then it'll rollback several versions. It was just me being stupid after all!  Dr Dec  ( Talk )    15:06, 4 September 2009 (UTC)


 * Say a user vandalizes a page n times in a row (the last n edits). If n < 3, pressing the revert button while showing any diff will revert those one or two edits, but if n ≥ 3, pressing the revert button while showing one of the middle edits (edit x where 1 < x < n) will only revert edits x through n, ignoring 1 through (x – 1), and may even get you a warning to confirm what you are doing.  While I think this behavior is somewhat silly and annoying, at least it is consistent.  Clicking on the toprightmost icon (the last edit for that page) or the third blue arrow and then pressing the revert button is a workaround for this behavior (to revert all n edits).    — Jeff G. (talk&#124;contribs) 03:04, 5 September 2009 (UTC)


 * Without this behaviour, it would be impossible to revert some but not all of a user's edits, which is sometimes necessary. Gurch (talk) 22:26, 5 September 2009 (UTC)


 * Ah, okay. I see. Thanks!  Dr Dec  ( Talk )    06:52, 7 September 2009 (UTC)

Huggle ap?
I think it would be REALLY cool if we were allowed to revert vandals on iPods. Also it would be really convient for some users.173.54.30.249 (talk) 21:06, 3 September 2009 (UTC)


 * Central to Huggle's workflow is reading large amounts of text at-a-glance. Doing that on a two-inch screen probably wouldn't be much fun. Gurch (talk) 21:35, 3 September 2009 (UTC)


 * Besides, do unregistered IP addresses even have rollback rights?  Dr Dec  ( Talk )    21:52, 3 September 2009 (UTC)
 * Unregistered accounts are not allowed to have user rights. Griffinofwales (talk) 23:56, 3 September 2009 (UTC)

Archive Index
I've added an archive index (link - with archive links at top of page). Indexes all archives and this page in one index with links to the articles. Only shows section heading, but might be useful. Index updates automatically.  Ron h jones (Talk) 00:22, 4 September 2009 (UTC)

Watching users
Many times, I notice that a user is vandalizing repeatedly, so I open a new tab and wait for him to edit again. The problem is that these tabs clutter up the interface, so I can't see the tab glow red when a change is made. I would like a feature for watching users/pages, in which you choose to watch the user or the page, then close the tab, and when the user does something, a tab showing what he did will open up. The watching need not be permanent, it is better if it is stored in the memory until HG closes instead of being stored on WP. Manish <i style="color:green;">Earth</i>Talk • Stalk 12:32, 4 September 2009 (UTC)


 * Hm. If you've already reverted or warned a user, any subsequent edits from them will show up near the top of the queue, so they should be easy enouhg to find. If what you're aiming to do is make sure you don't miss repeated vandalism, just taking edits from the queue should accomplish that. Gurch (talk) 14:27, 4 September 2009 (UTC)

Crash when requesting page protection
Huggle creates a nonspecific Windows error and closes when trying to request page protection. Huggle version 0.9.2, Windows Vista Home Basic.Alan (talk) 06:07, 7 September 2009 (UTC)

Many users, same revisions
One feature that has become quite annoying over time is that many different Huggle users may be viewing the same revision at the same time. So, while I'm checking a revision, I find that another Huggle user has reverted the revision. I mean, I see the revision take place whilst I'm reading the changes. This is a waste on time for everyone: there might be six Huggle users reading the same revision, and only the first one to act makes a change; the other five users' time is wasted. This leads to Huggle users scan-reading a revision and acting more quickly than they would like in order to make sure that they make the edit. To summerise: I propose that one revision can be seen by one user: once a user takes a job, it's his/hers until they hit space and move on. That revision would then be free in the pool of all revisions as it is now, so it would be checked. This would save a double, treble, or even quadruple overlap of users' time and may speed the process up by a factor of two, three, or even four. Clearly this change would make Huggle run more slowly which some users would, at first, be against; but once they thought about the time they'd wasted reading a revision which was Huggled before they had time to. Once they think about the gains to be had by pressure free, merit drivin revisions. They would surly agree that it's a good idea. Dr Dec ( Talk )    12:53, 7 September 2009 (UTC)
 * 1) Many Huggle users view the same revision at the same time.
 * 2) Many Huggle users' time is wasted on such an overlap.
 * 3) Some Huggle users edit faster so that theirs is the edit that counts.
 * 4) This leads to errors, and a general sense of vexation.
 * What happens if someone decides it isn't vandalism, or they don't want to revert. But it is. Alternatively, if a vandal got hold of huggle, changed it to remove the requirements (this is easy, it only requires the most simple knowledge of VB) and went through everything locking out the revisions, huggle would be essentially useless. And it would slow it down, which people wouldn't just dislike, they'd hate it. It's an interesting idea, but probably would never work: see this from ageees ago. A le_Jrb <sup style="color:blue;">talk  12:57, 7 September 2009 (UTC)
 * Who's talking about locking out edits? Once a decision has been made then the edit would go back into the pool (as I have already said). A few edits by the same user would be checked by several users for a while, so we would have the same overlap for a while. But we already have a whitelist of trusted editors that don't get reviewed by Huggle. The same would apply: we would have a whitelist of Huggle users that wouldn't get reviewed by Huggle. This change would replace the current delays with similar delays for a while, but once the whitelist bulit-up, then the delays would plumit. About the point "What happens if someone decides it isn't vandalism, or they don't want to revert. But it is." Well, what about the converse?! People often decide that revisions that aren't vandalism are! People often revert revisions that shouldn't be reverted! There's no real difference. In fact, if a few liberal Huggle users miss some problem edits then we've always got the Twinkle users to act as a safety net (which includes me too!) As for the point point about vandals having enough computer knowledge to crack Huggle, well if they could then they'd already be causing problems, and if they did then we've always got the sys-ops. They could rollback and block.  Dr Dec  ( Talk )    13:15, 7 September 2009 (UTC)


 * The main obstacle to providing this sort of functionality is knowing who is looking at what at any given time, which would require peer-to-peer communication between Huggle clients independently of the wiki itself. This would be very difficult to implement in such a way that it worked correctly for everyone, which it would have to do to be effective, and it would require me to set up and maintain my own server, which I don't have the resources to do.


 * Such a system would then have many problems. For a start, there would have to be some mechanism for explicitly indicating that revisions are good. Currently, there is no distinction between good revisions and revisions the user is unsure about; both are skipped over. Secondly, unless you're suggesting some sort of authentication mechanism whereby I distribute authentication keys only to trusted users, which I'm not doing even if I could, then the system would be trivial to exploit. A malicious user would simply keep taking edits from the queue and declaring them good. Or even just taking edits from the queue and then not passing judgment on them at all. There are all kinds of other issues with the actual implementation of it. Latency between clients can easily be much higher than the latency between the client and the wiki, and between the wiki's own database servers, both of which are already intolerably high at times. Several seconds would be the norm, and that is more than enough time for one client to take an edit from the queue and then another client to take the same edit before they've been notified that the first client had taken it, so you'd still have exactly the same situation anyway. And we haven't even got into what happens when someone takes an edit from the queue and then their connection drops or whatever. There are ways around these things but at the expense of time; I think you would be more annoyed if when you asked for a revision the client then spent five minutes synchronizing its state with all the other clients before showing it to you (and meanwhile the wiki would change and everyone would have the wrong state anyway).


 * I'm sorry for being so forthright, but did you actually read what I wrote earlier? For the third time: recent actions by Huggle would go into the queue; just like new revisions do. If the same user's Huggle actions are skipped over, i.e. not changed, after a given number of checks, then that Huggle user would join a Huggle whitelist. Or, as we have with normal revisions, we can choose to ignore edits by editors we deems as trustworthy. This is what we have for normal new edits: we have a whitelist of users and Huggle doesn't even bother to put those users' revisions into the Huggle queue: they are deemed trustworthy. All we need to do is to turn the Huggle machinery on itself for a little while (this excess would be balanced by the reduced overlap), but then after a while, once the Huggle whitelist built up there'd be very little of this Huggle cross-checking. As for the peer-to-peer, all we need if for Wikipedia to talk to Huggle and then Huggle to talk to the users. A job goes to Huggle, Huggle gives the job to a user. Instead of having a queue of jobs we would have a queue of users.  Dr Dec  ( Talk )    14:48, 7 September 2009 (UTC)


 * Yes, I did read what you wrote earlier. Specifically "I propose that one revision can be seen by one user: once a user takes a job, it's his/hers until they hit space and move on" and the stuff following that. In order for that to happen, when a user asks for a revision from their queue, all other Huggle clients have to instantly become aware of the fact that they've done that so they don't show the same revision to a different user. Merely viewing a diff is not something that is logged by MediaWiki, so this would all have to be handled by Huggle itself. And the implementation of this requires that Huggle clients be able to communicate with each other, which they currently don't; they only communicate with the wiki. You speak of "Huggle" as though it's a central entity. It isn't. It's a desktop application. You can't have "A job goes to Huggle, Huggle gives the job to a user" when there are multiple instances of Huggle none of which communicate with each other directly. Gurch (talk) 15:00, 7 September 2009 (UTC)


 * Just a side note (though i dont fully support the propsal at this time) you could also increase the requirements to actually get rollback. Though they are still pretty fair right now, just a thought. I do think that its annoying though when your edit doesnt go through becuase someone else is faster (and even more so when they make a mistake). The train of thought with this (and i may be wrong becuase im not using statistics or hvae them) is capable users who begin to use huggle for the first time get turned away when they see that their edits are not going through, but the same user always appears as undoing the edit. Ie, they find most of their edits dont count and some more experienced user racks in all the changes. So the train of thought by these new users may be, let the experinced users of huggle do it. I dont think changing the code could fix this, but perhaps a way to organize huggle editors. Have something like a 'team' of huggle users dedicated to a certain time of the day. There are always pockets of the day when few huggle users are working at the same time. Perhaps maybe even an info box telling you how many huggle users are activily editing (you can get some stats in huggle for this now). I think the way it is being run right now theres ways to improve but again, i dont see how changing the program itself will fix the way its evloved. Just throwing ideas out there.Ottawa4ever (talk) 14:17, 7 September 2009 (UTC)


 * It's a nice idea, but it seems to impose even more problems. Who can give the same time slot each day to use Huggle? How would we possible organise such a thing? So, what do we do? Organise a team of, say fifty, to patrol at the same time and exclude all other? That just makes Huggle short-handed. Do we organise a core of fifty users that will definitly be online and then anyone else can join in? Well, this would simply ramify this overlap problem. Making rollback harder to get doesn't make sense either: we're not talking about a shotgun license. What's the worst that a rollbacker can do? Undo multiple edits at a time? Well, a multiple revert can be rollbacked too! Obviously we don't want everyone to have it: that would be chaos, but we certainly don't want some modern day class system, some us-and-them system, here on Wikipedia. Seriously, my original idea still seems to hold water, despite some minor objections.  Dr Dec  ( Talk )    14:32, 7 September 2009 (UTC)


 * Minor objections? OK, you explain how the client protocol is supposed to work... Gurch (talk) 14:40, 7 September 2009 (UTC)

I've identified a real problem here, and offered a plausable, workable solution. Please stop trying to shoot me down without offering an alternative. Everyone's saying "Oh, that would never work...", but no-one's saying "What about this insead..." The staus quo is satisfactory. I would rather push for more that satisfactory solutions. I'm trying my best here. Gurch's comment is indicative: he's just picked up on my one phrase about minor objections, instead of trying to understand what I'm getting at. We're on the same team here. This is not a war. I've tried my best, now why don't some other people put their intelligence into trying to make my ideas practicable instead of just finding holes? Please! Dr Dec ( Talk )    14:48, 7 September 2009 (UTC)


 * The holes prevent me coming up with a workable implementation of your idea. I am not aware of a way to make it workable. Gurch (talk) 15:02, 7 September 2009 (UTC)


 * Please tell me in explicit detail exactly what the holes are. I'm sure that we could find solutions for each and every one of them. With all due respect Gurch, you are a single person. We can't expect you to solve every problem single-handedly. But as a team, I'm sure we could work towards a solution.  Dr Dec  ( Talk )    15:05, 7 September 2009 (UTC)


 * The biggest and most important problem is providing some sort of communication channel between Huggle clients. Because some clients are behind restrictive firewalls, this would have to be client/server HTTP; Wikimedia does not and is not going to provide this functionality, so a separate central server would be needed. This would completely change the architecture of the application, and render it useless if the server went down. You seem to be visualizing Huggle as some central entity that sits between the wiki and the user such that the user doesn't communicate directly with the wiki at all. Even if some sort of centralized inter-client communication were set up as you suggest, that wouldn't be the case, as clients would still have to retrieve recent changes and diffs and send edits. Unless you're suggesting all that is proxied through the central server, and I'm certainly not paying the bill for that kind of bandwidth usage.


 * In short, copies of Huggle are independent desktop applications and are staying that way. Gurch (talk) 15:16, 7 September 2009 (UTC)


 * Okay, so Wikipedia won't offer any more functionality. This is understandable given that it's a charity. The new edits come to us users via Huggle. Every job is sent to every user. What's stopping one job being sent to one user? A queue of users and a pool of jobs, instead of a pool of users and a queue of jobs? My laptop recieves an edit, I change it, and my changes get uploaded. So it wouldn't be at all difficult to change things to make it one user to one job. (All other issues of reliability have been addressed above.) It seems that my idea is theoretically possible. It's not the idea that's limited, it seems to be the resources available to us. Maybe if we pushed Wikipedia and showed our value then they may offer more functionality.  Dr Dec  ( Talk )    15:55, 7 September 2009 (UTC)
 * You don't really seem to understand how the system works. There is no central 'pool' of jobs. There is an IRC channel where all changes that get made to Wikipedia are listed as they happen. These are picked up by hugglers - all hugglers. They are displayed to users. The end. In order for each change to only be picked up by one copy of huggle, that copy would need to somehow tell all the others that it was taking the edit. How do you propose it does this? That is the problem. Also, this would be slow - because an extra channel of communication would be needed. You would need to wait for all the other huggle copies to register and then confirm that they aren't to display the edit, before displaying it. This is also where reliability problems occur - what happens if two copies decide to take the same edit at the same time, and both inform all the others at the same time, and both then display it before they are aware they shouldn't. What now? It really just doesn't work properly. The only way would be to have a filter that handles this on a central server before sending it to huggle clients, and this requires a central server which no one is going to provide. A le_Jrb <sup style="color:blue;">talk  16:23, 7 September 2009 (UTC)
 * Did you read my last post? (I'm starting to get grumpy having to repeat everything that I've already said.) It has already been established to be a functionality problem. If Wikipedia changed the way that it sent out the information then we might be able to solve the problem. Wikipedia feeds all of the jobs out through the IRC channel. Well, instead of Wikipedia giving everyone the jobs; my laptop could contact Wikipedia and Wikipedia could give it a job. It's no more complicated than a central email system. Things like that were done more than a decade ago: it's pre-1999 information systems.  Dr Dec  ( Talk )    16:54, 7 September 2009 (UTC)


 * So you're saying that Wikipedia itself should only let one person look at each revision? I don't think that's a good idea... Gurch (talk) 17:09, 7 September 2009 (UTC)
 * No! That's not what I'm saying and you know it. I'm talking about Wikipedia's information exchange with Huggle. Anyone's free to use Wikipedia in the normal way and see what ever they may choose to see.  Dr Dec  ( Talk )    17:18, 7 September 2009 (UTC)
 * (ec) Of course I read it. I expect other people are getting annoyed that you keep asking that, then repeating yourself, despite people trying to explain things to you. Changing the way Wikipedia sends out information is impractical and silly. You talk about 'asking' Wikipedia for a job. Define job! If you mean asking it to send out one recent change, you can do that - but it won't limit that change to one person. Anyone who asks for it will get it. You want there to be a server system where Wikipedia can remember who has received a change, and not send it out to someone else? What a (massive) waste of database space. It has no other possible use. And what if someone says that revision isn't vandalism when it is? Wikipedia wouldn't send it out again! There is an extension for patrolling changes, but we don't use it here because it's rubbish and essentially useless - open systems such as the current huggle are far superior.


 * You asked, and I quote, 'What's stopping one job being sent to one user?' I answered you. Then you accuse me of not reading your 'post'. Seriously... A le_Jrb <sup style="color:blue;">talk  17:10, 7 September 2009 (UTC)


 * I'm sure that people aren't getting annoyed accept yourself, and maybe Gurch. It's interesting to read your comments. I don’t, not for one second, try to parallel my thoughts with the theory of an expanding universe. But, its proponents met such hostility for many years. People don't like new ideas. I was simply trying to help, simply giving some thoughts of mine. It's the same argument over and over again. I'm putting forward a way to improve things and some users don't like change. Some users spend their time finding holes in the ideas that I've taken time to articulate. It's like any new idea: the champions of a new idea are always belittled and rebuked. But just wait. Like with any good idea: once enough people assuming good faith get behind a project they manage to iron out all of the creases. And those stalwarts steadfast against the idea find themselves saying: "Sh*t, he was right!". I see that there's no point trying to be helpful, trying to be thoughtful, trying to be anything. I withdraw from this discussion.  Dr Dec  ( Talk )    17:29, 7 September 2009 (UTC)
 * Annoyed? No, I find your comments mildly amusing - you are the one getting grumpy. If you feel the best way of preventing vandalism is to create a huggle-extension that stores revisions that have been viewed by a user and doesn't show them to anyone else, then go ahead and do it. You're taking the whole thing a bit seriously, to be honest - oObviously, it's great to be helpful. This idea happens to be technically impractical - maybe your next one won't be.
 * I do find it strange that you say how you don't parallel this idea with the idea of an expanding universe, and then go ahead and do so, though. :) A le_Jrb <sup style="color:blue;">talk  17:42, 7 September 2009 (UTC)
 * Any edits would be put back into the pool for checking. I've made this point four times now.
 * I don't, and didn't, compare my idea with the idea of expanding universe: I draw the parallel between those that disagree. Again this is clear above.  Dr Dec  ( Talk )    17:48, 7 September 2009 (UTC)

I would ask that any further posts address, as they originally should have, the following key points in a positive way: Dr Dec ( Talk )    17:54, 7 September 2009 (UTC)
 * 1) Many Huggle users view the same revision at the same time.
 * 2) Many Huggle users' time is wasted on such an overlap.
 * 3) Some Huggle users edit faster so that theirs is the edit that counts.
 * 4) This leads to errors, and a general sense of vexation.


 * I have to say that I would not want the functionality that you are proposing. I often watch a specific editor or page, and want to be able to see the edits that I choose to see. After reverting an edit, I often check other edits by the same person, and revert them as needed. I do not want to be locked out from seeing edits by someone who is vandalising.
 * Huggle usually prioritises the edits, so the ones most likely to be vandalism are at the top of the queue. These are the ones that need to be reverted first, so more eyes on those edits is better.
 * If you are finding that you are wasting your time, then don't use the default queue, use something else, or click on the edits halfway down the queue. This is how I first started using huggle.
 * With huggle, it is not about "whose edit that counts" it is about stopping vandalism. So what if someone reverts faster than you, the main thing is that the vandalism is removed.
 * If you are finding huggle vexatious, are you sure you should be using it?

Martin 4 5 1  (talk) 18:53, 7 September 2009 (UTC)
 * You make some good points, thank you! I also agree that it's not whose edit that counts, but some editors are driven by that and that is what causes some editors to skim-read and edit as fast as possible. But yeah, once again: you make some very good points.  Dr Dec  ( Talk )    21:06, 7 September 2009 (UTC)


 * OK, I'll address those points.


 * Yes, sometimes multiple people view the same revision at the same time. This in itself is not a problem.
 * In my experience the amount of time wasted is not that great; admittedly my experience was mostly back in 2007 when there was more editing and fewer people to deal with it. If you find that you're not having much of an effect while patrolling owing to others getting there first, that means that there are enough people patrolling already, so your time is likely better invested in a different maintenance task (not like there's any shortage of those). This would be the case regardless of how the revisions were distributed; if there's more than enough people patrolling, any attempt to share out the work would result in each individual not having a full workload, so they'd most likely get bored waiting for the next revision to arrive all the time, and switch to something else for a while to let the queue build up for a while before going back to it. This would actually increase the average time vandalism remained in place, which would be a bad thing.
 * Not a problem as far as I can see, assuming that your goal is for Wikipedia to be free of vandalism. If your goal is to inflate your edit count, then yes this is a problem.
 * I don't see how this leads to errors. Someone correctly reverting vandalism but being beaten to it by someone else also correctly reverting vandalism is not an error. Errors certainly abound due to people not paying attention, but I don't see how this is a contributing factor to that.

Remember, Huggle was designed with the intention of having enough throughput to allow one person to check the whole wiki for vandalism in real time (and at 2007 editing levels). During less busy times back then I frequently got bored waiting for more edits to arrive, and that was when I was the only one using Huggle, and sometimes the only one patrolling recent changes at all. This is by design, and it is a good thing, as it means there's less vandalism. Gurch (talk) 20:56, 7 September 2009 (UTC)


 * Thanks for your comments. I feel like you've actually listened to me. And, you know what? You've addressed each of my questions well. I wish we could have done this earlier. I see what you're saying, and you're probably right. So, keep up the good work! :o)  Dr Dec  ( Talk )    21:10, 7 September 2009 (UTC)

Behavior with 5,000 edits in queue
Huggle experiences severe difficulties once it hits 5,000 edits in queue: — Jeff G. (talk&#124;contribs) 03:40, 9 September 2009 (UTC)
 * No more edits are added (rather than new edits replacing the ones at the bottom of the queue, or the limit being removed).
 * Attempts to revert fail.
 * Attempts to warn fail.
 * The most effective option to alleviate the difficulties is to close the huggle window and restart the application.
 * A quicker way is to go to the queue options page, and click OK. It clears the queue. Another way is to set a time limit on edits. After x minutes, the edits would be removed from the queue. Griffinofwales (talk) 04:06, 9 September 2009 (UTC)

Sand boxs included in lists?
I have a question. A few of us editors have been having difficulty with sandboxes being included in the list such as Category: X1 and having someone blank the page without an edit comment or adding something that seems out of place with the name of the article or templete. I understand that pretty much anything can be edited onto these pages as they are meant to be for test edits and learning, thru these can appear to the huggle user as disrupting edits. Is there a way to tell if a article is a sandbox without having the /sandbox or is there a way of keeping them off the huggle lists? Thanks in advance &spades; B.s.n.   &hearts;  R.N.   06:30, 9 September 2009 (UTC)


 * There is a list of ignored pages here. Gurch (talk) 14:39, 10 September 2009 (UTC)
 * Thanks i'll add it to the list &spades; B.s.n.   &hearts; R.N. contribs 04:30, 11 September 2009 (UTC)

Installation issue
I can't install Huggle, under both limited user and admin user accounts on Windows. Application error, code (0xc0000135) Sephiroth storm (talk) 20:41, 12 September 2009 (UTC)


 * As specified on the download page under "Requirements", Huggle requires .NET Framework 2.0 -- Gurch (talk) 22:31, 12 September 2009 (UTC)


 * That did it, thanks! Sephiroth storm (talk) 12:44, 14 September 2009 (UTC)

Error
Excuse me that this is in traditional Chinese, as my computer runs in this language. This error causes everything I try to edit/revert to "time out." ObjectDisposedException: 無法存取已處置的物件. 物件名稱: 'WebBrowser'. 於 System.Windows.Forms.WebBrowser.get_AxIWebBrowser2 於 System.Windows.Forms.WebBrowser.PerformNavigate2(Object& URL, Object& flags, Object& targetFrameName, Object& postData, Object& headers) 於 System.Windows.Forms.WebBrowser.PerformNavigateHelper(String urlString, Boolean newWindow, String targetFrameName, Byte[] postData, String headers) 於 System.Windows.Forms.WebBrowser.set_Url(Uri value) 於 System.Windows.Forms.WebBrowser.set_DocumentStream(Stream value) 於 System.Windows.Forms.WebBrowser.set_DocumentText(String value) 於 Huggle.WebBrowser.set_DocumentText(String value) 於 Huggle.Processing.DisplayEdit(Edit Edit, Boolean InBrowsingHistory, BrowserTab Tab, Boolean ChangeCurrentEdit) 於 Huggle.Processing.ProcessDiff(Edit Edit, String DiffText, BrowserTab Tab) 於 Huggle.Requests.DiffRequest.Done 於 Huggle.Requests.Request.ThreadDone 於 Huggle.Misc.CallbackInvoke(Object TargetObject)

Thanks. Leujohn ( talk ) 03:17, 15 September 2009 (UTC)

Error report
Went to view the latest diff for one of the revisions on the queue and I got this error:


 * NullReferenceException: Object reference not set to an instance of an object.
 * at Huggle.Processing.ShowDiffToCur(Edit ThisEdit)
 * at Huggle.Main.HistoryDiffToCur_Click
 * at Huggle.Main._Lambda$__326(Object a0, EventArgs a1)
 * at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
 * at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
 * at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
 * at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
 * at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
 * at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
 * at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
 * at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
 * at System.Windows.Forms.Control.WndProc(Message& m)
 * at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
 * at System.Windows.Forms.ToolStrip.WndProc(Message& m)
 * at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
 * at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
 * at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

No idea what it means. Regards, --— Cyclonenim |<font style="color:#5a3596"> Chat 00:08, 16 September 2009 (UTC)

CRAP!!!!!
I'm sorry but this new build of Huggle is crap! It lags so badly and is slow in showing up the new edits! It also causes memory lag and PC lag on my desktop! Making everything go slow. Please fix it 'cause it's irritating me! -- A3RO (mailbox)  03:53, 16 September 2009 (UTC)
 * 1) We know it runs slow. It's because of feature bloat. 2) If it's causing your computer to lag, it's likely a problem with your computer, not huggle. As far as I know, huggle has yet to cause massive memory leaks. 3) It's not a problem that has a simple solution. Calvin 1998 (t·c) 05:17, 16 September 2009 (UTC)
 * No, it isn't because of feature bloat. It is slow in showing up new edits because the wiki is slow in showing up new edits. How, exactly, am I supposed to obtain information faster than a server is prepared to give it to me? Gurch (talk) 14:13, 16 September 2009 (UTC)
 * Ah! Sorry Gurch! Per your user page, I'm sorry I called it crap! I know you work really hard on Huggle. :( - It just frusterates me when I use it. Calvin, this is a brand new desktop computer, it has never froze on me before and my windows sidebar meter reads high resource use when Huggle is open, tracing it to the RC feed on Wikipedia, which leads me to believe it is the servers. I've used Huggle for a long time now and I remember how flawlessly it ran before. It was a quick vandal fighting tool. I mean this thing was lightning fast. I loved it, still do; but I think one of the problems might be with Wikipedia itself. I don't know. I'm not a programmer and I barely recognize how to write script but I hope Huggle works smoothly again. -- A3RO (mailbox)  05:28, 18 September 2009 (UTC)
 * It is crap, just not for the reasons Calvin1998 says. Gurch (talk) 09:43, 18 September 2009 (UTC)
 * :( -- A3RO (mailbox)  22:24, 18 September 2009 (UTC)
 * Hey, be nice. Just because Huggle has the occasional technical issue doesn't make it "CRAP!!!!!" Huggle is a wonderful tool for keeping Wikipedia all neat and clean. I don't know how anyone prevented Wikipedia from being eaten alive by the vandals before it was created. -<font color="#0000cd">sesu <font color="#b22222">PRIME  00:34, 19 September 2009 (UTC)
 * Over ruled. Sorry, but their was, and still is, a lot of other applications. The easy to user interface and swiftness made it popular. However, the developing problems, in no reference to the people, are now a major issue. It never was like this before. I've used Huggle for a very long time and today's build has a lot of bugs. Like I said, hopefully it gets worked out. -- A3RO (mailbox)  01:57, 19 September 2009 (UTC)
 * There are other tools like Huggle? Where? I'm not trying to be a smart aleck, I'm genuinely curious. -<font color="#0000cd">sesu <font color="#b22222">PRIME  22:42, 19 September 2009 (UTC)
 * I've used this one and this one. I actually believe there is a whole page dedicated to applications on fighting vandalism but I'm too lazy to search for it now. :P -- A3RO  (mailbox)  08:56, 22 September 2009 (UTC)

not responding
When I open Huggle, it works fine a minute or two, but then I get a message saying that Huggle is not responding, and I have to close the program. How do I fix this? Griffinofwales (talk) 19:17, 18 September 2009 (UTC)
 * You must purchase a super computer running with a T4 connection in order for it to not freeze and close down. :) - LOL, J/K! Actually, we are all experiencing this problem, myself included. It appears to be a problem that is beyond our control, per above. However, try closing down any unused icons running in your taskbar to free up some resources. Try that. -- A3RO (mailbox)  22:28, 18 September 2009 (UTC)


 * It's the Wikimedia servers that need a T4 connection... Calvin 1998 (t·c) 01:45, 19 September 2009 (UTC)
 * I never experienced a T4 connection, I wonder what it's like. Hmm? -- A3RO (mailbox)  01:59, 19 September 2009 (UTC)


 * Not really. You would need about 26 of them to handle peak Wikimedia traffic -- Gurch (talk) 09:44, 19 September 2009 (UTC)
 * Haha! -- A3RO (mailbox)  18:07, 19 September 2009 (UTC)

Errors - Sept 2009
I figure we should start bucketing the errors to help the people programming it. -- Mjquin_id (talk) 16:05, 19 September 2009 (UTC)
 * Version 0.9.2 - I tried to change "Filtered edits" to Dynamic List; from Watchlist...Now Filtered list gets me this error every time. BUT, only when I select the first page in the list! (Working to give you the most info around the error. As a programmer, I know it helps!) -- Mjquin_id (talk) 16:05, 19 September 2009 (UTC)
 * LOL, this is funny becuase I have no idea what all these codes mean. I only know HTML coding. Haha. Smart people. -- A3RO (mailbox)  18:09, 19 September 2009 (UTC)

Wrong revert
I don't know what led your software to think that it was "unconstructive" to fix the redirect NECCO to Necco per WP:MOSTM in this edit and to revert it, but it would be very much appreciated if it could please stop thinking like that. 62.147.26.72 (talk) 11:25, 20 September 2009 (UTC)
 * See your talk page -- A3RO (mailbox)  12:08, 20 September 2009 (UTC)
 * The software does not make such decisions itself, in this case the decision to revert was made by "Île_flottant" who, it would seem, couldn't revert his way out of a brown paper bag. Hopefully he'll be more careful in future. Gurch (talk) 19:09, 20 September 2009 (UTC)
 * Oh! Hmm. Yeah. I told him, but he doesn't seem to understand the concept that it's not alive. -- A3RO (mailbox)  22:02, 20 September 2009 (UTC)

Speedy Deletion warnings
Has anyone ever tried making a set of "removal of speedy deletion" templates (i.e. 1 to 4)? I'm often confronted with the need to apply the templates, and usually switch to Twinkle to revert, so I can apply the standard uw-speedyX that Twinkle uses (but of course one has to manually decide which one is next - there's no auto!). Should I have a go at making a set based on the standard uw-speedyX (i.e. huggle/warn-speedy-1, etc.)?  Ron h jones (Talk) 21:27, 21 September 2009 (UTC)
 * I end up reverting the removal of the deletion tag as vandalism if they do it more than twice. -- A3RO (mailbox)  05:20, 22 September 2009 (UTC)