Wikipedia talk:Huggle/Feedback/Archive 15

This is an archive of past discussions on Wikipedia:Huggle. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

Archive 10

←

Archive 13

→

Warning tags

Hey, been using Huggle for a little while and I love it. However, there's a few user warning tags I got used to when using Twinkle that aren't available for convenient tagging in Huggle. Specifically, I'd love to see uw-tdel, uw-afd, uw-blpprod, uw-redirect anduw-advert available as auto-warnings for reversion. This would be awesome. Thanks! elektrik SHOOS 09:47, 18 July 2010 (UTC)

I've been thinking about the same thing. Specifically, the uw-joke and uw-tdel templates.–dffgd talk·edits 19:06, 19 July 2010 (UTC)

I agree with Elektrik Shoos on this proposal. Moreso the uw-advert as I often find edits that are blatant advertising, but do not include any links, thus are not appropriate for a uw-spam warning. Thanks, Stickee (talk) 09:59, 20 July 2010 (UTC)

Advertising very rarely qualifies as vandalism, and in those rare circumstances where it does (someone overwriting an existing article with promotional material, say) just use a generic vandalism warning. The rule (and this is a rule, not my personal opinion) is that if it's not an edit so obviously problematic that reverting it needs no explanation, rollback (and thus, Huggle) shouldn't be used. – iride scent 10:11, 20 July 2010 (UTC)

Pending changes integration

I think if Pending Changes passes, Huggle should integrate with it. Allmightyduck  What did I do wrong? 15:26, 23 July 2010 (UTC)

Huggle is designed for use with wikis, not moderation systems. Gurch (talk) 15:59, 1 August 2010 (UTC)

Huh? Pending changes protection... Allmightyduck  What did I do wrong? 06:22, 6 August 2010 (UTC)

See the long section, several sections up... dffgd talk·edits

front page could do with some edit stats

I think the front page for Huggle could do with some summary stats of how much editing (or rather reverting) Huggle is used for e.g. Huggle was used to revert xxx,000 vandalism edits in May 2010 etc. Thanks Rjwilmsi 19:54, 23 July 2010 (UTC)

If you want to put it there and can be bothered to count them, I guess you can. I don't really see the point though. Gurch (talk) 16:00, 1 August 2010 (UTC)

Not logging in

I tried logging into Huggle but it kept saying "unable to login" not matter what I try. I've tried both passwords I know and neither seem to work. Could someone tell me what's wrongPaul 2387 00:27, 31 July 2010 (UTC)

"Both passwords you know?" Why do you know two passwords? The password you use to log in to Huggle should be the same password that your acccount has. dffgd talk·edits 01:25, 31 July 2010 (UTC)

Criticism and complement

First, I've been a Huggle user on and off for a few years now. It's a great tool, and it does a lot to keep vandalism and other inappropriate edits off Wikipedia, and it's probably the best tool we have right now.

However, I do see a major failing. Huggle works competitively rather than collaboratively. When the vandalism is blatantly obvious, this is a good thing. When the vandalism isn't as obvious is where Huggle fails. The competitiveness of RC patrol with Huggle means that users are trying to process as many diffs as possible as quickly as possible, so that they can get to the next "bad" edit. I'm noticing that this creates a tendency for "questionable" edits to just be skipped entirely - the concerns of not wanting to rollback a valid edit, wanting to get through as many edits as possible, and the time it would take to properly analyze an edit create a "perfect storm" of conditions that actually allow some forms of vandalism and otherwise bad edits to slip through. User:Gurch addressed some of these concerns with the addition of a button to add maintenance templates during review of articles, but the biggest problem - that of an edit that could either be correcting an error or introducing one, and not wanting to stop patrolling to actually review that edit remains.

I think that this proves we need a collaborative platform rather than a competitive platform for RC patrol - the pressure to "get to the next diff" must not overrule full examination of all changes, and the rate at which the English Wikipedia is edited (anywhere from 100 edits a minute upwards) means that one person cannot hope to inspect every single change -only by dividing and conquering can we actually approach a level of effective RC patrol. Triona (talk) 01:26, 9 August 2010 (UTC)

"Full examination of all changes" was never Huggle's goal -- go support the moderation system if you want that. It was intended to deal with obvious vandalism, not the introduction of subtle errors, dodgy formatting, or obscure policy violations. Since those require more extensive editing of the article, a task that does not particularly benefit from an alternative interface, there is nothing for Huggle to offer in this area.

One person can very easily inspect every change to the English Wikipedia, if you ignore an appropriate subset of contributors. Indeed this is exactly what Huggle users do. This wasn't quite true during busy periods in early 2007 but the huge drop in contributions from new and anonymous users since then (thanks to increasingly oppressive measures against them) means that it is now easy.

The issue of people treating recent changes patrol as a competition is a problem, but it isn't really one that could be addressed by Huggle itself because it is more an issue of self-discipline by contributors. People have thrown around the concept of a "collaborative platform" many times, but when pushed for implementation details all they have been able to come up with is some system where each revision is only given to one user who then has to decide what to do with it. Besides being technically infeasible, this simply doesn't provide any practical benefit, and has several drawbacks. Do you have a better idea? Gurch (talk) 10:05, 9 August 2010 (UTC)

My 2c (and I think this would be do-able, although I certainly couldn't implement it myself) would be to have a separate User:Huggle; rather than make the edits from the user's own account, they'd be routed via this role account. The edit summary would specify who requested each revert, to preserve the audit trail in case of errors. By not affecting the edit-count of users, it would (hopefully) reduce the tendency of some of the more enthusiastic users to "revert race" and encourage them to actually look more closely at what they're reverting. – iridescent 10:19, 9 August 2010 (UTC)

It's certainly possible technically, but could never be done in practise. If user's clients logged in to the Huggle account, anyone could change the password and lock everyone out. If user's clients sent change requests through some communication channel to a central server, this could be abused to e.g. falsely attribute changes, unless a server with its own user accounts and authentication system was set up. And I would have to pay the hosting bill for all that. If the Huggle account was blocked, nobody could do anything. Users wishing to communicate with whoever just reverted their edits would have an even harder time of it than now. Obviously it would violate half a dozen policies. And all that just so that a number in a database is not affected? It is trivial to count the number of contributions not made using Huggle, but by even trying to do that one is making the mistake of caring what the result is. Gurch (talk) 13:32, 9 August 2010 (UTC)

A "role account" would never be accepted. However it's certainly possible to coordinate the activities of groups of patrollers. Just create a new IRC chat room as a control channel on the same server, have the clients communicate. Privacy could be an issue but I think those servers auto-mask IPs anyway. There could be a trust system or people could just make groups themselves.

You'd need to add an "I'm not sure" button in addition to an ignore button, and you'd probably want to aggregate consecutive edits (which is the primary source of mistakes using HG). These would increase API load, but on the other hand you'd have fewer diffs to actually retrieve as you marked more and more edits benign.

That'd be the framework at least. Sounds easy but it'd take some time, and the GUI would be an issue too. I understand the reluctance. Shadowjams (talk) 04:53, 10 August 2010 (UTC)

Many users are behind firewalls that do not allow IRC connections. IRC also has no proper authentication.

There is already an "I'm not sure" button. Indeed, it's the largest button in the interface. If you're not sure about a revision, and you don't want to manually edit it, you leave it for someone else to look at. That is the way things worked before Huggle was around and I don't see the need for it to change.

Reverting already "aggregates consecutive edits" because all consecutive revisions by the same user are reverted. Not distinguishing between them at all for diffs would be problematic because it would leave the user unable to revert some, but not all, of those revisions, as is sometimes necessary. I'm not sure how it is the primary source of mistakes, either; as far as I can see, the primary source of mistakes is people reverting things they shouldn't. Gurch (talk) 14:18, 10 August 2010 (UTC)

Maybe. If we can figure out some sort of communication "on wiki", even minimal, so that there's a middle option between leave it alone and revert. Basically, something to say, this doesn't look right, but I'm not sure why. That could be a template, a category, a special page, something, that helps someone else find the questionable edits. Then we need to make sure that mechanism is policed with the same vigilance as the live feed. That removes the urgency - you can always go work the questioned edits when it's slow, and they won't go anywhere, and it also gives us a secondary tool to catch those vandals - if the editor who made the questionable edit in the first place tries to take it off the list, that's all the more reason to pay attention to it. Triona (talk) 03:56, 10 August 2010 (UTC)

If something doesn't look right but you're not sure why, then most likely you have one of these four situations:

You do know what's wrong, but it would take a long time to fix and you don't feel like doing it.
It looks like it might breaks some obscure guideline, but you don't know because nobody actually reads all the guidelines.
It is actually legitimate, you just don't agree with it.
The change may or may not be acceptable, but your knowledge in the article's subject area is not sufficient to know for sure.

None of these situations benefit from automation or an alternative interface, so there is nothing for Huggle to offer.

As for the whole "questionable edits" thing... again, if you want that sort of thing, go support the moderation system. I prefer wikis myself. Gurch (talk) 14:18, 10 August 2010 (UTC)

I am seeing one other situation beyond the above:

The change is legitimate, but your experience as an editor is too limited for you to see that.

As in those other situations, the proper thing to do is leave it alone. Gurch, have you considered switching keys so that the revert function is not under a dominant finger? Choose keys to make it easier to move on, harder to revert. Gurch, do you track the ratio of Q to R? That might be a useful statistic for assessing individuals' use of Huggle, and guide timely intervention. Some individuals may use one or the other key too often. 68.167.224.215 (talk) 14:42, 23 August 2010 (UTC)

I never used the keyboard, I always used the mouse on Huggle to revert edits. - Donald Duck (talk) 15:57, 23 August 2010 (UTC)

During a run of reverts does the mouse stay in one place, over a revert button? That would be a form of entrainment, making it easier to keep doing whatever the user did last, and harder to do anything else. 68.167.224.215 (talk) 16:49, 23 August 2010 (UTC)

"Revert and warn" (Q key by default) reverts using the standard summary and leaves a standard warning message. "Revert" (R key by default) lets the user choose the summary and is intended for use in conjunction with one of the other template messages besides the standard warning, or a specific message from the user. So the ratio of the two is not particularly meaningful: using R more could be a good thing (the user is sending more informative messages to users) or a bad thing (the user is not sending any messages at all).

By default Space moves to the next revision, which looking at a keyboard seems to be the easiest key to press. Moving the keys around may well make things more difficult to do, but I'm not a big fan of deliberately doing that in user interfaces; one might as well abandon shortcut keys altogether in that case.

If using the mouse, one needs to move to the appropriate button for each action, including "next revision". So no, the mouse does not stay in one place. Gurch(talk) 17:23, 23 August 2010 (UTC)

Unable to Log In

I'm getting the dreaded Unable to Log In message, I'm a reverter (and reviewer if that may flag up something bad), have enable:true in my huggle preferences page, have internet connectivity, windows 7 x64 and it has worked before. I've tried rolling back to previous versions and compiling the latest trunk build. Tried running it in XP Mode and double checked the password is right but it doesn't seem to want me in regardless Gsp 8181 19:08, 9 August 2010 (UTC)

I can log in in every other Wikipedia (to huggle is not enabled anyway) but en.wiki.x.io fails with unable to log in after logging in Gsp 8181 20:30, 10 August 2010 (UTC)

Sorted, commented out line 250 in Requests.vb as it wasn't parsing my login successful page properly Gsp 8181 22:09, 10 August 2010 (UTC)

I've been having the same problem. Could someone explain this to me in a more simple form or tell me how to do it- "commented out like 250 in Requests.vb as it wasn't parsing my login page properly". Andrewmc123 23:04, 10 August 2010 (UTC)

Here's a compiled version with the alterations, hope it helps :) huggle. Gsp 8181 09:07, 11 August 2010 (UTC)

Thanks. That's great. I've not been able to login for months and no one could tell me why until now.Andrewmc 123 14:30, 11 August 2010 (UTC)

Download error.

We reformatted my PC yesterday, and now when I try to re-download / re-install Huggle, I get this: http://i101.photobucket.com/albums/m62/AmauryGarcia/HUGGLEerror.jpg

Any idea what this could be? Thanks in advance. - Donald Duck (talk) 20:02, 9 August 2010 (UTC)

As stated on the download page, Huggle requires .NET Framework 2.0.Gurch (talk) 20:35, 9 August 2010 (UTC)

I don't think we did that last time we reformatted it, but I probably just don't rememeber. It's been so long since we've reformatted either of our computers. - Donald Duck (talk) 21:03, 9 August 2010 (UTC)

Scratch that. It was the automatic update thing that got it last time -- it just hadn't reached it yet this time. A .NET Framework update is installing now. - Donald Duck (talk) 23:49, 9 August 2010 (UTC)

Error message

Got this message. Didn't seem to change the way anything ran and the edit I attempted to make was done.

ArgumentNullException: Value cannot be null.
Parameter name: input
   at System.Text.RegularExpressions.Regex.IsMatch(String input)
   at Huggle.Processing.ProcessEdit(Edit Edit)
   at Huggle.Processing.ProcessContribs(String Result, User User)
   at Huggle.Requests.ContribsRequest.Done()
   at Huggle.Requests.Request.ThreadDone()

– Zntrip 05:05, 15 August 2010 (UTC)

"Dubious" edits

I posted the following to a talk page:

I see that you routinely revert unsourced edits with the edit summary "Reverted addition of dubious unsourced content." The particular edit which caught my attention, a table of leading goaltenders in the 1967 NHL season, is correct in every particular. The very next such edit of yours I checked has you claiming as "dubious" and "unsourced" changing the 'years active' date of a band planning an October release from "aug 2010" to "present." Among others is one where you use the tag to revert an item with the source and date named in the edit you reverted, and your marking as "dubious" that The Graduate soundtrack reached the top of the Billboard album chart on April 6, 1968 (which, in fact, it did) and was knocked off by the album Bookends on May 25 (which, in fact, it was). IMHO, it's a WP:AGF and WP:BITE violation both to hurl the word "dubious" at people when, in fact, the edits in question are accurate, and take only moments to ascertain whether or not they are. It is insulting to others to routinely categorize their edits as "dubious" and careless to do so indiscriminately without any notion as to whether they actually are.

... and the editor in question explained that this was a standard response given by Huggle, further explaining its appropriateness in BLP issues. Even given the premise that a routine categorizing of unsourced BLP edits as "dubious" isn't antagonistic or bitey - with which I disagree - I don't imagine that Huggle only works on BLP articles, any more than it did to generate any of the diffs to which I objected. Perhaps this issue has been discussed before, but if not, it deserves some debate. "Reverted addition of unsourced content" works just fine without being a provocation. RGTraynor 12:34, 22 August 2010 (UTC)

Except that merely adding unsourced content is not sufficient reason to revert a revision, much as some people wish it were. The exact rules about what can and cannot be reverted on sight does not fit into the edit summary field. Gurch (talk) 16:58, 22 August 2010 (UTC)

And doesn't need to be. I'm not talking about ADDING words to the edit summary. I'm talking about removing an objectionable one. RGTraynor 00:44, 23 August 2010 (UTC)

RGTraynor, I think Gurch agrees with you but is saying that furthermore the source of the problem lies in the revert itself. The revert itself was wrong. Huggle is to be used only on vandalism. The trouble is, too many people who fight vandalism have trouble recognizing what is not vandalism. Some of them rack up tens or hundreds of thousands of reverts with only a handful of contributions of their own. 68.167.224.215 (talk) 03:24, 23 August 2010 (UTC)

Ahhhh ... I understand; thank you for the clarification. The editor to whom I directed the original comment was plainly - and admittedly - using it for routine reverts. And, coincidentally enough, his contribution history is wall-to-wall reverts, "contribution" free. RGTraynor 23:44, 23 August 2010 (UTC)

Yes, that happens a lot, and I think it is very damaging to Wikipedia because unlike you many people subjected to such treatment do not stick around to ask questions. Do you want to file a complaint? The goal would be to improve the behavior of the editor who reverted you, but pressing the case could take hours spread over several days. This may be more than you want to bother with, and that's fine. 64.105.65.28 (talk) 01:06, 24 August 2010 (UTC)

I wasn't myself reverted; it was an article on my watchlist, and quickly seeing that the edit was legit, I started going over the reverter's own history. I spoke to him on his talk page, and he explained the situation, gave me this talk page if I wanted to comment, and went into his own monobook to alter the automatic message to delete "dubious." RGTraynor 13:57, 24 August 2010 (UTC)

I see. It looks like Huggle fever. 64.105.65.28 (talk) 21:17, 24 August 2010 (UTC)

flag legit article

Hi - I recently messed up identifying this edit as vandalism. I wonder if Huggle can be configured to identify at that precise time if such an article is a legitimate article and not just higlight the changes. What would have been useful is to know if the words in the link box comprised an actual article or a dead link. Shiva (Visnu) 19:07, 22 August 2010 (UTC)

Not sure what you mean by this. You want Huggle to identify whether links in articles are red or blue? If so, click the "view page" button to view the revision; the revert buttons will still work when you've decided what to do with it. Gurch (talk) 19:47, 22 August 2010 (UTC)

Huggle fever

User:Donald Duck is on ANI now for what I gather is a bad case of Huggle fever. Could this user's use of Huggle be suspended?68.167.224.215 (talk) 03:26, 23 August 2010 (UTC)

Yes, but not by me. Gurch (talk) 08:39, 23 August 2010 (UTC)

How is it done? And does using Huggle require having rollback permission? 68.167.224.215 (talk) 14:29, 23 August 2010 (UTC)

Huggle does require rollback permission, so the most effective way of suspending access to the tool would be to suspend access to the rollback account permission, an action that can only be performed by the administrators. Tyrol5 [Talk] 15:30, 23 August 2010 (UTC)

My access is suspended currently, but what DGG did was delete my "Huggle CSS" thing and protected it. - Donald Duck (talk) 15:56, 23 August 2010 (UTC)

Huggle issues?

I downloaded huggle as I do a lot anti-vandalism work. But when trying to log in to this English Wikipedia, it says unable to log in, and I do have set my huggle.css as the introduction page guided. Anyone else having this kind of issues, or is it only me having trouble? DARTH SIDIOUS 2^(Contact) 15:46, 26 August 2010 (UTC)

Try my compiled version of huggle, if you don't trust downloading things on the net I can provide diffs for the VB.NET code or the diffs for the MSIL Gsp 8181 21:40, 26 August 2010 (UTC)

Thank you a lot! It works nicely and well. :) DARTH SIDIOUS 2 ^(Contact) 13:18, 27 August 2010 (UTC)

