Two problems:

• It should not be linking to articles about the dates (like [[ko:1919년]] / [[ko:1월 1일]]) as the Korean Wikipedia's Manual of Style demands that "if the event cannot be linked from the dates page, it should not be linked to", and since algorithm cannot guess whether it is link-able or not, it should not link.
• Disambiguation - logic skipped https://ko.wikipedia.org/wiki/%EB%9D%BC%EC%9D%B4%EB%B8%8C%EB%9F%AC%EB%A6%AC and went to [[ko:라이브러리 (컴퓨팅)]].

IMO burden of proof is on the one who makes the claim, not us. /shrug

If nobody is around for testing at that moment, maybe ping me and I might be able to grant patrollers for few hours.

In T244165#5883590, @Bugreporter wrote:

Or acl*security_stewards will means stewards with no other ways accessing security tasks (but this means managing members of this group will not be easier than managing acl*stewards.)

In T245201#5883301, @mmodell wrote:

btw: I really don't like the the acl* convention because it doesn't normalize consistently. I really don't see why we can't use only the icon as the indicator of ACL projects and then we won't need a naming convention.

In T244165#5883579, @Bugreporter wrote:

acl*security_steward

We already have acl*stewards. Is it nececessary to make a second group? (per T131766, T163260 and T217361 stewards may often require accessing security issues)

RESTBase API is displaying the same thing as Page Previews.

In T234617#5813166, @aborrero wrote:

*snip*
My initial approach was to introduce DNS subdomain-based routing in parallel with the 'legacy' routing (URL-based). Tool owners can use both addressing methods during a transition period.
During this transition period, users are encouraged to make sure their webapp code is able to work in a new domain and URL: from tools.wmflabs.org/$toolname to $toolname.toolforge.org.
We can drop the the old routing mechanism when the transition period is over.
*snip*

If you know the target's email address (cough DB cough) you may be able to utilize email blacklist, but 1) it is public, so everyone else will be able to see banned addresses in raw format (and based on other logs, infer who is who) and 2) I'm not sure if this even works (even on wikimedia), because I have never tested it.

Base, HakanIST, Matanya, Wim_b are stew.

Note that the NMT (used for Papago) is on entirely different API endpoint of https://developers.naver.com/products/nmt/ (docs - both unfortunately only in Korean). NMT has 10,000 chars/day limit, probably needs some deal with Naver Corp?

Merged, deployed, done!

I don't know about Chinese IME stuff, but Can Reproduce on Chrome v79.0.3945.130 (stable)/Windows 10 Education Version 1909 (Build 18363.592). Using default Microsoft IME.

GIPBEs does not exempt you from the local blocks, check if there is local block against that IP on the project you are editing.

Only two accounts (pywikibot-oauth and pywikibot-test) were granted GIPBE, and you must authenticate as one of the accounts to enjoy the IP Block exemption. We are not willing to unblock Amazon Web Services/Google Cloud/Microsoft Azure/etc etc IPs as they are frequently abused for provisioning VPN node to vandalize Wikipedia.

GIPBE duly granted.

@Majavah If you are fine with me SWATing, I can do it for you.

Maybe provide a key like $userpage, $usertalk, $contribs, and convert it to wikilinks on saving?

In T226727#5592292, @Qgil wrote:

I tried to find information about https://lists.wikimedia.org/ policies and governance in order to know what is the benchmark, but at least after a quick search I have failed. If we have this benchmark, then we can check what is the difference with Space's policies and governance, and then we can discuss about specific changes.

• One user generally inactive, removed.
• Two users are not responding to questions:
  • 책읽는달팽 (R) is not responding to the question left @ 2019-11-28 and onwards. Had not edited for a while, except 3 edits on January. Should this be considered for immediate removal or followup?
  • 호로조 (H) has not edited since end of 2019, and question dated 2020-01-10 is awaiting response. Will follow up.
• Otherwise they had not received a question (because they recently signed up) or they are responding in a resonable timeframe.

I'm not angry at you, I just think you should not be editing /qqq via gerrit. What is done is done, indeed, and undoing what-is-done to prove a small point is pointless, so I was telling you you should rather just edit twn. I'm sorry if you felt I was angry at you.

MediaWiki.org Localization#translatewiki.net:

Only the English messages and their initial documentation must be done in the source code.

It is less efficient (I don't think the speed of git repo commit is important at all when the authoritative source is twn) — you have to wait 2 seconds (waiting for twn to load) versus at least 24 hours (max 3-4 days) — as a rule of thumb you should edit everything that is not en.json via twn.

Actually no.

In T226950#5759466, @Zoranzoki21 wrote:

How is possible to loginwiki is so big??

/qqq doesn't need a patch, just edit twn as if it is a translation.

For the records: I don't use cvn-unification that often, but I always get pinged by someone who uses it whenever the bot is down (within 12 hours, usually).

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)