This task should probably be done after T375441: Store expiry date and status of temporary account in database.
By the way, we should also purge all notifications (probably also include ones already read) once the temporary account is expired.
This task should probably be done after T375441: Store expiry date and status of temporary account in database
Agreed. Moving to Blocked on our end, please feel free to move back to Inbox once this is actionable.
And also trying to mention an expired temporary account should trigger a "mention failure" notification saying that the notification wasn't sent because the temporary account had expired.
Removing this as a major pilots blocker, since the dependent task was declined: T375441.
Should it be a global rollout blocker?
Yes, that would make sense to me.
In T375441: Store expiry date and status of temporary account in database we decided to not store expiry date / status in the DB. So I think this is no longer blocked for Growth. Expiry would be based on temp account creation time plus the number of days defined in config for the longevity of a temporary account.
Change #1306760 had a related patch set uploaded (by Matěj Suchánek; author: Matěj Suchánek):
[mediawiki/extensions/Echo@master] Ensure no notifications are sent to expired temporary accounts
Adding Product Safety and Integrity sprint to track code review from us, thanks for the patch
Change #1306760 merged by jenkins-bot:
[mediawiki/extensions/Echo@master] Ensure no notifications are sent to expired temporary accounts
Change #1309868 had a related patch set uploaded (by Matěj Suchánek; author: Matěj Suchánek):
[mediawiki/extensions/Echo@master] Notify user when they mention an expired user