Problem
Currently, resource-related limits appear to be primarily instance-wide.
While instance-wide controls are important, self-hosted communities may have very different requirements depending on their size, purpose, and member structure.
For example, a server owner may want temporary upload channels where files are automatically removed after a certain period, permanent archive channels that retain files indefinitely, or different upload limits for trusted members and new users.
Without more granular controls, administrators may have to rely on manual moderation and cleanup, which can become difficult as communities grow. It can also make storage management, bandwidth management, and backup planning more challenging for self-hosted instances.
Proposed solution
Consider introducing more granular resource management and policy controls in the future.
Examples could include:
- Upload limits per role
- Upload limits per community or channel
- Storage quotas for users, roles, channels, or communities
- Automatic file expiration and retention policies
- Community-specific resource policies in addition to instance-wide limits
- Optional streaming quality or bandwidth policies
- Trust-level based resource controls for new versus established members
The goal would not necessarily be to restrict users, but to give self-hosters more flexibility when managing storage, bandwidth, backups, and potential abuse.
Instance-wide limits could remain the default, while more advanced controls would be available for administrators who need them.
Notes (optional)
This is intended as a long-term discussion rather than a request for immediate implementation.
I asked about this in the Fluxer community and several users suggested moving the discussion to GitHub. The idea is mainly motivated by self-hosting use cases and curiosity about Fluxer's long-term direction regarding administration and resource management.