Wikipedia talk:Huggle/Feedback/Archive 2

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

Adding a notice

Hey. When you go onto a page and you send an "other message" (N) you type your message e.t.c. If the page changes behind whilst you are typing then this message gets sent to the new user that edited the page and not the old one. I hope you understand me and I hope you can fix this. see [1] which was meant to go to another user that I saw had not signed. ·Add§hore· Talk/Cont 16:59, 18 May 2008 (UTC)

You just missed 0.7.6, but it will be fixed in the next version -- Gurchzilla (talk) 17:27, 18 May 2008 (UTC)

error

I got this error once trying to move forward a diff once I had been afk for 30 mins still lodded in on huggle.

(snipped ArgumentOutOfRangeException in huggle.Misc.SubjectPage)

·Add§hore· Talk/Cont 19:00, 18 May 2008 (UTC)

Should be fixed in the next version -- Gurchzilla (talk) 10:56, 19 May 2008 (UTC)
Thanks for your hard work ! ·Add§hore· Talk/Cont 19:11, 19 May 2008 (UTC)

Quick question

I'm fairly new to using Huggle and I'm very impressed with what it can do. I was wondering, what is the number at the top right of every page. Sometimes it's positive other times it's negative. Thanks ——Ryan | tc 19:02, 19 May 2008 (UTC)

This number tells you the ammount of bytes removed (if its a minus) or added (if it is a positive) on the page you are viewing between eh 2 diffs. ·Add§hore· Talk/Cont 19:10, 19 May 2008 (UTC)
Ohh I see, that's similar to what appears in your watchlist and recent changes page. Thanks for the speedy response ——Ryan | tc 19:16, 19 May 2008 (UTC)
No problem and yes thats right =] ·Add§hore· Talk/Cont 19:20, 19 May 2008 (UTC)

Uncat Tagging

See [2] When huggle adds this tag it should add it to the bottom! ·Add§hore· Talk/Cont 19:30, 19 May 2008 (UTC)

The next version will allow tags to be added to the end of the page -- Gurchzilla (talk) 05:30, 20 May 2008 (UTC)

Cyrilic username

Hi. Huggle crash when I try to use it with my username. --Петър Петров (talk) 07:13, 17 May 2008 (UTC)

Based on the fact that Gurch is fairly great (and this afternoon) I'd expect a fix sometime... Alex.Muller 23:44, 17 May 2008 (UTC)
This is now fixed -- Gurchzilla (talk) 17:09, 23 May 2008 (UTC)

warning vandals

You have got to do something about your new system where it does "not warn [vandal] because they have not edited since they received their last warning". This is driving me absolutely crazy. 98% of the time, they have edited since their last warning. I cannot tell you how annoying it is to have to open up the vandal's talk page and warn them with Twinkle because Huggle doesn't think they have edited since their last warning. I actually seriously considered purchasing a professional decompiler (which cost $392), so that I could change the code and recompile it to force it to stop doing that. Seriously, can you get rid of that function? J.delanoygabsadds 15:18, 19 May 2008 (UTC)

Or at least give me the source code of huggle vs. 6.3 so I can continue to use that version? J.delanoygabsadds 15:18, 19 May 2008 (UTC)
Send me a message and I can send any old edition of Huggle back to 0.6.3 you like. Tiddly-Tom 15:52, 19 May 2008 (UTC)
I still have the old version, it's just he put something in the master config file so you can't use old versions, and I don't dare edit that because I would, at the least, get my Huggle privileges revoked and I would probably be temporarily blocked. J.delanoygabsadds 15:59, 19 May 2008 (UTC)
Yes; it's not great to be prevented from warning. Pseudomonas(talk) 16:11, 19 May 2008 (UTC)
It's not a new feature. Is it really happening 98% of the time? -- Gurchzilla (talk) 16:43, 19 May 2008 (UTC)
Also, if you want the source you can email me, which costs slightly less than $392. For that matter, if you want a decompiler you can use the .NET Reflector, which is free -- Gurchzilla (talk) 16:45, 19 May 2008 (UTC)
Well, I exaggerated there, but it still annoys me incredibly. I had been using vs. 0.63 until like 2 days ago when you made it so that it was no longer valid. If you could let me continue to use that version, I would appreciate it. The newer versions crash quite frequently on Vista. (which I am cursed with using)
I also owe you an apology for being so stupid above. J.delanoygabsadds 16:56, 19 May 2008 (UTC)
There does seem to be a problem with the latest version. It says "Did not warn, as they were last warned 10 seconds ago" whenever it's meant to send a Level-2 warning or above. Epbr123 (talk) 17:13, 19 May 2008 (UTC)
I've re-enabled older versions temporarily until I can figure out what is causing this; if I can do that it should be fixed in the next version -- Gurchzilla (talk) 17:21, 19 May 2008 (UTC)
I have to say that it was doing this quite allot for me also. But it was only about 30% of the time for me. ·Add§hore· Talk/Cont 18:34, 19 May 2008 (UTC)
I have just looked through my last 100 or so edits on Huggle and did not warn someone only once. That is about 2% of warnings. Tiddly-Tom 18:49, 19 May 2008 (UTC)
FWIW, I noticed this too - it's happening about 75% of the time for anything after the first warning.--Kubigula (talk) 03:45, 20 May 2008 (UTC)
Found an inconsistency in the way timezones are handled that could be causing this. Huggle uses UTC internally, but collects timestamps from a number of sources some of which are converted to local time and some of which aren't; it has to convert the former back to UTC, use UTC for date processing and later convert everything back to local time for display to the user. This should be fixed in the next version -- Gurchzilla (talk) 06:03, 20 May 2008 (UTC)
Thanks gurch! Keep up the good work! ·Add§hore· Talk/Cont 16:42, 20 May 2008 (UTC)
When I've had this happen on various version the conditions have been a little different. The vandal will have made 3-5 vandailzations (is that a word) on different articles in short order, and I'm seemingly the only person on vandal patrol at the moment. So I see one, revert it, the next page that comes up is the next act from the same vandal. Revert, no warning. Next page, revert, no warning. Next page, revert, no warning. Etc. So they are vandalizing as fast as they can on separate pages, I'm reverting as fast as I can (which is pretty fast), and after 10 acts of vandalism they have one or maybe two warnings. Obviously this then turns into a manual report to AIV, but they may decline because the vandal hasn't been sufficiently warned.
It would be nice if Huggle could somehow detect this sort of case, such as the vandal being reverted for changes on multiple pages in short order, and either go ahead and issue the warnings, or just trump with a level 4 or some such. Loren.wilton (talk) 22:34, 21 May 2008 (UTC)
That should hopefully not happen with the next version. Note also that you can go straight to a final warning by reverting and then selcting "Blatant vandalism" from the warnings menu, or choosing "Advanced..." and selecting as appropriate if it's something other than vandalism that you want a final warning for -- Gurchzilla (talk) 22:59, 21 May 2008 (UTC)

Todo list?

I was just wondering hat people would think of a list that showed what edits still had to be saved? ·Add§hore· Talk/Cont 06:15, 20 May 2008 (UTC)

It's a possibility, although I'm not quite sure how to fit it into the current interface -- Gurchzilla (talk) 06:37, 20 May 2008 (UTC)
Or maybe just a count of how many things there are in the queue to be saved? ·Add§hore· Talk/Cont 07:08, 20 May 2008 (UTC)
I like the idea of just having a number of edits that it has qued to do. I do notice at the bottom where is says the edits you have done there are two coloums but only one has things in it, for me at least... Tiddly-Tom 09:45, 20 May 2008 (UTC)
Yeah, you could have a message over there like "Reverting edits on "Xbox 360".... Done (and then it moves to the left column) Don't know if that would be worth it, but it would be very cool. (And hey, if you can't make a program cool, why make one? ;) ) Thingg 13:40, 20 May 2008 (UTC)
That could be a good idea. Me being on a 21" screen can see the 2 collums =] ·Add§hore· Talk/Cont 14:38, 20 May 2008 (UTC)
What if you split the "log" on the bottom of the page into two columns? The one on the left would be a log of completed actions, and the one on the right would be actions that are being processed or are pending. J.delanoygabsadds 14:41, 20 May 2008 (UTC)
The log already has 2 collums or is already split in 2 but only one is used. ·Add§hore· Talk/Cont 14:45, 20 May 2008 (UTC)
Well, I'm using vs. 0.7.5 because it isn't as bad with the not issuing warnings thing... J.delanoygabsadds 14:53, 20 May 2008 (UTC)
In fact the log has only one column; the line you can see merely marks where that column ends, and the space beyond that is just empty. The problem is that Huggle has to be usable with a screen resolution of 800x600, so the log can't be any wider than it is now -- Gurchzilla (talk) 16:44, 20 May 2008 (UTC)
Ahh. (my screen is too big ;p) well then maybe the count for the amount of things that are in the queue? ·Add§hore· Talk/Cont 17:02, 20 May 2008 (UTC)
The next version will show actions in progress in the log -- Gurchzilla (talk) 22:50, 21 May 2008 (UTC)

