IP Masking will affect lots of our products, features, tools, gadgets, etc. This task is for tracking work to update those that are owned by Language-Team, ahead of IP Masking being enabled on WMF sites.
See T326816: [Epic] Update features for temporary accounts, particularly What will be affected.
A preliminary investigation (T326759) has found that the following may be affected:
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Restricted Task | |||||
| Resolved | kostajh | T294511 2021 Security Team wikireplicas audit | |||
| Declined | None | T284948 Raw IPs of logged-out users disclosed in wiki-replicas | |||
| In Progress | Niharika | T324492 Temporary accounts - MVP | |||
| Open | None | T326816 [Epic] Update features for temporary accounts | |||
| Resolved | Nikerabbit | T326879 Update Language Team-owned products that may be affected by IP Masking | |||
| Resolved | abi_ | T340584 Ensure UserGroupManager::addUserToGroup is not called on temporary users from Translate extension | |||
| Resolved | abi_ | T337779 Prevent Translate from setting preferences for temporary accounts | |||
| Resolved | abi_ | T337780 Prevent UniversalLanguageSelector from setting preferences for temporary accounts | |||
| Resolved | abi_ | T337775 Prevent TranslationNotifications from setting preferences for temporary accounts | |||
| Resolved | Nikerabbit | T344151 Review ContentTranslation for IP Masking | |||
| Resolved | ngkountas | T344771 Update requireLogin() for temp users on ContentTranslation extension |
It seems that temp accounts will have access to Special:ContentTranslation. Growth works on Notifications, and tests the one regarding Translations. If CX is not given to temp accounts (and I think it should not be given to them, see below), then @Etonkovidova will save time testing something. :)
Most communities have that love/hate relationship to Translations, the most common critique is the fact that newcomers rush and don't work properly. As IPs (and consequently temp accounts) are often considered as low-quality contributors, opening Content translations to temp accounts might not be well perceived by big communities.
Also starting a translation locks it to the account for a year. I guess that the same applies to temp accounts?
If not already done, it would be good to document the decision somewhere.
Also starting a translation locks it to the account for a year. I guess that the same applies to temp accounts?
It is no longer a year. I think it's just a few days now.
We haven't yet created a task to review ContentTranslation.