Whitelist criteria

I was wondering if somebody could tell me what the criteria is for a user being put on the whitelist. A lot of times I see edits that could be vandalism but I'm not positive so I just let them go and move on. I want to make sure those users aren't getting whitelisted, because if they are in fact vandalizing, it would reduce effectiveness of Huggle.–CWenger (talk) 23:03, 28 August 2010 (UTC)

500 contributions. This is not an assertion that 500 contributions is necessary for one's contributions to be constructive, but a consequence of the requirement that the list not be too large. Gurch (talk) 14:38, 29 August 2010 (UTC)

I see. Thanks for the answer and especially thank you for the wonderful vandalism-fighting tool! –CWenger (talk) 23:52, 30 August 2010 (UTC)

Are there users with 500+ contributions that aren't on the whitelist? Perhaps because they have committed vandalism in those 500+ edits? Jsayre64 (talk) 00:52, 9 September 2010 (UTC)

Users with more than 500 contributions are added to the list automatically by Huggle. If a user with more than 500 contributions has not edited whilst someone was using Huggle since the whitelist was last cleared, they will not be listed there. The nature of contributions is not taken into account Gurch (talk) 12:18, 9 September 2010 (UTC)

Editing problems

Tried to edit a page using the edit option and it froze... --Imagine Wizard (talk) 14:21, 30 August 2010 (UTC)

Yes, it will do that sometimes, because the parser sucks. Gurch (talk) 15:13, 30 August 2010 (UTC)

New Users

Hi, is it possible to set Huggle up to monitor the new users log? [1] --Blehfu (talk) 12:43, 10 September 2010 (UTC)

Not really, because it only looks at revisions. Revisions from new users are given some priority, so it should already be monitoring those. Gurch (talk) 14:15, 10 September 2010 (UTC)

Error message at logon: "Failed to load message files: unknown error"

This began today -- I was using Huggle successfully as recently as yesterday. Anyone else getting this? -- Rrburke (talk) 22:06, 16 September 2010 (UTC)

Yep, I can't log onto Huggle or WikiCleaner either. --Funandtrvl (talk) 23:19, 16 September 2010 (UTC)

Seems to have cleared up -- for me, anyway. -- Rrburke (talk) 00:29, 17 September 2010 (UTC)

Unable to stay connected to IRC

Me, and at least 1 other person is having problems with Huggle not staying connected to the IRC recent changes feed. We start up HG, it acts like it's connecting to IRC, the queue starts filling, but then it seems to disconnect from IRC and fall back to the recent changes feed. The quit message for it is "-14:10:34- º¹º¹ Quit» (h_848393) (~h_848393@anonymous.user) (Read error: Connection reset by peer)". At least 2 people, me and AQ are having this problem, and afaik, AQ is using the normal version of Huggle, while I'm using my custom version. The Thing // Talk //Contribs 20:15, 6 October 2010 (UTC)

According to the server admin log, the IRC server was moved from browne to ekrem. The Thing // Talk // Contribs 03:06, 7 October 2010 (UTC)

From the quit message you provided, it looks like the IRC server is having issues, or perhaps changed its connection policies... something Gurch will have to look into.Calvin 1998 ^(t·c) 05:49, 7 October 2010 (UTC)

Me and User:Sidonuke have fixed the problem, and I have compiled a version for the, well, general public, that works like a charm. I have updated the meta configuration page with the necessary line that it needs to stay connected to the IRC feed, and I can upload the version somewhere. The Thing // Talk // Contribs 13:34, 7 October 2010 (UTC)

Do you have any intention of publishing these patches you keep making? I know there's no license requirement to do so but, well, there's this thing called "open source"...Gurch (talk) 15:10, 7 October 2010 (UTC)

Here is the patch for IRC thing, a hackish fix that works without too much modification but should outlast any changes diff patch. The IRC server is returning a hostname that isn't irc.wikimedia.org when it should and thats what huggle expects for some string searching. Also the patch has some compile fixes (for vb 2010 or whatever) and then a fix in string functions. Left out the speed modifications, config changers, and a few other silly things that are special purpose. Sido nuke 15:54, 7 October 2010 (UTC)

Also I would love to help out on huggle and keeping it maintained... If I could get commit access to the google code. I would push my fixes and updates throughout time. If not I can start a new competing huggle <.<. Sido nuke 16:10, 7 October 2010 (UTC)

Bit of a late comment, but afaik we were planning on publishing it. I'm not at the computer that has the source code, or the compiled version, and it looks like Sidonuke posted the necessary changes already, so I don't see any need to be redundant and post anything. The Thing // Talk // Contribs 17:14, 7 October 2010 (UTC)

I personally don't have a way to compile Huggle, is it possiable that someone can contact the maintainers, or possiably move the code to the Tool Server and offer it there? --Wolfnix • Talk • 16:54, 8 October 2010 (UTC)

Issue posted at Google Code - Projects Hosting named Issue 197--Wolfnix • Talk • 17:06, 8 October 2010 (UTC)

How do I put this new code into huggle? Access Denied ^{[FATAL ERROR]} 00:26, 9 October 2010 (UTC)

Its been fixed and a new release is out. Sido nuke 02:09, 9 October 2010 (UTC)

IRC

My Huggle don't work with IRC, any bug? Diegusjaimes complaints 20:25, 6 October 2010 (UTC)

Same here. Two nights in a row. Thanks! — Spike Toronto 18:05, 8 October 2010 (UTC)

Fixed in latest huggle. Sido nuke 02:10, 9 October 2010 (UTC)

Thanks a million! — Spike Toronto 19:47, 9 October 2010 (UTC)

Finnish Wikipedia

Hey, is it possible to have Huggle work in Finnish Wikipedia? If not, is there any other similar tool? --Olli (talk) 06:06, 30 July 2010 (UTC)

Warning's problems in es.wiki

Hi, on eswiki Huggle skip the warns left by others users, as you can see here, any idea about what is wrong? thanks Diegusjaimes complaints 19:02, 11 August 2010 (UTC)

Another problem...

This time it's crashing when I open the box to request page protection. It's happened twice in the last few minutes. Could someone please help? dffgd talk·edits 21:30, 11 August 2010 (UTC)

Yes, that doesn't work and hasn't for years. Also if you're requesting page protection that often, you're doing it wrong. Gurch (talk) 10:10, 12 August 2010 (UTC)

No, I tried to request the same page again when I opened HG back up. If it doesn't work, why is it still there? Plus, I've successfully requested protection with it here, and I may have done it multiple times in the past. dffgd talk·edits 12:29, 12 August 2010 (UTC)

Failure to load message files

Every time I try to log in, I get "Failed to load message files: Request timed out". Never had any problems before. Anyone know what might be up? I tried retyping my password several times and in case I was somehow entering it wrong changed it, but no dice. Falcon8765 (talk) 18:09, 16 August 2010 (UTC)

Nevermind. Updating Java appears to have fixed it. Falcon8765 (talk) 18:27, 16 August 2010 (UTC)

No, updating Java did not fix it. There is no Java code in this application. That message will occur if the wiki you are accessing is down or extremely slow to respond. Gurch (talk) 10:33, 17 August 2010 (UTC)

Tag Copyedit

Is it possible to quiqly put the tag {{copyedit}} with Huggle? I use Huggle in the Spanish wiki. Regards. --84.79.207.16 (talk) 21:08, 27 August 2010 (UTC)

Suggested change to one revert message

Currently, one of the revert message options is "(Reverted addition of unsourced negative content to a biographical article (HG))." Could I suggest we change this slightly? Since WP:BLP applies in all articles (actually, in all spaces, including userspace), could we change it to refer to the content, instead of to the article type? That is, make it say something more like "(Reverted addition of unsourced negative content about a living person per WP:BLP)". Qwyrxian (talk) 03:37, 28 August 2010 (UTC)

browser

forgive me if this is not the correct place to ask technical questions about huggle. it would be quite convenient to be able to click a link and have it open in the program or, preferably, a new tab in my browser; currently clicking links appears to do nothing. alternately, the "view in external browser button would suffice, but it always opens internet explorer while firefox is my default browser. i took a glance through the options but failed to find any settings for these features. does anyone know any solutions? cheers WookieInHeat (talk) 01:57, 6 September 2010 (UTC)

can't log in

I asked days before, but get no answer. Huggle worked in the past for me, but now I can not login. In german wikipedia it works for me. I use 0.9.6 - thanks for help, Conny (talk) 19:29, 15 September 2010 (UTC).

Diff zu last reviewed version

There should be an option, that it is possible to show the Diff to the last reviewed version. Is such a plugin planned? Greetings, Conny (talk) 22:06, 15 September 2010 (UTC).

More details in older query. Greetings, Conny (talk) 22:21, 15 September 2010 (UTC).

Huggle

Why doesn't Huggle let me log in because of an unknown error? Wayne Olajuwon chat 01:03, 17 September 2010 (UTC)

Huggle also doesn't let me revert some vandalism. Wayne Olajuwon chat 15:48, 18 September 2010 (UTC)

SLOW!!!

huggle is working VERY slowly for me lately, if at all. it works for about 10 - 15 minutes before it won't advance to the next revision, when it does manage to advance the features work intermittently (i.e. won't revert or reverts but doesn't indicate it has). it has been crashing on a pretty regular basis, but usually i have to restart it before that because it stops functioning. it was working fine since i started using it about a month ago, this just started in the past few days. any one else having similar problems? WookieInHeat (talk) 20:26, 22 September 2010 (UTC)

also, wikipedia pages are loading very slowly over the past few days. often an article or talk page will load but the wikipedia logo and links at top and left won't load for another 30 - 60 secs. i know my internet connection is fine, all other sites load normally and i have been doing regular speed tests. think this slow loading may have something to do with huggle timing out. WookieInHeat (talk) 20:38, 22 September 2010 (UTC)

You people voted for Pending Changes; you only have yourselves to blame. – iridescent 20:42, 22 September 2010 (UTC)

Yeah, Huggle operates on the assumption that web requests will take about 1-3 seconds. When they start taking 30-60 seconds, it becomes pretty unusable. As you have identified yourself, this is an issue with Wikipedia, not Huggle. Gurch (talk) 21:02, 22 September 2010 (UTC)

huggle timing out because wikipedia servers may be overloaded, although frustrating, is understandable. however this doesn't explain the regular lock ups and crashes, unless 20 or so page time outs makes huggle crash for some reason. WookieInHeat (talk) 21:16, 22 September 2010 (UTC)

been pinging wikipedia.org for the last ten minutes, seems to time out on the first couple requests, then requests start going through with minimal latency. this corresponds with having to advance past a few revisions (hit the spacebar) in huggle before it will load a new edit. what on earth is making wikipedia servers react so sluggishly for me? WookieInHeat (talk) 21:42, 22 September 2010 (UTC)