Admin tools bug

I don't know if I'm the only one experiencing this, but I'm having trouble using admin tools within Huggle. The delete button doesn't actually result in deletion and clicking the "block" function (in brackets after the user's name) does not respond either. Seraphim♥Whipp 20:46, 20 May 2008 (UTC)

Deletion will be fixed in the next version. Blocking currently works, though only via the toolbar button -- Gurchzilla (talk) 21:19, 20 May 2008 (UTC)
Block links in the browser window will also work in the next version -- Gurchzilla (talk) 16:39, 21 May 2008 (UTC)

Here's another 'red' dialog box - Need help!

I have been using 0.7.5 for a few days and for hours together with no problems. Today, it has twice given me a dialog box with an error, and options with 'CONTINUE' or 'QUIT', after half an hour of running. I notice that it gives these errors only when Huggle is idle (any connections?) Here's the error details. I have removed a list of loaded assemblies with details of assembly version, win32 version and codebase. Any help possible? Here goes:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

(snipped NullReferenceException in Processing.ProcessNewEdit)

-Error message ends- Thanks. Prashanthns (talk) 18:44, 29 April 2008 (UTC)

Damn null reference exceptions. Will be fixed in the next version if I manage to reproduce it Gurch (talk) 12:50, 2 May 2008 (UTC)
Whatever brings them on, I dont know. Have done a few days now without those errors!Cheers. Prashanthns (talk) 23:05, 2 May 2008 (UTC)
I think this one is fixed now -- Gurchzilla (talk) 21:40, 24 May 2008 (UTC)

Login to bgwiki

Hi. I can login to enwiki with both Latin and Cyrilic usernames now. But for bgwiki I get "Incorrect password" for both accounts. FYI User:Петър Петров is a SUL account. --Петър Петров (talk) 07:45, 20 May 2008 (UTC)

Hmm. As I don't have an SUL account it's hard to test that. Don't you have to be an administrator on some wiki to have one at the moment? -- Gurchzilla (talk) 07:52, 20 May 2008 (UTC)
User:Petar Petrov is not a SUL account and still does not work. --Петър Петров (talk) 16:44, 20 May 2008 (UTC)

Both accounts work with Huggle 0.7.7. Thanks. --Петър Петров (talk) 14:11, 24 May 2008 (UTC)

Spelling

I have run Live spellchecks recently and Template:uw-huggle4 seems to have a spelling error. Here is an example. receive is spelled incorrectly as recieve. Just reporting. WikiZorrosign 20:49, 21 May 2008 (UTC)

Fixed in the next version -- Gurchzilla (talk) 22:41, 21 May 2008 (UTC)
Great! WikiZorrosign 10:36, 24 May 2008 (UTC)

Huggle Errors

I've managed to get the partial text of one of the error messages:

(snipped Win32Exception in huggle.LoginForm.Credit_LinkClicked)

As you can see, some of it got cut off, both at the right and the bottom. But hope this helps... Calvin 1998 (t-c) 21:47, 21 May 2008 (UTC)

I would just like to point out thats what Wikipedia:Huggle/Feedback is for =] ·Add§hore· Talk/Cont 21:52, 21 May 2008 (UTC)
Yeah, I know, but this doesn't really matter to anyone but Gurch himself, and this way is far more direct. Calvin 1998 (t-c) 21:55, 21 May 2008 (UTC)
Hm. All clicking the credit link is meant to do is open my userpage in a browser window. Why it can't find a file, I don't know -- Gurchzilla (talk) 23:18, 21 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 18:39, 23 May 2008 (UTC)

Captcha

I seem to be having trouble with the CAPTCHA in 0.7.6 - Once I get the password incorrect twice, a window which supposedly contains a picture of the captcha given by Special:UserLogin comes up, but is blank except for a field for the code. Is something going on? I'll upload a picture of it later. Calvin 1998 (t-c) 23:45, 21 May 2008 (UTC)

Suggestion: Don't keep getting your password incorrect twice in a row :) -- Gurchzilla (talk) 23:53, 21 May 2008 (UTC)
I didn't, I was seeing if the CAPTCHA worked or not :). Anyhow, here's the picture:
(snipped)
Calvin 1998 (t-c) 23:56, 21 May 2008 (UTC)
Hm. I just typed in the wrong password ten times and the captcha came up correctly every time. Perhaps the site was being temporarily slow -- Gurchzilla (talk) 23:56, 21 May 2008 (UTC)
I've tested it 3 times, all 3 times it comes out like above, so I don't think it's server problems... Calvin 1998 (t-c) 00:00, 22 May 2008 (UTC)
I've changed the way the captcha is displayed. This might fix the problem, though since it was working for me before I can't be sure. Thanks -- Gurchzilla (talk) 00:23, 22 May 2008 (UTC)

It's still not working, so I'll see if it works on a different OS than Vista... And by the way, how are you going to remove the rollback rate limit on the next version? Calvin 1998 (t-c) 03:46, 22 May 2008 (UTC)

The Rollback rate is not limmited by huggle but is limmited by the mediawiki software its self. See [3] ·Add§hore· Talk/Cont 06:34, 22 May 2008 (UTC)
That's my point - but it says up at the top of this page under "Changes in the next version (0.7.7)" - Rollback rate limit removed. How's Gurch going to do that if it's controlled by MediaWiki? Calvin 1998 (t-c) 06:43, 22 May 2008 (UTC)
Because I asked the developers to remove it, which they have done (more accurately, they've raised it to 100 per minute, which is more than anyone is likely to encounter) -- Gurchzilla (talk) 10:53, 22 May 2008 (UTC)
Excellent :) Pseudomonas(talk) 12:59, 22 May 2008 (UTC)
It still won't be working for you because I've changed it in the next version; I can't modify the version you've already downloaded. When the new version is released you can test again and see if it works -- Gurchzilla (talk) 11:01, 22 May 2008 (UTC)

Error during revert

The following problem occured with huggle 0.7.6.

I was seeing this edit in huggle [4], which was vandalism, and pressed the revert button. This was however not the version huggle reverted. Instead it reverted this version [5], which was a reversion of the original vandalism by User:Tresiden. --Mdebets (talk) 22:07, 22 May 2008 (UTC)

see here. Also a few other prior threads. Known issue. Enigma message 23:35, 22 May 2008 (UTC)
This should now be fixed -- Gurchzilla (talk) 21:06, 23 May 2008 (UTC)

User contribs in the new version

