"Sudo Mode"
What feature would you like implemented?
We should put a preventative block behind things we might need to have as administrators, but may not be so good to have as a regular user. Things like the control panel, viewing a blocked user's posts should require the confirmation of the user's password & 2fa (see #856!). Otherwise, those features will return as if they were a user.
Why should we add this feature?
Having a point to intentionally slow down the user before they're able to do may clear the mind and prevent administrators from doing retalitory behavior, while also giving administrators the authority they need to manage the instance. Having it be only an option may be better for smaller or single-user instances.
Version
docker/devel - d14f0b14
Instance
kitsunes.club
Contribution Guidelines
By submitting this issue, you agree to follow our Contribution Guidelines
- I agree to follow this project's Contribution Guidelines
- I have searched the issue tracker for similar requests, and this is not a duplicate.
Activity
In my opinion, I think making the scope of actions requiring sudo mode maximal is best, given it is implemented in a user-friendly way. Any administrative action that affects the way the system or users interact should be inherently considered destructive; so any instance setting changes should require confirmation as it is a destructive change, changes to user account status should be considered destructive, and viewing private (if they do not already have access) or blocked user notes should be considered destructive, and these are just examples! There are many more actions that I've probably missed, but these are the ones I remembered.
Ideally, it shouldn't be asking for confirmation every time you do a destructive action, so it should request once, enable sudo mode, and expire after X minutes. It would also be nice for the expiry date of sudo mode configurable.
added enhancement label
mentioned in issue #924
marked this issue as related to #924
Just gonna leave these two upstream issues here where they are debating about remaking the entire login auth adding a sudo mode as well as using JWTs instead of the current token system and etc:
https://github.com/misskey-dev/misskey/issues/13865 https://github.com/misskey-dev/misskey/issues/15570
