Wikipedia talk:Huggle/Feedback/Archive 20

This is an archive of past discussions about 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.

I'm a keystroke-oriented user, and I frequently need to pull up the users' contributions while patrolling. Could we add a keystroke to do this, perhaps the C key?

This also brings up another concern. Here is my admin workflow which I think can be improved:

• When I revert after they've received a final warning, I am prompted about reporting to AIV
• I hit No as I want to handle the blocking myself. This brings me to the next edit
• I have to hit Back to get back to the user I want to block
• Go to User > Show contribs in browser so that I can review their recent edits
• Decide on whether to block

When I am prompted to report to AIV, could we have an additional button to open up the user's contribs? Ideally clicking that would also advance to the next edit, so that when I return to Huggle I'm ready to keep patrolling. Some admins might also want a Block button in the AIV confirmation dialog, but I personally prefer to block using Twinkle.

Many thanks! — MusikAnimal ^talk 17:01, 13 October 2015 (UTC)

Will be there in 3.1.19 https://github.com/huggle/huggle3-qt-lx/commit/cdcb52dce42a10c15430ff7be203c278c6b44dbc Petrb (talk) 10:02, 19 October 2015 (UTC)

I will rethink how to do what you ask for, but I don't really have an idea how it works when you are admin. I could test this on test.wikipedia.org where I have sysop rights, but it's a low traffic wiki and I will hardly be able to reproduce standard production use there. I for one never saw the message box you talk about, despite I might have been the one who created it :) Petrb (talk) 10:04, 19 October 2015 (UTC)

So if I understand you correctly, when there is a user with 4 level it ask you if you want to block him? And you hit no. If you hit yes I think a block form would be displayed. Would the next page in queue display in this case? I think it would. Which means that the button to display user's contribution should probably be on the block form, which is rather a trivial to do. Petrb (talk) 10:11, 19 October 2015 (UTC)

It might say "do you want to block" and not "do you want to report to AIV", can't remember, but either way the answer for me is no. I want to open their contributions in the browser and use Twinkle to block as I have better control over what I want to do. So really with that dialog that opens up, just have "yes" "no" and "open contributions". When the contribs button is clicked it also advances to the next edit. I realize this may be a specialized use case, but I figure one more button can't hurt? Either way the keystroke for opening up contribs will definitely save lots of time. Thank you! — MusikAnimal ^talk 20:14, 19 October 2015 (UTC)

Hi. It looks like Huggle will try to use templates that don't exist on other projects, e.g. here on Wikibooks. Matt (Talk) 11:11, 22 October 2015 (UTC)

I want to enable Huggle for urdu wikipedia project, would you plz? --Muhammad Shuaib (talk) 05:29, 30 October 2015 (UTC)

Normally, when warning an IP address, there is a 24 hour "grace" period between the current time and the time of the last warning. If the last warning was issued more than 24 hours ago, the warnings are "reset" and a level 1 warning is issued instead, even if the last warning was a level 4 (which would normally result in a report to WP:AIV). ClueBot NG, as well as the old Huggle, use this system. Huggle 3 doesn't seem to have this; while this is fine for user accounts (since accounts are expected to belong to one person and one person only, so warnings don't necessarily have to be reset), IP addresses can be shared by multiple users, so this warning "reset" system is needed to prevent new editors who made their first test edit to not be suddenly blocked without so much of a warning, or to receive a very stern, threatening warning because previous editors had accumulated the nicer warnings beforehand (Example of this happening). May I suggest this feature be added in an update to Huggle 3? Thanks, --I am k6ka ^{Talk to me!} _{See what I have done} 11:46, 30 October 2015 (UTC)

Huggle 2.1.16 almost constantly giving error messages

"yyyy-mm-dd hh:mm:ss (+hh:mm) -- Failed to retrieve user contributions: Passing ' ' for timestamp parameter ucstart has been deprecated. If for some reason you need to explicitly specify the current time without calculating it client-side, use "now"."

This also seems to happen when button-reporting a user for vandalism after final warning. This has become impossible since a while now. - DVdm (talk) 15:49, 22 October 2015 (UTC)

@DVdm: Unfortunately, support for Huggle 2 has been dropped a long time ago (I know, I miss it too!). A fix for this may be slow coming, if it ever happens at all. --I am k6ka ^{Talk to me!} _{See what I have done} 11:47, 30 October 2015 (UTC)

I was afraid of that. Too bad, as I'm not planning to start using H3 any time soon. Thanks for the reply. - DVdm (talk) 13:20, 30 October 2015 (UTC)

Hi,

Do you know how can I disable this month header when Huggle leave a message on a talk page?

I already unchecked "Use months as headers instead of name of page" but it doesn't seem to work. Plus, the header is in English instead of French.

Huggle local config : fr:Wikipédia:Huggle/Config

Thanks. Thibaut120094 (talk) 13:35, 4 November 2015 (UTC)

Oh never mind found it, just need to add headings:none to fr:Wikipédia:Huggle/Config. Thanks. Thibaut120094 (talk) 14:09, 4 November 2015 (UTC)

Whenever a diff is loaded using fallback rendering, Huggle does not revert the edit at all and I've had to use default rollback instead. lavender|^{(formerly HMSSolent)}|lambast 00:53, 12 November 2015 (UTC)

Hello Huggle maintainers. First, thank you for the excellent work you do. I was coming to download the new version of Huggle today but I noticed it is not signed. It would be good if you could sign the distributed binaries and publish the public key on-wiki so we can verify authenticity. Or as a simpler but still effective measure, you could publish SHA256 checksums on the download page. This is a reasonably standard measure, particularly in the free software world, and I think it is important to verify the software we use. Could you look into doing one of these things? BethNaught (talk) 19:17, 1 December 2015 (UTC)

Ubuntu PPA's are signed. Windows binaries are not, but they are located on GitHub and untrusted users can't publish any new releases. If you want to be 100% sure it's clean, I recommend building it yourself from source code. Petrb (talk) 15:17, 14 December 2015 (UTC)

Hello, what must I do for make active Huggle on AzWiki? Many vandalism acts happen on AzWiki. I think that for fight with vandalism Huggle will be more efficient. Regards, sysop on AzWiki --Serk@nl@nd 18:59, 19 December 2015 (UTC)

Can anyone provide me with a direct download link (when I click it, the download starts immediately)? It would be similar to STiki's download link. The reason behind this is so I can download Huggle at school and use Huggle there. The StormCatcher (talk) (contribs) 14:28, 14 December 2015 (UTC)

Hello, there is no such a link as it changes everytime there is a new release. However, if you want to run huggle in school, you will probably need to create your own portable version because huggle installer requires admin permissions, so that it can write to C:\Program Files which are restricted to admin users and so that it can install the VS redist package, required for huggle built with Visual Studio. If you install mingw32 version on any computer, you can just make a zip file of target folder and unzip it anywhere else and it should work. Petrb (talk) 15:15, 14 December 2015 (UTC)

@Petrb: I may be asking a bit much but could you provide me with a tutorial, maybe written steps or something? Anything? The StormCatcher (talk) (contribs) 02:19, 18 December 2015 (UTC)

Ok, here is step by step guide:

• Download huggle mingw version: https://github.com/huggle/huggle3-qt-lx/releases/download/3.1.18/huggle_3.1.18_mingw32.exe
• Install it to some computer you have admin rights on
• Zip the folder you installed huggle to
• Copy the zip to any computer you want to use huggle on
• Unzip
• Run huggle.exe

Let me know if anything wasn't clear Petrb (talk) 22:51, 29 December 2015 (UTC)

I'm new to using Huggle, and I have a couple questions right off the bat:

1. Can I filter the queue by a list of pages, or by links to articles and other pages from a specific page? I don't want to deal with the whole queue, as I'm mainly only interested in changes to pages in a couple wikiprojects. These wikiprojects have change patrols which work off of lists of their included pages.
2. Can I mark users I trust so I don't see their edits?

Thanks for any assistance. Stevie is the man! ^{Talk • Work} 17:14, 22 November 2015 (UTC)

1. You can't do that YET, unless, of course, you are programmer experienced enough to create your own feed provider. The options in queue filter only allow you to specify the namespace and tags. Which may help you a bit, but probably not entirely. On other hand, using huggle on some very specific page list only, makes it much less useful, as there probably isn't many changes per minute to these pages.
2. Yes, but you usually don't need to do that. Huggle does this for you. People who can be trusted are automatically whitelisted. Huggle has mechanisms that determine this, but if you want, you can also do that by hand. There is an option to decrease badness score of a user by 200 in user menu. Users with score <= -800 are inserted to global whitelist. Petrb (talk) 18:44, 22 November 2015 (UTC)

#2 satisfies my concern there. Thanks. As for #1, I don't really want to do full change patrol, but rather just that for some projects' included pages and associated talk pages, which is in the 10s of 1000s. If it moves slowly, that's fine. I would like something to present the most likely vandalisms to me rather than me having to look at all the diffs manually, including the edits of editors I should trust. I don't understand why I would need a new feed provider -- is there not some way to filter what is presented to me? Wouldn't it be simple to say "Only show me the pages on this list"? Stevie is the man! ^{Talk • Work} 20:07, 22 November 2015 (UTC)

There isn't such a filter right now, but might be implemented in the future. Petrb (talk) 22:56, 29 December 2015 (UTC)

I suggest there be an option that you could monitor edits of a user. For example, if there is a user that is reported to WP:AIV but still vandalizes, an alert could pop up on your screen. Dat Guy^Talk_Contribs 15:44, 28 December 2015 (UTC)

Sounds like an idea but keep in mind that users reported to AIV tend to have badness score around 8000, which results in their edits being almost always on top of the queue with various icons, most likely the red O symbol. Petrb (talk) 22:54, 29 December 2015 (UTC)

@Petrb: Not only reported users. How about some users you just want to monitor to check if they even vandals at all or if they are doing good faith edits or repeating vandals who still didn't receive a level 4 warning? Dat Guy^Talk_Contribs 09:09, 30 December 2015 (UTC)

That's exactly when you should increase a badness score using User menu. That way the user's contribs get much higher in a queue, no matter who they are. Petrb (talk) 15:59, 2 January 2016 (UTC)

I am trying to use Huggle after a long time - downloaded the latest from the download page(tried both 32 and 64 bit versions), doesn't let me login. Any help would be nice. Able to login fine into web, tried both in and out of VPN but --> Error: Login failed unable to retrieve global config, the api query returned no data

 A m i t  웃   21:27, 30 December 2015 (UTC)

You need to check SSL login. Petrb (talk) 15:59, 2 January 2016 (UTC)

Thanks, it worked  A m i t  웃   16:58, 3 January 2016 (UTC)

Can login to Huggle 3 but not to Huggle 2 (version 2.1.16). Message in login box: "Unable to login." Any idea? - DVdm (talk) 07:23, 22 January 2016 (UTC)

Suppose you mean 2.1.26. Same problem here in es:, en: and de:. --Jkbw (talk) 16:58, 22 January 2016 (UTC)

Yes, 2.1.26, sorry. - DVdm (talk) 17:07, 22 January 2016 (UTC)

Possibly same issue as being discussed at Wikipedia:Bot_owners'_noticeboard#Breaking_change. — xaosflux ^Talk 17:10, 22 January 2016 (UTC)

WP:STiki is also currently broken. Flyer22 Reborn (talk) 19:20, 22 January 2016 (UTC)

Huggle 2 back in business! - DVdm (talk) 14:44, 23 January 2016 (UTC)

Since recently (a week or two) the diff part of the window in Huggle 2 shows the page titles and navigation links and the left side bar, whereas it used to just show the diff of the viewed edit. That means that with each view we have to scroll to the right to be able to see the diff, which is pretty annoying. Have others seen this too or is it just me? - DVdm (talk) 15:03, 23 January 2016 (UTC)

Yes, it looks like a complete diff as seen by a browser. For every diff to be displayed there is an entry in the log field "Failed to retrieve 'title=pagename&diff=..... ' Unknown error". According to my recollection this problem arose for the first time when WP announced its 15th birthday on every page, but this might be an accidental coincidence. --Jkbw (talk) 00:51, 25 January 2016 (UTC)

Frequently, a vandal will vandalize multiple pages. When looking at a page that needs a revert, the "User info" box displays other pages edited by the same account / IP address. Clicking the pages in that user info box shows that user's edit to various pages. Often times, those are vandal edits. Unfortunately, the Diffs don't tell you if what you're looking at is current or not, so there is no way to know whether to revert - all you can do is attempt a revert, and wait for the popup box to tell you there is a newer version.

The pane in the middle that shows the diffs should always indicate whether the pane on the right is the current version of the page. This way, it's easy to go through a vandal account's history and revert several pages without having to head to a browser to do it the old fashion way.

Similarly, reverting automatically brings up the next article in the queue, which obviously changes the User Info box as well.

For the purposes of auditing edits of a vandal account, there should be some sort of "push pin" to freeze the user info box on the vandal account, even after doing a revert (preventing the next queue article from popping up).

Some of the fastest, best anti-vandal work is done in auditing vandal edit history, and if Huggle made it easier to go through those and revert one after another without the article cue popping in, it would be a great tool. - superβεεcat  09:21, 22 January 2016 (UTC)

That is exactly how it works, check the screenshot: http://snag.gy/LdWRx.jpg the bold items in User info widget are top revisions. You can instantly see that. In next huggle version the colors will be different but it's always bold if top revision. Petrb (talk) 15:59, 30 January 2016 (UTC)

Regarding "push pin" just do "Revert and stay on page" instead of revert. For example by default Q reverts and warn user. Shift + Q revert and stay on the page. Which is exactly what you need. Petrb (talk) 16:01, 30 January 2016 (UTC)

Hi there, I put this in #huggle ^connect but no response was given. In the latest versions of Mac OS X, command + space is an OS shortcut to open search. As such, the command isn't passed through to Huggle for 'clear queue' functionality. Is there a way to change this on the OS X release to another binding? Perhaps ctrl + space? Matthew Thompson ^{talk to me!} 13:55, 20 January 2016 (UTC)

Hello, sorry for late response but I am pretty busy these days and unfortunately not many people watch this page, unfortunately in current version you can't do that. In next version you will be able to open preferences -> shortcuts to change it Petrb (talk) 16:08, 30 January 2016 (UTC)

Is there a way to create or modify a queue that is basically filtered edits but much more strict? As in a very high score threshold. If that makes sense. --allthefoxes ^(Talk) 03:39, 2 January 2016 (UTC)

That is a perfect idea I will try to implement this. Petrb (talk) 16:09, 30 January 2016 (UTC)

Any particular reason why the A11 CSD tag isn't in Huggle? Dat Guy^Talk_Contribs

I will check that, does it require some paramters? These are usually harder to set up Petrb (talk) 16:09, 30 January 2016 (UTC)

Since somewhere yesterday when logging on to Huggle 2 I get:

Failed to load configuration pages!: HTTP used when HTTPS was expected.

Is it me only? - DVdm (talk) 14:46, 30 January 2016 (UTC)

It's just WMF loving to break stuff... Recent enforcement of SSL on wikimedia sites caused quite a nightmare for tool devs, including me. And probably also nightmare for people who can't use https (some countries on east actually block https as government there wants to sniff what people do on internet). So in fact, wikipedia is no longer encyclopedia that everyone can read, just some chosen people in western countries. Petrb (talk) 16:06, 30 January 2016 (UTC)

Fortunately I have full access to HTTPS. Perhaps it's something hardcoded in the exe? When I replace all the strings "http:" with "https:" in config.txt, and try again, I get the message

Failed to load configuration pages!: You must be logged-in to have a watchlist.

Strange... - DVdm (talk) 16:10, 30 January 2016 (UTC)

Problem with huggle 2 was that it wasn't using API for everything. Last version might use it for login, but some stuff was retrieved by screen-scraping the HTML code returned from normal web requests from wiki (eg. non-api). Huggle 2 is a successor of Huggle 0x (1) which was developed back then when API were in cradle and this stuff had to be done this way. Lot of stuff changed and as I said, people in WMF don't like to keep old stuff supported for very long. But I recall these problems with "You must be logged-in to have a watchlist" from past, they were generally related to some login issues. The source code of huggle 2 is available there: http://github.com/huggle/huggle and everyone is welcome to fix it and submit a pull request with patch. Petrb (talk) 16:18, 30 January 2016 (UTC)