I just told you. In their wisdom, the devs are now running a spectacularly cack-handed script which the servers can't cope with, and it's slowed every Wikipedia process down to a crawl. Get used to it, since the Defenders Of The Wiki are going to keep holding the "should we keep this feature?" vote until it gives them the result they want. – iridescent 22:34, 22 September 2010 (UTC)

That extension is not the sole source of the problem, although it isn't exactly helping. Gurch (talk) 23:01, 22 September 2010 (UTC)

I noticed on your huggle.css that your preload setting is at a low setting of 2. Try setting it to 5. You can do this by loading up Huggle, going up to the toolbar and clicking "System", then in the list clicking "Options". In the "General" tab, which should already be showing for you, make sure that the "Enable preloading of diffs" box is checked, and change the number next to that option to 5. This should speed things up quite a bit for you. The Thing // Talk // Contribs 14:17, 6 October 2010 (UTC)

excellent, thank you for taking the time to check that out, although the problem seems to have cleared up on its own. for about three days huggle was working excruciatingly slow and crashing every ten minutes, then whatever the problem was just magically cleared itself up. but thanks for going out of your way to assist me none the less. cheers WookieInHeat (talk) 14:44, 6 October 2010 (UTC)

Changing that value will do nothing to speed up anything when the issue is response times from the wiki itself; indeed, it will likely make things even slower in such cases. Gurch (talk) 17:02, 6 October 2010 (UTC)

Whitelist

It says:

This is a list of users whose contributions may be ignored while searching for vandalism. It is updated automatically by Huggle.

Instead of maintaining a long list of users, just check the account age. If its older than 30 or 90 days, thats good enough. --Matt57 ^{(talk•contribs)} 14:14, 29 September 2010 (UTC)

No—some of our most die-hard POV-pushers go back years, and any self-respecting vandal has a big stash of ripened socks. – iridescent 14:25, 29 September 2010 (UTC)

The actual reason for doing this is that maintaining a list of users is significantly faster and more efficient than checking the account age of every contributor as they edit (one large request at startup versus hundreds of small requests during the session). Gurch (talk) 16:02, 29 September 2010 (UTC)

Alright I guess if thats true, it makes sense. --Matt57 ^{(talk•contribs)} 20:25, 29 September 2010 (UTC)

Profanity highlighting

Another anti-vandal tool, igloo, highlights profanity added in the edit in pink, such as shit, penis, ass, emoticons such as :), and even repeating characters, such as ggggggggggggggggggg. I think Huggle should do the same thing. ~Nerdy Science Dude 03:18, 30 September 2010 (UTC)

Oh it's alright, if you're eagle-eyed enough, you should spot it anyway... ;) Orphan Wiki 09:43, 30 September 2010 (UTC)

Text changed by the edit is already highlighted. Multiple types and colors of highlighting may lead to confusion. In addition, instances of vandalism containing words like "shit" and "penis" are usually easy to spot, and "gggggggggggggggg" even more so; in five years I still have yet to come across an instance of a user adding a coherent, useful paragraph of text whilst slipping "penis" in the middle somewhere, which would be about the only situation where such a feature would be of significance. Gurch (talk) 10:01, 30 September 2010 (UTC)

Not warning vandals

On the computer I am currently using, Huggle's log shows that it is not warning vandals, because they haven't edited since their latest warning, yet they have.

Nothing new. The situation is as described. Just ignore it, and continue your work, it shouldn't happen regularly. Orphan Wiki 21:12, 1 October 2010 (UTC)

Huggle crashing

If I use Shift + P for a keyboard shortcut for Request Protection, huggle crashes with a error message: "Huggle has encountered a error and needs to Close. If you were in the middle of something any changes may be lost." Is there a technical reason why Shift + P causes huggle to crash? Thank you, --Alpha Quadrant ^talk 19:49, 1 October 2010 (UTC)

Although this has happened to me before, I just barely tested it in the Huggle sandbox, and it stayed up. I'm not sure exactly what causes it. The Thing // Talk // Contribs 14:22, 6 October 2010 (UTC)

New Templates

I was wondering if it would be possible over time to add the following to Huggle's list of templates:

a template akin to {{Uw-advert1}} up to Level 4
a template akin to {{Uw-copyright}}
a template akin to {{Uw-redirect1}} up to Level 4
a template akin to {{Uw-nor1}} up to Level 4
a template akin to {{Uw-coi}}
a template akin to {{Uw-selfrevert}}

Thanks! — Spike Toronto 20:38, 1 October 2010 (UTC)

Why would you warn someone for reverting themselves? Gurch (talk) 22:22, 1 October 2010 (UTC)

The self-revert template is for those IP editors who are testing the vandalism waters by making vandalizing edits, and then reverting them. That way they don't get blocked. But, if you hit them with {{Uw-selfrevert}}, it usually stops them messing about since they know that recent changes patrollers are on to them. Edits like that still slow us down because we have to stop and deliberate over the edit to determine if it is vandalism. The self revert template reduces the frequency of these types of edits and thus reduces the number of them that we have to look at. The template is not used for someone who reverts themselves because they messed up an edit. G-d knows I do that all the time! — Spike Toronto 22:35, 1 October 2010 (UTC)

You can do both yourself...

For the non-counting ones, you can add existing ones by editing your huggle.css file. See User:Ronhjones/huggle.css for example - they then appear when you click the 3rd button (red blob - "revert this revision [R]"). Note that this file can get re-written if you change preferences within Huggle or there's a new version - which has to write the version number in it. When that happens I have to revert it back and do any necessary changes manually.
For the counting ones, you need to create the templates like those shown at Template:Huggle and then edit Wikipedia:Huggle/Config to add them in. Ronhjones ^(Talk) 21:50, 7 October 2010 (UTC)

Wow! I don’t understand anything you’ve said! But, I know that it means that you’ve given me a solution … now, I just have to figure it out … Thanks Ron! — Spike Toronto 19:48, 9 October 2010 (UTC)

Thanks Ron. I added some non-counting ones to my config file. I’ll get into the counting ones later. Thanks again! — Spike Toronto 06:07, 6 November 2010 (UTC)

Constant minor bug

Hi. Every single time I revert an edit, with a custom summary (ie "advanced" on the drop down list) and I check "Revert only the selection" (ie- undo), it always tells me that the edit is being reverted by someone else, when it isn't. Thanks Tom my! 20:30, 2 October 2010 (UTC)

Interface localization is done

Japanese interface localization is done. When next update, please check this page (m:Huggle/Localization/ja). ~~And I want Global setting on ja.wikipedia enable.~~ I think testing and translation of settings and templates are next step. Thank you :) --Was a bee (talk) 04:01, 3 October 2010 (UTC)

After part is done. So I erased it. thanks. --Was a bee (talk) 09:31, 3 October 2010 (UTC)

Thank you for inclusion ! --Was a bee (talk) 07:49, 9 October 2010 (UTC)

Revert summary line length

When selecting Advanced from the menu for the leftmost revert button, the line length in the very latest version (0.9.7) is significantly shorter than in the previous version (0.9.6). Can it be put back to the longer length please? Thanks! — Spike Toronto 17:50, 9 October 2010 (UTC)

I honestly don't see what your talking about. Pics would help but it seems to be the same side as it always been. Sido nuke 18:28, 9 October 2010 (UTC)

In my earlier HG session today, it was truncating lines like the following:

Significant content change w/out citing a [[WP:V|verifiable]] [[WP:RS|reference]]/[[WP:CITE|citation]] and/or providing [[WP:ES|explanation]]. Pls use [[WP:ES|edit summaries]].

But, now it seems okay. Go figure … I’ll let you know if it happens aggain. — Spike Toronto 19:46, 9 October 2010 (UTC)

Huggle 0.9.7: unable to log in to Portuguese Wikipedia

I'm a rollbacker of Portuguese Wikipedia and I've downloaded the latest version (0.9.7), but I can't log in to Portuguese Wikipedia. However, I've logged in to other projects, including English Wikipedia, but the program displayed "Use of Huggle on this project requires rollback.". What's wrong? Francisco ^{talk contrib} 23:01, 9 October 2010 (UTC)

Approval and 500 edits are required. Make sure you meet those requirements. I'll check out a few things and verify its working. Sido nuke 01:35, 10 October 2010 (UTC)

Just tested it myself and Huggle works fine on pt.wikipedia. Of course I bypassed two requirement checks in order to test... But for the most part I can not repo this. Sido nuke 01:54, 10 October 2010 (UTC)

But I still can't log in to Portuguese Wikipedia. Could someone verify the code, please? Francisco ^{talk contrib} 02:41, 10 October 2010 (UTC)

Are you absolutely sure you attempting to connect to the right wiki? Have you tried deleting huggle, downloading a new one, putting it in a new folder so its configuration is gone? Try those steps and get back to me with an exact error message. Sido nuke 04:24, 10 October 2010 (UTC)

I deleted the program, downloaded a new one and saved it to a program file folder (example: C:\Program Files\Huggle), but it still displays Unable to log in. Francisco ^{talk contrib} 14:47, 10 October 2010 (UTC)

Have you added enable:true to your pt:Special:MyPage/huggle.css? Access Denied ^{[FATAL ERROR]} 17:24, 10 October 2010 (UTC)

Yes, I have. Francisco ^{talk contrib} 17:50, 10 October 2010 (UTC)

I have repo the issue myself. Ironically I can by attempting to login as you, any other account works fine X.x. I'm going to look into it deeper now since I can swift though why its happening. If anyone is curious, \Requests\Requests.vb Line: 262 (If Result.Contains("

") Then Return LoginResult.Failed) is the direct cause of his login failures. Sido nuke 19:50, 10 October 2010 (UTC)

Error message returned is this "Erro de autenticação

A palavra-chave que introduziu é inválida. Tente novamente, por favor." Translation please? Sido nuke 19:54, 10 October 2010 (UTC)

That appears to be a incorrect password message. That seems to be the only reason for login failure. Because its a different wiki we don't seem to be catching the incorrect password error. I'm going to go ahead and build you a custom huggle so we can get your detailed error message. Sido nuke 19:57, 10 October 2010 (UTC)

I've typed my correct password. Francisco ^{talk contrib} 23:03, 10 October 2010 (UTC)

Sorry about not getting back to you soon enough, I've been busy lately with various things. Just be patient for now and I'll try getting in here to help. Sido nuke 08:14, 21 October 2010 (UTC)

IRC not using given proxy

The IRC does not use the proxy that I put in, and as such, I can't access the RC feed. 930913 (Congratulate/Complaints) 07:22, 11 October 2010 (UTC)

Sorry but from what I see it will take a bit of code to get IRC to run via a proxy. I'm not technically competent enough to do such a thing. If someone else does it then I'll put it in. For now try using a program that makes any program run via proxy. Sido nuke 08:13, 21 October 2010 (UTC)

Huggle not receiving any edits from the IRC recent changes feed.

I would surmise it's because they renamed the RC feed bot from "rc" to "rc-pmtpa". The Thing // Talk // Contribs 15:20, 13 October 2010 (UTC)

I have fixed it. In "irc.vb", the lines which contain "rc!~rc@" need to have that string changed to "rc-pmtpa!~rc-pmtpa@", in all 17 lines which contain the string. The Thing // Talk // Contribs 16:00, 13 October 2010 (UTC)

It should be noted that according to the devs in #wikimedia-tech on Freenode, there are going to be more changes to the IRC RC feed, so this is in no way reliable, as is any fix until they get everything completely settled. The Thing // Talk // Contribs 16:01, 13 October 2010 (UTC)

Fixed, new version up. Sido nuke 16:55, 13 October 2010 (UTC)

Constantly crashing

Please help Whenever I try to login, Huggle crashes at "Updating message filters". I'm using Windows Vista and I get the following error message:

Problem Event Name: CLR20r3

Problem Signature 01: huggle 0.9.8.exe

Problem Signature 02: 0.9.8.0

Problem Signature 03: 4cb5e2a5

Problem Signature 04: mscorlib

Problem Signature 05: 2.0.0.0

Problem Signature 06: 4bf2c227

Problem Signature 07: 349d

Problem Signature 08: 1f7

Problem Signature 09: System.UnauthorizedAccess

OS Version: 6.0.6002.2.2.0.768.3

Locale ID: 1033

This happened with Huggle 0.9.6 as well; I have never logged in successfully. Can anyone assist me here? Thanks. —Justin (koavf)❤T☮C☺M☯ 20:39, 13 October 2010 (UTC)

Your .NET runtimes maybe corrupted or something. I suggest reinstalling .NET. Google it for more info. Sido nuke 21:44, 13 October 2010 (UTC)

Thanks I just ran it as an administrator and it worked. Thanks. —Justin (koavf)❤T☮C☺M☯ 22:32, 13 October 2010 (UTC)

Reverts my edits

Huggle has wiped out my edits four times now.

Fifth Amendment, Hanson, Massachusetts, Neologism and Radiology.

Are there any plans to fix that bug? Slightsmile (talk) 02:42, 14 October 2010 (UTC)

Trying to figure out what I'm seeing here, Everything seems to be working fine. Sido nuke 18:59, 14 October 2010 (UTC)

The problem is that huggle isn't realizing that the edit was already reverted; there have been issues with this in the past, despite the fact that there are built-in safeguards against this. Calvin 1998 ^(t·c) 22:31, 14 October 2010 (UTC)

This is a bug but for the most part it doesn't seem to be causing major havoc. I can't repo this for the life of me, so It's hard to fix. Sido nuke 08:09, 21 October 2010 (UTC)

Localization setting

During translation of Huggle into Japanese, I found some point. Some are I think important, some are not so. I list here along its priorities.

1. Settings of "ja.wiki.x.io" and "language ja" are not included in Huggle itself. Now installation of Huggle is very complex for beginners :s

Please add this file(ja.txt) to this folder(Localization), and please add here a line ja.wikipedia;http://ja.wiki.x.io/, like this file(DefaultLocalConfig.txt)

2. Documentation link and Feedback link is fixed to en.wikipedia. Not all people can read English and some settings must be solved at local project (e.g. templates, edit summries)
3.I found 9 strings that is not translated, but translation setteings are exist. I list that here.

I don't hope everything solved. But only first point is very needed xo Now nobody can install Huggle by myself. --Was a bee (talk) 05:28, 19 October 2010 (UTC) (rewrite) --05:52, 23 October 2010 (UTC)

Content disappearing

Why does the content disappear when I try to edit a page? This is a bug. Wayne Olajuwon chat 21:01, 19 October 2010 (UTC)

