As long as any 3rd-party-login still respects the following just like the current login:

@MMiller_WMF Didn't tag for Unbreak now! since you can (theoretically) remove the strings and re-type the word, but this should be solved ASAP.

@Ladsgroup and @Halfak: it's complete. 50 remainings are 'revision not found' when I retrieved the work set.

Translation for the data supplied is complete.

In T215126#4923474, @Tgr wrote:

Have you enabled the PHP7 beta feature?

One thing I noticed in the screenshot is that even the format how we display DMY is also broken. 월 should be behind the M in DMY, not in front of D as it currently is.

Question: will removal of this settings on kowiki lead to confirmed user being able to upload file? That is against the purpose of T85621.

위키백과:깨진 링크 [Wikipedia:Link rot]
문서에 인용한 링크들 중에서 웹사이트가 링크 변경, 사이트 폐쇄 등의 이유로 깨진 링크가 될 수 있습니다....

"영어"[English]:

위키백과:영어의 한글 표기 [WP:Transcription of English into Korean]
위키백과:외래어 표기법/영어 문서를 참고하십시오....

위키백과:오늘의 역사 [Wikipedia:Selected anniversaries]
기념일은 특별한 경우가 아닌 이상 적지 않습니다. 그림/사진은 1개만을 오른쪽에 배치합니다. 그림/사진의 권장 크기는 100px입니다. 사람의 얼굴 등을 배치할 때 가능하면 정면 또는 왼쪽을 보는 사진을 씁니다. 그림/사진 넣기: [[파일:파일이름.jpg|right|100px|파일...

I was unable to find topics (from my inbox) for:

WMF Internal only: Google Docs.

Removed James from assignee since he is no longer working for the Foundation. Someone else from Trust-and-Safety should review this but not sure who exactly will be that 'someone else'.

For the record: No issue @ kowiki.

Just wondering: why not force sitewide/indef blocking when you click 'hideuser' option? That would be less click <_<

@TBolliger: that's assuring. As long as the actual button for 'hideuser' stays in Special:Block, I'll happily leave any backend improvements to knowing devs :-)

Hidden users are within block's scope (I'd argue) since they usually violates local policy (only reason they're allowed to hidden under OS policy - is usually blockable offense as it's username like revi is a fuc*king b*tch living in Some Place. We do not want those accounts to edit, so unless other compelling reason to move hideuser off block, I'd say it is block's job.

Deployed. Resolving — again!

Scheduled for deploy on tomorrow's European Mid-Day swat (2100 KST) because morning swat at 0400 is too morning.

Changeset 483996 is marked [WIP] and not submitted for SWAT because I don't know if Help Panel can accept interwikis.

Created a patch (attached to T209467: Help panel: Determine what text and links to show in the help panel on KO wikipedia) to work on.

Also can repro on Korean Wikipedia where I have issued hideuser block in the past.

It probably is a good idea, but I don't know enough Abusefilter to write such complex logic. I'll ask an experienced local user if he can do that.

In T209297#4867640, @MMiller_WMF wrote:

I think the value you meant to put in cell E34 is https://www.mediawiki.org/wiki/Help:VisualEditor/User_guide/ko#각주_편집하기

Is that correct?

In T213186#4866905, @SBisson wrote:

In T213186#4866900, @MMiller_WMF wrote:

@SBisson -- since help pages exist for the rest of the year, is there a date that we have to remember to do something by? If so, what is the date, and what is the reminder? I'll put it on the calendar.

December 2019: Make sure kowiki help desk monthly subpages exist for 2020 (See T213186)

(Sorry for the delay)

I just checked the subpages for this year is complete, so I think this should not be blocking for the near term.

Text and link for the help docs has been decided and posted on spreadsheet.

It is highly discouraged, and should be avoided if possible. I don't think community will like that.

Usually created in advance, but there's currently no bot to automatically generate it so if someone forgets to create the page, it could be missing…

(I know this has been agreed on while ago... but want to voice a different opinion)

@kostajh mw:Help:VisualEditor/User guide/ko will be it.

@kostajh Question: We're planning to use mw: interwikis on the help URLs, will it be handled correctly? (Well IIRC we have an eventual goal to make it locally configurable but we aren't in that stage yet)

SITREP: Initial data is on the spreadsheet. I'll translate VE guide on MW.org (preferably) before the Christmas, and apply it onto the spreadsheet.

Heh, interesting that this only occurs on mobile: I had to take a screenshot while logged out since if I were logged in, I will just see the username instead of the bug. Also, it could be oversight, not just sysop-level removal.

<_<, thanks, Andre!

Hi, is this change deployed? Since I'm not sure... :-)

And I can't edit on enwiki, SecurePoll says me to go to votewiki to edit.

The votewiki one. "Edit" on votewiki 504 time out

Can reproduce with enwiki ACE, even tho I'm not sure if I am supposed to be able to edit (at least I can click "edit", so it's safe to assume I can!). I noticed this yesterday afternoon (KST).

New bot is approved and working fine. Calling it resolved but I hope someone can make some replacement bot so that we have a redundancy (and not having to wait for around 5 months to get a bot replaced)

Valerio, as long as file is below 4GiB (or 4GB), it is 100% acceptable to upload any file they wish (provided they are fit to Commons policy, which is outside scope of this ticket).

Beta Labs is not happy with me - my first session failed and I needed to create another account, which prompted me to log in again immediately after I created an account and clicking 'done' prompted me to log in, again...

Changes made less than a minute ago.

I'll ask community opinion @ VPT (whether this behavior change is fine to them), and will proceed with Option 1 if nobody cares (tm) until Tuesday KST. Is this fine to you or do you need this done quicker?

Preview showed me this. (Sorry, mobile) some sort of Regression , I guess? I never saw this kind of stuff.

Confirmed.

Big internet companies (Naver, Daum ...) generally do not do in-context helps found at the presentation screenshots: We don't know why (hehe).

I honestly do not think partial block won't be used just because it's seen on userpage/talk/contribs (hereafter $place). It's already very publicly seen on RC, Watchlist, logs, and anywhere it's logged. And the same things can be done by putting the "partial-blocked" template on user page, which has been done for almost all siteblock on Korean Wikipedia until 2017.

If the user is blocked (partial or sitewise), they're blocked from doing stuff. It just adds more work for admins&co. who probably will need to verify they're partially blocked from time to time. (Block interface might display that the user is partially blocked but non-admins don't have information.)

(By the standard set, I mean @jrbs' version.)

• I'm fine with the standard naming scheme.
• Requests are handled thru OTRS, this is discussion-only.