administration tasks in pleroma-fe #178
Labels
No labels
a11y
Bug
Bug fix
Critical Priority
Documentation
Feature
Feature request
Held for next release cycle
High Priority
Low Priority
Medium Priority
Minor change
Translation/Locale
WIP
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma-fe#178
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
so, i'll be able to take a crack at this once i'm back home, but i need to think about the implementation details:
anything else i forgot?
my personal view is that this sort of thing should go as a static page set in the backend instead of attached to a front-end
open to other takes on that
maybe for actual configuration file things but i think banning users, handling reports, and adding emoji ("moderation" rather than "administration") make sense to be attached to a frontend