Can you provide an example, diff, screenshot? Thanks Sido nuke 08:11, 21 October 2010 (UTC)

When I tried to edit a page the content just disappears such as I tried to do to my talk page. I had click show difference to tell that all of the content just disappeared. Wayne Olajuwon chat 16:52, 23 October 2010 (UTC)

Starting problem

This new version of huggle has problems starting. When I try to log in, it says "unable to log in" although the password, project and username are correct, just as they were with earlier versions. Is it only me, or is this some common, known bug? DARTH SIDIOUS 2 ^(Contact) 12:29, 21 October 2010 (UTC)

I have discovered why this message has appeared. The program works only when the correct language is set in the user preferences (en for English Wikipedia, pt for Portuguese Wikipedia, etc). If other language is set (en for Portuguese Wikipedia, pt for English Wikipedia, etc), it will fail to log in. Francisco ^{talk contrib} 22:05, 23 October 2010 (UTC)

Asterisk

Why is the "asterisk" showing in the boxes in the top right, if no edit summary has been made? Also, it covers the number of edits (like 2, 3, etc.) and makes it hard to see which number it is. Maybe it could be vertically aligned differently, rather than centered over the number? --Funandtrvl (talk) 18:51, 21 October 2010 (UTC)

The same thing is appearing when I use Huggle. Also, the (HG) isn't appearing in my reverts. ~Nerdy Science Dude 19:42, 21 October 2010 (UTC)

The * means automated assisted summary. Something has gone wrong in the regex or matching.... And the (HG) isn't appearing for now because I removed it in the project config. Sido nuke 20:37, 21 October 2010 (UTC)

Looks like Iridescent added it back. ~Nerdy Science Dude 00:52, 22 October 2010 (UTC)

Won't go into a edit war over it. So be it. Revolution is coming. Sido nuke 00:54, 22 October 2010 (UTC)

"Bad Word" Filter

Would it be possible to add a "bad word" filter? Such a filter would automatically detect words in diffs added that are commonly used in unconstructive edits, such as "hello," "was here," "gay," etc. Maybe make one of those colorful squares next to the article name show up in the queue? -down load ׀ sign! 04:00, 24 October 2010 (UTC)

You can do it at queue setting. 1. Open queue setting window from menu "Queue" => "Manage Queues". 2. Click "Add". 3. check "Load diffs for every revision in the queue". 4. switch to "Revision content" tab. 5. Set there regex, for example ([Hh]ello|was here|[Gg]ay) 6. Close queue window by clicking "OK" button. This would work. --Was a bee (talk) 04:40, 24 October 2010 (UTC)

Changing warning templates from final back to last

Should Huggle change the final warning templates back to last warning? Wayne Olajuwon chat 20:25, 25 October 2010 (UTC)

Also Huggle keeps having problems. Here's the error:

  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)

It also doesn't show anymore edits that I could possibly revert. Wayne Olajuwon chat 23:08, 25 October 2010 (UTC)

When Huggle throws one of those or similar error messages at me, it will also sometimes stop actually doing anything useful (getting new edits from the feed, showing diffs, reverting, warning, showing more than 0 edits per minute, etc). First, I will try to document the error on this page, staying civil despite any urges to the contrary. Then, if anything looks particularly hot, I will address it the old-fashioned way or with Twinkle or Rollback. Finally, I will restart Huggle, which will again behave. — $Jeff G. ツ$ 04:14, 9 November 2010 (UTC)

Double Reverting?

I've already done this twice today... doesn't the option to revert get grayed out if someone else has already reverted? Is it just my internet connection? -down load ׀ sign! 21:45, 27 October 2010 (UTC)

Sometimes HG does not update too rapidly when ClueBot reverts. And, it just about never updates when a revert is done by Twinkle. Best to always check each of your reverts before you leave the page by opening it in a browser. It only adds between 30 and 60 seconds to the transaction. — Spike Toronto 05:25, 28 October 2010 (UTC)

The main pane has the edits messed up

Yesterday when I used Huggle, it looked fine. Now, where it shows the differences in the article, all the differences are stacked on top of each other, making it impossible to read the article. I have tried rebooting Huggle, rebooting my computer, deleting the configs, and resetting the configuration file under my user page. Nothing seems to fix it. Does anybody know what I should do to fix this? Reaper Eternal (talk) 10:42, 30 October 2010 (UTC)

Same here - Happy sailor 12:35, 30 October 2010 (UTC)

I'm seeing the same problem...looks to be a rendering issue. Did Microsoft change something in their libraries? --Alan the Roving Ambassador (talk) 16:13, 30 October 2010 (UTC)

My screen has squashed text as well. I lack the technical wherewithal to address the issue; there seems to be no discussion re: this on irc. Tiderolls 16:16, 30 October 2010 (UTC)

Same here. I tried late last night (approx. 2:00AM EST) and had the same mess. I tried re-installing, in case the program itself had become corrupted, and deleted all the config files. No help. — Spike Toronto 17:05, 30 October 2010 (UTC)

When Huggle wasn't working for you guys, did you guys receive this: Huggle has encountered a problem and needs to close. We are sorry for the inconvenience.? Wayne Olajuwon chat 18:13, 30 October 2010 (UTC)

Not in this instance. Huggle doesn't want to shut down, it just doesn't display the article text properly. Now I find that I can copy and paste the text to a word doc and read the complete edit. Strange stuff Tiderolls 18:16, 30 October 2010 (UTC)

I’ve received no error messages either. Alternatively TideRolls, you can open the diff in a browser by pressing the

button. Then, review the diff and, should it need reversion, use HG to do the job. — Spike Toronto 18:27, 30 October 2010 (UTC)

I don't know why Huggle wants to shut down for me because it has some problem and I don't know what it is. Plus, I can't even keep up with some users to beat them to vandalism. Huggle needs to be faster. Wayne Olajuwon chat 18:48, 30 October 2010 (UTC)

I'm still getting the squashed text too. Using IE8. --Funandtrvl (talk) 19:56, 30 October 2010 (UTC)

Every paragraph is limited to 1.5 lines. I can see no recent changes in any of the Huggle config files that could upset it. I would guess that Wikipedia may have done something with their normal css entries, so that Huggle cannot understand the css in use. Ronhjones ^(Talk) 22:11, 30 October 2010 (UTC)

Yes, it just started today. Changing font in the css page doesn't help. (Using FF 3.6.12)Geoff ^{Who, me?} 22:12, 30 October 2010 (UTC)

Thanks Ron & Geoff. I checked the HG config files too and could see no changes. But, Ron’s explanation and Geoff’s test do provide us some information. I guess we have to wait for one of either User:Sidonuke or User:Gurch to fix it in 0.9.9 Thanks! — Spike Toronto 22:49, 30 October 2010 (UTC)

Glad to know it's not just me. LOL. --Ixfd64 (talk) 22:52, 30 October 2010 (UTC)

I tried using IGLOO just now, and for a couple of pages it complained about badly formatted XML markup. There might be a connection. Ronhjones ^(Talk) 22:58, 30 October 2010 (UTC)

I think I’ll just press the

button in HG, look at the diff in IE, then, if it needs reverting, I’ll make the appropriate selection in HG. That procedure should be okay until the issue is resolved. — Spike Toronto 23:57, 30 October 2010 (UTC)

Ok so hopefully a solution will be found, I am also glad that it is not just me Jab843 (talk) 00:42, 31 October 2010 (UTC)

This change broke it. Gurch (talk) 02:36, 31 October 2010 (UTC)

Thank you! Reaper Eternal (talk) 02:55, 31 October 2010 (UTC)

So whats the solution? --Jab843 (talk) 03:05, 31 October 2010 (UTC)

Version 0.9.9.[2][3] — $Jeff G. ツ$ 03:14, 31 October 2010 (UTC)

Thanks to those who fixed this problem. Hope you have a safe and vandal-free Halloween! (yeah, I know, that ain't gonna happen...) --Funandtrvl (talk) 04:25, 31 October 2010 (UTC)

Sorry for that. I don't know what HTML engine Huggle is using, but interpreting the height as an absolute is strange. The change in Monobook (and Vector) is a temporary fix until MediaWiki is updated to properly display empty context lines. So I'm a bit suprised to see the change in 0.9.9 describe the edit to Monobook as "unwanted". — Edokter • Talk • 11:18, 31 October 2010 (UTC)

Considering the frustration that the monobook/vector changes caused yesterday to us Huggle users, I think the word "unwanted" doesn't mean that the temp fixes to monobook and vector were unwanted, it means that Huggle had to be changed (unwantedly) by the people above, who had to spend a lot of extra time figuring out what was causing the problems with Huggle not displaying properly (especially on a high-vandalism Saturday). Maybe this is a good example about how communication needs to be improved between the coders for the skins, and the coders for these special programs, like Huggle. I still remember the problems with the "cite web" tools being wiped out when the change to vector was made back in May. (I'm sure you saw the massive comments about that!) So, this could be a good learning lesson for those who have to update codes (which I know nothing about) to be able to work together with the different tool-making people, a little more seamlessly? I'm not sure how that process could be implemented and improved, but there is definitely a need for it. --Funandtrvl (talk) 19:38, 31 October 2010 (UTC)

I think in this case the outcome was unforseen and unpredictable. The skins serve one main purpose: to display information. There are dozens of scripts and applications that interact with Wikipedia using different methods (API, HTML etc.); trying to account for all possible outcomes is near impossible. I don't know how Huggle works or how it gets its information, but it shouldn't barf at such a trivial CSS change. I tested it in all three major browser engines (Trident, Mozilla and Webkit) without problem. Anyway, it's been fixed. — Edokter • Talk • 19:55, 31 October 2010 (UTC)

Huggle now ignores the skin files completely for diff display, instead it re-constructs the basic appearance of the diffs from scratch. So there should be no issue in the future. As a result of this, you may notice some change in the way diffs are displayed. Gurch (talk) 19:57, 31 October 2010 (UTC)

Edit Summary for First Warning

The first data line of Wikipedia:Huggle/Config#Warning (or that area before the Warning section existed) read "Message re." from this initial edit by Gurchzilla (now Gurch) 22:40, 26 May 2008 (UTC) to this standardizing (to fit with the other levels' warnings) edit by Zhou Yu 23:54, 4 March 2010 (UTC) and then "Level 1 warning re." until this revesion edit by Wayne Olajuwon 00:40, 31 October 2010 (UTC), when it was changed back to "Message re." Following WP:BRD, please discuss the relative merits of these two options, as well as a modification (changing the dot "." to a colon ":"). Thank you. — $Jeff G. ツ$ 02:57, 31 October 2010 (UTC)

I used "Message" rather than "Level 1 warning" because of people's tendency to use it for things that were unwanted but that didn't really warrant a warning. Ideally they would use an appropriate message, of course. Gurch (talk) 03:04, 31 October 2010 (UTC)

I agree, the typical level 1 message is not a warning at all, it's a coddling welcome with a bit of advice. Level 2 is where we get serious. — $Jeff G. ツ$ 03:11, 31 October 2010 (UTC)

I changed it back to Message re. with this edit as you showed earlier. Wayne Olajuwon chat14:27, 31 October 2010 (UTC)

Huggle problems continue

Huggle again gave me a warning saying that it "has a problem and it needs to close. We are sorry for the inconvenience." Wayne Olajuwon chat 21:09, 31 October 2010 (UTC)

I also keep being beaten to vandalism by other Huggle users. Wayne Olajuwon chat 22:04, 31 October 2010 (UTC)

You keep saying that. How is that a bug exactly? How would I be able to fix it? What makes you so special that it's OK for you to revert before someone else does, but not the other way around? Gurch (talk) 22:13, 31 October 2010 (UTC)

Maybe because Huggle is sometimes slow and sometimes fast. No, I am not special. It may depend on your connection speed. It's a bug because it keeps stop responding and it keeps giving me that warning. Wayne Olajuwon chat 00:07, 1 November 2010 (UTC)

I haven't been getting the "has a problem..." message today, but when someone beats me to reverting a vandal edit, the window just stops working and freezes up for about 30 seconds. I usually have to view the page in the browser to see what happened, and most of the time, Huggle doesn't display the "do you want to revert a white-listed user?" nor does it show what's happening down in the log, but instead just stops working on that particular page. Then, I have to pick another page before Huggle will get going again. At least, that's been my experience today. Hope this helps to describe the problem! --Funandtrvl (talk) 00:17, 1 November 2010 (UTC)

Thanks but that doesn't happen to me but Huggle just gives a warning saying that it has to close but I keep using Huggle anyway and I use Huggle on a Gateway 2000 computer. It also stops responding for me for a few seconds, then I click another window myself until Huggle starts working again when I click the Huggle window. Wayne Olajuwon chat 00:34, 1 November 2010 (UTC)

I use Huggle on a Gateway 2000 computer

Then your system is at least 12 years old, and originally shipped with Windows 98. If you still have Windows 98 installed, while Huggle may happen to work, your configuration is not supported, and is not recommended as Windows 98's outdated Unicode support may lead to problems editing articles that contain special characters. If you have since upgraded the operating system, you are likely running at or near the minimum hardware spec for that OS. Don't expect Huggle -- or most other modern applications -- to be particularly responsive.Gurch (talk) 01:14, 1 November 2010 (UTC)

I do experience the same problem that User:Funandtrvl mentioned above. Also, HG seldom if ever seems to update when the revert has been done by a dreaded Twinkle user. Thanks! —Spike Toronto 04:43, 1 November 2010 (UTC)

No my system is not twelve years old and it is Windows XP and not Windows 98. Huggle is just to slow and I can't keep up with nearly everyone and it's the same users beating me to vandalism. It's just not fair because their Huggle is faster and mine is slower. Another problem is that I am persistently being beaten to vandalism because of how slow Huggle is.Wayne Olajuwon chat 21:52, 1 November 2010 (UTC)

Don't get paranoid Wayne, You've just beaten me about 20 times in the last hour, that's the nature of the beast. Ronhjones ^(Talk)22:25, 1 November 2010 (UTC)

Part of it too Wayne is the time of day. Lots of vandal fighters cover the hours after school ’til dinner time. We are all getting beat by others. If you want to have the field all to yourself, try after 3:00AM EST. There is less vandalism, but still enough that you are kept busy and your reports to AIV will keep the blocking admins busy! —Spike Toronto 23:01, 1 November 2010 (UTC)

The "being beaten" thing happens to all of us at times. Huggle is very busy in the background watching the IRC Recent Changes feed, pre-loading diffs, loading user data (such as number of user reversions and warnings). All it takes is for one of these actions to slow down, and things can come to a crawl. Earlier today, en.wikipedia was apparently bogged down, and Huggle came crashing down on me in a spectacular fashion after several diff/userinfo preloads timed out and/or failed. :) -KGasso(talk) 23:13, 1 November 2010 (UTC)