Is it me or are the user contribs (under the page's history - top right) not there? Or am I doing something wrong? Regards, ——Ryan | tc 10:15, 23 May 2008 (UTC)

They seem to be there for me. Perhaps it got stuck retrieving the contributions of a particular user – try restarting it -- Gurchzilla (talk) 11:15, 23 May 2008 (UTC)

This is what I mean. It appears like this for every case:

(snipped screenshot)

Or is there something I need to change in the options? It wasn't like this in the older version ——Ryan | tc 11:51, 23 May 2008 (UTC)

Still exceptions when attempting to open pages

When I pressed the "documentation" button on the window that opens before the log-in screen, an error message showed up. The "exception text" read:

(snipped Win32Exception in huggle.DisclaimerForm.DocsLink_LinkClicked)

So yeah. Calvin 1998 (t-c) 23:16, 23 May 2008 (UTC)
Yes. It is, as I said above, fixed in the next version. Which hasn't been released yet. :) -- Gurchzilla (talk) 23:32, 23 May 2008 (UTC)

Reverts getting stuck/Patrolling pages sometimes does it twice

Sometimes, when I was reverting changes, it would get stuck (highlighted in red) and it would stay that way until I close it out and re-open Huggle. Another problem that I encountered is that sometimes, when it is marking a page as patrolled, it sometimes does it twice, and also has a tendency to just get stuck and stay highlighted in red. Know why? Razorflame 00:39, 26 May 2008 (UTC)

I never get the reverts stuck but the patrols doing it twice I have had and I have already told gurch about. (note this means that one goes through (black) and one stays at the top (red) ·Add§hore· Talk/Cont 08:52, 26 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 11:28, 26 May 2008 (UTC)
Odd... the toolbars seem to be out of alignment. Not sure how that happened; it may be related to differences between the Windows XP and Vista GUIs; since I don't have Vista I can't test this, but I'll see if I can fix it so it doesn't happen again -- Gurchzilla (talk) 13:27, 23 May 2008 (UTC)
Confirmed - it's OS-related, it works fine in XP for me. It seems the Vista GUI is different from the XP one, messing it up... Calvin 1998 (t-c) 03:34, 24 May 2008 (UTC)
I thought maybe it was OS related, but it is something I can live without. Another thing I noticed (perhaps another OS diff) is when you mark a page as patrolled, it will come up in red in the history box "marking 'Page 1' as patrolled" but will remain there until a restart the session again. In other words, it fails to mark a page as patrolled and just sits there as red. ——Ryan | tc 14:07, 23 May 2008 (UTC)
Yes, I've had that a few times. The patrolling feature is new in this version and it seems there are still a couple of problems with it to be fixed -- Gurchzilla (talk) 14:53, 23 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 17:14, 24 May 2008 (UTC)
Please don't take it as a criticism though, I'm still in love with this program and you've done a great job :) ——Ryan | tc 16:06, 23 May 2008 (UTC)
I had the "edit stays as red" when I tried to revert a page creation and declined to tag it for deletion. I like the feature of showing queued edits though! Pseudomonas(talk) 16:35, 23 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 19:02, 23 May 2008 (UTC)
This should be fixed in the next version (though it's hard to tell as I don't have Vista) -- Gurchzilla (talk) 22:16, 24 May 2008 (UTC)

By the way, the CAPTCHA seems to work now. =] Calvin 1998 (t-c) 20:56, 23 May 2008 (UTC)

Warning templates

I'm using version 7.7, and there seems to be a problem with the warning templates. They're coming out like this. Epbr123 (talk) 14:18, 27 May 2008 (UTC)

Yeah, the configuration page was broken for about 5 minutes, but is fixed now; try restarting Huggle -- Gurchzilla (talk) 15:05, 27 May 2008 (UTC)

Comparison between uw-huggle1 and uw-huggle2

I think you should make a bigger contrast between the wording in the first and second warning. At first, the both looked like level 2 warnings and I thought there was a glitch but I realized that the first one was suppost to be a level 1 warning. Perhaps you should make the level 1 warning more like {{uw-vandalism1}}.--Sunny910910 (talk|Contributions|Guest) 01:09, 23 May 2008 (UTC)

Here are the two Huggle warnings:

Hi, the recent edit you made to $1 has been reverted, as it appears to be unconstructive. Use the sandbox for testing; if you believe the edit was constructive, ensure that you provide an informative edit summary. You may also wish to read the introduction to editing. Thanks.

The recent edit you made to $1 constitutes vandalism, and has been reverted. Please do not continue to vandalize pages; use the sandbox for testing. Thanks.


The key difference between these is that the level 2 warning refers to the edits as "vandalism", whereas the level 1 warning does not. The latter also links to the introduction and explains about edit summaries.
Here are the two uw-vandalism warnings:

Welcome to Wikipedia. Although everyone is welcome to make constructive contributions to Wikipedia, at least one of your recent edits did not appear to be constructive and has been reverted or removed. Please use the sandbox for any test edits you would like to make, and take a look at the welcome page to learn more about contributing to this encyclopedia. Thank you.

Please refrain from making unconstructive edits to Wikipedia. Your edits appeared to constitute vandalism and have been reverted. If you would like to experiment, please use the sandbox. Thank you.


Again, the main difference between them is that the level 2 warning refers to the edits as "vandalism". Again, the level 1 warning also links to a welcome page, when the level 2 warning does not.
The difference between level 1 and level 2 thus seems to be more or less the same in each case. What specific changes would you like to see? -- Gurchzilla (talk) 08:41, 23 May 2008 (UTC)
I'm not the original poster, but I agree with him. The initial warning feels a little 'bitey' to me. uw-test1 is a possibility, but it may be a little soft. On looking at the user warnings page, I see there are many escalating series, and at least three or four of them could be useful to provide a specific message. Maybe a droplist on the revert-n-warn button similar to the droplist on the revert button, but using some of the standard template series warning reasons. Just offhand the series starting with uw-delete1, uw-joke1, uw-create1, uw-spam1, uw-advert1, uw-unsourced1, uw-error1, and uw-defam1 all look to be things I would use commonly. Loren.wilton (talk) 11:54, 23 May 2008 (UTC)
The warn button already allows the user to select from vandalism, spam, tests, removal of content and personal attacks. The messages for these are similar to, but not identical to, those for uw-vandalism, uw-spam, uw-test, uw-delete and uw-attack, respectively. The revert-and-warn button is intended only for blatant vandalism; it is supposed to be up to the user to use the warn button to issue the appropriate type of warning in other cases. I realise the user does not always follow this, but forcing the user to use the tool in a particular way is tricky -- Gurchzilla (talk) 15:51, 23 May 2008 (UTC)
The part I was refering to was the "Welcome to wikipedia. Although everyone is welcome to make constructive contributions to Wikipedia...". Although it's rather minor, I always look for it when I look at a user's warnings. Without it, a level 1 and level 2 warning look the same at first glance.--Sunny910910 (talk|Contributions|Guest) 21:08, 23 May 2008 (UTC)
Indeed most (though not all) level 1 warnings start with "Welcome to Wikipedia"; though none except the vandalism one contain the "Although everyone is welcome to make constructive contributions..." part. If you wish, I can re-word the level 1 warning. What would you like it to say? -- Gurchzilla (talk) 21:11, 23 May 2008 (UTC)

(Outdent) Well this is only a suggestion but how about somthing like:

Welcome to wikipedia. A recent edit you made to ARTICLENAME appears to be unconstructive and has been reverted. Please use the sandbox for for any tests you would like to make; if you believe the edit was constructive, ensure that you provide an informative edit summary. You may also wish to read the introduction to editing. Thanks.

Something similar to that. (Ignore the links, I just used them as an example)--Sunny910910 (talk|Contributions|Guest) 21:25, 23 May 2008 (UTC)

I have added "Welcome to Wikipedia" to the start of all the level 1 messages -- Gurchzilla (talk) 21:54, 24 May 2008 (UTC)

A few CSD things

When tagging a page for CSD the 2008-05-23 5:23:25 PM (+01:00) -- (Marking 'Feast of the Flowering Moon' as patrolled...) comes up twice. ONe saying that it has carried out the action (black) and one saying it hasn't (red). Also I dont think that it checks to see if there are already tags on the page as happened here. [6] I hope this can be fixed easily. ·Add§hore· Talk/Cont 16:27, 23 May 2008 (UTC)

That diff has been deleted. What happened exactly? -- Gurchzilla (talk) 18:53, 23 May 2008 (UTC)
I think the same article had been speedy tagged 3 times. This has happened to me too. ——Ryan | tc 22:20, 24 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 18:13, 25 May 2008 (UTC)
Another CSD point, when tagging for WP:SD#11 and WP:SD#10 (there may be more but I've only tagged for those two), there's a typo in the edit summary ——Ryan | tc 16:48, 23 May 2008 (UTC)
This is fixed in the next version -- Gurchzilla (talk) 18:28, 23 May 2008 (UTC)

bug on 7.7 ?

If I leave Huggle on and not use it for while it states something about my session cookie being expired invalid, well when I reload the IRC feed. I start editing as an IP address. Does it suppose to do that?Antonio Lopez (talk) 23:11, 24 May 2008 (UTC)

Seems that Huggle is being logged out after a while. Recently I had to switch to using Special:Userlogin rather than the API, which may have caused this. I'll see if submitting the login form with "Remember me" checked (which it doesn't currently do, because there's no such option with the API) prevents this -- Gurchzilla (talk) 00:05, 25 May 2008 (UTC)
True, I noticed that on the list of changes. Either way it was fun editing as an IP address, but still had it's limitation Antonio Lopez (talk) 00:34, 25 May 2008 (UTC)
It seems even with option the user gets logged out after a few hours, which didn't happen when using the API. I think the only other thing to do is have it detect when this happens and log the user back in -- Gurchzilla (talk) 10:35, 25 May 2008 (UTC)
mw:Extension:Assert_Edit is installed on Wikipedia and could help --Chris 11:00, 25 May 2008 (UTC)
It already knows when it's logged out; I just need to make it do something about this -- Gurchzilla (talk) 11:03, 25 May 2008 (UTC)
Should be fixed in the next versions -- Gurchzilla (talk) 11:44, 25 May 2008 (UTC)

Tagging for CSD G12 (Blatant copyright infringement)

I tried to tag an article under this, but it didn't work correctly. To see if it was just a random error, I tried tagging the sandbox for speedy deletion. However, as you can see, it still didn't work. Hope my info helps you figure out what's up. J.delanoygabsadds 04:06, 27 May 2008 (UTC)

Yup, the correct template is {{Db-g12}}, not the non-existent {{Db-12}}. I think several other of the CSD tags Huggle's using are also messed up... Calvin 1998 (t-c) 04:11, 27 May 2008 (UTC)
I don't know if I dare to try tagging the sandbox again. Will it notify the original editor? J.delanoygabsadds 04:14, 27 May 2008 (UTC)
If huggle even does, it'll crash from attempting to find out... the sandbox has over 5,000 revisions or something like that :). Anyhow, how about make a yourself a user-subpage and tag that? Or you can use my spare sandbox... Calvin 1998 (t-c) 04:21, 27 May 2008 (UTC)
Thanks for the offer. I'll tag my own sandbox, cause if I warned you for copyright infringement in your sandbox, than may become a little interesting. J.delanoygabsadds 04:23, 27 May 2008 (UTC)
OK, here's the info [7]. It looks like g10, g11, and g12 are not working. All the others worked fine. J.delanoygabsadds 04:29, 27 May 2008 (UTC)
Nice job. :P Tagging a page for speedy deletion so many different ways. Poor sandbox! Thanks for testing it. Enigma message 05:06, 27 May 2008 (UTC)
Thanks. I've wanted to do something like that for a long time, but I never had a good reason before... :) J.delanoygabsadds 05:11, 27 May 2008 (UTC)
Just curious, but how did you do it? Did you actually tag through Huggle? Enigma message 05:39, 27 May 2008 (UTC)

←Yeah, I did. J.delanoygabsadds 05:46, 27 May 2008 (UTC)

As stated under "A few CSD things" above, this is fixed in the next version -- Gurchzilla (talk) 11:24, 27 May 2008 (UTC)
Heh, it would probably have helped if I had actually read that... J.delanoygabsadds 13:31, 27 May 2008 (UTC)

Bugs resolved in the new version

Just wanted to say that the contribs bug I brought up above and and the new page patrolled issue have both been resolved and are now working fine in the newer version. Thanks very much Gurch! :) ——Ryan | tc 10:03, 30 May 2008 (UTC)

