Currently a protected filter can not be unprotected even if it is protected by mistake. Proposed either:
- Create a new user right such as abusefilter-unprotect and assign it to a higher user group (such as stewards). Stewards should verify there are no sensitive information in old revisions/abuse logs before unprotecting a filter.
- (not recommended) Create a maintanence script to unprotect a filter (so user need to open a task to let sysadmins to run the script).
Note unprotecting an filter will also make older versions of it visible.