Change Details

We have functionality for allowing blocked users to bypass our restriction on block status, for example if they have a username block on a project they've never edited. We've granted this whitelisted status to a few dozen users. This whitelist, however, lasts forever, even if the user is subsequently given a more serious block. We want a system for reviewing whitelisted users in the case that their block status changes, so that we can evaluate if they should still be whitelisted. The solution we discussed is to store the user's block status as a hash. If a user's block status hash changes, an email should be sent to the team email with a link to the user's Special:CentralAuth page (e.g. https://meta.wikimedia.org/wiki/Special:CentralAuth/Samwalton9). The team can then review and make changes as necessary.

We have functionality for allowing blocked users to bypass our restriction on block status, for example if they have a username block on a project they've never edited. We've granted this status to a few dozen users. This, however, lasts forever, even if the user is subsequently given a more serious block. We want a system for reviewing users with ignored block status in the case that their block status changes, so that we can evaluate if they should still be whitelisted. The solution we discussed is to store the user's block status as a hash. If a user's block status hash changes, an email should be sent to the team email with a link to the user's Special:CentralAuth page (e.g. https://meta.wikimedia.org/wiki/Special:CentralAuth/Samwalton9). The team can then review and make changes as necessary.

We have functionality for allowing blocked users to bypass our restriction on block status, for example if they have a username block on a project they've never edited. We've granted this whitelisted status to a few dozen users. This whitelist, however, lasts forever, even if the user is subsequently given a more serious block. We want a system for reviewing whitelisted usersusers with ignored block status in the case that their block status changes, so that we can evaluate if they should still be whitelisted. The solution we discussed is to store the user's block status as a hash. If a user's block status hash changes, an email should be sent to the team email with a link to the user's Special:CentralAuth page (e.g. https://meta.wikimedia.org/wiki/Special:CentralAuth/Samwalton9). The team can then review and make changes as necessary.