If three people are actively monitoring changes, statistically speaking someone else will revert first two-thirds of the time.

If this is happening, it is a good sign that there are enough people monitoring changes and that your time may be better invested with some other maintenance task.

Gateway dropped the "Gateway 2000" line on October 31, 1998, so unless yours is a more modern model of Gateway system it cannot be any less old than that. Gurch(talk) 02:33, 2 November 2010 (UTC)

Wayne, go to here, and change the preload number from 2 to 5. That should significantly speed things up for you. The Thing // Talk // Contribs 03:57, 3 November 2010 (UTC)

Done, The Thing. Wayne Olajuwon chat 14:44, 4 November 2010 (UTC)

Also, I'm still being beaten to vandalism after setting the preload to 5. The preload number may need to be higher. I can't even beat both ClueBots to vandalism nor some other Huggle users. This preload hasn't completely paid off yet. It still has problems but not as much as before. What is going on with Huggle? Gurch needs to something about this.Wayne Olajuwon chat 16:37, 4 November 2010 (UTC)

Dude... stop it. You're not special. You're not supposed to be faster than everyone else all the time. Especially not the bots, which unless they experience network latency are faster than anyone. Gurch (talk) 16:44, 4 November 2010 (UTC)

I'm not special is that I'm telling Huggle what's going on with my Huggle. I'm just saying what's going on with my Huggle. That's all. I understand what you're saying. Also, how do some users are able to use Huggle and not update Huggle's whitelist when they exit Huggle? Wayne Olajuwon chat 16:48, 4 November 2010 (UTC)

(edit conflict)What kind of internet connection are you on? If it's anything less than broadband, then Huggle will not load things very quickly. If a lot of people in your home use the internet all at once, that may slow things down too. How much performance your computer has is also a good indication... like, how fast your CPU is. (How many Megahertz/Gigahertz it's rated at... anything less than 1 Ghz will slow things down) How much memory your computer has. (Anything less than 1 Gigabyte might slow things down) Running a lot of other programs in addition to Huggle will also slow things down. (Running just Huggle and something like a web browser should have no ill effects.) What operating system you use... (I've had the best speeds with Huggle in Windows XP. Windows 7 is slower.)

Of course, bigger figures might not always translate into better performance in the program... for example I have a laptop which has a 1.9 Ghz dual core CPU, 2 GB of memory, and a wireless card, with Ubuntu 10.10 as the operating system. I run Windows XP in a virtual machine with VirtualBox, which assigns the virtual machine 800 megabytes of memory. Running Huggle inside this XP virtual machine, it loads diffs practically instantly. I also have a tower computer which has a 2.1 Ghz dual core CPU, 3 GB of memory, and a wireless card, with Windows 7 as the operating system (it used to have a dual boot of XP and 7). Normally that would translate into better performance for Huggle, but in my case it doesn't. On the tower, there is a noticeable lag in the loading of diffs, in both Windows XP and 7. On my laptop, even with the Windows XP being run inside Ubuntu, with less than half of the memory being allocated to it, and less than 1/3 of the ram that my tower has, it still runs noticeably faster than the tower.

You see, in the tower, there is a bottleneck somewhere, one which I haven't found yet. There is always something in a computer which is slower than everything else, the aforementioned bottleneck. That one component is slowing some other things down along with it, because those other things, which rely on the slow component, have to wait for it to do its job. In my case, it could be the wireless card, maybe there's a latency resulting from where it connects inside the computer. Or it could be the memory... it may be a large amount, but it could also be slow at transferring information. Or it could be the operating system... maybe a setting somewhere is creating the bottleneck, or something else in one of the countless hundreds of system files that the operating system uses at any one time. Your computer could also be infected withmalware, which is slowing things down. Or maybe it's your antivirus software is using a lot of the computer's resources Switching to a different antivirus may speed things up. If you're running a theme like Windows Aero in Windows Vista/7, it may look nice, but it may be using a lot the computer's resources. Turning that off may speed things up. There's a countless number of things which can slow things down for you. Some of them can't be helped, but a lot could be fixed, both with the hardware of the computer (upgrading things), or the software (turning off unnecessary programs). Sorry for the tl;dr'ness and some of the technical jargon. The Thing // Talk // Contribs 17:47, 4 November 2010 (UTC)

Great explanation of other possibilities TTTSNB! — Spike Toronto 18:01, 4 November 2010 (UTC)

(edit conflict)Wayne, yesterday you and I were Huggling at the same time and you beat me to the punch almost 10 times in a row! This happens to all of us. As Gurch said above, if three Hugglers are looking at the same vandalizing diff at the same time, one of them will revert before the other two every time. That means, in that example, that one will be beat 67% of the time. It’s just a fact of Huggling. If you want to be the first on the scene most of the time, you have to pick a time when few of us are Huggling, like after midnight in the eastern time zone. Thanks! — Spike Toronto 17:42, 4 November 2010 (UTC)

P.S. Two more points: (1) Beating ClueBot is a rarity. So rare that there is even a userbox to mark the occasion. (2) Chances are, other users who are not updating the Whitelist when they exit are most likely crashing out of Huggle. Thanks! — Spike Toronto 17:56, 4 November 2010 (UTC)

I just barely noticed that you mentioned that you use a Gateway 2000. Of the only computer model I could find whose model name was Gateway 2000, it had these specs: A 300 MHZ processor, 256 Megabytes of ram, an 8 Gigabyte hard drive, internet cards, USB, all that stuff... Those specs are just barely meeting the recommended system requirements for Windows XP. To put it as a matter-of-fact, I don't see any way of speeding up Huggle on a computer so old and so slow. In fact I'm surprised that Huggle even runs at all, and doesn't just freeze up completely and refuse to run each and every time, like it did with a 750 Mhz system of mine that I used to have.

This may be of little help, but if Huggle lite (aka 0.7.12) were still around, it might have actually worked for you... it worked for me perfectly on my old system mentioned in the last paragraph. When the next version of Huggle came out after that one, 0.8.1 I think it was... I didn't know what was done to it, but it had so many bugs, became so slow and froze up so much on that computer that I never used anything other than the lite version(s) until I had gotten my current tower, and was able to use the new versions of Huggle, and the newest versions are improving in speed... <nostalgia>but man, frankly nothing will be as fast as 0.7.12 or the other lite versions. If those could have been fixed by someone, we'd probably all still be using them, but some MediaWiki update managed to completely kill off those versions.</nostalgia> The Thing // Talk // Contribs 18:26, 4 November 2010 (UTC)

The weird thing Spike, was that I was beating you to vandalism 10 times in a row on a computer that's not very fast. The Thing, I should get a modern computer with Windows XP and I would Huggle on there. WAYNEOLAJUWON 16:25, 5 November 2010 (UTC)

If you have a Windows XP installation disc handy, and enough money for a new computer, that shouldn't be a problem, though you may have problems finding device drivers for an extremely new computer for Windows XP. Microsoft stopped selling XP some time ago, so most computers come with Windows 7 or Vista (*shudder*) pre-installed. That may or may not be your best bet, as on one hand it would have all of the drivers necessary, and 7/Vista comes with the .net framework, so you can run Huggle right away. On the other hand, it would probably have bloatware that would slow things down, though you can easily uninstall anything that you don't want or need.

If you get one with Windows Vista, unless it's a high-end computer, install something else over it, it will save you a lot of trouble. If you can find all of the drivers for XP, and you're comfortable with running a 10-year old operating system, you can easily reformat the drive and install XP on it. Both 7 or XP on the new computer would probably be quite a bit faster than your current setup.

If you get a new computer, and are considering installing XP in place of the current operating system, before you do anything, I highly recommend running the XP setup disc up tothis screen. If, at that screen, nothing is listed in the box, XP can't find your hard drive.

Windows XP was made for hard drives with IDE interfaces, but most modern computers come with hard drives that use SATA. XP's setup program provides an option to load a SATA driver via a floppy disk. You can either make a floppy disk with the drivers on it if your computer has a floppy drive, or you can do this: If you know how to work your way around the CMOS setup utility, accessible by pressing a certain key such as F1 or delete immediately after you turn on your computer, you need find a setting that says something like "SATA mode" or "AHCImode", it may look like this depending on the computer you get. That needs to be switched to something like "ATA mode", "legacy mode", or "IDE mode", so that XP see the drive. If you can't find the option, and it doesn't have a floppy drive (most computers don't have them nowadays since they're so outdated), you're pretty much out of luck and will have to stick with the current operating system, or if it's running Windows Vista, you could always upgrade to, or do a clean install of Windows 7. The Thing ^T/_C 17:28, 5 November 2010 (UTC)

@Wayne: For me, I have the opposite experience of TTTSNB. My Dell XPS tower with hyperthreaded processors runs Huggle faster than my Dell Latitude D630 notebook with Core2Duo porcessors. But I think it’s because the tower has infinitely more RAM.

@TTTNSB: It’s interesting that you say the XP was designed for IDE drives, because each of our computers that shipped with XP Pro installed came with SATA drives. I haven’t had an IDE drive since Windows 98. I wouldn’t have known that XP was originally intended for IDE if you hadn’t mentioned it. By the way, like your new compact signature. How about some colour? — Spike Toronto 21:45, 5 November 2010 (UTC)

Well, it probably either already had the SATA drivers installed, or the hard drive controller is set to the legacy mode... my tower has SATA drives for example, but there is no such mode in the CMOS setup utility to change, so presumably the hard drive controllers are permanently set to legacy mode, which would be supported by the fact that I had no problems installing XP the dozens of times that I did when I was experimenting with dual-boot setups on it. The Thing ^T/_C 01:36, 6 November 2010 (UTC)

Windows XP is better, Spike. Gurch, when I press the Q button when I revert an edit, Huggle sometimes doesn't warn that user. WAYNEOLAJUWON 22:35, 5 November 2010 (UTC)

I only use XP. Whenever we ordered new computers during the Vista years, we still insisted that they have XP as the operating system. As for HG not always warning users, usually when that happens, if you look at the log at the bottom you will see a message indicating that the they have not edited since last warning, or that they were warned less than 10 seconds ago, etc. Also, if their talk is red, the log below will not indicate that they were warned even though they would have been. — Spike Toronto 04:58, 6 November 2010 (UTC)

Huggle also does that and it says unknown error and now Huggle has stopped responding. Also when I try to revert an edit on Huggle, sometimes it doesn't revert or it's too slow. I'm not trying to be special when I saying this is that Huggle takes a while to revert than normal. WAYNEOLAJUWON 16:17, 6 November 2010 (UTC)

This thread is hilarious. Speaking as a vandal fighter, I didn't know that some of my other Wiki comrades view it as a game where the point seems to be beating other Wikipedians. I always thought the point was to beat the vandals off the Wiki (if they won't convert to good productive editors)....or are we playingWhac-A-Mole? Is there a prize somewhere that I don't know about? If so, I can adjust my philosophies accordingly. At the present, I'm content seeing that one of my vandal-fighting colleagues beat me to it, so long as it gets done. I don't care which tool(s) they use to do it. I happen to use Twinkle because I'm usually on a Linux box. I'm not annoyed when other Twinkle users beat me to it nor am I annoyed if they use Huggle, popups, etc. With the end goal achieved, I wouldn't say there is a problem.

What are the personal goals/views of those who are trying to beat other Wikipedians to it? What are you after? Is this about increasing your edit count? ...or having a userbox that says "50,000+ Vandals Reverted"? What is your motivation?
⋙–Berean–Hunter—► ((⊕)) 18:37, 2 December 2010 (UTC)

Inadvertent reversion to vandalized revisions after another editor has removed vandalism

Obviously, edits such as [4] and [5] aren't intentional - and this isn't the first time Huggle has partially undone my reversions of vandalism. Since the users through whose accounts these edits are made are themselves whitelisted by Huggle, the reintroduction of vandalism may well go unnoticed. I suggest that a high priority be given to the resolution of this malfunction. Peter Karlsen (talk) 02:58, 3 November 2010 (UTC)

To be fair this is frequently an operator problem with people not paying enough attention before the press revert. James (T C) 05:42, 3 November 2010 (UTC)

Let's assume that these problems do result from operator error. The software could still be refined to eliminate them: this particular error almost always results from partially reverting an edit by a user on Wikipedia:Huggle/Whitelist (myself, in the case of these particular edits) to a revision by a user who isn't whitelisted. I believe that when an editor tells Huggle to do this, this action is usually a mistake, not the desired result. Therefore, reversion of a whitelisted editor to a revision by a non-whitelisted user should raise a warning dialog before the edit is saved. Peter Karlsen (talk) 07:31, 3 November 2010 (UTC)

There is a little, blue, arrow button — like this

— that lets one go backwards until one finds a clean version to which to revert. Your problem usually happens because someone before you — sometimes even ClueBot or some other bot — has not themselves reverted to a clean version, and then you or I come along and compound it. Try the

, or use Popups in these cases (software that I believe you already use). In all fairness, though, sometimes one cannot get back far enough with the

and you just have to manually go through the history, find the right version, and then use Popups to revert. After that, I use Huggle to template the intervening vandals so long as their vandalism has been within the past two days. Thanks! — Spike Toronto 20:45, 3 November 2010 (UTC)

Huggle is currently disabled on all projects

“Huggle is currently disabled on all projects,” is the message that many of us are getting when we try to log on. Does our favorite vandal fighting tool have a cold? Thanks! —Spike Toronto 05:05, 3 November 2010 (UTC)

Huggle is defunct and may not be used anymore. Sido nuke 05:18, 3 November 2010 (UTC)

That can't be serious...!? --77.11.61.179 (talk) 05:37, 3 November 2010 (UTC)

The Wordsmith has helpfully volunteered to take responsibility for problems with Huggle; please direct all future complaints to him. Gurch (talk) 05:55, 3 November 2010 (UTC)

Thanks, but it doesn't work at de.wikipedia at the moment: “Huggle ist im Moment auf allen Projekten deaktiviert. (Huggle is currently disabled on all projects.)”--77.11.61.179 (talk) 05:59, 3 November 2010 (UTC)

I think I fixed it on de.wikipedia. Please update to version 0.9.11, it should work. The Wordsmith^Communicate 08:10, 3 November 2010 (UTC)

Everyone just use igloo until Huggle is fixed andplease be careful qhere you discuss this, we don't want Hagger and his friends finding out huggle is down. Access Denied – talk to me 06:01, 3 November 2010 (UTC)

