Well, it is only true if there are namespace dupes :)

@Pginer-WMF, well, I use them in at least 3 scenarious:

The editor part does work, though I would still prefer a message that explains what those json configured thing actually expects. But I have stumpled upon a related bug, when I now opened the link to edit from my phone, mobile frontend version loaded. It shows an erroneous message saying that the editor will now load. Upon clicking the link there the second page opens which does have the error message.

NamespaceDupes.php is currently disabled

For the English Wikinews I see only one affected page,

{
    "pageid": 160790,
    "ns": 0,
    "title": "BBC: Ethiopian famine aid 'siphoned off' to buy weapons according to rebels, report"
},

but it would be a good idea to run the script in every single wiki as I assume there would be more wikis affected.

The same problem was in ukwiki, there were two pages with BBC:, I have just moved them manually via API (BBC: Дикі Кариби, and BBC: Life).

The deployments on ukwn and ukwq, as well as on Meta are still not undone. Opening the task back.

If possible, have a sense of quality: how many of the translations get reverted, percentage of modifications from the original suggestion, or similar.

@ovasileva, if you lack people in your team who are familiar with community processes I suggest you post a job posting for Wikimedians to apply as consultants. I am not sure why volunteers should be spending their valuable time to facilitate you in your paid work comprising pushing an unwanted product to the communities.

it is possible to add a comment without changing task status

As the other ticket was merged in I will also copy my comment from there,

I found that there was a notification on https://meta.wikimedia.org/wiki/Meta:Babel#The_Vector_2022_skin_as_the_default_in_two_weeks?_ . That is no place for such major sitewide change, it should have been an RFC instead. Babel is saturated with all different kinds of newsletters and nobody discusses important configuration changes there. Here is an example of RfC to introduce a configuration change: https://meta.wikimedia.org/wiki/Meta:Requests_for_comment/Adding_a_local_rollbacker_flag_or_alternatives . It would have been highly inappropriate to just write "we are having this change done in two weeks unless anyone notices this discussion and says no" on Babel. Please stop disregarding community processes and undeploy the change.

I insist on having the deployment rolled back from Ukrainian Wikiquote and Wikinews where I am an (interface) admin. There was an explicit NO to the proposal https://uk.wikinews.org/wiki/Вікіновини:Майдан#The_Vector_2022_skin_as_the_default_in_two_weeks?_ , https://uk.wikiquote.org/wiki/Вікіцитати:Кнайпа/Архів/2022#The_Vector_2022_skin_as_the_default_in_two_weeks?_ in both cases, nothing has changed since the previous proposal, but unfortunately what you, WMF guys, decided to do is to go ad nauseam and use attrition against the community: you posted the same wall of English text to the wiki where only few people understand English again and used no reply to it as an excuse to deploy this. If this is not rolled back I intent to use my Interface admin rights to roll back the changes with a hack, as as it is mentioned neither I nor other community members have the capacity to deal with all the changes that need to be done to adapt to the new skin.

There was no community consensus for this configuration change, why was it done?

resulting in «About half articles from CX2 have been reviewed as "Bad quality translation"». We analyzed the data further finding the deletion deletion rates for translations in the current (9.5%) or past year (6%) for Japanese Wikipedia were not matching the community perception

What can be more encouraging than to have your ticket closed as a duplicate of a bug from 14 years ago :)

Passer by comment, the paste name does not turn to a link for me so I assume it is private enough at least for that

The distinction is local rights are done via code, and global rights are done on-wiki. Yes, this is bizarre

Well, the premise of translate adminship was always that people need to go through a process to get those rights, such as to confirm and demonstrate that they are familiar with the relevant documentation. In some wikis admins can self-assign the rights, but I do not see why this should extend to global sysops, it is unlikely that a vandal would happen to be a translate admin and thus a translatable page would need to be deleted for CVN reasons.

Isn't "user profile" the most appropriate tab for something like this out of the existing ones?

I am getting tired being bullied by paid staff. I will reply when I have time, that might be in 5 years.

Hmm, that method signature would not get worse from getting another flag if that is what it is all about. (I mean not for me to criticise the code in the language I don't even know, but wtf those flags 😅...)

NoP is a global policy. Unless there is a global RfC to make an exeption, this should be declined. Boldly closing.

In enwiki only Create pages in the main namespace is restricted AFAIK, what is proposed here, at least the way the task is worded, seems to be several orders of magnitute more harsh.

What is a section?

@Tacsipacsi, well, it still have to be trusted users. Not to stray into BEANS too much, but in 2 weeks there are general elections in Cambodia and Spain. Imagine the Khmer and Spanish banner text saying something else during the right timing than the call for Wikimania registration. This is still a very sensitive access even without an ability to insert custom HTML let alone JS magic.

It is interesting that you have now published to live all open translation for this banner

WMF does use it too, I have just looked through my Meta ns8 contributions, and they do happen to be mostly hundreds of edits publishing the banner translations: https://meta.wikimedia.org/w/index.php?title=Special:Contributions&end=&namespace=8&start=&tagfilter=&target=Base&offset=20230302160107&limit=500 . Among those I have found at least ToU update and UCoC banners. And that is just the banners I have personally been publishing the translations for, there probably were more.

It is very unclear that it must be so

It is very unclear that it must be so, but that said it still works wrong, because my userpage does countain the Facebook link (but not the Telegram and Last.fm ones).

@RobinLeicester, are you familiar with the capabilities Kartographer has? https://www.mediawiki.org/wiki/Help:Extension:Kartographer

@Pleriche, well you can always get better results by preparing a page for translation manually. The special page is rather a convenience feature...

Adding Regression as there is a clear regress in the design from this change.

Was there a community consensus for this change? The new look is just humongous. Here is a piece of the interface from w:uk:4 Веста:

Thanks for the answers :)

