Hello everyone,
I am reaching out on behalf of the Wikimedia Foundation Trust and Safety
Product <https://www.mediawiki.org/wiki/Trust_and_Safety_Product> team,
working on the Temporary Accounts
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts>
project (formerly, IP Masking). We are making preparations for deployment
on testwiki.
We want to minimize the impact of temporary accounts on the ecosystem of
tools and features. Before deployment, we'll ask for stewards' confirmation
that critical workflows are not affected. Now, we would like to ask you to
check the impact on code you maintain. There may be breaking changes!
We do not have a firm deadline for deployment yet. We will let you know as
soon as we do. We would like to ask you to consider updating your tool's
code over the next weeks, if the tool works on any/all production cluster
wiki. If it only works on selected wikis and testwiki is not one of them,
you will have more time to update it. If you think it will take longer than
that to update your code, please let us know on our talk page
<https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…>.
For a full explanation of the technical change, please read our
documentation
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
In particular, the section on how your code might need to be updated
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
Some examples of ways code might be affected (not exhaustive):
- A feature looks for the IP address in the user name (it will no longer
be found).
- A feature that relies on looking at the user’s ID to identify if the
user is registered or unregistered. Temporary accounts will not have a
user_id of 0.
- A feature works differently for unregistered vs registered users.
See more examples
<https://www.mediawiki.org/wiki/Trust_and_Safety_Product/Temporary_Accounts/…>.
We may have discovered your issue already and filed a Phabricator task
using the #temporary-accounts tag. You may wish to file a subtask of T337012
<https://phabricator.wikimedia.org/T337012>. We hope that this task will
help us all as the technical community coordinates on tools requiring
updates.
If you have any questions or would like to learn more about the project,
take a look at our project page and reach out to us on the talk page
<https://www.mediawiki.org/wiki/Talk:Trust_and_Safety_Product/Temporary_Acco…>.
Thank you!
Szymon Grabarczuk (he/him)
Lead Movement Communications Specialist
(Product & Tech)
Wikimedia Foundation <https://wikimediafoundation.org/>
We will be performing maintenance on the Cloud VPS network next
Tuesday (2024-05-21) starting at around 14:00 UTC. During this window
we will be replacing some software on the Cloud VPS network router.[0]
During the maintenance window there will be a brief period during
which Cloud VPS and any services hosted there (including Toolforge and
PAWS) will not have any external network connectivity. Based on tests
done in our staging environment the full outage should last for less
than a minute assuming there are no unexpected issues.
There is no action required on your side, unless your tools are not
resilient to unexpected network outages - in that case you may need to
manually restart those tools after the maintenance is complete.
[0]: https://phabricator.wikimedia.org/T364459
Taavi (+ the rest of the WMCS team)
--
Taavi Väänänen (he/him)
Site Reliability Engineer, Cloud Services
Wikimedia Foundation
_______________________________________________
Cloud-announce mailing list -- cloud-announce(a)lists.wikimedia.org
List information: https://lists.wikimedia.org/postorius/lists/cloud-announce.lists.wikimedia.…
Hello all,
The next language community meeting is scheduled in a few weeks - May 31st
at 16:00 UTC. If you're interested, you can sign up on this wiki page: <
https://www.mediawiki.org/w/index.php?title=Wikimedia_Language_engineering/…
>.
This is a participant-driven meeting, where we share language-specific
updates related to various projects, collectively discuss technical issues
related to language wikis, and work together to find possible solutions.
For example, in the last meeting, the topics included the machine
translation service (MinT) and the languages and models it currently
supports, localization efforts from the Kiwix team, and technical
challenges with numerical sorting in files used on Bengali Wikisource.
Do you have any ideas for topics to share technical updates related to your
project? Any problems that you would like to bring for discussion during
the meeting? Do you need interpretation support from English to another
language? Please reach out to me at ssethi(a)wikimedia.org and add
agenda items to the document here: <
https://etherpad.wikimedia.org/p/language-community-meeting-may-2024>.
We look forward to your participation!
Cheers,
Jon, Mary, Oscar, Amir and Srishti
*Srishti Sethi*
Senior Developer Advocate
Wikimedia Foundation <https://wikimediafoundation.org/>
Hi,
You can ignore this message if your tools do not query abuse filter tables in Wiki Replicas.
In case you missed the announcement in Tech News <https://meta.wikimedia.org/wiki/Tech/News/2024/16>, I'm letting you know about the upcoming removal of four fields from two database tables.
The fields "af_user" and "af_user_text" of the "abuse_filter" table and "afh_user" and "afh_user_text" of the "abuse_filter_history" table are being removed in favor of the new "af_actor" and "afh_actor" fields, respectively. The new fields are already in sync with the legacy ones and available for read operations.
If you run queries involving those fields, you have to update them. The queries will now be structured the same way as, e.g., queries with "rev_actor" of the "revision" table (i.e., by JOIN'ing the new fields with "actor.actor_id"). There are examples of minimalistic migration of each field in the Phabricator task <https://phabricator.wikimedia.org/T361996> that tracks the migration.
No deadline has been proposed for the removal, but it will probably have been done by the end of May unless someone asks for more time.
Thanks,
Matěj Suchánek