More Warnings?

Is there a way to add more types of warnings? I often use uw-unsourced and uw-npov and sometimes uw-error. --NeilN talkcontribs 03:35, 21 May 2008 (UTC)

The selection of warnings is fixed but you can add additional items to the template messages menu (the blue button with an "i"). In Huggle, go to System -> Options, select the Templates tab and click Add to add a new template to the list. I'll add the three templates you have suggested to the default list for the next version of Huggle, since they seem to be quite commonly used -- Gurchzilla (talk) 11:19, 21 May 2008 (UTC)
I was very unclear (sorry). I was wondering if you could implement the 1, 2, 3, 4 warning levels for the warnings above like you do for vandalism, spam, etc. --NeilN talkcontribs 17:36, 24 May 2008 (UTC)
Uw-unsourced and uw-error don't have a level 4 warning; what do you want me to do about that, just not add it? -- Gurchzilla (talk) 17:48, 24 May 2008 (UTC)
Use uw-generic4 or uw-huggle4. --NeilN talkcontribs 18:03, 24 May 2008 (UTC)
This is fixed in the next version -- Gurch (talk) 01:40, 2 June 2008 (UTC)

Huggle rocks.

I used Huggle the first time today, after using RC and NP. It is awesome, and except for my connection lagging behind a little when I go through the queue too fast, I couldn't find any flaws. Maybe streamlining CSD? Thanks heaps for the effort you have put in. Azazyel (talk) 09:48, 23 May 2008 (UTC)

This was suggested by Loren.wilton above; I've made some changes in the next version, though it would seem the notifications also need to be a bit more comprehensive, which I have not addressed yet -- Gurchzilla (talk) 09:49, 23 May 2008 (UTC)

NullReferenceException when

Hi. I'm not sure if this is known bug already. I got it on bgwiki, not sure if it happens on enwiki.

Scenario to reproduce:

  1. Vandal creates a new page.
  2. Huggle user click on Revert-and-Warn button
  3. Huggle asks "Article was created, Flag for speedy deletion instead of revert?"
  4. Click 'No'.

(snipped NullReferenceException in huggle.Processing.DoRevert

P.S. I have admin permissions there, maybe in this case change the dialog to "Article was created, do you want to [report for speedy deletion] [delete page] [blank the page] [ignore the page/cancel]".

--Петър Петров (talk) 08:03, 28 May 2008 (UTC)

The option to speedy the page for admins is implemented in next version Calvin 1998 (t-c) 05:37, 29 May 2008 (UTC)
This should now be fixed -- Gurch (talk) 02:14, 2 June 2008 (UTC)

Load CFG

Whenever I start to use a new version it doesn't read my old config. Then when I exit huggle it will update my config to this [8] even though I haven't changed in huggle. Hope u can fix ·Add§hore· Talk/Cont 08:48, 29 May 2008 (UTC)

This is fixed in the next version -- Gurchzilla (talk) 19:48, 29 May 2008 (UTC)
Works fine in 0.7.9. Thanks. --Петър Петров (talk) 20:31, 1 June 2008 (UTC)

0.7.8 Crashes During Login & Previous Versions No Longer Work Either

0.7.8 crashes for me the minute I try to log in. I press Log In the green bar shows a bit of progress and immediately I am given the message that Huggle has crashed and stopped working. I tried changing the version number on my huggle.css page but that didn't solve the problem. I tried to run previous versions of Huggle but get an error message during log in that says "Failed to load watchlist." What should I do :(? I am running Windows Vista.¤~Persian Poet Gal (talk) 17:56, 29 May 2008 (UTC)

Mine currently dies on checking user privs. ·Add§hore· Talk/Cont 18:04, 29 May 2008 (UTC)
mine's crashes too, I say downgrade Antonio Lopez (talk) 18:13, 29 May 2008 (UTC)
could it be the config ? Antonio Lopez (talk) 18:22, 29 May 2008 (UTC)
I had crash problems with 0.7.8 do downgraded to 0.7.7. On startup I now get the "failed to load watchlist" error message. – ukexpat (talk) 18:46, 29 May 2008 (UTC)


The problem is being caused by single user login. Logging into an SUL-ed account does not work. Until this morning it was not possible to do this unless you were an administrator, so I had no way of testing it – Gurchzilla (talk) 19:05, 29 May 2008 (UTC)

Should be fixed in the next version -- Gurchzilla (talk) 19:21, 29 May 2008 (UTC)
Comment: Why dont you just got for an RFA god dammit? :D ·Add§hore· Talk/Cont 19:56, 29 May 2008 (UTC)
It wouldn't have made any difference in this case; I'm an admin with SUL and the issue didn't affect me before today. It must be a problem with the global rollout of SUL as the admin-only implementation of it didn't affect Huggle. Waggers (talk) 19:58, 29 May 2008 (UTC)

Thanks Gurch, its all fixed now :).¤~Persian Poet Gal (talk) 20:23, 29 May 2008 (UTC)

