In T239695#5815917, @Trizek-WMF wrote:

Yes. Please inform the community that we would need to work on it at some point.

Care to define the definition of Activity?

• Few hotfixes (including missing translations) deployed (Revision 25588448, 25588451, 25588609, 25588628, 25588634, 25588641, 25588667, 25588680) - I have a reminder to delete them once the train has stopped at Korean Wikipedia station :P
• I get different results for re-try. Some topic has less article (i.e. biography has 83 to draw from), so it might be more likely that people will notice result reuse if they try getting list quite often, though.
• Quality seems to have significantly dropped: at least 3 mismatches in all topics. (Geography got 0 correct articles in first 10, history got 4/10, music 4/10, Sports 2/10, literature 2/10, religion 2/10, pop culture 4/10, entertainment 5/10, foods 2/10, biography 4/10, military 7/10, economy 3/10, )

Community Proposal to change the Help Desk format to one of the following:

We, at Korean Wikipedia, used the following CSS hack to avoid submitting (and waiting for) configuration changes: maybe try this one? (According to our records, this was last used in 2017 so I can't guarantee it will work in 2020.)

.mw-wiki-logo {
	background-image: url('{REPLACE HERE WITH upload.wikimedia.org THUMBNAIL LINK}') !important;
}

Did a quick skimming: Geography had 3~4 (depending on how generous you are)/10, craft-hobbies had 5/10, but otherwise 7~10/10.

It is probably configured via Mediawiki namespace page to show that interface message.

Renamers know that the notes are public.

Meta has two blacklists: there is a global one(in main NS), and another one is local one (in MW namespace). You can't realistically merge them.

Config LGTM after small fix, topics are generally in bad shape: Popular Culture and Entertainment only had more than 5 good matches; rest (analyzied at this moment) were generally 0-2 good matches.

☑. Those I did not comment on was good link.

✅

✔

Yup.

Help page for 2020 is now created, so it should be safe for next 12 months.

With the CentralAuth being affected, I assume global LOCKs will be unavailable, but does it also affect global BLOCKs? (Locks for account, BLocks for IPs.)

(Contacted Alaa privately: He speaks Arabic and is also S, admin, int-admin @ arwiki.)

Catrope's version LGTM from my eyes. Nothing cut from the above.

Disabled https://phabricator.wikimedia.org/p/SokoteZaman for spamming (looks like autogenerated) security bugs without responding to the questions.

from the removed task description

Host: wikicod.ir

You need to specify the domain name.

LGTM; sorry for the delay.

When I first tried, it showed something behind the checkbox, so I closed it without saving it.

Deployed. Closing.

I thought this was supposed to be closed but seems I forgot it. (Work completed, result discussed on Wed)

License is provided via COPYING file, not the LICENSE file as GitHub demands.

Part of T212268: Make the abusefilter-blocker user not be a sysop: See tech news 2019-02.

Hold on while I grab the task... I recall there's a task about that.

[[mw:Extension:AbuseFilter]]

Sounds like an abusefilter account?

Biography and electricity are homonyms in Korean (both are written "전기") and it seems like biography is polluted with Electricity.

In T235321#5570640, @Ammarpad wrote:

If a user requested a rename at their local wiki (and it's accepted) that's a valid request; irrespective of whether a renamer on GlobalRename queue declined their request.

I think it was something related to #flea-attacker-mitigation which included a full swing on phab? (CF T198974: Rate-limit is too harsh and affects human users)

I'm assuming the English label is "Link" based on the image below - am I correct?

In T117736#5545298, @stjn wrote:

Having tried using the new form, not having a username autocomplete on the first field is a grave omission that can’t be explained rationally (Firefox 69 if that makes a difference).

I mean, it is technically correct to say "It's not hidden by default" but given that most people don't browse it that way (rather than going to Special:contribs and putting their target, people click the Contribs page from somewhere else which means their forms are pre-filled) it is practically hidden by default.

In T117736#5545101, @Volker_E wrote:

In T117736#5544964, @stjn wrote:

I think the assumption that people won’t use the form on 95% of their visits is incorrect.

I didn't say that anywhere. ;) My point was that there are different use cases for the same form/view, and we tried to address them in our approach, by making the form not collapsed if directly accessed and collapsed when the parameters target, start and end date are set (also on subsequent pages).

@kostajh Where is the translation coming from? Can't we just use English as we all know English? (The last one "모래밭" is plain gibberish)

Can someone make this pref configs (or a JavaScript snippet) so that I can disable this automatic collapse? Do you want a ticket? I posted this on Tech#Reverting the new "collapsed search interface" on Special:Contribs and digging thru MW commit log pointed here.

Yes, all should be good.

For myself: Riot Web is licensed under Apache-2.0 license so screenshots should be fine for Commons. (I'm working with Tgr for the docs.)

I cannot use password login because I am required to use 2FA (mandated by WMF Security's policy for super advanced rights (like Stewards and/or Interface-Admins, which both applies to me)) and with it, I don't think password-based login would work.

In T27471#5342832, @DannyS712 wrote:

Tagging special pages for wider feedback on conversion to a full special page

Meanwhile duly noted!

Mostly done - one or two topics have missing article id 5, those are that I couldn't think of 5th topics.

Content of user-password.py: (u'-revi', BotPassword(u'Pywikibot', u'[REDACTED]'))

I use one directory for -revi, and another directory for Revibot. Revibot doesn't hold any adminships so it cannot be used to replicate anything, so I didn't include it here.

Latest (As far as I can recall) namespace changes on kowikisource was T183836: Create a namespace for Korean Wikisource, FYI.

I have a plan to create a bot (or just a script) to create monthly subpages in advance (to avoid this kind of problem in future) but for now I'll have to do it manually. :-p