It'll take a while until the changes appear on scowiki though. If urgent, we can cherry-pick to wmf.22 now but maybe we can let the MediaWiki train take care of all of this for us :)
on #wikipedia-es we've set +q $~a so unregistered users cannot speak. We've also Sigyn in the channel with +o and BanBot helps issuing bans for the offending IPs for some time. So far it's working, although they keep comming :/. I also suggest adding wmopbot to the channels if you don't have it so wikimedia-ops can monitor in case nobody is around.
Pretty sure the last time I generated captchas for beta I did not use those words
@revi As partial colourblind myself, I can tell you I have difficulties sometimes :-)
Thanks for clarifying. Shall I file a task to disable es-formal, nl-informal and hu-formal labels as well?
Tue, Sep 18
I did some tests today. I could add a label for es-formal, so I'm not sure if this is working as expected.
While logged out I indeed see the error message reported in this task.
I see the topic and page is already deleted. But accesing the Topic linked above I see a deletion template (archived history?)
I am good with the proposed new format, with one additional info: display what right was added/removed with green/red display (temporary right expiration change should count as added). It will help identifying which right was modified.
Examples can be found in past commits (also RELEASE NOTES needs to be made for these). I can volunteer to watch this task and related commits, and help if needed.
Okay so I have a random list of 3251 words. Shall I upload a patch with them?
Mon, Sep 17
Okay. How many words would you say would be appropriate for beta. A sample of 5,000 words for the words file would be enough?
Please don't tell me we're just using these three for all account creations.
We currently have to do this, which is using indeed the reason field: copying the default text and adding the Phab ticket. Being able to keep the default text and just adding |task=Txxxx would be more elegant IMHO. I'd do the change myself if the template syntax weren't so complicated to read.
I apologize for not having done this yet, but I'm still waiting for a review in my patch and in the process as I do not want to have a namespace mess with broken titles afterwards. Thanks.
MediaWiki does now warn whether a page is protected when you try to edit it. Does this extension do anything else appart from that?
Deployed afaics. Close? Regards.
This is already scheduled at T203534#4567846. There's no need to open a new task for that unless they missed to do it. The namespace has not been created yet. Thank you.
While we're on Datacenter-Switchover-2018 we ain't allowed to create new wikis. In addition, data such as the type of wiki you want (public, private or fishbowl) among other things are missing here. Thanks.
I guess either @Daimona or @Huji will know better but maybe the db-patches that need to be applied for such table to be created ain't part of update.php. See https://phabricator.wikimedia.org/diffusion/EABF/browse/master/db_patches/. Thanks.
Sun, Sep 16
@Ponani Vandalizing Phabricator is unnaceptable. I have disabled your account.
For me it is working fine, but if it is not for others indeed this is worth investigating.
CCing the current admin.
If you need another one, I can volunteer as well. I have experience at some public and private Wikimedia mailing lists too. Thanks.
Well, code-style fixing and deprecated functions removal is important as well I'd say. If the only issue is with duplication, I'd say we can have a look at it. However I cannot test this on my own because I suspect that, for the bot to work we need some other config files that ain't in the public repo, right?
T105972 is now a subtask of this one.
Sat, Sep 15
Dupe of T105972: Digitally sign AWB?
This is being requested also for Huggle at T105560: Add a publisher certificate for Windows binaries but the main problem here is the price of code-signing certificates (that Microsoft trust), which are prohibitively expensive for an open source and volunteer-run project.
So, to clarify, you want that when somebody checks an IP or user not for the whole standard duration but for a limited period of time (last week, last two weeks, etc.), the logs say so. Right?
Hello. As I've stated on Conpherence the field is visible for all tasks at this moment. Was this the desired outcome or just a side-effect? Thanks.
Fri, Sep 14
Stalling per T137937#2386610, which is still true at this moment; but translatewiki.net translation stats shows 99% of translated messages so that shouldn't be a blocker. Ping @Dereckson and @Nemo_bis just in case. Thanks.