I find the first part of the messages in the EN.TXT, but there's no trace of the second part, so I guess it is part of what the program receives from the system. Anyway, I don't have a VS installed anymore (or yet), so this is (or might be) for later. Thanks. Meanwhile let's wait ^{(wishfully thinking)} till this problem (and the previous one with the diffs) somehow gets fixed all by itself. - DVdm (talk) 20:02, 30 January 2016 (UTC)

@Petrb: I downloaded the ZIP with the project. I installed an old VS2008 on an old XP3. When loading the project I get a large number of missing (unregistered) stuff. Apart from the zip, is there anything I can download to be able to successfully load and compile it? - DVdm (talk) 17:37, 31 January 2016 (UTC)

Problem solved. But still, I'd like to know: can H2 be compiled with Visual Studio 2008 or do I need a more recent version? There's a massive number of syntax error and warnings as well. Obvioulsy not here, but where can I ask if/when I encounter problems? Thx already. - DVdm (talk) 17:23, 1 February 2016 (UTC)

Hi, my old Huggle 2.1.26 worked again without any modification starting 31 January. About one and a half hour ago the HTTP/HTTPS problem arose again, but it vanished after about 30 minutes. Obviously it is a lottery, hope to hit the jackpot some day. --Jkbw (talk) 02:19, 2 February 2016 (UTC)

Huggle 2 suffers from HTTPS problem again. Vandals can do their thing... - DVdm (talk) 10:30, 5 February 2016 (UTC)

I managed to compile and debug H2 with Visual Studio 2015. Unfortunately the error "Failed to load configuration pages!: HTTP used when HTTPS was expected" is not generated in the program, but is a result coming from the server. There seems to be nothing that can be changed to Huggle itself. Must be something on the server. Any idea where I can escalate this? Anyone? - DVdm (talk) 11:56, 9 February 2016 (UTC)

@DVdm: if it's a Wikimedia server issue, Phabricator is where you'll want to raise it. ~ Matthewrbowker ^{Drop me a note} 17:00, 9 February 2016 (UTC)

Thanks! Will keep you posted. - DVdm (talk) 18:03, 9 February 2016 (UTC)

Follow Phabricator task T126357. - DVdm (talk) 18:45, 9 February 2016 (UTC)

Do you think there could be a way that we can filter edits by WikiProjects? For example, I spend most of my time editing in WikiProject Professional wrestling and WikiProject National Football League and I would like to be able to select an option that allows edits to articles and templates in those projects appear only. Except have it set up to were we can add any WikiProject we'd like. CrashUnderride 18:01, 30 January 2016 (UTC)

Any thoughts??? CrashUnderride 11:06, 10 February 2016 (UTC)

Sound interesting, but how do you actually figure out which wikiproject page belongs to? This is definitely enwp only feature. Petrb (talk) 11:47, 12 February 2016 (UTC)

On the article's talk page. The projects banners. I would suggest using the categories at the bottom of the page. CrashUnderride 13:05, 13 February 2016 (UTC)

Hi,

It's sad but my poor mac mini I got for huggle builds broke :( which means I can't build a Mac version. Because it wasn't cheap I can't get any other any time soon. So if there is someone with Mac and development skills who is willing to install whole X-Code and qt (about 2gb) on their OSX, please let me know so that we can prepare the .dmg for last version. Petrb (talk) 18:21, 12 February 2016 (UTC)

I have no experience with macs, but can't you run a virtual OSX under WMWare? - DVdm (talk) 18:43, 12 February 2016 (UTC)

I tried once, it wasn't even legal as you need a license for OSX and it didn't work. Answer from virtualbox was "running OSX on non-apple hardware is not supported". Petrb (talk) 18:47, 12 February 2016 (UTC)

+ you need to download stuff from apple store to which you don't have access on pirated OSX versions. Petrb (talk) 18:48, 12 February 2016 (UTC)

@Petrb: Give me a poke when you have the time, I have a MacBook and I'd be glad to build if you need it for a little while. Just can't do nightly ones, because my MacBook is also my personal machine. ~ Matthewrbowker ^{Drop me a note} 21:38, 12 February 2016 (UTC)

Can't you hack something up though travis.ci ? —TheDJ (talk • contribs) 11:16, 16 February 2016 (UTC)

• Problems with H2

1. Stops at login with error: "HTTP used when HTTPS was expected"
2. Diffs show page headers and left navigation frame. Scroll to right needed with every diff
3. Crashes when reporting a user through User menu, Report
4. Crashes when requesting page protection through Page menu, Request protection
5. Massive amounts of errors: "Failed to retrieve 'title=....&diff=.....&oldid=.....&uselang=....": Unknown error

• Problems with H3

1. Always opens in full screen mode (not a big issue, just mildly annoying with a large 4K UHD monitor)
2. Many updates of pages not seen (while I do see them appear in H2)
3. User warning level blobs almost never update in Page editbar, never update in User editbar, sometimes update in Page history window.

Numbers 2 and 3 still make H3 essentially unusable for me ^{(sob sob)}, so I only use it for user reporting and page protection requests.

Are there any plans for fixing some of these problems? Hope you don't mind my insisting.- DVdm (talk) 11:34, 2 February 2016 (UTC)

FWIW, meanwhile —with a few simple hacks in a private version— I managed to solve Huggle 2 problems 1, 2, 5. Problem 3 does not occur anymore. Problem 4 status unknown.

If this is off-topic, please let me know. - DVdm (talk) 14:49, 10 February 2016 (UTC)

If you did some hacks to make huggle 2 work you might want to share them with others through a pull request on GitHub so that other HG2 users can keep on using it. Some of them can't use HG2 right now. Petrb (talk) 11:48, 12 February 2016 (UTC)

Hi Petr, I'd be glad to share, but I have no idea how and where to make a pull request on GitHub. And is that a pull of the source, or of the compiled (and renamed) exe? See also Phabricator task T126357 where I asked a similar question, and which is also where I documented the hack that made it work again.

By the way, at this moment H3 and H2 don't work at all, so there is not much point in sharing, see [1]. - DVdm (talk) 12:00, 12 February 2016 (UTC)

H3.1.19 seems okay. In order to fix my hack of H2 (and share it), can I find some kind of diff between H3.1.18 and H3.1.19 somewhere? - DVdm (talk) 18:45, 12 February 2016 (UTC)

https://github.com/huggle/huggle3-qt-lx/commit/2da6e2383624c423b856d61d0be50dcd8a4750ce Petrb (talk) 18:52, 12 February 2016 (UTC)

Thanks. Do you think^{(wishful thinking aloud here)} there will be something similar in the H2 source??? Too bad I only have a VS2015 at the office, but perhaps I can install one here as well. We'll see about that. - DVdm (talk) 19:27, 12 February 2016 (UTC)

@Petrb: I have a properly running multi-dirty-hacked version 2.1.27 here. Alle my mods are documented with the string DVdm. How do I go about handing this over to you for scrutinizing and publishing? - DVdm (talk) 09:43, 13 February 2016 (UTC)

@Petrb: Obviously this hack is running quite successfully in enwiki. I would like to check its functionality in eswiki. Can you manage a redistribution via the well known location? Thank you in advance. --Jkbw (talk) 23:17, 28 February 2016 (UTC)

It also runs in the German Wiki (see User talk:DVdm#HG) and it probably does too in the other langauges, as it counts on standard HTML tags, which are universal. I have left a version 2.1.27.5 in our common dropbox folder, but Petr hasn't given any sign of life since a few weeks. Probably ski holidays. I tried to upload to GitHub, but it looks like I have no access—or like I miserably fail to understand how the procedure works. Meanwhile I am (almost desperately) looking for a way to have the user warning levels (1,2,3,4) show up again in newly added queue entries. IIRC Huggle used to do that, but it does not anymore. Huggle 3 does it, but the levels don't show anywhere else. - DVdm (talk) 08:07, 29 February 2016 (UTC)

I have left a new version 2.1.27.6 in our shared dropbox, ready to be picked up, tested, honed and published by Petrb. Caught bug reading resources file WarningSummaries.txt by ConfigIO.vb. Separator char CRLF was used instead of vbLf, resulting in a corrupt lookup table. I made the config reader try both split schemes. User warning levels (1,2,3,4) correctly appear in the coloured blobs in the queue again. - DVdm (talk) 15:15, 2 March 2016 (UTC)

I tried to do a clean install of 3.1.19 but when I try to run Huggle after the installer is finished I get the following error:

"This application failed to start because it could not find or load the Qt platform plugin "windows". Reinstalling the application may fix this problem"

Reinstalling did not fix the problem. -- Rrburke (talk) 15:57, 13 February 2016 (UTC)

And no Huggle directory or files were created during the install. -- Rrburke (talk) 16:00, 13 February 2016 (UTC)

Which one is that? 32/64/mingw? 89.177.100.4 (talk) 18:18, 13 February 2016 (UTC)

I tried installing both 64 and 32; both generated the same error on exiting the installer. -- Rrburke (talk) 20:38, 13 February 2016 (UTC)

I can't replicate this can you check if there is folder Huggle in your Program Files directory? If yes, can you send me complete listing of all files in that folder? 89.177.100.4 (talk) 13:12, 14 February 2016 (UTC)

Hi and thanks for your help. No, there is no Huggle folder. -- Rrburke (talk) 13:48, 14 February 2016 (UTC)

Ok can you restart the installer and provide the logs from it? Petrb (talk) 14:46, 14 February 2016 (UTC)

I ran C:\Downloads\huggle_3.1.19_x64.exe /L*V huggle.txt from the command prompt to create a log, but no log called huggle.txt appears to have been created. -- Rrburke (talk) 15:52, 14 February 2016 (UTC)

Do you see any errors or something while you install it? Are you sure there is no Huggle folder not even in (x86) dir? Petrb (talk) 16:37, 14 February 2016 (UTC)

I get an error when I try to run Huggle at the end of the install:

"This application failed to start because it could not find or load the Qt platform plugin "windows". Reinstalling the application may fix this problem"

Other than that, there are no error messages. -- Rrburke (talk) 17:21, 14 February 2016 (UTC)

Bump. -- Rrburke (talk) 16:44, 21 February 2016 (UTC)

Now I get a different error message after (supposedly) installing:

• The application was unable to start correctly (0xc000007b). Click OK to close the application.

No Huggle files or directory are created during the install, and the error is the same whether I use 32/64/mingw. -- Rrburke (talk) 16:29, 29 February 2016 (UTC)

Hello. where can I download the source code? — Preceding unsigned comment added by 2003:70:CF41:301:D4B2:CA7C:62D4:110D (talk) 18:56, 5 March 2016 (UTC)

Here: https://github.com/huggle/huggle3-qt-lx/releases -- Rrburke (talk) 21:16, 5 March 2016 (UTC)

I'm trying to connect with huggle, but I'm getting a error message. After the "Retrieving white list" step, I get the error:

ERROR: api.php responded with unknown result: WrongToken

I've already tried on en.wiki, pt.wiki and test.wiki, and the same. Anyone knows what is going on? - Editeur ^? 02:41, 12 February 2016 (UTC)

Same problem. Donner60 (talk) 03:33, 12 February 2016 (UTC)

Anomie debugged this and found that Huggle3 was assuming that the token returned by the API was safe to include in a URL without applying URL encoding. The SessionManager changes to MediaWiki that are included in the 1.27.0-wfm.13 branch which was deployed to all wikis at 2016-02-11T20:01Z included a change to the session tokens that invalidated this assumption. There is a proposed patch on GitHub that appears to fix the problem. I'm sure that Petrb will get a new build out as soon as the fix can be properly tested and confirmed. --BDavis (WMF) (talk) 04:09, 12 February 2016 (UTC)

Thanks. Donner60 (talk) 04:21, 12 February 2016 (UTC)

Huggle2 too: "Unable to log in." Yesterday I have been working with it without any problem. After that change, when H3 stopped, H2 stopped too. - DVdm (talk) 07:19, 12 February 2016 (UTC)

New release of huggle 3 is on the way, please be patient. HG2 might take some more time, not sure what is broken there, I thought we always encoded the token in that one. 89.177.100.4 (talk) 11:45, 12 February 2016 (UTC)

Huggle 3 binaries for Windows 7 and newer are prepared, build for MacOS and older windows should be done today. Petrb (talk) 12:23, 12 February 2016 (UTC)

• Problem fixed. Huggle is now working. - Editeur ^? 17:07, 12 February 2016 (UTC)
  • @L'editeur and Petrb: Problem not fixed. I just tried to log in, and got a WrongToken error.  I dream of horses (My talk page) (My edits) @ 17:34, 12 February 2016 (UTC)
  • At least not on macs.  I dream of horses (My talk page) (My edits) @ 17:39, 12 February 2016 (UTC)

It looks like the newest release, 3.1.19, resolves the issue (it is working for me now) - Mac users will have to wait. ~Oshwah~^{(talk) (contribs)} 18:04, 12 February 2016 (UTC)

Yes, the 3.1.19 release for macs is coming. - Editeur ^? 21:49, 12 February 2016 (UTC)

The 3.1.19 OSX build is now available on GitHub. --BDavis (WMF) (talk) 22:04, 12 February 2016 (UTC)

For me didn't worked. If I tried to use old version? I use HUggle for Linux/Ubuntu. Vitor Mazuco ^Talk! 13:10, 13 February 2016 (UTC)

Didn't work for me either: I'm having the same problem. -- Rrburke (talk) 13:54, 13 February 2016 (UTC)

I also get the "Unable to log in" error with Huggle 2. -- Rrburke (talk) 14:16, 13 February 2016 (UTC)

I have a solution for that, but I have no idea how to upload it. See previous thread. - DVdm (talk) 14:25, 13 February 2016 (UTC)

@DVdm Uploaded what? Vitor Mazuco ^Talk! 21:56, 13 February 2016 (UTC)

Huggle 2.1.27, working better than it did before. I found and fixed a few bugs in the original 2.1.26. I have the source package and/or the compiled executable. - DVdm (talk) 22:00, 13 February 2016 (UTC)

Oh yes, but this Huggle didn't work in unix-like. Vitor Mazuco ^Talk! 15:54, 14 February 2016 (UTC)

Vitor, You need to download last version for it to work Petrb (talk) 16:41, 14 February 2016 (UTC)

Thanks Petrb. Vitor Mazuco ^Talk! 21:10, 14 February 2016 (UTC)

@DVdm: Since you updated your HG config earlier this month, it hasn't been including the standard edit summaries when issuing user warnings – i.e. instead of something like "Level 4 warning re. Interstate 24 (HG))",[2] we're just getting "(HG)".[3] Can this be fixed?  —SMALLJIM  11:27, 15 February 2016 (UTC)

Strange. Don't know what happened. Restored last know good ([4]) and updated version ([5]). Will keep an eye on it. - DVdm (talk) 12:39, 15 February 2016 (UTC)

Looking good. Thanks!  —SMALLJIM  14:01, 15 February 2016 (UTC)

Hi, I'm on Huggle 3 QT-LX and getting the above-mentioned error. What should I do? Thanks, <<< SOME GADGET GEEK >>> (talk) 18:48, 18 March 2016 (UTC)

How do I create a huggle3.css page? I tried to look for information but I found nothing. Waiting for an answer. Thanks Boruto720 (talk) 19:43, 27 March 2016 (UTC)

Hello, you probably don't even need to create it, huggle will do that itself, if there is anywhere that you need to do it, can you please link me to that? It might be some obsolete documentations that needs to be fixed. Petrb (talk) 11:56, 2 April 2016 (UTC)

Title says it all Wishva de Silva (talk) 04:24, 4 April 2016 (UTC)

@Wishva de Silva: Got at least one other tool(or the "main" toolbar, which has the reverting, reporting, etc. options on it) still open? If so, right-mouseclick on one of those, click "Queue". AddWittyNameHere (talk) 04:48, 4 April 2016 (UTC)

I got the same problem as above with the token error on 3.1.11. I am trying to install version 3.1.20 with the fix, but it just hangs, even if I run it as administrator. Constant spinner and no way to stop it. Going to have to reboot now. BollyJeff | talk 23:44, 16 March 2016 (UTC)

Nothing improved after rebooting (except the spinning stopped). To make things even more interesting, I cannot uninstall Huggle either. Settings - System - App & features shows no icon, size as unavailable, and clicking uninstall produces another hang. Help please, BollyJeff | talk 01:10, 17 March 2016 (UTC)

Huggle is built and tested on Windows 10 so the version definitely is no problem. There is nothing within huggle installer that would cause this other than VC-redist package from microsoft. Maybe try installing that one by hand? Petrb (talk) 15:16, 27 March 2016 (UTC)

You can also install mingw package on some other system that isn't broken and copy the directory, mingw version in fact doesn't need install, it basically just unpack the files to a folder. Petrb (talk) 15:18, 27 March 2016 (UTC)

I appreciate the feedback, but don't really understand your responses. What are VC-redist and mingw packages and where can they be found? What do you mean install on another system? I only have one computer, that's the one that I need fixed. BollyJeff | talk 21:10, 27 March 2016 (UTC)

Try this zip https://github.com/huggle/huggle3-qt-lx/releases/download/3.1.20/huggle_3.1.20_mingw32_il.zip just unzip it anywhere you like and run huggle.exe which is inside. Petrb (talk) 11:51, 2 April 2016 (UTC)

Hey @Petrb: I unzipped it on C:, opened up the resulting huggle_3.1.20_mingw32_il folder and double clicked huggle.exe. The result is an endless spinner over File Explorer until I close it. Task Manager does not show any apps running. I really liked this program and made hundreds of edits with it, but it seems my time is up unless you have another suggestion. BollyJeff | talk 00:41, 5 April 2016 (UTC)

Hello, try launching huggle.exe using the --syslog parameter. Here is a step-by-step if you need it :) first, please extract the huggle zip from above onto your desktop. Now open cmd (click the Search Windows button, type "Command Prompt", it should be there as a desktop app). Now in the new black cmd window, type "cd Desktop" and press enter. Now type "cd huggle_3.1.20_mingw32_il" (or whatever else if you renamed the folder in the zip above), and press enter. Now type "huggle.exe --syslog" and press enter. If it gives the error "huggle.exe is not recognized as an internal or external command", then you are not in the proper folder; make sure huggle.exe is located in that huggle_3.1.20_mingw32_il folder! If it gives no error, check in the huggle folder in a few seconds for a file called "huggle.log". Now kindly upload that somewhere and link it here; this should give more information on why it does not work for you, and can hopefully give some help on that. Thanks! Harry- (talk) 11:46, 7 April 2016 (UTC)

