Hello, I am Petr Bena also known as Petrb (my SUL). I am a volunteer developer working on multiple projects, including Huggle, wm-bot and many others
Fri, Feb 16
But it was already activated long time ago, did you hit "Reload" in login form?
Wed, Feb 14
instance huggle-pg was shut down by someone, I booted it back up, this instance hosts the postgre DB for browser.
Thu, Feb 8
now, before we close this we need to check which tasks were finished and these that were not, can be reopened
Sun, Feb 4
Yes, I agree. Don't have time now though to implement this, maybe during hackathon?
Sat, Feb 3
it's available in read only now
Same with Windows 10
Fri, Feb 2
Thu, Feb 1
We definitely need to use what API say but is there even any information like the actual username in response?
does it still happen?
I wasn't able to reproduce this for a very long time, unless there is more feedback from users I will consider this resolved
Huggle is not part of mediawiki core, it's a separate project
of course, anyone who can edit pages on mediawiki and upload pictures to commons can do this.
I am not sure why you ask about codebase (which is at https://github.com/huggle/huggle3-qt-lx). This is a documentation for users, not developers. This task is for update of obsolete screenshot in user documentation (or manual).
Hi, the documentation in question is located here: https://mediawiki.org/wiki/Manual:Huggle
or maybe not.
Tue, Jan 30
Can you show me pywiki bot EventStream so that I don't need to spend 2 weeks searching its source code tree? :)
Sat, Jan 27
I replaced the config page that you copied from enwiki with the official default config, it's much better than the one from english wiki, which is optimized for enwiki only.
Mon, Jan 22
Sun, Jan 21
BTW Huggle on wikidata is pretty cool, did you try it? I did for few minutes, the edits per minute is crazy. Also I noticed that API response time is pretty high! Looks like web servers that handle API requests are pretty loaded on wikidata.
@Addshore I think you could help here a bit as you know wikidata more than me, are there even any warning templates there?
Config is missing warning templates though: https://www.wikidata.org/wiki/User_talk:Petrb
In dry mode I get this, is there anything wrong with these API?
Sat, Jan 20
Jan 17 2018
Hi xmlrcs server was unexpectedly rebooted (due to security patch), so service was temporarily down.
Jan 15 2018
Just in case for XmlRcs maintainers the workaround right now in case the python script hangs, from labs:
T179986 is reason for this
T179986 is reason for this
Dec 28 2017
Yes, let's remove it from GCI for now. I don't speak French :( also it's rather complex thing
Dec 18 2017
Dec 4 2017
Yes it can
Dec 3 2017
yes, restrict for channels and users are two completely different things, it might even be easier to implement if the commands were named differently, like "ignore" or "blacklist" for users
Dec 1 2017
Great, let me know if you needed any help! Also, if you do this within GCI, please claim the task :)
Nov 29 2017
the choice is defined by options for configure script, either it's --qt4 or --qt5
Yes, I can mentor this, but first I need to create a task for this in GCI website
Keep in mind that these students possibly never edited Wikipedia and therefore have absolutely no idea what these things are and possibly mean, each of these terms should be somehow explained in task description:
Given my experience with previous years of GCI, I doubt that we could find a student skilled enough to do this. This task is IMHO too easy for GSoC and too hard for GCI, but we can try if @Framawiki creates a simple explanation of what he wants and how to implement it. By simple I mean simple enough that 15 years old student with 0 wikipedia / huggle experience would understand it, not just me ;)
We might want to create 2 "flavors" of that role though, also one for Qt5, but that is really low priority
Nov 24 2017
I suppose that we host these files ourselves, since many other wmflabs projects depend on them. If not, then by "host them locally" I mean download them from these URLS, place them somewhere in repo and refer to them using relative path, so that they aren't loaded from jquery.com but from whatever server this PHP code lives on.
Nov 20 2017
test3 and test4 even use the same icon :/
wow, these templates auto-translate, so there isn't really easy way for Huggle to determine which warning level they represent... maybe by icon? It would be nice if there was some invisible magic like it's on enwiki, for example: <!-- vandalism-lvl1 -->
If you wanted to do any of this, here is documentation for almost every key: https://www.mediawiki.org/wiki/Manual:Huggle/Deploying/DefaultConfig.yaml
tasks were prepared :) so I am closing this
No response.... I believe it works
Seems fixed in 3.3.4 with chromium
It seems this is fixed in 3.3.4
Fixed in 3.3.4
OK so, I disabled the warning types other than "Vandalismus" as there aren't any other templates than "Experimenty"[2,3]
Nov 19 2017
Yes, I decided to close every GCI task that was imported to GCI website, we track them and this way it's easier to see which was imported already and what still needs to be done: https://phabricator.wikimedia.org/T179983
Nov 18 2017
When the GCI is over, all tasks that weren't finished should be reopened.
Thanks for import, I am going to completely rewrite the task description on GCI site, here is the original:
Nov 17 2017
browsing through docs I found "torelative=prev": https://www.mediawiki.org/w/api.php?action=compare&fromrev=2620781&torelative=prev
@Anomie: first thing that I am having troubles with is that old method required me to only know the revision ID of the actual edit made by someone in order to compare it with previous edit. All I did was to provide current edit as rvstartid and then "prev" as rvdiffto.
So, I got some time now so let's finish this.
Nov 16 2017
Nov 14 2017
So I replaced the old config with new one which is documented pretty well.