Still not working for me. 0.7.8 still crashes and after downgrading to 0.7.7. I still get the "failed to load watchlist" error. :( – ukexpat (talk) 21:41, 29 May 2008 (UTC)
You should get the error on all versions. You will have to wait for 0.7.9. ·Add§hore· Talk/Cont 21:43, 29 May 2008 (UTC)
0.7.9 can be downloaded now -- Gurchzilla (talk) 21:49, 29 May 2008 (UTC)
Just noticed / got told, thanks gurch! ·Add§hore· Talk/Cont 21:54, 29 May 2008 (UTC)

Bug in Huggle block template

Much as I'd love a dollar for every block, I'm not convinced this is what the block message should really say. Any idea why it's doing this? (It's only doing it since today, but it's done it three times in a row so it's not a one-off glitch.)iridescent 18:08, 28 May 2008 (UTC)

Umm... that's supposed to return something - the username or something like that. Must be a huggle bug... should be fixed in 0.7.8 Calvin 1998 (t-c) 01:06, 29 May 2008 (UTC)
This is now fixed -- Gurchzilla (talk) 16:34, 1 June 2008 (UTC)

Huggle

0.7.8 is still crashing at "checking user rights." Can you please explain what is wrong? RedThunder 21:25, 29 May 2008 (UTC)

I do believe you should have received v0.7.9, which was an urgent bugfix, released about 2 hours ago. Calvin 1998 (t-c) 22:29, 29 May 2008 (UTC)
This should be fixed in the current version -- Gurchzilla (talk) 16:35, 1 June 2008 (UTC)

Potentially serious apparent Huggle bug

Not sure if your talkpage is the place to report these, but you'd better note this; I've confirmed that his huggle.css page was definitely blanked at the time, and he's right; his contrib history shows him using Huggle since the blanking. I blanked my huggle.css page as an experiment, and it also letting me log on just fine. Any thoughts?iridescent 00:45, 28 May 2008 (UTC)

This should now be fixed -- Gurchzilla (talk) 15:56, 1 June 2008 (UTC)

Copyright

What's the copyright status on Huggle? All I know is that it uses images under the LGPL, but what's the entire program under? It's useful when making snapshots, etc., so we don't assume it's PD. Calvin 1998 (t-c) 20:58, 23 May 2008 (UTC)

Nevermind, it's obviously LGPL. Going to have to fix a few images' license tags... Calvin 1998 (t-c) 21:01, 23 May 2008 (UTC)
The program itself is public domain. Screenshots that incorporate the icons are LGPL as derivative works -- Gurchzilla (talk) 21:04, 23 May 2008 (UTC)

I reverted an admin (actually, two)

I think that Huggle should unconditionally prohibit the reverting of any user with admin, rollback, or bot permissions (except yourself, read ahead), to prevent accidental reversion of good edits. If you're reverting yourself, it should prompt "Are you sure you want to revert yourself?" The two users I've reverted (FisherQueen, Maxim) are both on the whitelist, but it doesn't seem effective enough. -- King of ♠ 23:09, 19 May 2008 (UTC)

Yeah, occasionally someone on the whitelist can get reverted to. It's shown up in the past. Not sure why. Enigma message 23:11, 19 May 2008 (UTC)
I've encountered this on occasion and I think it happens when the new edit by the whitelisted user flashes up a split second before or after you hit the revert button. I'm not sure if that's the only time it happens, but that seems to be the most common time for it. Thingg 13:46, 20 May 2008 (UTC)
Hmmm, this shouldnt happen. What were the admisn names? That is if you know? ·Add§hore· Talk/Cont 14:39, 20 May 2008 (UTC)
FisherQueen and Maxim, both of whom are on the whitelist, of course. Enigma message 15:53, 20 May 2008 (UTC)
hmm /me must be blind :D ·Add§hore· Talk/Cont 16:42, 20 May 2008 (UTC)
Huggle now asks for confirmation when reverting edits by whitelisted users. Unconditionally preventing reversion of whitelisted users is probably not a good idea as it makes it harder to undo other contributors' mistakes -- Gurchzilla (talk) 17:09, 23 May 2008 (UTC)

Shortcuts

In the new version some shortcuts done work, e.g. Tag with CSD (S) and PROD (P). I will list any more If and when I find them ·Add§hore· Talk/Cont 18:41, 21 May 2008 (UTC)

Also [-] for closing a TAB and [+] for opening a TAB don't work for me =[ ·Add§hore· Talk/Cont 18:42, 21 May 2008 (UTC)
These should now be fixed -- Gurchzilla (talk) 17:07, 23 May 2008 (UTC)

Tagging for request page translation?

Just came across a new page in spanish that looks reasonable, if only translated. I can't find an appropriate tag in the Page->tag menu. Loren.wilton (talk) 07:55, 22 May 2008 (UTC)

Once you've opened the tagging window, you can type anything you like into the "Tags" field – the drop-down list is only there to make common cases easier. I will add {{notenglish}} to the list of tags, note however that it is meant to take the name of the language the article is currently in as a parameter, so you should add that yourself once you've selected it -- Gurchzilla (talk) 10:59, 22 May 2008 (UTC)
I'd suggest wording it as {{notenglish|language_name}} (assuming that is the correct syntax) to remind the user of the insert parameter. A simple double-click to select language_name and overtype with the assumed language. Loren.wilton (talk) 01:14, 23 May 2008 (UTC)
done -- Gurchzilla (talk) 09:22, 23 May 2008 (UTC)

UnDo AgaIn