@Harry-: It hung at the cmd prompt and did not generate any huggle.log file. BollyJeff | talk 01:18, 9 April 2016 (UTC)

There is really something wrong with your system. I bet it would work if you tried in virtual box. From what you say it doesn't even instantiate the process. Sounds like if there was some broken anti-virus program preventing the binary from loading. Petrb (talk) 19:23, 12 April 2016 (UTC)

How do you do that? My Avast Virus program says it is not a threat, but Windows Compatibility Troubleshooter says it is not compatible, but fails to be able to fix it. BollyJeff | talk 01:48, 13 April 2016 (UTC)

If the warned user removes the received warnings from their userpage, Huggle treats it as though they've never been warned before and thus starts anew, leaving first-level warnings rather than whichever level would be appropriate. Any chance Huggle can be made to take recent page history into account? AddWittyNameHere (talk) 22:00, 31 March 2016 (UTC)

Yep, I need to think of some efficient way of preserving it. Petrb (talk) 19:59, 12 April 2016 (UTC)

I've created a Maniphest for this issue. --Laber□^T 12:16, 23 April 2016 (UTC)

Please include the entire diff on a revert warning. Currently, only the last diff is added. This might be confusing to the editors. It has caused a problem for me with an admin here. The user added a unsourced content, but the last edit did not require sourcing. The admin warned me on WP:BITE. Also, see Warning templates below. Jim1138 (talk) 22:46, 30 April 2016 (UTC)

Warning templates seem to assume that the all warnings given to a user are of the same category. The higher level warnings exclude information of previous levels. Example:

Hello, I'm Jim1138. I noticed that you made a change to an article, but you didn't provide a reliable source. It's been removed and archived in the page history for now, but if you'd like to include a citation and re-add it, please do so! If you need guidance on referencing, please see the referencing for beginners tutorial, or if you think I made a mistake, you can leave me a message on my talk page. Thank you.

You may be blocked from editing without further warning the next time you add unsourced material to Wikipedia.

This can cause problems if the previous warnings are of a different category. For instance: if a user is warned twice for removal of a speedy deletion template, then is warned for unsourced content, the user is, IMO, not given sufficient information for them to correct their problem. i.e. WP:RS, WP:V are lacking and WP:CITE is rather disguised. Perhaps a link to a page on how to avoid/resolve the problem would allow more information to be added? Jim1138 (talk) 22:46, 30 April 2016 (UTC)

This should probably be discussed on a different level, you basically want to change the way how users are notified about vandalism, it always was like this, people didn't get different levels for different vandalism. If you did vandalism, you received level 1, if you did another vandalism, even if of different kind, you received level 2. If it's not vandalism, then you shouldn't use templates. Otherwise I don't see how it should be, the templates could be changed so that they can be used for all sort of vandalism I guess? Petrb (talk) 19:54, 8 May 2016 (UTC)

Hi, Petrb, I'm having an issue with the user-defined filter I use 99% of the time. It's basically a mainspace-only filter. I don't think it's a configuration issue on my end as I've used it for quite some time and haven't had an issue up till now. When I select it, the "Processes" pane clearly shows that the software is working but no edits are displayed in the Queue. If I select a different filter, the software works normally. By the way, I'm running 3.1.20 on OSX. Any assistance would be appreciated. --Non-Dropframe _talk 17:35, 17 April 2016 (UTC)

Hi, fixed here https://github.com/huggle/huggle3-qt-lx/commit/70be6684500076718eb0ae665196aa19e18b4946 will be in next huggle. Petrb (talk) 20:04, 8 May 2016 (UTC)

What is the function or purpose of the Users subpage? It contains many editors who do not have rollback rights, have never used Huggle, indeed some who have made hardly any edits at all. It started off alphabetic but new users are now added in time order to the bottom of the list. Should the updating of the page be reviewed, or should it be deleted as non-functional and misleading?: Noyster (talk), 10:30, 17 April 2016 (UTC)

There is description in header of page explaining what it is for. Which users are there that never used huggle? When you check the history of page, you will see that nearly everyone was added by huggle itself. Petrb (talk) 10:42, 17 April 2016 (UTC)

Thanks for replying Petrb. The only statement I can see about the purpose of this list is "provided for convenience", but it doesn't seem very convenient to have a list containing users and non-users mixed in no consistent order. If you go to the bottom of the list where the most recent additions are, entries with no rollback right and no use of Huggle include: AlvaroMolina (7 edits), KurodaSho, Recollected, fluff, and so on: Noyster (talk), 11:31, 17 April 2016 (UTC)

Hey, just took a quick look at it, and it's a bug. Offending lines 619 to 634. Because in the Wikipedia project config, approval=false, so line 619 continues. And then because userlistsync=true, it syncs the user to the list, regardless of other config settings. Yes, Huggle then won't run still, and will give error saying lack of rollback, but it still syncs the user. This bug needs to be fixed (perhaps run userlistsync after the main GUI starts, meaning everything else checked out?), and then the list should be ideally wiped. :) Harry- (talk) 12:04, 18 April 2016 (UTC)

Wow I am surprised that someone is able to navigate through that garbage which whole login.cpp is :P Petrb (talk) 20:07, 8 May 2016 (UTC)

https://github.com/huggle/huggle3-qt-lx/commit/264de251092312db4e8f81b805ed446147e1839e Petrb (talk) 20:17, 8 May 2016 (UTC)

It seems to me that currently, this word does not increase the "suspiciousness" of an edit. Could you add it to the relevant list? --Laber□^T 06:20, 20 April 2016 (UTC)

Hi, I don't see it in any list? If it doesn't increase the score, why should it be in any list? Petrb (talk) 19:51, 8 May 2016 (UTC)

I mean that it should increase the score, and added to the list of words that do so. --Laber□^T 21:43, 8 May 2016 (UTC)

This list is located here: https://en.wikipedia.org/wiki/Wikipedia:Huggle/Config but I fail to see how "Shemale" is problematic in any way, I've seen words like "gay" or "nigga" being misused for vandalism, but I have never seen shemale being used in vandalism. Did you? Petrb (talk) 21:54, 8 May 2016 (UTC)

Yes I had, this is why I started this section. --Laber□^T 22:29, 8 May 2016 (UTC)

It seems that Huggle can't save proxy settings, so I have to enter proxy settings every time I use Huggle. I hope that Huggle can save such settings in future versions.--Techyan (talk) 14:07, 8 April 2016 (UTC)

Will be in next version, I am happy it even works, I never had a chance to verify proxy form that I have implemented :), you are probably first user who gave any feedback to it. Petrb (talk) 19:26, 12 April 2016 (UTC)

This beta version fixes it http://petr.insw.cz/huggle/huggle_3.1.21_x64.exe Petrb (talk) 20:40, 9 May 2016 (UTC)

Recently I've been trying to change my Huggle options (under system -> options) so that I don't automatically welcome users after a good edit, as well as to update some other options. However, whenever I do this, the change doesn't seem to effect Huggle and continues to welcome users by default. When I relaunch the program and look at the options menu, it's the same as before I changed it. Is there something I'm doing wrong? Omni Flames ^{let's talk about it} 09:16, 12 May 2016 (UTC)

Hi, I can't reproduce it, when I change the option it is updated in my config https://en.wikipedia.org/w/index.php?title=User:Petrb/huggle3.css&diff=720263444&oldid=719305628 and it is loaded the next time I start huggle. Petrb (talk) 19:31, 14 May 2016 (UTC)

Hi, I don't know if it's a Bug, but since Version 3.17 (I think) some Users in the german Wiki (me included) can't use the Queue Filters anymore. Maybe it's an error in the configuration, but every time I select the Filter no edits will displayed in the Queue. In the german Wiki we discussed it here and here. Any suggestions? Thanks…--Spuk968 (talk) 12:22, 3 April 2016 (UTC)

Yes this is a bug, I will try to fix it but I recommending making a phab task :) thanks! Petrb (talk) 19:58, 12 April 2016 (UTC)

This beta version fixes it http://petr.insw.cz/huggle/huggle_3.1.21_x64.exe Petrb (talk) 20:40, 9 May 2016 (UTC)

Thank you for fixing the bug. I am testing this versions now, so far it seems to be working. Again, thank you very much…--Spuk968 (talk) 12:41, 15 May 2016 (UTC)

Here's a fun question: will Huggle work on an iPad? This a new iPad Pro, with plenty of storage. But I don't seem to be able to down load the latest version of Huggle. Advice? Thanks. Jusdafax 21:38, 18 May 2016 (UTC)

As of right now, Huggle is not compiled into a native iOS app, only an OSX app. I'm not sure if it's possible, but it would be something interesting to look into. ~ Matthewrbowker ^{Drop me a note} 22:05, 18 May 2016 (UTC)

Ok, question answered, thanks, and I hope progress can be made for iOS. In my view, the future is mobile! Standing by. Jusdafax 00:33, 19 May 2016 (UTC)

It's technically possible, Qt can target iOS as well as Android, the only problem right now is, that Android Qt port doesn't support WebKit which is used to render web pages, and regarding iOS, the problem is that it's too much proprietary. I don't have iPad and even if I had, I would need an extra Mac just so that I can compile the app for iPad. Future is in open source ;) Petrb (talk) 16:07, 21 May 2016 (UTC)

What permissions is needed to use Huggle on meta: ? — xaosflux ^Talk 04:12, 31 May 2016 (UTC)

The permission is called "overlord of huggle". It's not configured there yet, so it can't be used. Petrb (talk) 19:34, 31 May 2016 (UTC)

Huggle can't open on my computer. It runs a Windows 8 software programme.—Oluwa2Chainz »» (talk to me) 16:02, 27 May 2016 (UTC)

Can you be more specific? Do you get some error message or what's the problem? Petrb (talk) 20:31, 31 May 2016 (UTC)

Hi, I realized every time I revert with a warning (Q) the warning level counter is not updating, so I end up sending the same warning over and over again and need to manually edit the user discussion page. Does anyone else have the same issue, or have some idea what might be the problem? The settings are correctly adjusted to increase the warning level automathically. Regards --RedTony (⇨ ✉) 06:24, 31 May 2016 (UTC)

Hi, on english wikipedia? Is that a normal warning? Petrb (talk) 19:36, 31 May 2016 (UTC)

Works? https://en.wikipedia.org/w/index.php?diff=723070785 Petrb (talk) 20:32, 31 May 2016 (UTC)

The reason is simple. Here's my very bad attempt at a rage comic explaining what happens to me occasionally. :-) ~Oshwah~^{(talk) (contribs)} 02:23, 31 May 2016 (UTC)

Do you realize you can make a keyboard shortcut for it? I just press Ctrl+T and it's reverted as editing tests... Petrb (talk) 20:26, 31 May 2016 (UTC)

Shortcuts -> main-revert-and-warn-4 Petrb (talk) 20:27, 31 May 2016 (UTC)

OHHH!!! So that's what that means!!! ~Oshwah~^{(talk) (contribs)} 01:06, 2 June 2016 (UTC)

Petrb - I have a question. Say I want to add a shortcut for "Failing to provide a reliable source", which is number 13 on the drop-down menu. The interface doesn't let me add it, and adding it to my huggle3.css file as main-revert-and-warn-13;<shortcut>, isn't doing it. How do I bind the shortcut key? ~Oshwah~^{(talk) (contribs)} 03:41, 2 June 2016 (UTC)

That's because the shortcut handler is *****. I made it even bigger one. https://github.com/huggle/huggle3-qt-lx/commit/ae605bb3dac03f7bddbe51439ceea7543851c67e Petrb (talk) 16:30, 2 June 2016 (UTC)

Since a few months, upon opening Huggle 2 (yes, my "private" version 2.1.27.7 ), I get "Unable to connect to IRC recent changes feed. Using slower API queries instead". Not only is it slower, it also misses a lot of edits. Any advice or tip, other than switching to Huggle 3? - DVdm (talk) 10:23, 4 June 2016 (UTC)

Try to run huggle in debugger and put breakpoints on code that raises this error in order to debug what is causing it. My guess it that either the name of IRC server changed, or something prevents you from connecting to it. Petrb (talk) 10:38, 4 June 2016 (UTC)

Ok, will try later. Thx. - DVdm (talk) 11:02, 4 June 2016 (UTC)

Nok. Tried and got no useful information of what goes wrong. But Huggle 2 uses nickname h_nnnnnn (nnnnnn being 6 random digits) with channel #en.wikipedia. I can manually connect with these params at https://webchat.freenode.net/?channels=#en.wikipedia provided I can convince them that I'm no robot, which of course I cannot do with Huggle. When did they implement this captcha? And is there no way to bypass this? - DVdm (talk) 11:43, 4 June 2016 (UTC)

But that's probably not what's going wrong, as Huggle is not connecting through webchat.freenode.net. - DVdm (talk) 11:57, 4 June 2016 (UTC)

The IRC recent changes feeds are not located on freenode, they are on irc.wikimedia.org. —k6ka 🍁 (Talk · Contributions) 12:40, 4 June 2016 (UTC)

Yes, I had found that in the debug session:

config.IrcServer = "irc.wikimedia.org"
config.IrcServerName = "irc.pmtpa.wikimedia.org"

Then 3 lines are written to the stream:

USER h_nnnnnn 8 * :h_nnnnnn
NICK h_nnnnnn
JOIN #en.wikipedia

For some unknown reason it doesn't work anymore in Huggle 2. - DVdm (talk) 13:08, 4 June 2016 (UTC)

You need to put it here https://github.com/huggle/huggle/blob/master/Irc.vb#L134 then check what is content of Message, that will be line by line output from IRC server, which is what you are interested in. Petrb (talk) 16:06, 4 June 2016 (UTC)

Yes, the inner while loop is worked without any problem, no errors, nothng. At a certain point Private Sub IrcTimer_Tick(ByVal O As Object) is triggered which fires IrcLog(Msg("irc-error")), sets Connecting = False, and Private Sub IrcProcess() dies in its corner, leaving no Message to check. I can't debug this. - DVdm (talk) 20:35, 4 June 2016 (UTC)