Huggle is back up. The Wordsmith^Communicate 06:33, 3 November 2010 (UTC)

Patched huggle

~~http://toolserver.org/~overlordq/huggle.exe~~

Advertises itself as 0.9.10 and ignores the enable-all flag. Q ^TC 06:10, 3 November 2010 (UTC)

Thanks! --77.11.61.179 (talk) 06:13, 3 November 2010 (UTC)

The current version is 0.9.11. - Mike Rosoft (talk) 08:01, 3 November 2010 (UTC)

Yeah, that version is back to normal. Sorry about that. Sido nuke 08:42, 3 November 2010 (UTC)

Would someone please update the change log? Thanks! — $Jeff G. ツ$ 02:09, 5 November 2010 (UTC)

Updated it. Sido nuke 00:50, 7 November 2010 (UTC)

Thanks. Does that mean that 0.9.9 and 0.9.11 are identical to each other, other than the version number? — $Jeff G. ツ$ 01:13, 9 November 2010 (UTC)

Yes, that's what it means. However, 0.9.11 is the only usable version on en.wikipedia currently. The Wordsmith^Communicate 01:18, 9 November 2010 (UTC)

Thanks for the explanation. I would suggest a new capability: selective disabling of particular version numbers that either have terminal design flaws or are no longer compatible with enwp. — $Jeff G. ツ$ 01:58, 9 November 2010 (UTC)

ways to speed up reverting?

Huggle is the fastest anti-vandalism tool I've ever used, but some edits will occasionally take much longer to revert than usual. Although this doesn't happen very often, it can be a little annoying to have to wait half a minute for a revert to go through. I've noticed that the following settings seem to decrease the reversion time:

Enabling preloading on Huggle
Selecting "Preload diffs when queue is active"
Enabling "Do not show page content below diffs" on Wikipedia

Is there anything else I can do? --Ixfd64 (talk) 23:48, 4 November 2010 (UTC)

I am experiencing some of the same problems as you are. Although the revert itself is not slow, loading up diffs takes a really long time for some reason. —MC10 (T•C•GB•L) 04:14, 5 November 2010 (UTC)

Ixfd64, I cannot find in Huggle your second setting option: Selecting "Preload diffs when queue is active". Where does one locate it? Thanks! — Spike Toronto 04:28, 5 November 2010 (UTC)

It's under Queue > Manage Queue... (not System > Options...). --Ixfd64 (talk) 05:35, 5 November 2010 (UTC)

Found it! Turns out that my settings already had the two you recommended. Another question: Why does Enabling "Do not show page content below diffs" on Wikipedia affect the speed of Huggle? Thanks! — Spike Toronto 06:02, 5 November 2010 (UTC)

I'm not sure, but it seems to help (at least for me). I'm guessing it's because it reduces the amount of data that has to be loaded. --Ixfd64 (talk) 06:13, 5 November 2010 (UTC)

I guess I’m confused because I thought that the browser and HG ran independently from one another. I do not even have a browser open when I use HG, although I do stay logged into WP (i.e., I do not log out) before closing the browser and loading HG. Thanks! — Spike Toronto 06:16, 5 November 2010 (UTC)

Huggle appears to use some of the built-in capabilities of IE and Windows to fetch and render diffs; reducing the amount of data sent by a server in a diff should reduce the amount of time it takes to fetch and possibly render that diff, and that could result in a perceived increase in speed both for the Huggle user and for other users of WMF projects and the infrastructure between the Huggle user and the data in the WMF databases. — $Jeff G. ツ$ 16:15, 5 November 2010 (UTC)

Thanks for the explanation Jeff. On my recent-changes-patrol account, then, I’ll enable "Do not show page content below diffs." Thanks! — Spike Toronto 21:33, 5 November 2010 (UTC)

UPDATE: Thanks Ixfd64 and Jeff. Turning off the content below the diffs seems to have made quite a difference! — Spike Toronto 06:39, 6 November 2010 (UTC)

No problem. --Ixfd64 (talk) 22:36, 6 November 2010 (UTC)

You're welcome. — $Jeff G. ツ$ 01:12, 9 November 2010 (UTC)

I've had a few reverts today that took over ten seconds. Are there any other ways to speed them up? --Ixfd64 (talk) 00:51, 8 November 2010 (UTC)

I don't get questions like this at all. Do you forget when using Huggle that there's an Internet connection involved? Have you never experienced randomly slow response times on any other website ever? Why do you expect Huggle to magically be able to extract faster response times from Wikimedia servers than your web browser doing the same thing?

Pages with pending changes on take twenty seconds to load, be thankful your reverts are only taking ten. Gurch (talk) 09:21, 8 November 2010 (UTC)

Hi Gurch, I figured that the Internet connection was the main factor, but I noticed that using certain settings (such as preloading diffs) seemed to speed Huggle up. I was just wondering whether there were any other settings that I could use for optimum speed. This was not a request to "make a faster version of Huggle"; sorry if I wasn't very clear.--Ixfd64 (talk) 18:56, 8 November 2010 (UTC)

Protection of config files

Why have Huggle's config files been left totally unprotected, both here and on Meta? PleaseStand ^(talk) 04:53, 6 November 2010 (UTC)

The config file here is protected.. [edit=autoconfirmed:move=autoconfirmed] and on meta [edit=autoconfirmed] [move=sysop] ·Add§hore· ^{Talk To Me!} 16:21, 6 November 2010 (UTC)

Anyone determined enough to mess with the configuration would know how to get an account autoconfirmed. PleaseStand ^(talk) 18:40, 6 November 2010 (UTC)

Occasionally people who are not admins find a good reason to change the config page. Calvin 1998 ^(t·c) 21:30, 6 November 2010 (UTC)

And, it is well-policed. When there was an incident last Spring wherein an editor was unilaterally and globally changing the default edit summary, it was quickly dealt with each time by one of the regulars. When the editor making the changes wouldn’t get the point, it was dealt with by an Administrator. You can review from this edit tothis edit. — Spike Toronto 23:46, 6 November 2010 (UTC)

Huggle configuration is monitored by a bot that will alert me of any changes. We would be able to catch any malicious activity and quickly revert it.Sido nuke 00:49, 7 November 2010 (UTC)

WP:Huggle/Users

Why would this be removed if some those users are still using Huggle and all of them should be there as a list of people who have used Huggle? WAYNEOLAJUWON 20:24, 7 November 2010 (UTC)

I noticed that yesterday too. The entire list was cleared out. I add to re-add myself yesterday, as has everyone since. Also, I can find no discussion at WP:HGF from that time. Is there some way to notify Hugglers that they may need to re-add themselves? Thanks! — Spike Toronto 21:07, 7 November 2010 (UTC)

Both the userlist and whitelist are occasionally cleaned out to remove users who no longer use huggle. As huggle will re-add you automatically the next time you use it, it shouldn't be necessary to re-add yourself manually. Calvin 1998 ^(t·c) 00:20, 8 November 2010 (UTC)

Half of that must not be correct all the time. Otherwise, the edit history would not be filled with edit summaries where Hugglers are adding themselves. Maybe’s it a bit of a glitch like how SineBot sometimes signs unsigned comments on my talk page and sometimes (most often) does not. — Spike Toronto 00:47, 8 November 2010 (UTC)

The majority of edits on that page are due to Huggle adding the user automatically. And some users seem to be adding themselves before using the program for the first time. Cases where users had to add themselves manually appear to be quite rare. I noticed Alpha Quadrant added himself manually, but he was also added automatically in an earlier edit. I'm not sure how or when he disappeared from the list, whether that was intentional removal or an actual Huggle bug. Reach Out to the Truth 16:53, 8 November 2010 (UTC)

Thanks for the explanation Truth. In my own experience, I edit from two accounts. I used to Huggle using my main account, which was added automatically; I did not manually add it since the big cleanout in July. I now Huggle from a “maintenance” account, which I had to add manually. If this is a glitch, I would imagine that it’s not important enough to worry about. Thanks again! — Spike Toronto 18:59, 8 November 2010 (UTC)

Some of the users that were using Huggle when WP:HG/U was blanked at that time, some of the users that were on that list aren't on the current even though they still use Huggle. You shouldn't remove the current Huggle users. WAYNEOLAJUWON 21:10, 8 November 2010 (UTC)

The software will re-add them automatically. We clear out users and whitelist periodically, otherwise they'd be the length of pipe rolls and overload the memory of the software's users. This is not up for debate. – iridescent 21:23, 8 November 2010 (UTC)

I don’t think anyone’s debating Iridescent. As it says at the top of WP:HG/U:

This page contains a list of editors who use Huggle. It is provided for convenience, not approval purposes. It is not necessary to add users to the list; this happens automatically. Inactive users may wish to remove themselves from the list; however, the list is also cleared semi-regularly so that it stays current. [Emphasis added.]

What Wayne’s post, and my post above, simply say is that, whatever part of the program is supposed to automatically add users, it can be glitchy sometimes. But, as I sort of said above, “Who cares?!” If this is as glitchy as the program gets, it’s of little importance. I am not even sure what purpose the list has … unless it is to be used by the programme’s developers to periodically notify users. Thanks! —Spike Toronto 23:12, 8 November 2010 (UTC)

inconsistent behavior when reverting a page that has already been rolled back

I've noticed that if another user beats me to a revert, then one of the following things will happen:

Huggle does nothing - it just displays the "Reverting <page name>..." message, which then disappears
Huggle prints a message saying that the page has already been rolled back
Huggle prints a message saying that the target revision is identical to the current one
Huggle tries to revert the user who reverted the page
If the user being reverted has made more than one edit in a row, then Huggle may revert the article to the user's second-to-last edit (which would most likely be vandalism)

This seems rather inconsistent, and it should be fixed. The correct response should be (2), which doesn't actually very often. Response (3) is technically correct, but it's a little vague because it doesn't say that another user has reverted the page; it can imply that the vandal reverted their own edit, which usually isn't true. (5) is somewhat troublesome because it also does not indicate that the page has been reverted. --Ixfd64 (talk) 02:31, 8 November 2010 (UTC)

It can't be "fixed". Gurch (talk) 09:22, 8 November 2010 (UTC)

Thanks Gurch. The charts should be very instructive. — Spike Toronto 09:28, 8 November 2010 (UTC)

Thanks Gurch, that's a lot of helpful information. Is it OK if I add that link to the manual? --Ixfd64 (talk) 19:11, 8 November 2010 (UTC)

Well, it's not really information you need to know in order to use Huggle. But it is information you need to know if you want to complain about Huggle. Gurch (talk) 20:22, 8 November 2010 (UTC)

It's a good diagram - hopefully, no one will moan any more... I get beaten all the time, if I check it's normally as US based editor, my poor old edit has got to go the length of England, then over to the Dutch server, and then over the pond... Ronhjones ^(Talk) 21:22, 8 November 2010 (UTC)

I'd also like to thank you for that, Gurch, and for all your work on Huggle (and against vandalism). Should you want to expand closer to the real world, you might want to include multiple slaves with multiple caching proxies, each with their own latency to the master. There is also latency on the IRC network - does Huggle try to use the same Freenode IRC server (node) being used by the IRC bot? If not, there is a way for you to help with the delays. :) — $Jeff G. ツ$ 01:31, 9 November 2010 (UTC)

The diagrams are complex enough already. And there is no Freenode IRC sever involved at any point, only irc.wikimedia.org, which is only on one server. Gurch(talk) 06:16, 9 November 2010 (UTC)

I don't know how feasible it would be, but what if each huggle client got its revision list from a dispatch server, instead of the IRC feed directly? That way the server could ensure no two huggle users are viewing the same revision concurrently. Should cut down on accidental edits and undefined behaviour resulting from edit overlap. I figure the server could populate a queue from the IRC feed and dish out revisions to active users. After a minute or so, it checks its revision list against the time of the latest edit for each revision, and sends out any unreverted revisions again, so each revision gets checked twice before being discarded. Yes, it will introduce more lag to the system, but it should cut down on errors. Thoughts? Throwaway85 (talk) 10:58, 18 November 2010 (UTC)

Who is going to pay for that dispatch server?

How would this work with HTTP-only clients?

How would users feel about revealing their usernames and IP addresses to a non-Wikimedia host?

What happens when someone loads vandalism and then goes idle, so it sits there for a minute longer than it should?

What happens when someone opens up two clients and maliciously skips through all the revisions on both so that nobody ever gets to see anything?

How would users during quiet periods when only one person is monitoring the feed feel about having to check every damn revision twice?

Why can't people just stop giving a toss about whether it's them who gets to a revision first as though it's some sort of competition?

Gurch (talk) 20:02, 18 November 2010 (UTC)

Point by point:

1) I have no idea what kind of traffic numbers Huggle deals with , but if they were low enough we could use a free EC2 mini shard, for a year at least.

2) Not my area of expertise, so I wouldn't be able to answer this.

3) No need. The dispatch server wouldn't need to know who you are, just that you are. Its job would simply be to feed you revisions; all other functionality remains as-is.

4) Who cares? Vandalism sticking around for a couple minutes longer isn't going to hurt anyone. I suspect you were being sardonic here. At any rate, it's pretty easy to monitor activity and toss any unmonitored revisions back to the server.

5) Take away their rollback bit? There's a certain amount of trust involved in being given huggle access, misuse will, as always, result in that access being taken away. Also, it'd be pretty easy to make sure you could only use one client per username.

6) They wouldn't. The whole point of sending it twice is to have two sets of eyes look at it. If there's only one person active, then that's unnecessary. Also, the whole "send it twice" bit is optional; it's only there to make coverage better.

7) My proposal was not intended to give people warm fuzzies about winning every revert race, it was intended to reduce the errors that arise from overlapping reverts, which can lead to vandalism being restored and all kinds of undefined behaviour within Huggle itself. I don't give two shits whether it increases or decreases a user's edit count and resultant ePeen.

Throwaway85 (talk) 09:04, 19 November 2010 (UTC)

Thanks and a question

I just started using Huggle today and I wanted to say "thanks" to Gurch for developing it. I see a fair number of complaints on here so I wanted to balance that out with a little appreciation for your hard work.

I have a (probably dumb) question about the blue triangle; does it flag the revision as "not vandalism" in any way, or does it just skip it on my queue and allow the revision to appear on others' queue? There have been a couple of cases where I wasn't really sure if the revision was vandalism and I wanted to make sure that clicking the blue triangle wouldn't "endorse" the edit in any way or remove it from other editors' queues. Thanks, 28bytes (talk) 08:31, 18 November 2010 (UTC)

No, it just moves to the next revision. It doesn't do anything else. Gurch (talk) 16:30, 18 November 2010 (UTC)

