In T287322#7245481, @chungchungfei wrote:

In T287322#7245473, @Sanmosa wrote:

The consensus is NOT obvious at all, and I even see some comments which are strong opposes. Some users ignored those comments while handling the proposal. Please DO NOT add extendedconfirmed user right and extended confirmed protection on zhwiki until a clear consensus is formed.

Are you sure? who are strong oppose? since the new discussion is open I agree hold on until a clear consensus is formed.

The consensus is NOT obvious at all, and I even see some comments which are strong opposes. Some users ignored those comments while handling the proposal. Please DO NOT add extendedconfirmed user right and extended confirmed protection on zhwiki until a clear consensus is formed.

In T30441#6213240, @Ladsgroup wrote:

Oh, we renamed one wiki only (be-x-old to be-tarask) years ago and it's still causing issues (last week its interwiki links broke altogether) and for example lots of it doesn't still work (like T235505: Rename be-x-old as be-tarask in Wikidata). Renaming a wiki is almost impossible and really hard. That being said, if we revisit the problems we might be able to do it better this time.

• The DNS fix is not hard, we can redirect the traffic of yue.wikipedia.org to read zh_yuewiki (the old db name), it doesn't solve the wikidata's problem and some other bits though.
• Fixing database is the tricky part, We can duplicate the database, close the old wiki and ask people to use the new wiki and once we are sure everything works fine, redirect the DNS traffic and drop the old database (hopefully this would take only a couple of hours). Does that work?

. It might require a read-only time period for all of small wikis (s3) plus collaboration with the cloud team to get it fixed in toolforge replicas. Duplicating the database might cause some unforseen side-effects, let me give an example, imagine some parts of the database store the db name as prefix for example when hashing the password. Just duplicating the database wouldn't be enough and would cause every one to lose their passwords (this wouldn't happen at our setup because we don't put the wiki's db name in the password hash). I should scan the whole database to see if there's anything obvious. But I'd say let me ask our DBAs like @Marostegui to make sure duplicating the database would work because they will be the ones who will do it.

There is a local discussion on it. It may probably make a consensus.

Referring to the discussion deryckchan mentioned above, I can see that a strong consensus is made in Cantonese Wikipedia. I hope that the renaming will get done as soon as possible if there are no technical issues.

I am afraid that evaluating the user rather than the content is unavoidable, unless CX usage is completely disabled for all people in zhwiki. That's already the minimal impact on the community if the latter cannot be performed.

In T193983#4294561, @Urbanecm wrote:

Can do.

"zh-my" is still blacklisted by Chinese Wikipedia site for unknown reason. How to solve?

Please enable zh-my as soon as possible, and also zh-sg should change its name to 新加坡简体.

As @Wang_Qiliang had mentioned me, I shall translate the conversation into English:
Stang: Is there any consensus made in the discussion of enable zh-my language localization?
Sanmosa: Stang, it shall be certain. As I can see in the discussion above, most of the users joining the discussion agreed enable zh-my language localization.
Stang: Now we start a 7-day publicity, please raise if you have any comments.