Temporary accounts will receive notifications, but they don't have access to adjust preferences.
Temp accounts should keep the default notification preference (to keep it simple and because then we aren't adding as much to the user_properties table bloat)
However, Temporary accounts won't have access to the newcomer homepage and suggested edits, so we don't want them to receive Growth notifications.
Given an account is a Temporary account,
Then it shouldn't receive Growth notifications
| 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 | KStoller-WMF | T326877 [Epic] Update Growth Team-owned products that may be affected by IP Masking | |||
| Resolved | BUG REPORT | Etonkovidova | T330509 [IP Masking] Make Echo Notifications available to temporary users | ||
| Resolved | Etonkovidova | T333531 Temporary users should have default notification preferences | |||
| Resolved | Etonkovidova | T335171 Temp accounts shouldn't receive Growth notifications |
This should already happen: if homepage isn’t enabled, Growth notifications shouldn’t get triggered. So I'm moving this to QA.
@Urbanecm_WMF - Is this task ready for testing, or are we waiting for more patches related to T341976: IP Masking: Change User::isRegistered() and User::isAnon() with User::isNamed in Growth-managed extensions before testing?
This should be ready for testing, GrowthExperiments is supposed to be fully IP-Masking ready for now. T341976 will receive patches related to other Growth-maintained extensions, but that won't affect this task at all.
Checked as part of T333531: Temporary users should have default notification preferences and T341839: [QA task] IP masking - temp users testing in production.
Closing as Resolved - after IP-masking deployment the task will be checked in the scope of T341839: [QA task] IP masking - temp users testing in production