Well just another thing I would like to point out is that if you try to undo a page that only you have contributed to (such as a warn) then you can and huggle crashes for me =[. I also hope this can be fixed with maybe blanking or csd'ing? ·Add§hore· Talk/Cont 16:45, 23 May 2008 (UTC)

Also If I try to undo myself it asks me If I want to undo the whitelisted user (me). Not sure if this is meant to happen :D ·Add§hore· Talk/Cont 16:49, 23 May 2008 (UTC)
The majority of people who we revert on Huggle are new to Wikipedia, as far as I am aware. They get this weird orange bar appear that says 'You have new messages', they click it. They're going to get confused if they find a blank page, probaly even more so if they find a Speedy tag on it! If it was the creation and you undo it, it should be replaced with a welcome message. If you did not create it, but undo a warning, an appology should be left. That's what I think at least. Tiddly-Tom 17:31, 23 May 2008 (UTC)
In the next version, trying to undo a page creation will offer to tag the page for speedy deletion, unless it's a user talk page, in which case it will blank it. This is what was intended for this version, but I made a mistake implementing it. It is at least better than it crashing. I am not sure that automation of apologising for automated edits is a good idea -- Gurchzilla (talk) 18:13, 23 May 2008 (UTC)

AfD

There isn't a way to nominate pages for AfD within Huggle, is there? I see pages all the time that don't fit the speedy-deletion or PROD criteria, and I'd like it if there was a way to auto-nominate it for AfD. Calvin 1998 (t-c) 22:10, 23 May 2008 (UTC)

Presumably you also want TfD, RfD, CfD, IfD and MfD? -- Gurchzilla (talk) 22:11, 23 May 2008 (UTC)
Yeah, maybe something like Twinkle's XfD - you press the button and you choose the type. Or you could have Huggle find the page type automatically... Calvin 1998 (t-c) 22:25, 23 May 2008 (UTC)
All except IfD done in the next version -- Gurchzilla (talk) 21:39, 24 May 2008 (UTC)
No point in implementing IfD anyhow - uploads are log actions, and don't show up in recent-changes (only in Special:Log). Calvin 1998 (t-c) 01:09, 25 May 2008 (UTC)
IfD is also done in the next version -- Gurchzilla (talk) 13:39, 30 May 2008 (UTC)

Suggestion: multiple session logging

The action log is nice, but it appears to go away when Huggle is closed. If I make some real messup and someone calls me on it the next day on my talk page, I might be left guessing what really happened. It might be helpful to go back to the log, but the log is long gone.

Perhaps there could be a "save log" item in the File menu to write it to a text file, and then automatically append to that file every time Huggle shuts down? (Or maybe ask if you want to appeand to the log on shutdown.)

This is a rather low-priority enhancement request. The first version I used did quite a number of strange things over several hours, and I got called on a number of them and could only say mea culpa, solly. However, recent versions have had very few problems, and only vandals have been complaining recently about my reverting them. So a permanent log would be a lot more "nice to have" than "I really need it". Loren.wilton (talk) 06:49, 25 May 2008 (UTC)

As far as I can tell, the log at the bottom of the window is just a copy of the user's contributions. In that if I make an edit in my browser while using Huggle, it will show up at the bottom there. Reviewing Special:MyContributions should be just as helpful as that log, in my opinion Alex Muller 08:43, 25 May 2008 (UTC)
Just make it automatically save the logs. You could save these to a wiki page in wiki format with the diff url or you could save to a txt file on your local machine /logs. Example of what I was thinking off
* [http://en.wikipedia.org/w/index.php?title=User_talk%3A76.84.25.207&diff=214520074&oldid=214308723 Notification: {{uw-editsummary}}]

I think This is a good idea. It would display as

NOTE: If it says templates it will need to add them into nowiki tags! ·Add§hore· Talk/Cont 08:48, 25 May 2008 (UTC)
The problem with saving to a wiki page is that said page would get very large very fast -- Gurchzilla (talk) 10:58, 25 May 2008 (UTC)
Alex is right. I don't see what the issue is. The log at the bottom is a simple copy of contributions that's updated whenever you make an edit of any sort, not just a Huggle edit. If you screw up using Huggle, it will be in Special:MyContributions. Enigma message 08:51, 25 May 2008 (UTC)
In fact actions other than edits are also listed in the log, though they will appear in Special:Log so they're still recorded on-wiki. The only things that aren't recorded anywhere else are messages telling you when actions failed or were not done for whatever reason -- Gurchzilla (talk) 10:28, 25 May 2008 (UTC)
In the next version I've added a "Save log" menu option which allows you to save the log to a text file. At this point it doesn't do this automatically -- Gurchzilla (talk) 10:58, 25 May 2008 (UTC)
This is fixed in the next version -- Gurch (talk) 22:37, 1 June 2008 (UTC)

Cannot login

I get a "Unable to login" message on 077. ffm 01:36, 28 May 2008 (UTC)

Does trying again after a while help? There seem to be intermittent problems with Wikipedia at the moment (database was locked just now for "emergency maintenance") so that might be causing it -- Gurchzilla (talk) 02:29, 28 May 2008 (UTC)
No, it still does not work. I am not using a proxy, and it is different from the "Incorrect password" message I get when I use a wrong password. I have tried on two different computers on different versions of windows on different networks. ffm 14:15, 28 May 2008 (UTC)
The irony is it works on the es wikipedia. ffm 14:27, 28 May 2008 (UTC)

I get the same error. I think it may be because I'm accessing the internet through a proxy server. Am I SOL, or is there a way to get around that? --Kbdank71 13:54, 28 May 2008 (UTC)

Login is completely broken now; these issues may or may not exist when the next version is released, hard to be sure -- Gurchzilla (talk) 20:07, 29 May 2008 (UTC)

0.7.9 CAPTCHA

Erumm, WTF? So it wants me to put in the CAPTCHA image but the image is cut in half so I can't read it.  ???? - ALLST☆R echo 10:12, 30 May 2008 (UTC)

Sorry, forgot to account for people with extra large titlebars. :) This is fixed in the next version -- Gurchzilla (talk) 11:52, 30 May 2008 (UTC)
I know, you can't remember everything. ;] - ALLST☆R echo 11:54, 30 May 2008 (UTC)
BTW the captcha is "coasttrip" :D -- Gurchzilla (talk) 11:56, 30 May 2008 (UTC)

Copy part 2

Could ya fix the right click Copy Shortcut so it copies the URL like it used to, instead of about:/wiki/List_of_characters_from_Coronation_Street (example)? - ALLST☆R echo 12:06, 30 May 2008 (UTC)

This is fixed in the next version -- Gurchzilla (talk) 13:53, 30 May 2008 (UTC)

Possible security risk

I think I may have found a potential problem with Huggle. I'm not sure if it would be a problem, but if it is, it will need to be fixed. I am emailing User:Huggle about it (I don't accidentally pull a case of BEANS). Thingg 18:38, 30 May 2008 (UTC)

Said email concerned the fact that the user whitelist is a wiki page and can thus be updated by anyone, raising the possibility that vandals could add themselves. If this is a problem, the page can be semi-protected, though there's no way to restricti editing further than that without preventing updates by legitimate users -- Gurchzilla (talk) 19:53, 30 May 2008 (UTC)
Couldn't the whitelist be placed off-wiki? Then it can be configured to not accept edits by anything but Huggle... Calvin 1999 (talk) 19:55, 30 May 2008 (UTC)
In theory, yes, though doing that would be difficult if not impossible (some sort of FTP arrangement with 'secret' password hardcoded into the application?) Is there anything wrong with just having things as they are now? I don't see any problems in the four months Huggle has been in use -- Gurchzilla (talk) 20:00, 30 May 2008 (UTC)
I'm proud to say I thought of it first. :D I actually asked Andon to semi-protect it, but he gave me the old answer of not protecting pages preemptively. Obviously there will never be a reason, IMO, for an IP to edit that page. In such cases, I would be in favor of protection. Oh well. Enigma message 20:00, 30 May 2008 (UTC)
By the way, that was just an idea, not a suggestion or anything... I'm not suggesting there is a problem... Calvin 1998 (t-c) 06:49, 31 May 2008 (UTC)
If you just reviewed the page history once in a while to see whether there are any edits that don't include the 'Automatically updating whitelist' then just revert that change. ——Ryan | tc 06:53, 31 May 2008 (UTC)
The whitelist has been semi-protected -- Gurchzilla (talk) 10:04, 1 June 2008 (UTC)

You must be absolutely sick of this kinda stuff but...

Can I request that in the next version of Huggle there is a shortcut to clear the queue? Saves me having to go to the menu everytime ;) Regards, CycloneNimrodTalk? 11:05, 31 May 2008 (UTC)

This is fixed in the next version (Ctrl + Space) -- Gurchzilla (talk) 16:39, 1 June 2008 (UTC)

Window position remembering bug

