[go: up one dir, main page]

Page MenuHomePhabricator

Add ability to centrally revoke ipinfo reveal permissions from users who should not have them
Open, Needs TriagePublic

Description

Motivation

There could be scenarios where we want to withdraw IP address reveal permissions from a user in a situation where the user has caused enough of a trust & safety concern to have them not view IPs but not severe enough to block them from the project.
This permission should work globally - so a user can be blocked from revealing IP addresses from all wikis. This should also work irrespective of whether the user has opted-in to IP reveal ability.

Event Timeline

Basically a global group with the same revoke ability as the local no-ipinfo group. Obviously something only for staff/stewards to manage.

I think this is going to need to be blocked upstream, 2 reasons:

  1. Doesn't appear this functionality exists (ability to have a global group with "revoke" permissions)
  2. Unclear on the governance model that would be needed for (1) - it appears the primary use case of this would be to override a local project's governance authority (who may or may not do what locally) - this may be necessary and appropriate for certain things on WMF wiki's

A feature request for #1 should be created for the general condition if this is going to be done via global groups with central auth.

Xaosflux renamed this task from Add ability to revoke reveal permissions from users who should not have them to Add ability to centrally revoke ipinfo reveal permissions from users who should not have them.May 22 2023, 6:31 PM

Would it be possible to implement this without adding a new user right, please? User rights should not be used to revoke permissions.

Would it be possible to implement this without adding a new user right, please? User rights should not be used to revoke permissions.

IMO I don't see any easy way to implement this without using $wgRevokePermissions, because:

  • The revoking of the right via this user group means that the existing checks will not need to know that the user has the right revoked. Using any other method will require extra code that checks for revokes.
  • I can't see an obvious way to achieve this without adding a new database table.

If you have any suggestions as to how an alternative method would work, I'd be all ears.