Lately being logging into the program, I get the error that api.php responds with unknown results, this is somewhat cumbersome when I try to login, I use Wikipedia in Spanish much this program to reverse vandal and I had to close and open the program a lot of times to work me. I hope that in a future update to correct this problem. Thank you.
Alvaro Molina (Let's Talk) 15:08, 14 May 2016 (UTC)

Hi, which version of Huggle is that? Petrb (talk) 19:33, 14 May 2016 (UTC)

It is the version 3.1.20. Thanks. --Alvaro Molina (Let's Talk) 21:38, 17 May 2016 (UTC)

I'm still getting a WrongToken error. Should I reinstall the program? <<< SOME GADGET GEEK >>> (talk) 13:12, 18 May 2016 (UTC)

I will try to reproduce this, so version 3.1.20 and which target wiki? Petrb (talk) 16:02, 21 May 2016 (UTC)

Any - I've tried enwiki but I don't have rollback so that's understandable. I've also tried simplewiki and that didn't work either which is surprising cause I have made reverts on simplewiki with Huggle; there's no requirement like on enwiki. Even testwiki fails. It worked before. <<< SOME GADGET GEEK >>> (talk) 14:12, 22 May 2016 (UTC)

Fails how? Petrb (talk) 16:59, 1 June 2016 (UTC)

https://www.mediawiki.org/wiki/Manual:Huggle/Debugging Petrb (talk) 17:08, 1 June 2016 (UTC)

The update to version 3.1.21, the problems have been solved. Thanks. --Alvaro Molina (Let's Talk) 04:29, 5 June 2016 (UTC)

What is the revert description parameter name for huggle3.css? I have the default-summary in the config, but that does not work for reverts. Well, it does put the description of the revert, but keeps mixing its $2 and $1 paremeters, making them equal. And it looks really silly when i "revert John Does's edits to John Doe's revision" in description. Manslay (talk) 17:00, 7 June 2016 (UTC)

OK, nevermind, just edited the localpedia Huggle config. Manslay (talk) 17:40, 7 June 2016 (UTC)

Hello. Why whitelist for Ukrainian Wikipedia empty? [6] --Максим Підліснюк (talk) 22:54, 12 June 2016 (UTC)

I might have mentioned this before:

If this could somehow be fixed, perhaps I would start using Huggle 3 and even forget about good old Huggle 2. Please please please... - DVdm (talk) 09:30, 5 July 2016 (UTC)

I've noticed two of my rollbacks did not occur today (they appear on the queue but as soon as I move on to the next review, they disappear), even though welcome messages are being sent out normally. Is this isolated? Best, FoCuS contribs; talk to me! 18:17, 20 July 2016 (UTC)

I am using Huggle 3 QT-LX ,64 bit version . When I try to login , this message appears:

ERROR: api.php responded with unknown result: Failed Razer^{Text me} 07:35, 13 September 2016 (UTC)

Sorry for getting so late to you, running huggle with option --qd would produce a log file that contains a traffic exchange between mediawiki, maybe the reason would be more obvious from there. Please see https://www.mediawiki.org/wiki/Manual:Huggle/Debugging for more information. Also, which vesion of huggle is that? Petrb (talk) 17:29, 16 October 2016 (UTC)

When a vandal has removed the warnings from his talkpage, Huggle is fooled into delivering a level one warning instead of a warning at the next level or AIV report, as appropriate. I would appreciate any assistance available in fixing this error. DavidLeighEllis (talk) 23:07, 18 August 2016 (UTC)

Yes this issue is tracked - T133331 Petrb (talk) 17:30, 16 October 2016 (UTC)

When reverting a page creator's edit, please add another option to the dialog box "This edit was made by a person who created this page, do you want to request a speedy deletion instead" Please add a "Do nothing" button? Sometimes I get this dialog and then realize I should leave it alone. So, I need to undo my edit and remove my warning. Thanks Jim1138 (talk) 19:47, 15 August 2016 (UTC)

Added as https://phabricator.wikimedia.org/T148334 Petrb (talk) 17:31, 16 October 2016 (UTC)

 New proposal , can we make it so speedy notifications with huggle give section headings automatically, i've noticed with the attack CSD tag with huggle sections aren't created automatically, I haven't look to see about the others. This should be fixed/added asap please! --Ⓩⓟⓟⓘⓧ (talk) 22:07, 23 September 2016 (UTC)

Can you give me some example link of what is wrong and how it should look? You say that some headings are missing? When a message is sent to user? Petrb (talk) 17:36, 16 October 2016 (UTC)

Yesterday I installed the "regular" version v3.1.21 for 64 bit Windows, to replace the sort-of portable huggle_3.1.2x_mingw32.exe version that I had running before, and of which I was never really satisfied because of hangs, crashes, misses, and whatevers. I must say that finally I have a Huggle 3 that works properly, provided of course the queue setting When queue is full, remove old edits is enabled. So I've been using it now during some long sessions, and I must say.... yes, it's becoming a valid replacement for (that phenomenal) Huggle 2 . Thanks, developers! - DVdm (talk) 19:39, 13 October 2016 (UTC)

Hi, yes it's true that mingw32 doesn't perform very well, it's built using GNU GCC compiler, which isn't a best option for modern Windows these days. The reason why that package exists are people with Windows XP or older and people who don't have administrator rights to install SW on computer, because unlike "normal" version, it doesn't require MSVC redistributables package, which require admin rights for installation. The binaries produced with mingw seem to use far more operation memory and CPU in order to do a same job. Petrb (talk) 17:42, 16 October 2016 (UTC)

It seems very slow to revert an edit. I will sometimes be several pages ahead before I get a notice that there are new edits. This has become enough of a problem that I restored 3.1.21

The "View in external browser" on 3.1.22 did not go to the default browser. It also changed the browser 3.1.21 opens Jim1138 (talk) 10:21, 20 October 2016 (UTC)

Hmm, that sounds weird, you say different browser is opened with each version of huggle? I don't even recall we changed the code responsible for opening. Regarding reverts, that is also weird, do you have instant reverts enabled in preferences? On other hand if you didn't they would be probably slow in .21 as well Petrb (talk) 11:13, 20 October 2016 (UTC)

Hi,

Just wanted to post is here as well, Huggle 3.2.0 is coming, now with Blink (Chromium) backend instead of WebKit: https://lists.wikimedia.org/pipermail/huggle/2016-October/000159.html Petrb (talk) 23:46, 20 October 2016 (UTC)

After upgrade Ubuntu 14.04 to 16.04, my Huggle cannot install, see below

LANG=C sudo apt-get install huggle Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package huggle

How to fix this problem of ppa? Vitor Mazuco ^Talk! 14:24, 20 September 2016 (UTC)

I will add it to PPA, for now you have to compile it yoursef, it's not that hard, basically it's just:

sudo apt-get install qt4-dev cmake build-essential git
cd ~/Downloads
git clone https://github.com/huggle/huggle3-qt-lx
cd huggle3-qt-lx
git submodule init
git submodule update
cd huggle
./configure --qt4 --extension
cd huggle_release
make
./huggle

Petrb (talk) 17:35, 16 October 2016 (UTC)

If you are still having troubles you can also try this snap: https://petr.insw.cz/huggle_3.2.0_amd64.snap

Once you download it just run: sudo snap install --force-dangerous huggle_3.2.0_amd64.snap Petrb (talk) 23:57, 22 October 2016 (UTC)

Would someone mind explaining what the difference is between using my regular Wikipedia login and using Special:BotPasswords is? — Gestrid (talk) 02:38, 25 October 2016 (UTC)

mw:Manual:Bot_passwords has a write up on it - if you are creating a new bot you should use OAuth instead these days for the most part. BIGGEST difference - you can only use the API when logging in with botpasswords. — xaosflux ^Talk 03:03, 25 October 2016 (UTC)

@Xaosflux: So I should only use the "Bot Password" functionality if I actually created a bot? (Also, Huggle 3.1.22 seems to have dropped support for OAuth.) 208.95.51.43 (talk) 03:13, 25 October 2016 (UTC)

For the most part unless you really know what you are doing and why - don't use BotPasswords, someone from the huggle group here can talk to the OAuth support. — xaosflux ^Talk 03:15, 25 October 2016 (UTC)

I know the OAuth form was present in 3.1.21, but the capability wasn't implemented. Also, I'd forgotten to login before putting up that last comment. — Gestrid (talk) 03:18, 25 October 2016 (UTC)

Also, I found the difference between bot passwords and normal logins, as far as Huggle is concerned: mw:Manual:Huggle/Bot passwords. — Gestrid (talk) 03:37, 25 October 2016 (UTC)

Hello, it's explained on welcome dialog that you likely skipped without reading, it's literally first thing explained when you open huggle. Also there is this link to explanation page right under the dialog. So now about "bot passwords" and why they exists and why we use them and not OAuth. First of all the name is really stupid, they aren't really "bot passwords" they are application passwords that were aliased to bot passwords because someone thought that are primarily going to be used by bots. There is no reason not to use them by anything else and it's a preferred and recommended way to login to Huggle. So yes, if you want to use them, then please do. The reason why they are more secure than providing your regular password is that in case it somehow was leaked or stolen, it's giving the attacker much less options to do something wrong. Also, they can't steal your account, they won't be able to change the real password. Another reason is that standard legacy login is deprecated now and may be removed from future MW versions with no warning. Why we don't use OAuth? Because it's a horrible authentication technology when it comes to real applications compared to web-based applications. It's basically an authentication mechanism for websites that are running on 3rd server, not for something that is executed locally on your computer. The whole thing was built with web-browser login on web pages in mind from beginning and never was designed to be used by applications running directly on your PC. So it's a very bad login method which for obvious reasons was dropped from the road map and replaced with bot passwords as soon as I figured out they were implemented to MW. I really wish they were just renamed to application password which makes it much more clear what they are for. Petrb (talk) 18:46, 25 October 2016 (UTC)

I did read the welcome message, but it didn't really help me understand if I should use a bot password or if it was just for bots to use. Thanks for answering. — Gestrid (talk) 19:45, 25 October 2016 (UTC)

Hello! I recently opened huggle and now I'm getting an error "ERROR: api.php responded with unknown result: Aborted" any ideas on whats going on? I'm on a mac OS X 10.9.5 build 13F1808 ----Cameron₁₁₅₉₈ ^(Talk) 16:08, 27 October 2016 (UTC)

Resolved --Cameron₁₁₅₉₈ ^(Talk) 06:41, 28 October 2016 (UTC)

Two problems I've noticed:
I recently used the "report a username violation" ( at the top under User -> Report username) feature in Huggle for the first time. When I clicked "Report user" after finishing filling everything in and checking if they had already been reported, I clicked "Report user" and... nothing. The username was reported successfully, but the dialog box didn't close or give a "Report successful!" type of message. Instead, it just sat there, except the "Report user" button had grayed out. I feel it should do something. Otherwise, we're left wondering if Huggle actually did anything unless we check our user contributions at Special:Contributions to see if the report is there.
Also, when I went to check how it looked at UAA, I noticed a minor typo in the report. See this revision at the bottom for my report. I'd checked the "promotional username" box in the report and then filled in the custom reason with why it was promotional (the part about the draft). There should be space between the two reasons on the page, but there isn't.
I realize these two things are nowhere near important enough to fix right away, but I would still like them fixed.
— Gestrid (talk) 01:43, 2 November 2016 (UTC)

Hello,

Is anyone able to compile and post the newest macOS package? I'm not sure how to do that and I notice it isn't posted for download.

-- Dane2007 ^talk 01:36, 3 November 2016 (UTC)

 Done I have compiled this. Not sure how it gets posted. -- Dane2007 ^talk 04:46, 4 November 2016 (UTC)

Seems they forgot to post it. Perhaps Petrb could help. They seem pretty active here. — Gestrid (talk) 05:27, 4 November 2016 (UTC)

Thanks Gestrid! It took me like 3 hours to get compiled and I just realized the version number is ahead of the current release...showing 3.2. Not sure what I did to achieve that. -- Dane2007 ^talk 05:41, 4 November 2016 (UTC)

It's possible you accidentally compiled a beta version of Huggle, Dane2007. I'd suggest going back to your previous version of Huggle until someone resolves this issue. Nobody (especially you) wants a beta version of Huggle running rampant on English Wikipedia doing who-knows-what when it's not supposed to. Or, if you haven't already, try compiling Huggle using this method. — Gestrid (talk) 05:50, 4 November 2016 (UTC)

@Gestrid: Yeah, that is the method I used to compile. I will run it again tomorrow and see if I get a different result, not quite sure how I got a beta version or whatever the heck I compiled today. I did use it a bit and nothing was broken but I probably won't touch it again until theres some feedback on whats up just to be safe. -- Dane2007 ^talk 05:52, 4 November 2016 (UTC)

Yeah, you don't want to be banned from using Huggle because of this. Like WP:HG says, You take full responsibility for any action you perform using Huggle. — Gestrid (talk) 06:05, 4 November 2016 (UTC)

Indeed. I remember that warning haha. Just downloaded the source manually instead of through the brew method. Compiled up to version 3.1.22 but for some reason it's giving errors about the package script. Such a mystery. -- Dane2007 ^talk 06:24, 4 November 2016 (UTC)

Hi, I will try to bring some light into this. I can't compile MacOS packages atm because my Mac died. As of now @Matthewrbowker: is in charge of that. I guess he was too busy until now. Now regarding why you see huggle 3.2.0 in your version: you probably checked out master branch, instead of last stable. That will indeed give you development version of Huggle. On other hand you don't really need to be scared, the chances it break something are minimal, there isn't so many changes compared to previous version other than that 3.2.0 has completely rewritten web-browser backend component, reasons for that were posted in https://lists.wikimedia.org/pipermail/huggle/2016-October/000159.html if you wanted to run stable version though, you can do that by executing "git checkout 3.1.22" in terminal after you clone the repository. If you do this in repository that you already used to compile huggle, you will probably need to cleanup couple of files, especially whole folder huggle_release needs to be nuked prior re-packaging. Petrb (talk) 16:00, 4 November 2016 (UTC)

If you can't compile stable version it's maybe directly related to the web browser backend. As I posted in e-mail Qt dropped support for WebKit, so you will be unable to compile Huggle (older than 3.2) with Qt newer than 5.4. Which you probably have, and that's why new Huggle compiles and old doesn't. Petrb (talk) 16:05, 4 November 2016 (UTC)

@Petrb: Actually, I have been working on getting a macOS version out. Since I am using MacOS Sierra, I'm having some trouble with the compile script. Rest assured I'm still working on it. ~ Matthewrbowker ^{Drop me a note} 19:19, 4 November 2016 (UTC)

@Matthewrbowker and Petrb: Thank you for shedding some light on this. I am on macOS Sierra as well which is probably part of why I see the weirdness with attempting to package 3.1.22. Glad it's being worked on still though! -- Dane2007 ^talk 01:35, 5 November 2016 (UTC)

Could this post be updated to include the problem with using Mac? — Gestrid (talk) 01:38, 5 November 2016 (UTC)

Is it like a list of editors who have been blocked? --NikolaiHo^☎️ 06:16, 6 November 2016 (UTC)

@Nikolaiho: No, a whitelist is a list of trusted users. —k6ka 🍁 (Talk · Contributions) 12:45, 14 November 2016 (UTC)

Could someone explain what this is and why it happens? -- Rrburke (talk) 15:00, 21 November 2016 (UTC)

Due to a wave of accounts recently being compromised, many admins have enabled two-factor authentication on their accounts. This apparently means we cannot login into tools like Huggle and STiki. My guess is logging in via OAuth would work, but it appears that is not yet supported. I have an alternate account to use but it would be great to be able to use Huggle with my primary. Thanks for all the awesome work :) — MusikAnimal ^talk 20:09, 15 November 2016 (UTC)

@MusikAnimal: Try using bot passwords to log in. —k6ka 🍁 (Talk · Contributions) 23:18, 15 November 2016 (UTC)

That does it! Thank you! :D — MusikAnimal ^talk 23:52, 15 November 2016 (UTC)

@MusikAnimal and K6ka: I, like MusikAnimal, enabled 2FA on my main account, and now I find myself unable to login to tools. I took a look at the bot passwords page, but unfortunately the instructions there are not so clear to those of us not software adept, such as myself. Could either of you help me out? Also, do you know if the same system can be used for WP:STiki? Cheers, Vanamonde (talk) 03:29, 2 December 2016 (UTC)

@Vanamonde93: mw:Manual:Huggle/Bot passwords — MusikAnimal ^talk 16:43, 2 December 2016 (UTC)

• See Wikipedia:Using_AWB_with_2FA for setting up bot password. Biggest note - don't share that long password with anyone - and for Huggle, you will need to grant your bot password the ability to use your rollback access. — xaosflux ^Talk 04:25, 2 December 2016 (UTC)

• @Xaosflux: thank you, that was helpful. @MusikAnimal: I'd seen that page, but that comes closer to answering the why rather than the how of bot passwords. Cheers, Vanamonde (talk) 17:12, 2 December 2016 (UTC)

Good evening, I've downloaded Huggle, and I find it very handy.

But I messed up and accidentally deleted the queue "section". Could you help me getting it back (as well as all other sections that I also deleted (⌣_⌣”) )?

Thank you in advance !

PS: Sorry for bad English, It is not my mother tongue... Pititnatole (talk) 20:51, 14 December 2016 (UTC)

Right click anywhere in the darker gray title area of some section that you still see (Tools, System logs, Editbar, History, User info, History of your changes, System logs, ...), and you'll be able to select the Queue section again. - DVdm (talk) 21:20, 14 December 2016 (UTC)

Thank you very much! Pititnatole (talk) 17:02, 15 December 2016 (UTC)

How does ORES score work? Is the higher the score, the more likely the edit is to be bad? Thanks. NikolaiHo^☎️ 06:02, 26 November 2016 (UTC)

Hi, yes, that's exactly how it works. Petrb (talk) 00:31, 15 January 2017 (UTC)

I would like to have the option to have a sound played every time a new "item" gets added to the queue. I also would like the warnings/block messages written on users talk pages to have my signature automatically added at the end. //Skottniss (talk) 21:37, 10 December 2016 (UTC)

Nice idea! T155332 Petrb (talk) 00:35, 15 January 2017 (UTC)

I want to exclude edits with the tag "Mobile edit", but when I enter this into "Ignored tags" for my user-defined queue filter, it strips out the whitespace and saves as "Mobileedit".

Also, it'd be nice to filter out registered users so I only see anon edits. Many thanks! — MusikAnimal ^talk 04:17, 3 January 2017 (UTC)

Hi, thanks for reporting this T155334 and T155333 just created... Petrb (talk) 00:39, 15 January 2017 (UTC)

I occationally notice that Huggle adds a warning at the wrong level such as here. It added a level 2 just after a level 3 was added. Is there a way to fix this, please? Thank you Jim1138 (talk) 14:09, 29 November 2016 (UTC)

Hi this is a known problem possibly caused by warning parser, I will have a look why this happened, probably a simple update in project config might fix that. Petrb (talk) 00:41, 15 January 2017 (UTC)

Hey--quick question. If you use Huggle and revert something you consider vandalism, is there no edit summary marking it as such? See this conversation, User_talk:Marianna251#January_2017, and this automated edit summary. I'm chatting about this with Marianna251. Thanks, Drmies (talk) 19:01, 20 January 2017 (UTC)

Following on from this, is there a way to add "Reverting vandalism" (or "Rv"/"Rvv", if you want to avoid using vandal/vandalism) to the default Huggle edit summary after rolling back vandalism? Drmies has made some good points showing that it would be useful for admins looking at blocking requests further down the line. Marianna251TALK 20:01, 20 January 2017 (UTC)

@Drmies and Marianna251: By default Huggle leaves a generic edit summary, much like rollback does. Twinkle's "rollback (VANDAL)" option does the same as well. Reverting an edit without leaving an edit summary implies that the edit being reverted is vandalism, or when the reason for reverting is obvious and very clear. Huggle's default edit summary has always been like this, even since the days of Huggle 2 (Which I used extensively). I don't quite see the need of forcing patrollers to revert edits with undo or Twinkle's standard rollback to leave a quick "Vandalism" edit summary when MediaWiki rollback suffices in such circumstances (I don't think I'd appreciate seeing a templated warning for using rollback; what's the point of rollback, then?).

To answer your questions, there is an option to declare a reverted edit as vandalism by clicking on the drop-down menu and selecting "Vandalism", which leaves an edit summary of "Nonconstructive editing". It works, and it leaves the same warning message as the standard revert option does, but it is not accessible by keyboard shortcuts and requires two extra clicks to basically do the same thing as pressing "Q" or clicking the big revert & warn button does. —k6ka 🍁 (Talk · Contributions) 21:59, 20 January 2017 (UTC)

@K6ka: Thanks for the info! I didn't realise that the dropdown option differed from the keyboard shortcut. I'll keep that in mind for the future. Marianna251TALK 22:24, 20 January 2017 (UTC)

@K6ka:, thank you for your help. However, yes edit summary. You may not see the need, but I do, and as an administrator I am expected to act on the reports that patrolers make. If you don't make it explicit that you are reverting vandalism, or if it needs to be explained how something is vandalism when that's not obvious, then you are not succeeding in your mission. I really don't see why this is so difficult. Please do not presume that a. all other editors and admins see vandalism and whatnot the exact way you do and b. administrators are there at your beck and call and don't require the courtesy of an explanation. Finally, edit summaries are good practice. If you can't be bothered to explain why you made a certain edit, don't be surprised if you are reverted with the summary "rv unexplained revert". This is not a competition, there is no prize for highest number of reverts per minute. Thank you. Drmies (talk) 00:07, 21 January 2017 (UTC)

Hi, just to clarify one thing, it is certainly possible to create a shortcut for dropdown items as well, see preferences of Huggle. Edit summaries, including the default, vague, one can be changed at project config page: WP:HGC Petrb (talk) 18:25, 21 January 2017 (UTC)

Just to clarify - can individual users change their default edit summaries, or does it have to be done on a project-wide basis? (Not that it makes much difference to me overall, because I'm so out of my depth that I think I need an instruction manual to explain the instruction manual, but it would still be useful to know.) Marianna251TALK 20:26, 21 January 2017 (UTC)

I would like to say Special:MyPage/huggle3.css... but it would seem that Huggle doesn't follow the "default-summary" option there, which still lists the edit summary for Huggle 2. —k6ka 🍁 (Talk · Contributions) 03:00, 22 January 2017 (UTC)

That sounds like a bug then, https://phabricator.wikimedia.org/T155994 Petrb (talk) 11:21, 23 January 2017 (UTC)

The WMF Collaboration Team is looking into ways to improve Huggle. We've proposed a suite of new tools aimed mostly at helping reviewers get better information about edits in the queue.

There's a page on Mediawiki that describes the project's goals and proposed improvements. We want to hear from the Huggle community, so please check out the ideas presented and tell us what you think. (The best place to leave your thoughts is on the project talk page.)

We look forward to working with you! JMatazzoni (WMF) (talk) 01:17, 27 January 2017 (UTC)

@JMatazzoni (WMF): : Having read through the full proposal I cannot shake the feeling this proposal was written with the absolute best of intentions, but without full working knowledge of Huggle as a tool. To explain i'd like to highlight two main characteristics of Huggle:

• Huggle is realtime only: Huggle connects each editor to the recent changes feed and generates a local list of edits that have to be checked without prioritization beyond listing edits from previously reverted editors first.
• Huggle is for high-speed editing: On an average evening EnWiki had about 170 edits a minute with spikes to 220 and more edits a minute. By default Huggle filters whitelisted editors (long term editors, bots and so on) but there is still a very sizeable portion that has to be verified every minute. Huggle pre-caches all diffs before adding them to the queue so navigation between diffs is nearly instant. When reverting Huggle will handle the work in the background (Rollback + warn) while the user can review the next edit in the meantime.

Huggle as of such excels at a single job: It allows a user to single handedly monitor a wiki that is as large and busy as the English wikipedia. It is essentially a single queue that a user can navigate at high speed in order to cull any clear cut vandalism that got trough Cluebot NG or the edit filters. It is not well suited for slow patrol as it will not load old edits, and won't list any more edits if it reaches its queue capacity of 200 edits (Which on EnWiki is reached in minutes). Comparing this to the proposal as written I would conclude that the suggestions included wouldn't truly fit Huggles methodology of vandalism patrol - though I hasten to add I am but one user and other users may use Huggle in an entirely different fashion.

To explain: The proposal as written seems to focus on extending the Huggle interface so that it provides more contextual information about editors, chiefly based on the calculated ORES score / editor account age. Due to Huggle's nature i would personally find this information irrelevant: For me using Huggle equals looking at the displayed diff while using keyboard shortcuts to navigate the edit queue. I wouldn't take note of any added queue icons or the ORES score. The queue icons wouldn't be too useful as any edit in the queue would be reached in seconds: On average I spend about 2 seconds looking at a revision before concluding it is fine or clear-cut vandalism and moving to the next one. If an edit cannot be readily be identified as clear vandalism it shouldn't be dealt with trough Huggle in the first place. Using the same methodology i am not using the ORES score either: I am manually checking each edit so a machine evaluation is redundant.

The proposal as written would make a lot of sense in another vandalism patrol tool though: Stiki. While Huggle is real-time Stiki uses a server backend to log edits. Logged edits are forwarded for evaluation to editors who use Stiki. Since Stiki will happily serve weeks old edits it is much better suited to slow patrol and thus handling edits that may not be ideal yet aren't clear cases of malicious intent. I find that both tools complement each-other well: Huggle is perfect for first-line defence against clear cut vandalism while Stiki is better suited at dealing with the edge cases or cases where good faith editors may run into trouble. Since the goal of this project is new editor engagement i would argue that a slow patrol tool that doesn't have a time limit on its queue is the better option to implement this. Excirial ^{(Contact me,Contribs)} 22:58, 7 February 2017 (UTC)

@Excirial: Thanks so much for your feedback. It’s essential we hear from people like you so that we avoid just the type of missteps you’re describing.  I started a new thread on the project talk page to discuss a particular aspect of your remarks: Queue ordering and the value of icons. I'm eager to hear what you—and other Huggle users—think. JMatazzoni (WMF) (talk) 01:07, 9 February 2017 (UTC)

What is needed to implement Huggle on Wikispecies? Dan Koehl (talk) 02:42, 12 February 2017 (UTC)

I recently downloaded Huggle 3.1.21. It said I needed to run 10.11 or higher. So I went and downloaded 3.1.16. Then I got "ERROR: ap.php responded with unknown result: WrongToken" just like mentioned in the previous thread titled WrongToken. On that thread, they said to download 3.1.19, which I just did. Now when I try to login, I get this error: "Error: api.php responded with unknown result: Failed". What is wrong with me/my mac/Huggle3? Do I just need to leave off Huggle until I install Os X 10.11 or 10.12? It won't let me login to testwiki either.L3X1 My Complaint Desk 14:15, 16 February 2017 (UTC)

Hello, what happened when you tried to start huggle 3.1.21? I am afraid that older version of huggle no longer works with this version of MediaWiki, because MW breaks compatibility extremely often :( in case you can't start 3.1.21 you will have to compile it on your OS - https://github.com/huggle/huggle3-qt-lx/wiki/Building-on-MacOS Petrb (talk) 14:31, 16 February 2017 (UTC)

Hi, when I tried to launch 3.1.21 a notice popped up saying: You can’t use this version of the application “Huggle” with this version of OS X. You have OS X 10.10.5. The application requires OS X 10.11 or later. I will try my hand at compiling it. Thank you. L3X1 My Complaint Desk 16:02, 16 February 2017 (UTC)

Now that 2FA has been activated for users with admin rights, it's now not possible for admins to log into Huggle. Is there any chance Huggle will be updated soon to add support for users with 2FA enabled, possibly by switching fully to OAuth? —Tom Morris (talk) 14:17, 20 February 2017 (UTC)

Hi Tom, All plans to switch to OAuth were dropped since that technology is very useless for desktop applications, it adds extreme overhead of stuff that doesn't help security at all (server secret would have to be part of source code thus not being secret at all). We implemented application (bot) login though. It's called very inappropriately "bot login" (decision made by MW devs) but in fact it's application login and it should allow you to login just fine. Petrb (talk) 16:37, 20 February 2017 (UTC)

See https://www.mediawiki.org/wiki/Manual:Huggle/Bot_passwords for more info Petrb (talk) 16:38, 20 February 2017 (UTC)

@Tom Morris: see Wikipedia:Using AWB with 2FA for a walk through in doing this (it is the same for AWB and Huggle). — xaosflux ^Talk 00:33, 24 February 2017 (UTC)

There is a "huggle" virtual machine running on Wikimedia Labs with the Ubuntu Precise operating system. Ubuntu Precise is deprecated and any virtual machines running it on March 31 will be shut off and deleted. Andrew Bogott, who is the Wikimedia Foundation employee working on this transition, noted in his announcement email that no one has claimed ownership of the Huggle virtual machine. The relevant support ticket is here on Phabricator (you can log in with your Wikipedia credentials). Can someone reach out to them? Harej (talk) 17:56, 27 February 2017 (UTC)

I was doing some testing just now in Huggle and observed the function titled "Mass Actions", which contains options for mass reversion or deletion. I used an alternate account to make a couple of test edits in my userspace and then attempted to mass revert them, but the "revert" button is greyed out. The delete function, of course, failed to do anything since I am not an administrator. Is this mass revert function not yet available, or is it something that I have not configured properly? I can see myself using it in cases of vandalism-only accounts, where currently I load their contributions in the browser and then revert any others with Twinkle or standard rollback instead. Home Lander (talk) 20:32, 23 February 2017 (UTC)

Hi, indeed this is not yet finished, it's actually not a core function, it's an extension to huggle: https://github.com/huggle/extension-mass-delete and it still needs some work. Petrb (talk) 10:25, 28 February 2017 (UTC)

Thanks for replying. The function still sounds good, whenever it comes around. Home Lander (talk) 17:16, 1 March 2017 (UTC)

{{edit semi-protected|Wikipedia:Huggle|answered=yes}}

Can somebody add the Start date and age template from "{start date|2008}" to "{start date and age|2008}" to correspond to Huggle's official launch year? — Preceding unsigned comment added by 173.73.227.128 (talk) 03:39, 26 November 2016 (UTC)

Done — Train2104 (t • c) 15:16, 4 March 2017 (UTC)

I was huggling in eswiki when suddenly and edit from simplewiki appeared and i tried to revert it, giving this result. Any ideas?--Jcaraballo 18:09, 4 March 2017 (UTC)

Hello, that is really weird, I will investigate this in https://phabricator.wikimedia.org/T160626 Petrb (talk) 11:24, 16 March 2017 (UTC)

Seems not all functions implemented, please see my revert edit Dan Koehl (talk) 22:09, 19 March 2017 (UTC)

I authenticate using Huggle's legacy login, but cannot get in because of the following error: You do not have rollback permissions on this project. Do you really need rollback permissions? UpsandDowns1234 16:30, 27 March 2017 (UTC)

Yes. This is clearly documented at WP:Huggle. — JJMC89 (T·C) 16:48, 27 March 2017 (UTC)

Hello,
I am very well aware that one can not use Huggle without rollback. Is there any way to byapass this? I mean, can you guys do something kike they do with STiki?

I mean, if one does not have rollback right, they can request for STiki right, resulting that user can access STiki. It would be a great thing if you could do same thing with Huggle.

I think Huggle is the best option for my usecase, and I can do a lot of good contributions through Huggle. But unfortunately, my request for tollback was denied recently.

Would you please look into the suggestion that I provided? Thanks. —usernamekiran[talk] 20:51, 5 April 2017 (UTC)

@Usernamekiran: Software rollback is already a feature Huggle supports and this functionality is availible on multiple other language editions of Wikipedia. On EnWiki having rollback is mandatory for huggle usage though. This requirement was put in place after multiple incidents involving well-intentioned editors who unfortunately didn't fully understand what exactly constituted vandalism.

Reading through the rollback request it would appear to me you wouldn't truly need rollback or Huggle specifically. If you are merely interested in seeing an automatically updating list of recent changes one of these userscripts may work well enough for your needs. Excirial ^{(Contact me,Contribs)} 07:06, 6 April 2017 (UTC)

Actually this might be possible in the future version, we already implemented read-only mode into huggle 3.2.0, so maybe there could be a fallback - in case user is not eligible to use huggle on given project, they might be allowed to use it in read-only mode for purpose of watching the changes on projects Petrb (talk) 11:03, 6 April 2017 (UTC)

• @Excirial and Petrb: thanks for the reply Exciria. Your name sounds very familiar, did we interact before?

yes, I tried Lupin, Snuggle, and STiki. But they didn't fulfil my expectations/needs. Thanks a lot for the scripts, I am going to try two of them

But as Petrb said, giving access to read-only Hugghe would be great too. —usernamekiran[talk] 16:18, 6 April 2017 (UTC)

Hi beta testers!

If you wish to do testing of next version of huggle, you can download x64 version for windows here: http://petr.insw.cz/huggle/huggle_3.2.0_beta.exe this version has about 120 commits since last release, and major change is use of different web backend, while old huggle was WebKit based, new version is based on Chromium. This allows us to use newer version of Qt framework as WebKit was deprecated by Qt devs. Full list of changes can be found here https://github.com/huggle/huggle3-qt-lx/compare/3.1.22...3e12f6f053fcc0a8c147dc9a0d56d4a7e071e5cc Petrb (talk) 11:18, 4 April 2017 (UTC)

Hi Petrb,

I just attempted an upgrade to the 3.2.0 beta of Huggle, but so far it doesn't seem to work as intended. After starting Huggle the usual login screen pops up and generates the usual login tasks window after using a bot account to login. It will report green marks for all operations except "Checking user info for EnWiki". The second this is the only operation not marked as complete Huggle will just close (Eg: Proces simply terminates, no error).

I'm currently testing the 3.2.0 beta on a Windows 7 machine. So far i tried:

• Upgrading (3.1.22 to 3.2.0)
• Deïnstalling and reinstalling Huggle.
• A downgrade to 3.1.22 to verify this wasn't just my system huggle works again. (3.1.22 works as intended).

I've gone over the system / AV logs to see if anything was blocking huggle but i see no indication any third-party program is interfering. Neither can i see any logs of any kind that would provide a clue as to what the problem might be. Excirial ^{(Contact me,Contribs)} 12:20, 4 April 2017 (UTC)

OK that sounds like a first bug :) I will try with clean Windows installation and see what is missing Petrb (talk) 20:57, 4 April 2017 (UTC)

Same issue on a separate Windows 10 system after upgrading 3.1.22 to 3.2.0. Excirial ^{(Contact me,Contribs)} 18:03, 4 April 2017 (UTC)

I fixed this problem (I hope) - try new build http://petr.insw.cz/huggle/huggle_3.2.0_beta.exe Petrb (talk) 11:04, 6 April 2017 (UTC)

@Petrb: Seems to work just fine now - after updating the Windows 7 machine Huggle started correctly, and executed a single revert and warn (For test purposes) just fine. Excirial ^{(Contact me,Contribs)} 11:23, 6 April 2017 (UTC)

Just got around to giving 3.2.0 a whirl. One issue I immediately ran into is the rendering of the diff's using the new engine - see the screenshot. Whenever a multiline diff is displayed the lines seem to overlap which hurts readability quite a bit. Playing with the font size or font type doesn't appear to solve the issue. Excirial ^{(Contact me,Contribs)} 18:39, 6 April 2017 (UTC)

I've noticed a little bug in Huggle when trying to revert an edit to a user talk page where the warning regarding the edit also needs to be placed. Here, an IP replaced the month header with an attack, so I loaded it in Huggle to revert it and warn the user. However, when Huggle made the second edit to warn the user, it also reverted the edit it has just made (restoring the attack), forcing me to manually restore the month header. This only seems to happen on user talk pages when you're reverting an edit to, and issuing a warning to, the same page. Home Lander (talk) 20:02, 19 May 2017 (UTC)

Thanks for the report. https://phabricator.wikimedia.org/T166106 Petrb (talk) 07:53, 23 May 2017 (UTC)

I get this message quite regularly: Huggle then displays the diff, but in a version that can't be rolled back using the Huggle interface. Can someone explain why this happens and how I can avoid it? -- Rrburke (talk) 12:35, 1 May 2017 (UTC)

Hi, yes this is a known issue, it happens because MediaWiki wasn't able to give us the diff via API, so Huggle falls back to alternative way, where it just asks for a diff using standard web request :( but there are plans to fix this! Petrb (talk) 07:57, 23 May 2017 (UTC)

Hi guys,

New beta: https://petr.insw.cz/huggle/huggle_3.2.0_beta2.exe Petrb (talk) 09:32, 5 May 2017 (UTC)

@Petrb: I can't run this beta, since the checkbox for "run SSL" is deactivated, and can't be pressed, and enwp reqired SSL to be used. (t) Josve05a (c) 18:32, 2 June 2017 (UTC)

Posted this on Phab a while ago but I just wanted to post here to see if anyone else has been able to confirm this? Whenever I was using my custom keyboard shortcuts it was giving totally different warning messages vs. what it should have been. -- Dane ^talk 20:57, 27 June 2017 (UTC)

I believe I found a minor bug. See bottom edit summary here. I reverted an edit on /æ/ tensing. When Huggle warned the user, it properly linked to the article in the actual edit, using [[:/æ/ tensing]] as shown here. In the edit summary, however, it did not use the ":", resulting in [[/æ/ tensing]]. This causes a redlink in the edit summary pointing toward "whateverpageyourecurrentlyon/articlename" like this: /æ/ tensing (for example, on this page it points to "Wikipedia:Huggle/Feedback/æ/ tensing"). Home Lander (talk) 02:13, 20 June 2017 (UTC)

Thanks for report T170449 Petrb (talk) 18:02, 12 July 2017 (UTC)

Greetings. I am currently trying to install Huggle in Linux Mint 18.1, and I'm having some problems. I've added the ppa with

sudo add-apt-repository ppa:huggle-devs/ppa
sudo apt-get update

but attempting to use

sudo apt install huggle

returns

E: Unable to locate package huggle

Further, opening the "Software Sources" app and selecting the huggle-devs ppa and hitting "Open PPA" returns an error:

The content of this PPA is not available. Please refresh the cache and try again.

My only lead is that on this page, the Xenial build is showing as returning errors for amd64. Anyone know what I'm doing wrong, if anything? Cheers —  crh ₂₃  (Talk) 09:13, 19 April 2017 (UTC)

Hi you don't do anything wrong, it's a problem with packaging... I will see what I can do about it. Petrb (talk) 09:33, 5 May 2017 (UTC)

@Petrb: I had the same problem trying to install Huggle on Ubuntu 16.04 LTS yesterday. Any progress? --Hume42 (talk) 23:22, 26 May 2017 (UTC)

I have this problem for some weeks. Only informing, thanks. Ixocactus (talk) 06:34, 6 July 2017 (UTC)

Hi all, sorry for late reply, there are multiple workarounds while I am looking how to fix the ppa repo, the best one is compiling huggle from source code, which is great if you know how to do that, but less great if you have no clue how to compile programs. In that case there is option to use the snap version, which is only experimental, but works on latest ubuntu I will try to build newer snap soonish. I will post a link to some working version. Petrb (talk) 16:55, 10 July 2017 (UTC)

I dropped support for PPA completely, you can download snap version from meta download. Petrb (talk) 19:15, 13 July 2017 (UTC)

Hi beta testers,

If anyone from beta testing team is interested, I fixed the nightly builds for Windows, you can find more information here: https://github.com/huggle/huggle3-qt-lx/wiki/Nightly-builds

Thanks to this HEAD version of our master branch will be always available for various platforms prebuilt for you to test.

Please, be careful when running these, and let us know if you find any problem on phabricator! Thank you Petrb (talk) 19:43, 14 July 2017 (UTC)

Hello, I'm having an issue of the latest version of huggle crashing when I launch it. The old version runs fine when I re-install it. Oshwah and AntiCompositeNumber tried to help but we couldn't figure out the issue. Any help would be appreciated.

 Library not loaded: /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth
 Referenced from: /Applications/huggle.app/Contents/Frameworks/QtWebEngineCore.framework/Versions/5/QtWebEngineCore
 Reason: image not found

   0x7fff69a8d000 -     0x7fff69ac0887  dyld (239.5) <1D3130FE-FE7E-3C4C-8E74-EB51895B6BA5> /usr/lib/dyld
   0x7fff8c99e000 -     0x7fff8c9c7fff  com.apple.DictionaryServices (1.2 - 208) <A539A058-BA57-35EE-AA08-D0B0E835127D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
   0x7fff8ca11000 -     0x7fff8ca2cff7  libPng.dylib (1048) <C14F8741-9F67-32DA-896A-F873705B3EC6> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
   0x7fff8ca44000 -     0x7fff8ca49ff7  libunwind.dylib (35.3) <78DCC358-2FC1-302E-B395-0155B47CB547> /usr/lib/system/libunwind.dylib
   0x7fff8ca4c000 -     0x7fff8ca63ff7  com.apple.CFOpenDirectory (10.9 - 173.90.1) <D7F2E159-CF6B-3EB1-9806-3BC59E63D24F> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory
   0x7fff8ca64000 -     0x7fff8cd38fc7  com.apple.vImage (7.0 - 7.0) <D241DBFA-AC49-31E2-893D-EAAC31890C90> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
   0x7fff8cd72000 -     0x7fff8cf1ff27  libobjc.A.dylib (551.1) <AD7FD984-271E-30F4-A361-6B20319EC73B> /usr/lib/libobjc.A.dylib
   0x7fff8cf20000 -     0x7fff8cf84fff  com.apple.datadetectorscore (5.0 - 354.5) <D4DBCCF4-9622-3AB9-9076-32579FCC2E39> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore
   0x7fff8cf85000 -     0x7fff8cf94ff8  com.apple.LangAnalysis (1.7.0 - 1.7.0) <8FE131B6-1180-3892-98F5-C9C9B79072D4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis
   0x7fff8d0c4000 -     0x7fff8d0c8ff7  libGIF.dylib (1048) <53A30C22-410C-3DFF-9236-0CC56D2E64A5> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
   0x7fff8d0e6000 -     0x7fff8d145fff  com.apple.framework.CoreWLAN (4.3.3 - 433.48) <1F17FA12-6E84-309D-9808-C536D445FA6E> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN
   0x7fff8d146000 -     0x7fff8d176fff  com.apple.IconServices (25 - 25.17) <4751127E-FBD5-3ED5-8510-08D4E4166EFE> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices
   0x7fff8d177000 -     0x7fff8d191fff  libdispatch.dylib (339.92.1) <C4E4A18D-3C3B-3C9C-8709-A4270D998DE7> /usr/lib/system/libdispatch.dylib
   0x7fff8d2a0000 -     0x7fff8d329fff  com.apple.ColorSync (4.9.0 - 4.9.0) <B756B908-9AD1-3F5D-83F9-7A0B068387D2> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync
   0x7fff8d32a000 -     0x7fff8d335ff7  com.apple.NetAuth (5.0 - 5.0) <C811E662-9EC3-3B74-808A-A75D624F326B> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
   0x7fff8d359000 -     0x7fff8d44aff9  libiconv.2.dylib (41) <BB44B115-AC32-3877-A0ED-AEC6232A4563> /usr/lib/libiconv.2.dylib
   0x7fff8d44b000 -     0x7fff8d4ccfff  com.apple.CoreSymbolication (3.0.1 - 141.0.6) <D46DE002-1FEB-38B7-8583-3DF3496274F5> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication
   0x7fff8d4dc000 -     0x7fff8d90fffb  com.apple.vision.FaceCore (3.0.0 - 3.0.0) <F42BFC9C-0B16-35EF-9A07-91B7FDAB7FC5> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore
   0x7fff8d931000 -     0x7fff8d960fff  com.apple.DebugSymbols (106 - 106) <E1BDED08-523A-36F4-B2DA-9D5C712F0AC7> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols
   0x7fff8d961000 -     0x7fff8da45ff7  com.apple.coreui (2.2 - 231.1) <187DF89C-8A64-366D-8782-F90315FA3CD7> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
   0x7fff8da46000 -     0x7fff8da51fff  libkxld.dylib (2422.115.15) <8850BC2B-EB64-3B0F-8047-DCC113021292> /usr/lib/system/libkxld.dylib
   0x7fff8da95000 -     0x7fff8da95fff  com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
   0x7fff8dc69000 -     0x7fff8dc8eff7  com.apple.ChunkingLibrary (2.0 - 155.1) <B845DC7A-D1EA-31E2-967C-D1FE0C628036> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary
   0x7fff8dc8f000 -     0x7fff8dca7ff7  com.apple.GenerationalStorage (2.0 - 160.3) <64749B08-0212-3AC8-9B49-73D662B09304> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage
   0x7fff8dca8000 -     0x7fff8dcaffff  com.apple.NetFS (6.0 - 4.0) <8E26C099-CE9D-3819-91A2-64EA929C6137> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
   0x7fff8dcb0000 -     0x7fff8df20ffd  com.apple.security (7.0 - 55471.14.40) <58F50B4A-FC1E-3AE0-A5DB-DD737E50AC17> /System/Library/Frameworks/Security.framework/Versions/A/Security
   0x7fff8e088000 -     0x7fff8e089ff7  libDiagnosticMessagesClient.dylib (100) <4CDB0F7B-C0AF-3424-BC39-495696F0DB1E> /usr/lib/libDiagnosticMessagesClient.dylib
   0x7fff8e08a000 -     0x7fff8e35bffc  com.apple.CoreImage (9.4.1) <7B28C3F3-8EB3-3150-A55D-EBCDBDCA4977> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage.framework/Versions/A/CoreImage
   0x7fff8e76c000 -     0x7fff8e76dff7  libSystem.B.dylib (1197.1.1) <F727296D-D066-31BD-A9F9-5CAA1BD7A6A7> /usr/lib/libSystem.B.dylib
   0x7fff8e7b8000 -     0x7fff8e844ff7  com.apple.ink.framework (10.9 - 207) <8A50B893-AD03-3826-8555-A54FEAF08F47> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink
   0x7fff8ea1f000 -     0x7fff8eb73ff3  com.apple.audio.toolbox.AudioToolbox (1.10 - 1.10) <69B273E8-5A8E-3FC7-B807-C16B657662FE> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
   0x7fff8eb88000 -     0x7fff8eb88fff  com.apple.Carbon (154 - 157) <EFC1A1C0-CB07-395A-B038-CFA2E71D3E69> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
   0x7fff8eb89000 -     0x7fff8ebb8fd2  libsystem_m.dylib (3047.16) <B7F0E2E4-2777-33FC-A787-D6430B630D54> /usr/lib/system/libsystem_m.dylib
   0x7fff8ebe6000 -     0x7fff8ec7aff7  com.apple.Bluetooth (4.2.7 - 4.2.7f5) <A7F0360A-DBDA-32EA-AA37-6937B94E6A72> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
   0x7fff8ec89000 -     0x7fff8ec8bfff  libRadiance.dylib (1048) <5D66AE6D-1B0B-33CC-91F0-D93AE7016C7B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib
   0x7fff8ecdc000 -     0x7fff8ecf8ff7  libsystem_kernel.dylib (2422.115.15) <34ABAF79-E147-3C34-B05D-46A566E689CC> /usr/lib/system/libsystem_kernel.dylib
   0x7fff8ecfd000 -     0x7fff8ed50fff  com.apple.ScalableUserInterface (1.0 - 1) <CF745298-7373-38D2-B3B1-727D5A569E48> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableUserInterface.framework/Versions/A/ScalableUserInterface
   0x7fff8eda5000 -     0x7fff8eec7fff  com.apple.avfoundation (2.0 - 651.12.1) <FDCF1F41-E0BD-3F8C-974A-3F48A0A85B00> /System/Library/Frameworks/AVFoundation.framework/Versions/A/AVFoundation
   0x7fff8eec8000 -     0x7fff8ef19ff7  com.apple.audio.CoreAudio (4.2.1 - 4.2.1) <07F2B103-AE29-3118-BBC4-9A72E13B013B> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
   0x7fff8ef45000 -     0x7fff8ef55fff  libbsm.0.dylib (33) <2CAC00A2-1352-302A-88FA-C567D4D69179> /usr/lib/libbsm.0.dylib
   0x7fff8f10e000 -     0x7fff8f169ffb  com.apple.AE (665.5 - 665.6) <9B17E7B7-D493-346A-827E-6DF1474E4977> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE
   0x7fff8f1c0000 -     0x7fff8f2aafff  libsqlite3.dylib (158) <00269BF9-43BE-39E0-9C85-24585B9923C8> /usr/lib/libsqlite3.dylib
   0x7fff8f2ab000 -     0x7fff8f2acffb  libremovefile.dylib (33) <3543F917-928E-3DB2-A2F4-7AB73B4970EF> /usr/lib/system/libremovefile.dylib
   0x7fff8f364000 -     0x7fff8f368ff7  libheimdal-asn1.dylib (323.92.2) <979AEAA0-59B3-3E99-94B1-9BB9C6C45273> /usr/lib/libheimdal-asn1.dylib
   0x7fff8f369000 -     0x7fff8f374fff  libGL.dylib (9.6.5) <A5F36623-33E8-379D-A423-8F873018CD79> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
   0x7fff8f375000 -     0x7fff8f376fff  libunc.dylib (28) <62682455-1862-36FE-8A04-7A6B91256438> /usr/lib/system/libunc.dylib
   0x7fff8f377000 -     0x7fff8f39bff7  libJPEG.dylib (1048) <3C999DC3-8A51-3CA9-9AB8-7F9DBA278FE6> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
   0x7fff8f39f000 -     0x7fff8f3e1ff7  libauto.dylib (185.5) <F45C36E8-B606-3886-B5B1-B6745E757CA8> /usr/lib/libauto.dylib
   0x7fff8f3ed000 -     0x7fff8f3fafff  com.apple.Sharing (132.2 - 132.2) <F983394A-226D-3244-B511-FA51FDB6ADDA> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing
   0x7fff8f3fb000 -     0x7fff8f4c6fff  libvDSP.dylib (423.32) <3BF732BE-DDE0-38EB-8C54-E4E3C64F77A7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib
   0x7fff8f4ee000 -     0x7fff8f5b0ffd  com.apple.CoreText (367.23 - 367.23) <C799261E-2E19-3D69-8A8D-098B7DD8D31D> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
   0x7fff8f7a3000 -     0x7fff8f7defff  com.apple.bom (14.0 - 193.1) <EF24A562-6D3C-379E-8B9B-FAE0E4A0EF7C> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
   0x7fff8f837000 -     0x7fff8f83aff7  libdyld.dylib (239.5) <CAE7A50D-F156-3D47-81C0-DC41EB975D38> /usr/lib/system/libdyld.dylib
   0x7fff8f83b000 -     0x7fff8f843ff7  com.apple.speech.recognition.framework (4.2.4 - 4.2.4) <98BBB3E4-6239-3EF1-90B2-84EA0D3B8D61> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition
   0x7fff8f844000 -     0x7fff8f9e0ff3  com.apple.QuartzCore (1.8 - 332.4) <CFB972D1-FA37-380C-9A47-2A67A84B7442> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
   0x7fff8fd9d000 -     0x7fff8fda0fff  com.apple.TCC (1.0 - 1) <32A075D9-47FD-3E71-95BC-BFB0D583F41C> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
   0x7fff8fdab000 -     0x7fff8fdc4ff7  com.apple.Ubiquity (1.3 - 289) <C7F1B734-CE81-334D-BE41-8B20D95A1F9B> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
   0x7fff8fded000 -     0x7fff8fdf6ffd  com.apple.CommonAuth (4.0 - 2.0) <BD720379-757B-305C-A7BE-E00E680F8218> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
   0x7fff8fe4f000 -     0x7fff8fe51ff3  libsystem_configuration.dylib (596.15) <4998CB6A-9D54-390A-9F57-5D1AC53C135C> /usr/lib/system/libsystem_configuration.dylib
   0x7fff8fe83000 -     0x7fff8fecaffb  libFontRegistry.dylib (127.0.1) <F267F500-6E4A-3BE3-97C1-08AAA649E02E> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib
   0x7fff8ff3a000 -     0x7fff8ff56fff  libresolv.9.dylib (54) <11C2C826-F1C6-39C6-B4E8-6E0C41D4FA95> /usr/lib/libresolv.9.dylib
   0x7fff90043000 -     0x7fff90044ff7  libsystem_blocks.dylib (63) <FB856CD1-2AEA-3907-8E9B-1E54B6827F82> /usr/lib/system/libsystem_blocks.dylib
   0x7fff90048000 -     0x7fff90048fff  com.apple.Accelerate.vecLib (3.9 - vecLib 3.9) <F8D0CC77-98AC-3B58-9FE6-0C25421827B6> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib
   0x7fff90049000 -     0x7fff900d9ff7  com.apple.Metadata (10.7.0 - 800.30) <E107CE36-FBC3-35A5-84E0-864B4178FC5D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata
   0x7fff900da000 -     0x7fff900dafff  com.apple.Accelerate (1.9 - Accelerate 1.9) <509BB27A-AE62-366D-86D8-0B06D217CF56> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
   0x7fff90238000 -     0x7fff9023fffb  libcopyfile.dylib (103.92.1) <CF29DFF6-0589-3590-834C-82E2316612E8> /usr/lib/system/libcopyfile.dylib
   0x7fff90240000 -     0x7fff90240fff  com.apple.quartzframework (1.5 - 1.5) <3B2A72DB-39FC-3C5B-98BE-605F37777F37> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
   0x7fff90241000 -     0x7fff90293fff  libc++.1.dylib (120) <4F68DFC5-2077-39A8-A449-CAC5FDEE7BDE> /usr/lib/libc++.1.dylib
   0x7fff90294000 -     0x7fff902c3ff9  com.apple.GSS (4.0 - 2.0) <27FCA2B4-0767-3002-8755-862B19B5CF92> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
   0x7fff906ba000 -     0x7fff90712ff7  com.apple.Symbolication (1.4 - 129.0.2) <3DCCAB8A-6FA1-3BB9-B4D3-A3CBDB3BDF04> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication
   0x7fff90791000 -     0x7fff9079eff7  libxar.1.dylib (202) <5572AA71-E98D-3FE1-9402-BB4A84E0E71E> /usr/lib/libxar.1.dylib
   0x7fff907a1000 -     0x7fff9080efff  com.apple.SearchKit (1.4.0 - 1.4.0) <B9B8D510-A27E-36B0-93E9-17146D9E9045> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit
   0x7fff90868000 -     0x7fff90874ff7  com.apple.OpenDirectory (10.9 - 173.90.1) <383F96FF-1DF3-37E8-8540-03A697C873F6> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
   0x7fff90b8f000 -     0x7fff90c96ff7  com.apple.ImageIO.framework (3.3.0 - 1048) <FDFAFDEA-3559-330F-9578-40F4F62F51B3> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
   0x7fff915bf000 -     0x7fff915c0fff  liblangid.dylib (117) <9546E641-F730-3AB0-B3CD-E0E2FDD173D9> /usr/lib/liblangid.dylib
   0x7fff915c1000 -     0x7fff915cbff7  com.apple.CrashReporterSupport (10.9 - 539) <B25A09EC-A021-32EC-86F8-05B4837E0EDE> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport
   0x7fff915cd000 -     0x7fff915d2fff  libmacho.dylib (845) <1D2910DF-C036-3A82-A3FD-44FF73B5FF9B> /usr/lib/system/libmacho.dylib
   0x7fff915d3000 -     0x7fff915dcfff  com.apple.speech.synthesis.framework (4.7.1 - 4.7.1) <383FB557-E88E-3239-82B8-15F9F885B702> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis
   0x7fff915dd000 -     0x7fff915e4ff8  liblaunch.dylib (842.92.1) <A40A0C7B-3216-39B4-8AE0-B5D3BAF1DA8A> /usr/lib/system/liblaunch.dylib
   0x7fff915f0000 -     0x7fff91637ff7  libcups.2.dylib (372.6) <CBD2F0CF-FA10-36E1-A1D5-1B946B45B3B3> /usr/lib/libcups.2.dylib
   0x7fff9164f000 -     0x7fff91677ffb  libxslt.1.dylib (13.10) <367D404A-6065-3A8D-A94A-4838F9F9DB4A> /usr/lib/libxslt.1.dylib
   0x7fff916bf000 -     0x7fff916c2fff  libCoreVMClient.dylib (58.1) <EBC36C69-C896-3C3D-8589-3E9023E7E56F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib
   0x7fff916c3000 -     0x7fff916c8fff  com.apple.DiskArbitration (2.6 - 2.6) <A4165553-770E-3D27-B217-01FC1F852B87> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
   0x7fff916c9000 -     0x7fff916cfff7  libsystem_platform.dylib (24.90.1) <3C3D3DA8-32B9-3243-98EC-D89B9A1670B3> /usr/lib/system/libsystem_platform.dylib
   0x7fff916d0000 -     0x7fff9171efff  libcorecrypto.dylib (161.1) <F3973C28-14B6-3006-BB2B-00DD7F09ABC7> /usr/lib/system/libcorecrypto.dylib
   0x7fff91bbc000 -     0x7fff91bc0fff  libpam.2.dylib (20) <B93CE8F5-DAA8-30A1-B1F6-F890509513CB> /usr/lib/libpam.2.dylib
   0x7fff91bc4000 -     0x7fff91bebff7  libsystem_network.dylib (241.4) <0D630D53-C772-3EC5-8257-EFB0ACCE3153> /usr/lib/system/libsystem_network.dylib
   0x7fff91c5a000 -     0x7fff91c6bff7  libz.1.dylib (53) <42E0C8C6-CA38-3CA4-8619-D24ED5DD492E> /usr/lib/libz.1.dylib
   0x7fff922fa000 -     0x7fff9233fff6  com.apple.HIServices (1.23 - 468) <FD17FE8C-A355-3B6B-B8B7-E56E5C595EDE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices
   0x7fff92345000 -     0x7fff923b2ff1  com.apple.ApplicationServices.ATS (360 - 363.6) <828C2711-4577-3F75-B436-3BDF328DFB11> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
   0x7fff923b3000 -     0x7fff923bbfff  libsystem_dnssd.dylib (522.92.3) <1418DF66-01BE-3A87-8553-09EAA945F4FE> /usr/lib/system/libsystem_dnssd.dylib
   0x7fff9365a000 -     0x7fff93668fff  com.apple.opengl (9.6.5 - 9.6.5) <4FAEADD8-EEB3-3FD9-ADC6-BA65806228CC> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
   0x7fff93669000 -     0x7fff93a4affe  libLAPACK.dylib (1094.5) <7E7A9B8D-1638-3914-BAE0-663B69865986> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
   0x7fff93a9f000 -     0x7fff93b0bfff  com.apple.framework.IOKit (2.0.1 - 907.100.14) <10932113-9F7E-38A0-A158-A019A555CAC3> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
   0x7fff93b84000 -     0x7fff93b84fff  com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
   0x7fff93b96000 -     0x7fff93bceff7  com.apple.RemoteViewServices (2.0 - 94) <3F34D630-3DDB-3411-BC28-A56A9B55EBDA> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices
   0x7fff93bcf000 -     0x7fff93eb9fff  com.apple.CoreServices.CarbonCore (1077.17 - 1077.17) <3A2E92FD-DEE2-3D45-9619-11500801A61C> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
   0x7fff93eba000 -     0x7fff93ec4ff7  com.apple.bsd.ServiceManagement (2.0 - 2.0) <2D27B498-BB9C-3D88-B05A-76908A8A26F3> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement
   0x7fff93f33000 -     0x7fff93f6cff7  com.apple.QD (3.50 - 298) <C1F20764-DEF0-34CF-B3AB-AB5480D64E66> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
   0x7fff9434e000 -     0x7fff94350ff7  libquarantine.dylib (71) <7A1A2BCB-C03D-3A25-BFA4-3E569B2D2C38> /usr/lib/system/libquarantine.dylib
   0x7fff9436f000 -     0x7fff943aefff  libGLU.dylib (9.6.5) <7463B411-2DB0-3338-BC8D-403293E2CA34> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
   0x7fff9440d000 -     0x7fff9440dfff  com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
   0x7fff94677000 -     0x7fff9475fff7  libxml2.2.dylib (26.8) <75424553-B02C-37FB-BCDD-19A288D3F306> /usr/lib/libxml2.2.dylib
   0x7fff94760000 -     0x7fff94763ffc  com.apple.IOSurface (91.3 - 91.3) <E93485CC-12B1-318E-BAE3-AB532B264935> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
   0x7fff94764000 -     0x7fff947edfff  libsystem_c.dylib (997.90.4) <EA812F03-8AD2-3776-AD50-6BEBC90F1F5F> /usr/lib/system/libsystem_c.dylib
   0x7fff947ee000 -     0x7fff947eeffd  com.apple.audio.units.AudioUnit (1.10 - 1.10) <68B21135-55A6-3563-A3D6-3E692A7DEB7F> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
   0x7fff94931000 -     0x7fff94932fff  libsystem_sandbox.dylib (278.11.2) <0C93EB23-7364-3670-B511-212A7A524695> /usr/lib/system/libsystem_sandbox.dylib
   0x7fff94ddb000 -     0x7fff94e4efff  com.apple.securityfoundation (6.0 - 55122.3) <0AFCF575-97C3-3458-A72E-39DA07804EB9> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation
   0x7fff94e4f000 -     0x7fff94fbdff7  libBLAS.dylib (1094.5) <DE93A590-5FA5-32A2-A16C-5D7D7361769F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
   0x7fff957b1000 -     0x7fff957ccff7  libsystem_malloc.dylib (23.10.1) <A695B4E4-38E9-332E-A772-29D31E3F1385> /usr/lib/system/libsystem_malloc.dylib
   0x7fff9586c000 -     0x7fff9586cffd  libOpenScriptingUtil.dylib (157.1) <D3B6E577-3CDB-3139-9B94-19496DFA7318> /usr/lib/libOpenScriptingUtil.dylib
   0x7fff9586d000 -     0x7fff95a52fff  com.apple.CoreFoundation (6.9 - 855.17) <729BD6DA-1F63-3E72-A148-26F21EBF52BB> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
   0x7fff95a53000 -     0x7fff95a5aff7  libsystem_pthread.dylib (53.1.4) <AB498556-B555-310E-9041-F67EC9E00E2C> /usr/lib/system/libsystem_pthread.dylib
   0x7fff95a5b000 -     0x7fff95bf6ff8  com.apple.CFNetwork (673.6 - 673.6) <CAA196FE-BF5A-384F-975E-E0F81359805B> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
   0x7fff95bf7000 -     0x7fff95bfbff7  libsystem_stats.dylib (93.90.3) <2304C7C2-BE45-35DE-BCC6-707D61B7AE7E> /usr/lib/system/libsystem_stats.dylib
   0x7fff95bfc000 -     0x7fff95c3dfff  com.apple.PerformanceAnalysis (1.47 - 47) <95435F84-C251-3C48-B6CD-9EE7A63D6E26> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis
   0x7fff95c3e000 -     0x7fff95c8bff2  com.apple.print.framework.PrintCore (9.0 - 428) <8D8253E3-302F-3DB2-9C5C-572CB974E8B3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore
   0x7fff95c8c000 -     0x7fff95cdaff7  com.apple.opencl (2.3.59 - 2.3.59) <E37E2219-6EA7-3666-8DB5-8FC60EFB0BC9> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
   0x7fff95cdb000 -     0x7fff95d3effb  com.apple.SystemConfiguration (1.13.1 - 1.13.1) <339A2A90-DA25-33AF-88E5-2FB38A758FEE> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
   0x7fff95e17000 -     0x7fff95e19fff  libCVMSPluginSupport.dylib (9.6.5) <9DE29AD9-5F59-3B9B-899C-4DED190CB817> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib
   0x7fff95e1a000 -     0x7fff95e7fffb  com.apple.Heimdal (4.0 - 2.0) <C28DBCAE-01AC-363A-9046-3BD33F225526> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
   0x7fff95f17000 -     0x7fff9615fff7  com.apple.CoreData (107 - 481.3) <E78734AA-E3D0-33CB-A014-620BBCAB2E96> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
   0x7fff9619a000 -     0x7fff961c3ff7  libc++abi.dylib (49.1) <21A807D3-6732-3455-B77F-743E9F916DF0> /usr/lib/libc++abi.dylib
   0x7fff96213000 -     0x7fff96b3c12b  com.apple.CoreGraphics (1.600.0 - 599.35.13) <142EF2C9-6B8F-3ACB-9C46-B20628DFE134> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
   0x7fff96b9a000 -     0x7fff96c4aff7  libvMisc.dylib (423.32) <049C0735-1808-39B9-943F-76CB8021744F> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib
   0x7fff96d9b000 -     0x7fff96ecbff7  com.apple.desktopservices (1.8.3 - 1.8.3) <225BEC20-F8E0-3F22-9560-890A1A5B9050> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv
   0x7fff96ecc000 -     0x7fff97084ffb  libicucore.A.dylib (511.36) <9AAC5980-2C1F-3B86-8A16-DB533F5E7C84> /usr/lib/libicucore.A.dylib
   0x7fff97949000 -     0x7fff97a37fff  libJP2.dylib (1048) <19B37CB6-C864-3830-87FE-BB53F8542FB0> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
   0x7fff97a38000 -     0x7fff97ce2ff5  com.apple.HIToolbox (2.1.1 - 698) <A388E773-AE7B-3FD1-8662-A98E6E24EA16> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
   0x7fff98259000 -     0x7fff98272ff7  com.apple.Kerberos (3.0 - 1) <F108AFEB-198A-3BAF-BCA5-9DFCE55EFF92> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
   0x7fff98288000 -     0x7fff9828cff7  libcache.dylib (62) <BDC1E65B-72A1-3DA3-A57C-B23159CAAD0B> /usr/lib/system/libcache.dylib
   0x7fff98293000 -     0x7fff98e09ff7  com.apple.AppKit (6.9 - 1265.21) <9DC13B27-841D-3839-93B2-3EDE66157BDE> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
   0x7fff98e29000 -     0x7fff98e32ffb  libsystem_notify.dylib (121.20.1) <9B34B4FE-F5AD-3F09-A5F0-46AFF3571323> /usr/lib/system/libsystem_notify.dylib
   0x7fff98e33000 -     0x7fff98e45ff7  com.apple.MultitouchSupport.framework (245.13.1 - 245.13.1) <38262B92-C63F-35A0-997D-AD2EBF2F8338> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport
   0x7fff98e46000 -     0x7fff99146ff7  com.apple.Foundation (6.9 - 1056.17) <E0B0FAF6-5CA8-3EEB-8BF2-104C0AEEF925> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
   0x7fff9935e000 -     0x7fff99383ff7  com.apple.CoreVideo (1.8 - 117.2) <4674339E-26D0-35FA-9958-422832B39B12> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
   0x7fff998fa000 -     0x7fff99924ff7  libsandbox.1.dylib (278.11.2) <5C750008-A22B-35E8-8B11-D84F82E08680> /usr/lib/libsandbox.1.dylib
   0x7fff9992d000 -     0x7fff99986ff7  libTIFF.dylib (1048) <923096A6-02CC-311D-9596-1961430C0EF7> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
   0x7fff99987000 -     0x7fff999d0fff  com.apple.CoreMedia (1.0 - 1273.57) <74FA3D80-A6DB-331A-B32A-683C8E0CC0A6> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
   0x7fff999d1000 -     0x7fff999f8ffb  libsystem_info.dylib (449.1.4) <12CD9E42-8CEE-3A8D-B006-F8A6EB98804D> /usr/lib/system/libsystem_info.dylib
   0x7fff99a15000 -     0x7fff99a1cfff  libcompiler_rt.dylib (35) <4CD916B2-1B17-362A-B403-EF24A1DAC141> /usr/lib/system/libcompiler_rt.dylib
   0x7fff99a1d000 -     0x7fff99a27fff  libcommonCrypto.dylib (60049) <8C4F0CA0-389C-3EDC-B155-E62DD2187E1D> /usr/lib/system/libcommonCrypto.dylib
   0x7fff99a28000 -     0x7fff99af2ff7  com.apple.LaunchServices (572.32 - 572.32) <A4699DED-5101-3068-94F8-8D0B7A84BC79> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices
   0x7fff99cc2000 -     0x7fff99ccfff0  libbz2.1.0.dylib (29) <0B98AC35-B138-349C-8063-2B987A75D24C> /usr/lib/libbz2.1.0.dylib
   0x7fff99cd0000 -     0x7fff99ce1ff7  libsystem_asl.dylib (217.1.4) <655FB343-52CF-3E2F-B14D-BEBF5AAEF94D> /usr/lib/system/libsystem_asl.dylib
   0x7fff99ce2000 -     0x7fff99da6ff7  com.apple.backup.framework (1.5.5 - 1.5.5) <CA77A4FC-7B76-30C7-94BE-FF4B8140D05A> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
   0x7fff99dd1000 -     0x7fff99dd9ffc  libGFXShared.dylib (9.6.5) <FCCD0CD3-02FD-3A79-B048-A14745D76CC8> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib
   0x7fff99e28000 -     0x7fff99e34ffb  com.apple.AppleFSCompression (56.92.2 - 1.0) <16542F97-9D21-317D-8A50-4C34AAD35F41> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression
   0x7fff99e42000 -     0x7fff99e42ff7  libkeymgr.dylib (28) <3AA8D85D-CF00-3BD3-A5A0-E28E1A32A6D8> /usr/lib/system/libkeymgr.dylib
   0x7fff99ec1000 -     0x7fff99ee5fff  libxpc.dylib (300.90.2) <AB40CD57-F454-3FD4-B415-63B3C0D5C624> /usr/lib/system/libxpc.dylib
   0x7fff99ee6000 -     0x7fff99fe0fff  libFontParser.dylib (111.1.6) <77253632-B3F6-3151-ABA0-C1EF458668A8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib
   0x7fff9a012000 -     0x7fff9a013fff  com.apple.TrustEvaluationAgent (2.0 - 25) <334A82F4-4AE4-3719-A511-86D0B0723E2B> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent
   0x7fff9a3d4000 -     0x7fff9a412ff7  libGLImage.dylib (9.6.5) <C242B319-6F4B-3FB3-8FCE-0B77424F0BED> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib
   0x7fff9a438000 -     0x7fff9a453ff7  libCRFSuite.dylib (34) <FFAE75FA-C54E-398B-AA97-18164CD9789D> /usr/lib/libCRFSuite.dylib
   0x7fff9a5d9000 -     0x7fff9a650fff  com.apple.CoreServices.OSServices (600.4 - 600.4) <6BC86B46-AFD3-3F06-8659-2C954CBEBD43> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices

--Cameron₁₁₅₉₈ ^(Talk) 03:16, 15 July 2017 (UTC)

Looks like it's failing to load some dependencies or libraries that's required for Huggle to work (bluetooth Framework? Wat?). I tested the latest release of Huggle on my MacBook (it's running El Cap, but I'm also a developer and I've loaded a lot of libraries onto it) and it works just fine for me. ~Oshwah~^{(talk) (contribs)} 03:20, 15 July 2017 (UTC)

I just walked him through installing the xcode command-line tools to see if he was just missing a developer library, but to no avail. I'm having him update his OS version to a newer version. ~Oshwah~^{(talk) (contribs)} 03:36, 15 July 2017 (UTC)

Upgrading to MAC OSX 10.12.5 (Sierra) seems to have solved the issue. It might be worth noting that the latest version of Huggle requires 10.12 --Cameron₁₁₅₉₈ ^(Talk) 17:52, 15 July 2017 (UTC)

I'm running 10.11 and it works fine, so it appears that you must be running macOS 10.10 or newer to be able to run this version of Huggle (I believe that 10.10 uses the same libraries and mostly the same Frameworks as 10.11). I'll give it a try on 10.10 to be certain and I'll update this discussion when I've done so. ~Oshwah~^{(talk) (contribs)} 21:11, 15 July 2017 (UTC)

Update: Well... it was working for me just fine (lol). I'm going to need to start a new discussion about my unique issue now :-P ~Oshwah~^{(talk) (contribs)} 12:55, 16 July 2017 (UTC)

Yes, it's a missing dependency, I don't have a working Mac to try it out, but I guess there is something wrong with packaging process, all the libraries needed should be automatically bundled by Qt's packaging tool that we use. Petrb (talk) 20:20, 17 July 2017 (UTC)

I'm having a bit of an issue with dashes: they don't seem to be showing up correctly. The hyphen (-) is fine, but the ‒, –, —, ― charecters get replaced with – and the minus sign (−) is replaced with âˆ` (including on the left side of the diff view). I'm using Version: 3.2.0 build: production build without python support, compiled using QT 5.9.1 Running on QT 5.9.1, based on WebKit, target platform: linux, built from the AUR which uses the source tarball. This doesn't seem to break anything, it just looks a bit funny. --AntiCompositeNumber (Ring me) 04:28, 15 July 2017 (UTC)

AntiCompositeNumber - What Linux distro and version are you running? ~Oshwah~^{(talk) (contribs)} 05:45, 15 July 2017 (UTC)

That would probably be important...Arch Linux, rolling release, fully updated. Kernel Linux 4.9.37-1-lts. --AntiCompositeNumber (Ring me) 05:49, 15 July 2017 (UTC)

Cool. If weird dashes are biggest problem on Arch, then Huggle has to work really well there :P other distros have far bigger issues. Petrb (talk) 20:32, 17 July 2017 (UTC)

To provide some background: I own and frequently use different computers that either run Windows, macOS, or Linux. I'm running macOS 10.11 on my MacBook and just installed the 3.2.0 release by replacing the older .app file. I launched and began using the new Huggle release immediately after and with no issues at all. However, since rebooting my MacBook, I now can't launch it due to the OS stating that I'm required to be running macOS 10.12. However, if I open the .app contents and launch the executable file directly with the Terminal, the program opens and runs just fine. Is anybody else experiencing this when trying to launch 3.2.0 on their Mac? (Assuming you're running an older OS version, of course... lol)

To the development team: Was this release by any chance compiled under macOS 10.12, perhaps accidentally? If it was and this was not your intention, you'll want to re-compile it for an older version of macOS (I suggest 10.9) and replace the new .dmg with the one you're distributing now. This'll allow users running older versions of macOS to launch it without any trouble. Am I wrong in my assumption that this version was compiled under macOS 10.12? Am I missing something? Input and responses from anybody will be greatly helpful; I'd like to figure out why there's an OS version check occurring on launch and why it's set to such a high requirement. ~Oshwah~^{(talk) (contribs)} 13:18, 16 July 2017 (UTC)

Yes this build was probably built using last Mac OS, whichever it is. It was build by @Rich Smith: no idea if he can rebuild or retarget it. I am afraid that Mac is not able to do such magic like building for different targets, which is mostly domain of Linux. Petrb (talk) 20:30, 17 July 2017 (UTC)

The reason why these checks are implemented is simple, when you link dynamic libraries, you usually don't have problem running program compiled against older libs with newer libs, because they tend to maintain backward compatibility. Forward compatibility is far more complex and often not available, so Mac prevents you from running the program if it was built on newer OS and thus linked against newer system libraries, even if it, in theory, could work. It could also blow your system up though (very unlikely) :P Petrb (talk) 20:42, 17 July 2017 (UTC)

OK, so it's possible to build for older Macs with newer one, you just need to download and install SDK for that version, and then convince the compiler to actually use them :P which is probably non-trivial task. I can't help much as my Mac is broken, but I guess it will involve lot of CMake magic, you can probably specify SDK version in there. Petrb (talk) 20:47, 17 July 2017 (UTC)

According to http://doc.qt.io/qt-5/osx-deployment.html (Section called macOS Version Dependencies) it can be done... so I'm gonna try that and maybe someone can try it - Rich^T|C|E-Mail 20:52, 17 July 2017 (UTC)

Hi,

New huggle was released, it comes with many changes, most notably the web browser backed was changed to chromium from webkit, but we also moved to newer Qt. This combination of Qt + Chromium doesn't support MinGW, so I can't provide mingw32 builds that worked on Windows older than Vista. On other hand, I am not sure if anyone is using older Windows anymore. I am talking about Windows 2000 and XP. Is anyone using these? Is there any point in me creating builds based on Qt 5.4 and WebKit made with MinGW? It's technically possible, but it's not easy and time consuming activity so I would rather avoid doing that and I certainly will unless someone tell me that they are still on XP or Windows 2000 and need these. Thank you Petrb (talk) 17:58, 12 July 2017 (UTC)

Huggle notified me upon opening that 3.2.0 was available but needed to be manually updated because it couldn't detect my operating system. I manually downloaded and tried to install, and it overflowed my ram, locked everything up. Hard rebooted and tried again, same thing, can't get it to install. Windows 10 home 64 bit. Home Lander (talk) 15:39, 13 July 2017 (UTC)

Same here, I tried installing in a different folder, and this resloved the issue. KGirlTrucker81 ^{huh? what I've been doing} 15:43, 13 July 2017 (UTC)

It won't even start loading for me; as soon as I open it my screen goes dark, then flashes, and eventually it locks up entirely. Home Lander (talk) 15:47, 13 July 2017 (UTC)

@Home Lander: Did you get a Blue Screen of Death during the crash? KGirlTrucker81 ^{huh? what I've been doing} 17:23, 13 July 2017 (UTC)

@KGirlTrucker81:, no, lol, I've thankfully never gotten the BSOD in Windows 10, yet. It just causes my screen to go dark, then come back, go dark again, and then the whole machine bogs down, ultimately freezing and forcing a hard reboot. Home Lander (talk) 18:15, 13 July 2017 (UTC)

@Home Lander: Naahh, I just asking a weird question lol. :P KGirlTrucker81 ^{huh? what I've been doing} 19:33, 13 July 2017 (UTC)

Hi, can you explaing that dark screen or "memory overflow" a bit? Did you really see that huggle consumed more than 150MB of ram, or is that your guess? Do you get dark screen when you run huggle or installer? Windows usually dim your screen when they want to display message box where they ask for permissions, which is typical when you run some setup program. Is it happening when you try to start the installer or huggle itself? Are you trying 64bit or 32bit? Also there is _il version (installer less) available which may work for you, but this really shouldn't happen. Petrb (talk) 18:45, 13 July 2017 (UTC)

Hello, Petrb. I can tell it's overloading my machine because it starts running hard, rapid fan speeds, lots of heat, and the screen goes dark, then comes back (with sluggish functionality), before eventually going dark and ultimately freezing. I can run the old version of Huggle just fine. I frequently get the dimmed screen when Windows is asking for permission with other things, and this clearly isn't the same. I'll have a look at the download page again and see what I can figure out. Home Lander (talk) 22:25, 13 July 2017 (UTC)

OK, so I just tried the 64 bit installer again, and it did the same thing. It happens as soon as I try to run the installer. This isn't the highest performing machine ever (laptop with 3 GB ram) but it virtually never bogs down like this. Home Lander (talk) 22:34, 13 July 2017 (UTC)

FWIW, the message I'm receiving when opening old Huggle reads:

There is a new version of Huggle available: 3.2.0. However, the updater wasn't able to identify your operating system or has no detailed update instructions for your version. Because of that you will need to perform manual update. Please visit https://meta.wikimedia.org/wiki/Huggle/Download and find a suitable download for you.

Home Lander (talk) 22:39, 13 July 2017 (UTC)

Yes that message is OK, so you get this performance problem when you start installer, not huggle itself? Or do you get it when you start huggle? Does it even start up? Do you see login screen? Huggle while on login screen shouldn't use more than 50MB of RAM and CPU usage should be pretty much idle, because it doesn't do anything but receiving messages in the event loop, just as any other GUI event based application, which I believe is every Windows application. It does however use OpenGL acceleration for web page rendering, just as Google Chrome does. That is only thing which comes to my mind regarding graphics / driver issues, but that shouldn't start happening until main windows gets loaded, which is first windows to instantiate browser components. Petrb (talk) 08:30, 14 July 2017 (UTC)

Correct, I get this as soon as I open the installer for the new version. Can't get it to even start installing. The old Huggle version (3.1.22) runs fine; I virtually never have any performance problems when using it, though one thing I have noticed recently is that the user whitelist in 3.1.22 does take a longer time to load when logging in, then when it does load it goes through a big list of users (including ClueBot NG) stating it's adding them to the whitelist. This seems to have little performance impact once you're logged in, though. Home Lander (talk) 15:31, 14 July 2017 (UTC)

That looks like a problem with installer, not Huggle. You can try getting last nightly build here: http://petr.insw.cz/huggle/nightly just unpack the zip file somewhere, it should work. Petrb (talk) 20:18, 17 July 2017 (UTC)

Petrb, the above link times out for me, whether I try from here or through the page in the below discussion. Home Lander (talk) 21:00, 19 July 2017 (UTC)

I downloaded Huggle 3.2.0 and sometimes is showing this message when I search the user or the article history. This never happens to me before. What this means? What can I do? Thanks. --Hume42 (talk) 00:20, 21 July 2017 (UTC)

Hi, this is pretty old feature which broke some time ago and now it was fixed :). So it's nothing new really. The way huggle works is that it by default gets all edits in real time, but fetches the history of edit only when you open it (to ensure that history of page you see is fresh). The thing is, by default option "Switch to last revision in case currently loaded edit is not last revision" is enabled. This option does exactly what is says, because that is what most people want. In case you happen to load revision of a page that is not top edit, it will jump to top edit. To prevent you from doing anything with the intermediate version it display "hold your fire" and disable editing features, until top revision is loaded. If you disable this option in preferences, huggle will stay on intermediate version of page history, but you probably can't revert from that point as rollback works only on top revisions, also if you see vandalism which is not top revision it's most likely reverted already. Petrb (talk) 09:52, 21 July 2017 (UTC)