Could you umm... disable window size and position remembering across sessions in Vista or something... now huggle disappears when the main window loads (the application still has focus and the keyboard shortcuts still work) but the window disappears off to the top left. No idea why (I certainly didn't stick it there). It's making the application useless unless it's in full-screen. So... um.... either disable it altogether in Vista or figure out why it's doing that and fix it. By the way, it works fine in XP. Calvin 1998 (t-c) 02:40, 2 June 2008 (UTC)

Never mind, I found out where the config.txt file is located and manually fixed it. So far I don't think it's reverted me back to the wrong numbers yet. Calvin 1998 (t-c) 02:55, 2 June 2008 (UTC)
This should be fixed in the next version (does a sanity check on the numbers now), though as I don't have Vista I can't be certain -- Gurch (talk) 02:56, 2 June 2008 (UTC)
Well, mine had left/top margins in the negative thousands... keeping the margins >0 makes sense to me... especially the top one, as you can't move the window if it's out of the screen... Calvin 1998 (t-c) 03:31, 2 June 2008 (UTC)
I've been bit on this before -- some bits of code interpret the window rectangle as unsigned and other bits treat it as signed. So you move the border a pixel or two to the top left of the origin, save the position, and zowie! You now have a window opening 65,535 pixels away. Loren.wilton (talk) 07:38, 2 June 2008 (UTC)

Limiting Huggle for newbies

See the section User:Dynamization at WP:ANI. This seems to be a case of some newbie with about 15 edits who immediately grabbed Huggle and started reverting darn near anything as vandalism, and any attempts to communicate with them are seemingly reverted as vandalism.

This is the second case at ANI similar to this in the last few days, where someone fresh out of the egg thinks it is really wonderful to be able to revert like mad, but doesn't much look at what they are reverting.

I'm concerned about Huggle getting a bad name, and possibly getting banned by the misuse of newbies. The Admins seem to be showing that they are unable to agree on blocking Huggle to these people, even though they know how and obviously should.

So I think Huggle should block itself. The AWB page says that you have to ask for it, and are unlikely to get it until you have 500 edits. I've seen similar notices for other anti-vandalism tools. I think Huggle should have something similar. Specifically, I think it should maybe check the edit count on the user it is running for and flat refuse to run until there are some reasonable number of mainspace edits, or at least total edits. 500 would probably not be an unreasonable number, but I think 100 or 200 edits should be an absolute minimum before Huggle will allow itself to be turned on. It really doesn't take that long to use Recent Changes and manual undo or editing to revert vandalism, and it gives you a chance to decide what is vandalism and what isn't, rather than just clicking the red circle to advance to the next article to look at.

Thoughts? Loren.wilton (talk) 01:59, 23 May 2008 (UTC)

I'm in support of using the approval: true feature in the next version (0.7.7) of huggle so that we can have some sort of approval method, but Gurch appears to be against having any sort of approval mechanism... Calvin 1998 (t-c) 03:15, 23 May 2008 (UTC)
Even so, it's easy enough for admins to either block them (which they should be doing) or just full-protect their configuration page. Calvin 1998 (t-c) 03:17, 23 May 2008 (UTC)
Since a user can create a lot of disruption quickly before he's blocked or huggle page is protected, I agree that the program should do a check. Anyone who has the program can use it (nevermind how they got it in the first place; could be several ways), so you could have someone make socks all using Huggle or something. Best way to prevent this is to have the program check the contribs before allowing access. Enigma message 03:47, 23 May 2008 (UTC)
Yeah, the approval :true will do that - except then we'll need to full-protect the userlist. Calvin 1998 (t-c) 03:53, 23 May 2008 (UTC)
Well it could just read one of the apecial API functions and that would tell it how long the user has been registered for and how many edits they have e.t.c. I dont think this should be too much of a challenge for gurch to do. ·Add§hore· Talk/Cont 06:37, 23 May 2008 (UTC)
I'm not sure what the "approval: true" option is, but it sounds lie something that needs human intervention of some sort to either enable or disable Huggle. I'm not against that; there has to be a way to manually disable it, which of course exists now if the admins will just use it. But I hadn't even considered the sock argument. I think that adds even more weight to simply checking for 100 or so edits before being willing to run. You can get that many in a couple of hours of manual vandal fighting with no tools at all. Loren.wilton (talk) 08:09, 23 May 2008 (UTC)
Setting "approval:true" in the configuration will turn the existing user list into an approval list; if someone not on the list tries to use the program, they would be denied access rather than being added to the list. And yes, the user list would need to be fully protected.
Setting a minimum time and/or number of edits is also possible. The problem with that is that there are often cases where it would be nice to have an exception to the rule. For example, if a contributor who has already been using the software for some time wishes to set up a separate account purely for reverting vandalism, as several have done, or wishes to use the software on a separate account they use when editing from a public computer, as several have done – Gurchzilla (talk) 08:48, 23 May 2008 (UTC)
Hum. I'd suggest a combination of a minimum edit limit, combined with a perhaps new 'approved users' list rather than the current user's list. The new list would be used to handle the exceptions. Of course it could be done by using the existing list and method, but a new exception list seems a little cleaner to me. (Though obviously a bit more work to set up.) Loren.wilton (talk) 11:27, 23 May 2008 (UTC)
Hmm, how about we have an approval list but we have an automated php script that will add any one with rollback to the list on request. If they abuse the tool they get removed from the list and lose rollback. This should allow for control of the tool while not having a massing backlog of requests to be added to the access list --Chris 11:46, 23 May 2008 (UTC)
If you want to limit the tool to users with rollback, no list is necessary; Huggle can simply check the user groups -- Gurchzilla (talk) 15:21, 23 May 2008 (UTC)
In that case, I think you should restrict the program to users with Rollback. Most vandal fighters and recent change patrollers have been granted with rollback. If a user is so desperate to use Huggle, then they should request rollback beforehand. Leave it to the administrators to decide whether or not they can be trusted. If you leave it the way it is and allow anyone access to the tool, I can see Huggle being given a really bad name. My two cents ——Ryan | tc 16:10, 23 May 2008 (UTC)
I agree - though I'd also be happy with (Rollback OR 500 edits OR individual approval) - or some other such construct, for flexibility. Just using rollback conveniently means that there are already admins doing the vetting. Pseudomonas(talk) 16:32, 23 May 2008 (UTC)

<outdent>This discussion was just mentioned on WT:RFA---but as a regular there, I would support having access to this tool limited/restricted.Balloonman (talk) 16:36, 23 May 2008 (UTC)

I can't see any problems with it checking that the user has been granted rollback. Further up this conversation Gurch mentions that some people create second accounts just for Hugs. As far as I am aware theise accounts can be given rollback as long as the primary acocunt says it's theirs. So this is not a problem. Tiddly-Tom 17:24, 23 May 2008 (UTC)
Limiting by number of edits, account creation date, possession of rollback and approval list will all be possible in the next version -- Gurchzilla (talk) 17:31, 23 May 2008 (UTC)
Just limiting it to people with rollback should be sufficient to prevent abuse of the tool. This is a good idea; it probably won't be necessary to put the other restrictions into use, and this should resolve most concerns about its use. And as RyanLupin stated above, most RC patrollers... ...already haz rollback. Pyrospirit (talk · contribs) 23:48, 3 June 2008 (UTC)
Huggle now requires rollback to run per its configuration page. Calvin 1998 (t-c) 23:52, 3 June 2008 (UTC)
In the next version... Calvin 1998 (t-c) 06:06, 5 June 2008 (UTC)

Edit summary

Is there any chance that the edit summary can be changed? The "reverted edits by...to last version by..." format currently used is same that is used for rollback edits. This means it is impossible to distinguish between a Huggle revert and a rollback revert (which can be an important distinction in investigating roll back abuse). Thanks, Metros (talk) 00:53, 24 May 2008 (UTC)

I thought Huggle used rollback where it could anyway. Pseudomonas(talk) 01:09, 24 May 2008 (UTC)
Yeah, but it still appears as "Reverted edits by..." even when the user doesn't have rollback capabilities. Metros (talk) 01:24, 24 May 2008 (UTC)
We could make having rollback a requirement for having huggle as soon as 0.7.8 is out, but other than that... there isn't much we can change it to, is there? Calvin 1998 (t-c) 01:27, 24 May 2008 (UTC)
Perhaps Metros is asking that the "faked rollback" message be different than a real rollback message? Loren.wilton (talk) 10:08, 24 May 2008 (UTC)
The non-rollback reverting message doesn't have a "talk" link after the user's name. The problem with changing the summary used for rollback is that you lose information. The rollback summary gives the name of the user being reverted to, which isn't always available to Huggle when reverting; retrieving it would mean an extra page history request which would slow things down – Gurchzilla (talk) 10:36, 24 May 2008 (UTC)
As far as "investigation of abuse" is concerned, surely abuse of rollback while using Huggle is no different to abuse of rollback while not using Huggle, and surely someone abusing either of rollback and Huggle should have access to both removed? -- Gurchzilla (talk) 10:38, 24 May 2008 (UTC)
I would add something like "(WP:HUGGLE)" at the end of the message, so that people know that it is huggle LegoKontribsTalkM 06:11, 25 May 2008 (UTC)
Well, seems like Gurch is against advertising in edit summaries like that, so I don't know... Calvin 1998 (t-c) 17:16, 25 May 2008 (UTC)
My main objection is that there is enough of a problem with abuse of the software as it is without advertising its existence in every page history -- Gurchzilla (talk) 17:45, 25 May 2008 (UTC)
This is fixed in the next version -- Gurch (talk) 21:23, 1 June 2008 (UTC)
To clarify, it shows up as "<usual edit summary> (huggle)". Calvin 1998 (t-c) 01:32, 2 June 2008 (UTC)
The exact format can be changed in the configuration -- Gurch (talk) 01:39, 2 June 2008 (UTC)

Copy

Gurrrrrch! Please PLEASE bring back the ability to copy text. It makes it much easier to be able to highlight any text in the Huggle window and be able to copy it for pasting it elsewhere, such as URLs, usernames, etc. Copy is gone. Can't copy, can't right click over an article's link or user's link and copy link location, can't do any of that anymore. Can't even CTRL C to copy highlighted text. No keyboard shortcuts for copying. Am I just missing the ability? It was perfect in 0.6.3 which I was using until recently when I got 0.7.7. - ALLST☆R echo 05:22, 29 May 2008 (UTC)

I belive it was since 0.7.3 not 0.6.3 Antonio Lopez (talk) 18:10, 29 May 2008 (UTC)
I said 0.6.3 was perfect and was the version I was using until recently when I got 0.7.7. In other words, I meant 0.6.3, not 0.7.3. ;] And for the record, because of the missing copy text function, I have went back to using 0.6.3 and it's working flawlessly. - ALLST☆R echo 19:04, 29 May 2008 (UTC)
I took it out because it can cause crashes for people still using IE6. It is re-added in the next version -- Gurchzilla (talk) 19:51, 29 May 2008 (UTC)
What causes the crash? Copy-to-clipboard should be a pretty standard function I would think. (And I agree it is real useful!) Loren.wilton (talk) 07:26, 2 June 2008 (UTC)
IIRC just right-clicking at all in the browser window was causing the crash -- Gurch (talk) 08:05, 2 June 2008 (UTC)

