@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.

In T194400#4719898, @D3r1ck01 wrote:

Is this still not fixed? Even something as trivial as this?

I'm asking per discussion above, and yes it's trivial but do we need it? Maybe people specialized in this domain would give a signal? :)

Why not Special:PermanentLink?

Please note that both of us (Alaa and me) are completely new to SecurePoll stuff! Tho I don't expect this to cause any delay if we're educated.

For the Korean Wikipedia, the change was deployed as of the Sunday (28th).

I don't think we are doing anything with that anytime soon (with the upcoming test), but I was pointing out that WMF has installed the extension without any community consensus, made no attempt to let the community know about the extension (so they can be used) - except the small snippet of Tech News in sometime during 2014 "GettingStarted now available on 2* more Wikipedias", then now discussing uninstall. Well, what was done is done, though.

In T206374#4702087, @Trizek-WMF wrote:

In T206374#4699296, @revi wrote:

Nobody has informed Korean Wikipedia that this extension was available. Provided we knew about the extension, I would've bring it to the community attention to use them.

You mean to enable it?

In T206374#4698312, @kostajh wrote:

1. GettingStarted extensions
   
   GettingStarted is enabled on Korean wiki, and it is configured to load a copyedit tour after account creation (you can see what this looks like on enwiki by going to https://en.wikipedia.org/wiki/Main_Page?gettingStartedReturn=true). However, no copyedit task is defined in the configuration for Korean wiki, so the console shows Failed to request single page for task type "copyedit" and no overlay is displayed. We might want to consider uninstalling GettingStarted on Korean wiki.

Variation A

Care to clarify about "Enwiki-only topic"? Is this about "(Your wiki name)-specific topic", which just happen to be "English Wikipedia" in this example or does it really mean "English Wikipedia" and nothing else? If latter, what is "enwiki-only topic" in Korean Wikipedia?

P7718 is the sign pursuant to User:-revi/GPG, just in case.

This should be the first to be deployed or otherwise super prioritized, we've just hit.

In T207306#4679157, @MMiller_WMF wrote:

But the open question is for @revi: are there important external links to newbie materials in Korean Wikipedia? Either to online courses, videos, or social media?

In T206376#4679913, @Trizek-WMF wrote:

Use translatewiki.net

• Pros:
  • we can open Personalized First day to more wikis almost when we want because translations would be ready (the translatewiki community is really reactive)
• Cons:
  • for now (and until fixed, WIP), sync with translatewiki is only done once a week through the train

IIRC Stewards are admin on at least one wiki right now, so I'd assume admin's strict rule wins over steward's rule...

In T197150#4281032, @Rxy wrote:

I'm not sure, but If you assume this apply same logic as password change, must I input password and 2FA for each re-authorize? if that so, some one disable a 2FA IMHO. I like same logic as Google's implement. Also phabricator's high security mode. Current OATHAuth does not supplying option to bypass a prompt for "Trusted devices".

I don't feel comfortable using my volunteer account for work reasons (already discussed with Benoit and Marshall this week) and even if I felt comfortable, Korean Wikipedia currently has problem with IntAdmin policy and as a result there is no IntAdmin. (And I'm not allowed to use Steward access there because kowiki is homewiki)

List is now complete.

List of Wikiprojects by activity: (incomplete right now) 사용자:Revi (WMF)/LOW

I know how :) I just wanted to check if I need to make additional span tag to make it look like an plainlinks.

One thing I just remembered is that the call-for-mentor checkbox kinda implies you (WMF) may share email with mentors so that mentors can contact mentee, which is probably not the case here.

Korean Wikipedia exclusively uses the internal link ([[Blah|Meh]]), does this mean we have to convert it to [https://(snipped) Meh]?

kowiki one provided by Urbanecm is correct one.

IIRC It is a gadget to link Commons file to Commons, not a configuration.

1 week with "nobody cares", this is good to go from usual Wikimedia-Site-requests perspective.

Please know that shouting is not good manner. Read the Phabricator etiquette (and the following Code of Conduct).

Probably this, and the user is probably referring to the Preferences > Site > Project 's "Wikia".

@MusikAnimal Completely forgot about this.

Red/Green idea came from the diff's red/green, I dunno how colorblinds deal with that part of MediaWiki? (Maybe bold the changed part and/or the coloring?)

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.

Not a bug.

I don't know about peachy so I'll leave the testing to Steinsplitter. Though I'd like to have another bot waiting for archival if our primary one fails.