Excellent. Thanks. 28bytes (talk) 17:43, 18 November 2010 (UTC)

Question

Aside from the routine measures, what should be one if an editor on this list is being disruptive and violating 3RR? Erikeltic ^(Talk) 20:28, 20 November 2010 (UTC)

Uh, none? What did you have in mind? Gurch (talk) 22:30, 20 November 2010 (UTC)

My point was that an editor on this list has been blocked twice in less than 48 hours for edit warring and I was curious if that would be a reason for her removal from this whitelist. Erikeltic ^(Talk) 21:55, 22 November 2010 (UTC)

If they’re edit warring and using rollback to effect their reverts, I would imagine that it would be a basis for removing their rollback bit. — Spike Toronto 22:19, 22 November 2010 (UTC)

Windows 7 instability

I've been using Huggle on an old Windows XP machine with hardly any RAM that runs just fine. Now that I'm on a brand new PC with Windows 7, Huggle seems to have many more stability problems, crashing without letting me continue. I still switch off to my old machine and Huggle crashes there every once in a while, but not as often as on my new computer. Any thoughts anyone? (Please note that I'm not complaining -- I love Huggle -- I'm just asking). Alansohn (talk) 02:39, 1 December 2010 (UTC)

Probably Huggle hasn't been the same as it used to be, especially loading diffs. Like Gurch said in 2008, "Sadly, Huggle is a piece of junk." You're not the only user with Huggle problems. What I suggest is, go back to your old PC because Huggle crashes less or you should buy a new PC that's modern or fast at Best Buy or somewhere else that sells computers. The quote Gurch said, in 2008 is how Huggle has problems since it started. Hope this helps. WAYNESLAM 00:13, 3 December 2010 (UTC)

~~While I have experienced a few Huggle crashes, with the recent updates Huggle hasn't crashed on me yet, and I'm using Windows 7. -down load ׀sign! 20:49, 5 December 2010 (UTC)~~

I take that back; Huggle just crashed on me. I think it's caused by too many items in the editing queue (the one on the bottom). -down load ׀sign! 21:17, 5 December 2010 (UTC)

Alansohn, if you happen to still have your Windows XP CD, can find all of the device drivers for your new computer, and are experienced with resizing hard drive partitions and installing operating systems, you could always install XP in a Dual boot configuration. Or, if you have Windows 7 Professional or above, there is something available from Microsoft called Windows XP mode, which runs a fully functional copy of Windows XP in a virtual machine. Or, if you have the aforementioned XP CD, you could install something like VirtualBox, and install XP in a virtual machine, which wouldn't need any extra drivers to run other than what it already comes with.The sock that should not be (talk) 15:11, 6 December 2010 (UTC)

Something's currently wrong with Huggle that didn't happen a few years ago which is loading diffs takes a lot longer than normal. I don't think it's the computer that makes Huggle work better it's probably Huggle itself that has the problems. How could Gurch fix this problem himself? I don't think Windows 7 has to do with Huggle's problems WAYNESLAM 22:58, 7 December 2010 (UTC)

Can't login in

Huggle is not working at all for me; when I try to login I get this error:

WebException: The remote server returned an error: (403) Forbidden.

... and then a list of .NET objects where the error occurred. This seems to be a problem with the IRC server; could somebody fix this? Thanks. Usb10 ^Connected? 23:17, 2 December 2010 (UTC)

I just logged in as usual. Could there be a problem with your .NET? Is it up-to-date? What version of Windows are you running? Thanks! — Spike Toronto 23:26, 2 December 2010 (UTC)

Works fine now for me. BTW I am running an Windows 2000 VM with .NET 2. Usb10 ^Connected? 17:05, 3 December 2010 (UTC)

Glad it’s working! I was asking about your operating system, etc., in hopes that the more techinically minded here might have some guidance for you. — Spike Toronto 18:31, 3 December 2010 (UTC)

Huggle for Uncyclopedia

Uncyclopedia suffers from vandalism you know; it would be a helpful tool for us because everybody knows recent changes is so naf. The Merchant of Uncyc ^talk /_stalk 21:03, 12 November 2010 (UTC)

That site gets about 1 edit every 5 minutes. Even accounting for the suckiness that is Wikia it should be possible to review all of those manually. Gurch (talk) 21:14, 12 November 2010 (UTC)

The whole thing is vandalism. -down load ׀ sign! 20:50, 5 December 2010 (UTC)

Huggle problems still continue

My Huggle problems still continue: One: It's forcing me to close because it keeps giving me warnings saying that it has to close because its got problems and Two:It's too slow. It's hasn't made a huge effect since I set my preload to 5. Like you said, Gurch, "Sadly, Huggle is a piece of junk". When do you guys think this problem will stop? WAYNEOLAJUWON 22:11, 17 November 2010 (UTC)

I was saying to Wayne on my Talk page, that the whole Wiki speed has definitely reduced since Flagged Revisions started. It did improve somewhat after the start of FR (when people complained), but it just is not at the speed it was - just using FF, for each page load, there is often a definite pause in the loading - maybe there's just more users, and the servers are well loaded? HG has never been perfect for me, it's always refused to load some diffs - press space, title box changes, but no diff appears, no mater how long I wait, so if there is no diff quickly appearing, I press apace and try for another page, until one works - certainly the percentage of non loading pages is higher than say one year ago.. Maybe if I had one of those rare superfast 20Mbit connections it would be better, but I love living in the country, so I'm stuck with 5, with a vague promise of ADSL2+ next year to give me 6Mbit. Ronhjones ^(Talk) 23:03, 17 November 2010 (UTC)

Huggle definitely needs to be better by next year. You're right, Ron, there's more non-loading pages than there was a year ago. WAYNEOLAJUWON 21:22, 18 November 2010 (UTC)

Question about Queues

In Huggle, is there any way to create a queue that contains only edits tagged by a certain edit filter(s)? Cheers. Usb10 ^Connected? 21:25, 22 November 2010 (UTC)

Question about Huggle's regular expressions

In Huggle is there a way to make a queue that does not include any text that matches the regular expression(s) for that queue? Usb10 ^Connected? 00:01, 6 December 2010 (UTC)

CSD G10

I recently placed a g10 csd tag on a page, Autumn rupe, and Huggle indeed blanked the page of all but the deletion tag, but it didn't put the blanked=yes parameter in the template. Could somebody fix it so that it will do that? Thanks Usb10 ^Connected? 01:20, 10 December 2010 (UTC)

Huggle working in any language

Currently Huggle will work only if correct language is set in the user preferences. If other language is set, it will fail by displaying "Unable to log in". Couls someone modify the code for Huggle to work in any language, please? Thanks. Francisco ^talk 23:21, 12 December 2010 (UTC)

Unexpected CSD template used

I was going to revert this edit, but Huggle offered to tag the article for speedy deletion (which is what I should have done in the first place). I accepted the offer, but Huggle used the {{db-g7}} template, which is odd, seeing as how the page creator clearly did not make this request. I went back and updated the template to {{db-a7}}, and I wonder why Huggle used the wrong template in the first place. Orange Suede Sofa (talk) 21:10, 19 December 2010 (UTC)

Huggle doesn't work after a while

Why does Huggle seem to work, then cease to function after about 10-15 unless I quit and relaunch it? Even logging out and logging back into Huggle doesn't seem to work. Problem report: After 10-15 minutes, Huggle stops receiving new edits, and when I try to revert any of the edits already in the queue, it doesn't even attempt to revert. Please fix this problem. T3h 1337 b0y 23:17, 23 December 2010 (UTC)

Allowing rollbackers in Portuguese Wikipedia

Until recently, only users in pt:Wikipedia:Huggle/Users had access to Huggle, but it has been decided that rollbackers should also be automatically able to use it. Is there any way to do that without having to add all rollbackers manually in the list? There is an option require-rollback, but I imagine it would make it available only for users with rollback and listed in pt:Wikipedia:Huggle/Users. – Opraco (talk) 20:04, 25 December 2010 (UTC)

All users who are rollbackers can be allowed by changing global settings to approval:false. Petrb (talk) 20:10, 25 December 2010 (UTC)

But there still needs to be approval for non-rollbackers. – Opraco (talk) 20:15, 25 December 2010 (UTC)

Namespaces

Currently, in queues, Huggle recognizes only 16 namespaces, from main namespace (ns-0) to Category talk (ns-15). Other namespaces, like Portal (ns-100) on English and Portuguese Wikipedias and Anexo (ns-102) only on Portuguese Wikipedia, are not recognized, even if these namespaces are configured in Wikipedia:Huggle/Config#Queues. Could someone fix this problem for the program to recognize all namespaces, including ns-100 and ns-102, please? Francisco ^talk 21:14, 25 December 2010 (UTC)

User flagged by mistaken warning

Long story short -- I mistakenly sent an only-warning to the wrong user. I realized my error and actually deleted his talk page (my warning was the only edit) but his edits are still flagged with a red "4" in Huggle. I'm worried that another admin will reflexively revert and block the user. I know in about 24 hours the flag will be removed but is there any way to clear it before then? I've looked in the Feedback archives and didn't see anything that addressed this issue. ... discospinster _talk 23:15, 30 December 2010 (UTC)

Framework

I have released testing which should work with .net 2 if you had troubles running stable you should use that, next versions will be compiled with that Petrb (talk) 19:25, 3 January 2011 (UTC)

Keeping config folder from previous version

Resolved

Just a quickie. Can we keep the Config folder from the previous version Huggle 0.9.11? Or do we have to configure from scratch? DVdm (talk) 19:44, 10 January 2011 (UTC)

Hold on, we are now going to merge huggle and huggle2, configs will be most probably merged with next version Petrb (talk) 20:07, 10 January 2011 (UTC)

Ok, I have kept a backup of my 0.9-config for safety and gave it a try anyway. Found no problem with the old config. Cheers and keep up the good work. DVdm (talk) 22:04, 10 January 2011 (UTC)

Bug

Hey! Little bug in the Testing version, trying to click on a talk page after a revert leads to a error:

NullReferenceException: Object reference not set to an instance of an object.
   at Huggle.Processing.ProcessHistory(String Result, Page Page)
   at Huggle.Requests.HistoryRequest.ProcessHistoryPart()
   at Huggle.Misc.CallbackInvoke(Object TargetObject)

-- Rich (MTCD)^{Talk Page} 01:12, 11 January 2011 (UTC)

Rollout/Merger

Resolved

I’ve noticed that there are a number of bugs reported on this page for Huggle2. This suggests to me that it is still very much in beta testing and not ready to completely replace 0.9.11. Yet, I noticed yesterday that there were edits made to the Huggle/Config to prepare for the merger/rollout. Are we jumping the gun a bit? Version 0.9.11 is fairly stable. Should we not wait until HG2 is at least as stable, and been beta tested by a lot more users, before it replaces 0.9.11? Thanks! — Spike Toronto 06:56, 11 January 2011 (UTC)

Don't worry any change I made to config will not affect you next version will be more stable than 0.9.11. Petrb (talk) 07:05, 11 January 2011 (UTC)

Thanks Petrb. What’s your timeline for HG2 replacing Version 0.9.11? Thanks again. — Spike Toronto 07:07, 11 January 2011 (UTC)

We now do it together with addshore I hope we will fix all stuff in few days, anyway hg 2 does not have more bugs than 0.9.11 those reported bugs are still from previous one, Reported stuff was already fixed. Petrb (talk) 07:32, 11 January 2011 (UTC)

Testversion Huggle2 and 0.9.11

Hello,
is it possible that I can use Huggle in en.wikipedia again please. I havent change my config, but I can't log in. Thank you (this is my third ask which were archived without any comment). Conny (talk) 18:43, 13 January 2011 (UTC).

This is not enough, when it happens, why and so. Your config must have enable:true there Petrb (talk) 08:13, 14 January 2011 (UTC)

Local config directory

Hi, does Huggle 2.1.0 need the old local config directory from older huggle versions? Here is an user who can't use huggle on dewiki, and he didn't use an older huggle version before. Regards, --Inkowik (talk) 16:56, 15 January 2011 (UTC)

Open in browser

Resolved

– This is fixed in the next version ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

When you press the 'O' key to open the dif in the browser, it sometimes (as in: in one of two attempts) opens it twice.

Also, opening the page in browser is handled inconsistently: pressing 'O' opens it in the default browser, right-clicking on a link and selecting "open in new window" opens it in Internet Explorer. (There should be some way to select which browser Huggle uses.) - Mike Rosoft (talk) 17:28, 31 October 2010 (UTC)

Thanks for this, sorry for the slow response. We will add it to out list and see what we can do about it! ·Add§hore· ^{Talk To Me!} 16:55, 11 January 2011 (UTC)