Another tip

Right now, hovering on the contributions buttons gives the user who did the edit, the time, and the edit summary. Could you change the name of the user who did the edit to the page name? We know who did the edit, it says in the box. But we need to know the name of the page the edit was done to... Calvin 1998 (t-c) 03:50, 2 June 2008 (UTC)

This is fixed in the next version -- Gurch (talk) 17:11, 2 June 2008 (UTC)

Other wikis

Hi. How big is the effort for you to adjust Huggle for other Wikimedia projects (other language Wikipedias, sister projects etc.) provided the user warning templates exist? --Петър Петров (talk) 14:18, 12 May 2008 (UTC)

I think it should be quite easy. The question is can gurch be bothered =]. ·Add§hore· Talk/Cont 19:47, 12 May 2008 (UTC)
Which projects? Huggle is designed with the English Wikipedia in mind. It doesn't use warning templates, but it does need somewhere to report vandals and some agreed-upon system of warning levels, as well as translations of all possible messages, edit summaries and so forth. It would need to be rewritten significantly to be able to deal with multiple projects. Additionally, Huggle was designed to maximise the rate at which edits could be reviewed; with the level of editing found here; on most if not all of the other wikis (with the possible exception of the German Wikipedia) most of your time would be spent waiting for someone to edit Gurchzilla (talk) 02:54, 13 May 2008 (UTC)
I need an anti-vandalism support tool for bg.wikipedia. The "revert the edit + warn the user" is a common task. I can help with translating messages and testing. --Петър Петров (talk) 10:26, 13 May 2008 (UTC)
Does bg.wikipedia have an equivalent of Wikipedia:Administrator intervention against vandalism? Does it have a system of four warning levels; if not, how many warnings do you want it to issue before reporting/blocking? Can you point me to templates or provide translations for at least vandalism warnings; if you want other sorts of warnings I'll need them too. Do you want other things such as speedy deletion tagging? If so I'll need an appropriate template and edit summary for that (is bg:Шаблон:Бързо изтриване the right template?) -- Gurchzilla (talk) 12:42, 13 May 2008 (UTC)
All vandals in bgwiki are reported on bg:У:ЗА, literally "Wikipedia:Requests to the administrators"; there is no separate dedicated page for vandal reporting. If this is a must, it can be created.
Over time I have translated some of the user warning templates from en to bg; see bg:Category:Предупредителни шаблони за беседи. There is no strict agreement how many times a vandal should be warned, sometimes blatant vandals are warned only once or twice before been blocked for a short time. When translating the templates, I tried to maintain the iw links.
It might be useful for others to flag articles for speedy deletion; I have sysop rights on bgwiki and I would appreciate a direct deletion option with proper edit summary. And yes, the bg:Шаблон:Бързо изтриване is the right template. --Петър Петров (talk) 13:48, 13 May 2008 (UTC)
Do you need the Links for the Spanish Wikipedia? Antonio Lopez (talk) 11:48, 24 May 2008 (UTC)
It would be helpful, yes -- Gurchzilla (talk) 11:51, 24 May 2008 (UTC)

afd:Wikipedia:Consultas de borrado mediante argumentación
aiv:Wikipedia:Vandalismo_en_curso
aivbot: none
cfd: none?
rfd: none?

These are the only ones I can find for now. Antonio Lopez (talk) 19:23, 24 May 2008 (UTC)
Thanks. It will probably be some time before XfD process for other projects will be implemented, anyway; warnings are easier to do cross-project -- Gurchzilla (talk) 21:30, 24 May 2008 (UTC)
Yeah I noticed that, I also found out that the es.wikipedia has the same warning process as en.wikipedia seen here. Antonio Lopez (talk) 00:10, 25 May 2008 (UTC)

Assorted suggestions

I've been using Huggle for several releases, and have queued up a handful of suggestions. Herewith:

  1. Put a lockout delay on the revert buttons and on the keyboard shortcuts for same, if you have live update enabled and the page you are trying to revert gets updated. When first using Huggle I was using the keyboard shortcuts, and ended up with LOTS of problems reverting the person or bot that reverted just as I hit the R key. I gave up on the keyboard and only use the buttons, because I noticed that they do grey out when a new update comes by. However, I apparently managed to revert a reversion last night even with this. Perhaps extend the lock out to 1 second or until the 'next diff' button or spacebar is hit to try to prevent this. (Note: I almost always wait for the action to complete before going on to the next diff, so I really shouldn't be having problems in queue-land.)
  2. As others have asked for, some form of "I'm sorry!" undo button that will undo a warning and leave an apology. I've tried using the undo button several times, but for me it has never worked, and I've ended up opening a browser and cleaning up manually.
  3. I'd like to see some of the variant reasons for CSD, like bio, band, etc. These could leave nicer warning messages for 'notify author' like "thanks, but your band isn't notable" rather than the generic "that isn't important" tag it may be leaving now. (The main reason I'd like to see the variants (in alphabetical order) is because I think in terms of those variants and then have to translate back to the more generic reasons.)
  4. Reporting to pages other than AIV. Specifically, improper username blocking requests. Being able to report a page to RFPP would also be nice occasionally.
  5. I use Huggle at much less than full-page size since I run a huge screen. Remembering the size and position of the page when I close it and using that size and location next time it starts would be real nice.
  6. An option to remember my username (but not password) would be nice. I'm the only one using this machine, so it is safe to remember me. Probably a "remember me" checkbox on the login dialog to be consistent with how other apps do this.
  7. Put CSD tagging in a menu, or on its own button that shows the droplist. CSD tagging is very slow compared to vandalism tagging since you have to go through about 4 actions to tag a CSD, vs the one click for a vandal. I should be able to do a CSD as fast as a vandalism revert where I select a message.

Thanks for considering these, Loren.wilton (talk) 23:01, 21 May 2008 (UTC)

To report to Wikipedia:Usernames for administrator attention, click the Report button and select "Wikipedia:Usernames for administrator attention" in the drop-down box. To request page protection, select "Request protection..." from the Page menu. (I have not added a button for this to the toolbar because Huggle needs to be usable with a screen resolution of 800x600, and space is limited) -- Gurchzilla (talk) 23:10, 21 May 2008 (UTC)
In the next version, username, project, recent changes source and window size and location will be remembered -- Gurchzilla (talk) 11:52, 22 May 2008 (UTC)
To summarise, 4 was already implemented, 5, 6 and 7 have now been implemented, 1 should be less of a problem now that it asks for confirmation when reverting a whitelisted user, 3 is not yet implemented but should be at some point; as for 2, Undo should now work in all situations, and the addition of the Cancel button should make things easier, but as I've said elsewhere I'm not entirely comfortable with the idea of automating the process of apologizing for mistakes made with an automated tool, especially given the complaints that have been aired about use of Huggle -- Gurchzilla (talk) 21:48, 24 May 2008 (UTC)
3 is now implemented -- Gurch (talk) 02:39, 2 June 2008 (UTC)