I might have missed some questions and answers, but let me ask my own:

Quarry doesn't get a lot of support

Then provide it with a lot of support, duh.

@MarcoAurelio, hm, but this is quite a small page

@Tacsilacsi, I don't know what it looked like before, but I don't see any underscores now:

Is there any progress here? For me as a Ukrainian it is sad to see that the maps maintained by Wikimedia Foundation are still insisting on the Russian narrative that Crimea is part of Russia.

(Just in case, because this and many of the subpages are translatable pages this means that Translations: namespace pages also need to be renamed; Though I am not sure why one would do that via Phabricator (so I am assuming a shell script execution is expected?) rather than just making the moves via the normal GUI)

@Quiddity, I think it is fair to guess that rollout will not go through on 15th given T336556 , tech news probably need to be tweaked

I have never read these security reports, could someone tell me why is canvas repeated twice and d3-array 12 times in the outdated packages table?

This guide provides the most comprehensive detail on migration from Vega 2.

Not that it is important but just had it again on [[:uk:Вікіпедія:Запити на перевірку користувачів]]. A reload has fixed it, the problem also didn't appear on other pages I opened.

I do think it is a good idea to link to the policy, so I think we do need it. Though I guess in reality it would also be good if there was a way to link to the requesting wiki's local policy too...

It appears that the mobile App reuses the MediaWiki:Notification-link-text-* interface messages that are also used in the desktop notifications. According to https://www.mediawiki.org/wiki/Help:System_message#Avoid_message_re-use messages should not be reused accross different purposes. In this case while the translation is likely to be technically correct in both usages, if there is a technical limitation of the length in the mobile app there should be separate messages for it, with the restraint clearly documented in the respective /qqq documentation pages.

But really from my perspective this is a bug and regression introduced by WMF, rather than a site request </wmf bashing>

Well, I just follow the policy, and the policy states that

(If only WMF followed policies too :( )

Scripts to calculate eligibility is a normal thing. One also has to do very similar things to complile some MassMessage lists to send out invitations to a context that is happening for another year, etc. Mostly in bigger communities there is expertise to do that.

Or perhaps we should be more liberal with considering the use of CentralNotices..

/me expresses unhelpful grumbling about where and when the web has turned wrong way for such simple forms to require JS nowadays

The idea is good, but we will not be able to convert all graphs quickly.

Actually yeah, I am wrong in the comment above, T334940#8791797, regarding why the new tracking category was created. As there is no sensitive information there I will just quote a relevant part of @Lucas_Werkmeister_WMDE's original message from the private task:

@stjn, all graphs created via Extension:Graph (<graph>) are disabled. Some wikis also use graphs created via some custom means, such as CSS, or timelines made via Extension:EasyTimeline (<timeline>), those still work of course.

@Iniquity , as a matter of fact it is now merged it seems, thanks @Lucas_Werkmeister_WMDE for the work!

But in general, yes, some kind of intelligible description is needed instead of emptiness.

The description is worded very poorly:

+1 to have the default empty.

@Tgr, in the public task @Seddon has promised an announcement

For the record I have already posted in @WikimediaAnnouncements in Telegram a few mins ago, https://t.me/WikimediaAnnouncements/146 , feel free to edit/replace it (and feel free to poke me for admin rights in the channel if you don't have them)

Yep, I have written in the non-public task that I think there should be a message right away, rather than only in Tech News next Monday. I am thinking about sending one myself, but I hope WMF comms would do that and I am afk for a couple of hours anyway.

@Iniquity, given what is going on in T334895, the non-public task where the issue is tracked, I don't think it is likely they will be for at least couple of days.

@Msz2001, graphs are disabled at the moment following a security issue tracked in currently non-public T334895

Given the massive impact this has (as opposed to Score that was only used in a few pages) I would say there has to be a communication right away, rather than just next monday in the Tech News. People would obviously compain a lot.

Is it possible to return an interface message or something? So that wikis either customise it "You are supposed to see a graph here, but..." or leave empty.

I didn't know the lists could be shared. There definitely has to be a way to redact content of the name and description of the list, perhaps at least as crudely as w.wiki links can be deleted by stews.

@MusicAnimal, oh, I didn't know they are (was there some way of knowing that but through the config file linked?). I guess it would make sense to verify whether they are indeed counted, but if they are then this task is redundant (and I will make tasks about other admin actions instead 🙃)

@Ladsgroup, yes, that's the thing I was thinking of

@Aklapper, oh, makes sense, I didn't check their global account :) But hopefully the comments would be of use to someone genuine who might try look to do the same thing in the future.

@Aklapper, how would that policy help with an affiliate wiki? I think there was another page with regards to those.

Creating new wikis is a 1-time thing. There are a lot of things that need to happen when new wikis are created. We can update documentation about how to customize Cite rendering.