This is fixed in the next version [= https://code.google.com/p/huggle/issues/detail?id=199#c1 ·Add§hore· ^{Talk To Me!} 17:11, 11 January 2011 (UTC)

ArgumentOutOfRangeException

Resolved

– Added to our todo list ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

ArgumentOutOfRangeException: Value of '-1' is not valid for 'Value'. 'Value' should be between 'minimum' and 'maximum'. Parameter name: Value

  at System.Windows.Forms.ScrollBar.set_Value(Int32 value)
  at Huggle.Main.DrawQueues()
  at Huggle.Processing.ProcessNewEdit(Edit Edit)
  at Huggle.Processing.ProcessRcEdit(Match Match)
  at Huggle.Processing.ProcessRc(String Result)
  at Huggle.Requests.RcApiRequest.Done()
  at Huggle.Requests.Request.ThreadDone()
  at Huggle.Misc.CallbackInvoke(Object TargetObject)

MorganKevinJ^(talk) 01:01, 10 December 2010 (UTC)

Thanks for this. I will add it to our TODO list ·Add§hore· ^{Talk To Me!} 16:55, 11 January 2011 (UTC)

Page protection

Resolved

– Fixed in 2.1.1 / now ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

In new Huggle, I still can't request page protection. It lets me fill in the boxes, lets me submit but then comes up "format of request page unknown". Totally confused! Is this supposed to be fixed now?--5 albert square (talk) 01:36, 13 January 2011 (UTC)

Twinkle is having similar problems with page protection. (For example, see discussion here.) It may be better, for now, to make requests manually at WP:RFPP. — Spike Toronto 05:59, 13 January 2011 (UTC)

Thanks will be fixed ~~in 2.1.1~~ immediately Petrb (talk) 12:04, 13 January 2011 (UTC)

Try now. Petrb (talk) 12:48, 13 January 2011 (UTC)

Difference between this and Huggle

Resolved

What are the major differences between your fork of Huggle and the official version? Logan _Talk^{Contributions} 15:36, 23 December 2010 (UTC)

The difference is that previous one is no longer developed as far as gurch told me if we want to continue development we need to reestablish dev team. This one will have several improvements if you have any suggestions just say! (if you want to add some features and so or report bugs) Petrb (talk) 16:30, 23 December 2010 (UTC)

I am currently working on stability improvements and fixing bugs which were reported. Petrb (talk) 16:33, 23 December 2010 (UTC)

Will it have Mac compatibility? ~Nerdy Science Dude 17:41, 23 December 2010 (UTC)

It's written in vb, but if some mac devs join the team then you could ask them. I would like to make it cross platform, there is already uhuggle maybe it's sources could be used.Petrb (talk) 18:04, 23 December 2010 (UTC)

Gurch may no longer be developing HG, but I understand that others have taken it on (User:Sidonuke, ~~User:Mike Rosoft~~, User:The Wordsmith, etc.). Why would you not use your efforts to make the existing one — the one that has been rolled out to hundreds of Wikipedians — a better, more stable, more powerful, anti-vandalism tool? Why not work on perfecting version 0.9.11 and rolling out a perfected version 0.9.12 instead, especially since all the documentation already exists for HG as opposed to HG2? Thanks! —Spike Toronto 02:47, 8 January 2011 (UTC)

P.S. Are you not required to obtain approval of HG2 from the Bot Approvals Group before publishing it? Or, have you already? Thanks! —Spike Toronto 02:49, 8 January 2011 (UTC)

No as gurch told me the development was stopped so there is no one currently developing previous versions I wanted to help but he told me that old huggle is no longer developed, concerning bot approvement old huggle had some? Petrb (talk) 09:20, 8 January 2011 (UTC)

If anyone who is now working on previous huggle wants to get developer access to svn, I would grant it to them but I've seen no evidence from trackers that someone worked on previous version since 0.9.11 which is old several months. I am not trying to overtake this project from previous developers if anyone wanted to join they can Petrb (talk) 09:40, 8 January 2011 (UTC)

I’m still curious about my other question, Petrb: Why start a brand new Huggle instead of putting your considerable and tremendous efforts into creating a prefected 0.9.12 of the existing Huggle, especially since all of its underlying infrastructure already exists? — Spike Toronto 21:31, 8 January 2011 (UTC)

Just read my answer, developement was stopped it's not possible, huggle 2 is next version of huggle, it's not brand new I can't just release next version for huggle there is no possibility to gain access to it's project pages on google - it was canceled Petrb (talk) 21:44, 8 January 2011 (UTC)

Would it not be easier if we could continue development in the google code project? I see that nothing major has changed really just some people have continued where others have left. I think keeping everything together would defiantly have its benefits in the long term ·Add§hore·^{Talk To Me!} 18:17, 10 January 2011 (UTC)

If you really believe that it would be better to continue with old pages, I think we could if we kept current versioning, that mean next version 2.0.3 would switch back to huggle 1 config locations, configs would be updated and users of previous versions (0.9) would easily upgraded to 2.0.3 just with regular update of huggle it would use previous location of configs so no one would have troubles, users who switched to 2 would see no difference and users of version 1 would automatically updated, so no one would be affected, I know it may not be best way but it's most friendly and easy to hg users, question is if the development in the future should be done on google or sf. I am sorry for bringing more chaos to this, I really did not know that there is someone who still have dev access to repositories of hg 1. Petrb (talk) 19:08, 10 January 2011 (UTC)

I think we should defiantly keep HG2 running for now. We need to update the repo of HG1 to reflect the changes that you have made to the code but keep it 'branded' as plain old huggle. Once the old repo has been updated we could then release the new version being at a guess 2.0.3. We could then advice users of HG2 to move back to HG development would continue :) Sound good? ·Add§hore· ^{Talk ToMe!} 19:17, 10 January 2011 (UTC)

What I meant was that we could use huggle pages for HG2, I have no troubles with changing 1 to 2 dunno why it should be problem, I will try to describe it step by step :),

1. I would switch paths back
2. Configs of huggle would be updated so they would be compatible with hg2
3. I would test it properly (this may take a day or more)
4. 2.0.3 would be released on google repositories as huggle.exe (not huggle2 as it is now, but internal versioning would be still 2.0.3)
5. Users of previous versions would be notified on update and would automaticaly update to 2.0.3, same would users of 2x huggle

huggle would use previous pages, repositories and everything would be put back while all users would see no big difference. Of course we could release it as 0.9.12 but as I said - we are recreating dev team I see no reason why not to keep v2 numbering as some users already become familiar with that, that is something we can discuss now. Anyway I will need svn access to google code. Petrb (talk) 19:28, 10 January 2011 (UTC)

I'll stop posting on your talk page now and focus the discussion here. I think it would be a better idea if we merge the configs of "huggle2" into the current HG and then release a v1 of huggle with the fixes and additions in place. Then we can start from a clean slate ish. I think to be tidy it would definatly be a good idea to leave huggle with the current huggle configs as I said earlier there are still many more people using huggle1 than huggle2 ·Add§hore·^{Talk To Me!} 19:53, 10 January 2011 (UTC)

I have uploaded sources, compile and test, it will most possibly work only on english wiki, I am now about to update all other configs, as I said we can make 2.0.3 which would use configs of hg1 it's just a number :) I wanted to make it 2 so it would be less confusing, but it would still use all hg1 pages. Petrb (talk) 20:09, 10 January 2011 (UTC)

If you have irc could you please come to #huggle2, thanks :) Petrb (talk) 20:15, 10 January 2011 (UTC)

So the result is that project will continue on previous page. Petrb (talk) 23:12, 10 January 2011 (UTC)

I think that this is a good decision, when the time is right (see below.) — Spike Toronto 06:58, 11 January 2011 (UTC)

Crashed

Resolved

– False Alarm ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

Hi. I just tried Huggle2 (the 'testing' version from SourceForge) and it crashed when it says "Updating message files..." Do you know why this is? I added enable:true to my huggle2.css page. Thanks in advance. –Cwenger (talk) 17:41, 25 December 2010 (UTC)

Hi you tried it on test or english WP? what OS do you have, try it on test wiki if it would fail again I am now using last version which was published few hours ago, try that one if you have older. Petrb (talk) 18:35, 25 December 2010 (UTC)

New hg must not be in same folder as previous version, try to remove config.txt if the problem still ocur Petrb (talk) 18:54, 25 December 2010 (UTC)

False alarm, it was just a file permissions issue in Windows 7. Working great now--thanks! –CWenger (talk) 22:03, 25 December 2010 (UTC)

Edit summary suggestion

Resolved

– Done ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

First of all, I love that Huggle 2 has more descriptive edit summaries. This is a huge win. But could I make one suggestion regarding the most common edit summary? Currently it is(Reverted edits by X identified as unconstructive modifications (HG 2)), but the word "modification" sounds too technical and more importantly, is not the term we use for edits. The edit summary could just as easily read (Reverted edits by X identified as unconstructive (HG 2)) which is shorter, simpler, and still proper English. Regards, Orange Suede Sofa (talk) 19:56, 4 January 2011 (UTC)

Version 2.0.1 comes with customizable summaries they are defined in global conf file, I can change it to whatever you want. Petrb (talk) 20:13, 4 January 2011 (UTC)

Done, if you want feel free to change it Petrb (talk) 20:54, 4 January 2011 (UTC)

Bugs

Resolved

– fixed and checking ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

The two bugs I had reported for the original Huggle still occur in Huggle 2:

If you press "O" to open the edit in a browser, it sometimes opens the page in two panels.
The "All new pages" listing apparently only returns pages created by whitelisted users, and the "Filtered new pages" list yields nothing. - Mike Rosoft (talk) 23:24, 6 January 2011 (UTC)

1 - fixed

2 - checking

(try it on test wp with testing hg) Petrb (talk) 05:56, 7 January 2011 (UTC)

Thanks. - Mike Rosoft (talk) 16:14, 9 January 2011 (UTC)

Another edit summary suggestion

Resolved

– Bug Accepted ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

Currently when I choose "factual error" as my rationale for reverting, it returns an edit summary of "(error (HG2))". Could we get this changed to "introduction of factual errors (HG2)" or something along that line? Thanks. --Diannaa ^(Talk) 02:17, 10 January 2011 (UTC)

And how about "WP:BLP violation (HG2)" instead of "Bio (HG2)" ? Thanks --Diannaa ^(Talk) 02:21, 10 January 2011 (UTC)

It is a bug, I should rather disable those two till next version is out. Petrb (talk) 08:24, 10 January 2011 (UTC)

Bugs

Resolved

– Fixed in 2.1.1 ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

In case nobody's noticed before:

I've turned "Confirm multiple reversions of edits by the same user" on and whenever it prompts me, it does it twice

Hope you can fix it sometime soon. Thanks for improving Huggle! Guoguo12 --Talk-- 00:46, 11 January 2011 (UTC)

If you press revert or revert and warn? Petrb (talk) 07:30, 11 January 2011 (UTC)

Revert and warn, although I just press "Q". Guoguo12 --Talk-- 20:27, 11 January 2011 (UTC)

Will be fixed in 2.1.1, it really ask twice but not, if you use menu. Petrb (talk) 20:10, 12 January 2011 (UTC)

Bug in queue view

Resolved

– in 2.1.1 ·Add§hore· ^{Talk To Me!} 10:55, 16 January 2011 (UTC)

Hi, the description says that it is necessary to copy huggle2 into his own directory. But in this case, huggle2 don't work at dewiki. If it is in the same directory as the old huggle version, all edits are marked as assisted edits (with a star in the icon). ([6]) Greetings,--Inkowik (talk) 18:18, 12 January 2011 (UTC)

No please ignore that if you downloaded the last one you don't have to place it to different folder, anyway afer restart it should work versions like 2.0.1 which you probably downloaded is not last. Petrb (talk) 18:27, 12 January 2011 (UTC)

Hi… Huggle2 is now working at dewiki, but there is still the bug Inkowik was talking about. All Edits in the queue look like item 27 in this picture:

Greetings--Spuk968 (talk) 00:45, 13 January 2011 (UTC)

Not for me. Petrb (talk) 16:33, 13 January 2011 (UTC)

Yes, in r2.1.0, all is correct. Thanks! --Inkowik (talk) 17:06, 13 January 2011 (UTC)

Sorry, but for me it's not fixed, all edits are still marked as assisted. What am I doing wrong? Greetings--Spuk968 (talk) 00:23, 14 January 2011 (UTC)

The same happens with eswiki, if I use the old config folder all edits are marked as assisted, if I delete the folder I can't use Huggle (can login only to en.wikipedia ru.wikipedia and testwiki) -- Màñüé£†¹5 ^talk 10:04, 16 January 2011 (UTC)

I am just about release fix be patient, anyway you can use old config.txt to patch this Petrb (talk) 10:07, 16 January 2011 (UTC)

~~You must add summary to your config with something like HG, you must ask sysop to do that~~ Petrb (talk) 10:12, 16 January 2011 (UTC)

Fixed in 2.1.1 Petrb (talk) 10:22, 16 January 2011 (UTC)

Thank you, it works! -- Màñüé£†¹5 ^talk 11:21, 16 January 2011 (UTC)

New pages feed

The "new pages" lists don't seem to work properly: the filtered list returns nothing, and the unfiltered one apparently only returns pages created by whitelisted users. - Mike Rosoft (talk) 13:35, 19 November 2010 (UTC)

Ditto here. The only thing that I get is new talk pages created by LaraBot and redirects and articles created by whitelisted users. Usb10 ^Connected? 14:56, 27 November 2010 (UTC)

thanks for this :) We will add it to our list of stuff to check and try and fix ·Add§hore· ^{Talk To Me!} 16:55, 11 January 2011 (UTC)

As a trial, I ran Huggle on English Wikipedia from cca 14:30 to 14:40 CET. During that time "Filtered new pages" returned nothing, and of the pages in the "All new pages" only one was in article space (Sadler Rogers). Special:NewPages reports the following pages created during that period of time: Inmote, Sadler Rogers, Amstar, No Cause for Concern, Sheldon Axler; of these, Inmote and Amstar were obvious candidates for speedy deletion. (Their creator made his first edit today, and wasn't on the whitelist. On the other hand, the creator of Sadler Rogers wasn't on the whitelist, either.) - Mike Rosoft (talk) 14:10, 13 January 2011 (UTC)

it does not work with irc feed only, I will try to do something with that but it does not affect other wikis. Petrb (talk) 15:32, 13 January 2011 (UTC)

I tried without IRC feed (I guess it takes all from the API) and it fetched the new pages perfectly, without any delay (at least on eswiki) maybe the bug is with the regex to parse the RC-bot on IRC. -- Màñüé£†¹5 ^talk 15:57, 17 January 2011 (UTC)

Warning tags

Pending changes integration

front page could do with some edit stats

More problems with Huggle

Not logging in

Criticism and complement

Unable to Log In

Download error.

Error message

"Dubious" edits

flag legit article

Huggle fever

Huggle issues?

Whitelist criteria

Editing problems

New Users

Error message at logon: "Failed to load message files: unknown error"

Unable to stay connected to IRC

IRC

Finnish Wikipedia

Warning's problems in es.wiki

Another problem...

Failure to load message files

Tag Copyedit

Suggested change to one revert message

browser

can't log in

Diff zu last reviewed version

Huggle

SLOW!!!

Whitelist

Profanity highlighting

Not warning vandals

Huggle crashing

New Templates

Constant minor bug

Interface localization is done

Revert summary line length

Huggle 0.9.7: unable to log in to Portuguese Wikipedia

IRC not using given proxy

Huggle not receiving any edits from the IRC recent changes feed.

Constantly crashing

Reverts my edits

Localization setting

Content disappearing

Starting problem

Asterisk

"Bad Word" Filter

Changing warning templates from final back to last

Double Reverting?

The main pane has the edits messed up

Edit Summary for First Warning

Huggle problems continue

Inadvertent reversion to vandalized revisions after another editor has removed vandalism

Huggle is currently disabled on all projects

Patched huggle

ways to speed up reverting?

Protection of config files

WP:Huggle/Users

inconsistent behavior when reverting a page that has already been rolled back

Thanks and a question

Question

Windows 7 instability

Can't login in

Huggle for Uncyclopedia

Huggle problems still continue

Question about Queues

Question about Huggle's regular expressions

CSD G10

Huggle working in any language

Unexpected CSD template used

Huggle doesn't work after a while

Allowing rollbackers in Portuguese Wikipedia

Namespaces

User flagged by mistaken warning

Framework

Keeping config folder from previous version

Bug

Rollout/Merger

Testversion Huggle2 and 0.9.11