Hello @Jdlrobson, I have added this:

An update was made on March 18th 2024 to how various projects load site, user JavaScript and CSS in Vector 2022 skin. A checklist is provided for site admins to follow.

to the current Tech News draft, let me know if the wording is okay.

Another additional work paid "improved" vector WMF staff is putting on unpaid projects' volunteers.

In T360384#9660135, @Base wrote:

Another additional work paid "improved" vector WMF staff is putting on unpaid projects' volunteers.

How many freeform javascripts do you get to install in your Facebook or Instagram page again?

(I keep saying this, but the only way to NOT have these kinds of problems is NOT having gadgets/userscripts/common.js and if any of this were to have been build after 2010, that's how it would work).

The global changes required on frwiki have been completed. Actives users (since may 2023 ; Vector 2022 generalization) potentially affected (a few hundred and not less than 50 as mentioned in the main task) will be notified this week. We don't have the capacity to manually review each personal user script.

How many freeform javascripts do you get to install in your Facebook or Instagram page again?

If your point is that WMF is a for-profit corporation just like Meta Platforms is, and thus it should not hold its userbase in any regard, then I would agree with you.

In T360384#9662874, @Base wrote:

How many freeform javascripts do you get to install in your Facebook or Instagram page again?

If your point is that WMF is a for-profit corporation just like Meta Platforms is, and thus it should not hold its userbase in any regard, then I would agree with you.

It is more, because of its volunteers, but this also creates more cost (in every meaning of the word) for both paid developers and volunteers alike.

@Lofhi thank you for setting a fine example of how this can work. If you could share how you went about the MassMessage I think that could be helpful to others!

Actives users (since may 2023 ; Vector 2022 generalization) potentially affected (a few hundred and not less than 50 as mentioned in the main task) will be notified this week.

Sorry about that, I can see 677 users have vector.js so yeh it looks like this number was very wrong.

Mmm my script was supposed to check for users who met the following criteria:

• Had a Vector.js or Vector.css user page that was not empty. (e.g. page length > 0)
• Did not have a Vector-2022.js or Vector-2022.css user page
• Was not a redirect

Looking again at the quarry query I used it does seem to be different to the numbers in the spreadsheet. I wonder if there was a typo and the query pulled for a similarly named wiki e.g. frpwiki of if when importing to the spread sheet a number was lost.
Apologies again for this. I messed up here.

@Base please let me know if you need help with your wiki the intention is to not create work for communities but to make things work better for them. I am only doing this as a favor for various site administrators to do this as they have complained that the current setup is confusing and works non-intuitively. We have also had cases where projects are loading the same code twice because of this confusion which I hope you agree is not what we want.

In T360384#9682707, @Jdlrobson wrote:

@Lofhi thank you for setting a fine example of how this can work. If you could share how you went about the MassMessage I think that could be helpful to others!

This message was sent to users found with this query. You can use the history of the query to get a version to find redirects (old personal pages before renaming in main cases).

Thank you for sharing!