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
Mon, Nov 20
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]
Sun, Nov 19
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
Sat, Nov 18
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:
Fri, Nov 17
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.
Thu, Nov 16
Tue, Nov 14
So I replaced the old config with new one which is documented pretty well.
Mon, Nov 13
Just a little update, the extension Flow was merged into master branch, so Huggle de-facto does support Flow content model to a point.
BTW is there any wiki or any plan for a wiki, where flow is default for IP users?
Well, it's not hard for me to make Huggle submit the target user name as parameter to template, but it won't work for existing templates, each wiki that has Flow would need to update all of templates that are being used by Huggle, some of these templates are not dedicated for Huggle only, but are rather standard templates and they all probably use this magic word, so in that case they would need to be copy pasted to version which supports Flow.
Sun, Nov 12
Does anyone from flow team have a clue how to modify the templates so that greeting contains the name of user?
Sat, Nov 11
Meaning we might need to adapt the current templates we have so that they could simply be substed on flow talk pages
So, first working version produced this: https://test.wikipedia.org/w/index.php?title=Topic:U1r2zu0wdqr16wip&topic_postId=u1r2zu0xxv6oj38h&topic_revId=u1r2zu0xxv6oj38h&action=single-view
That mean, we should keep this tracking task open until end of GCI, even if all tasks get imported
Each task that was imported was closed, if it's not done during this GCI, we can reopen it
https://www.mediawiki.org/wiki/Manual:Huggle still look like an index for big amount of tiny subpages, so I suppose it's not done, importing to GCI
I am slightly confused, you said you fixed this task and now you want to mentor it? So I suppose this task is not fixed?
So, here is the text I am going to copy paste as header for every task:
Fri, Nov 10
Thu, Nov 9
I started working on this in this branch: https://github.com/huggle/huggle3-qt-lx/compare/flow
Tue, Nov 7
An example python code from wikimedia stream team which is capable to hold a working connection forever and handles all kinds of connection errors would be great.