It's likely that we will need to introduce additional tables to support the new features and improvements we're planning. These new tables will be implemented in conjunction with Version 2 of the moderation tools. I am considering a shift towards a role-based access control system, which would replace the current setup of having separate lists for different user roles and statuses. Currently, we have: - A list of users banned from the website. - A list of users who are moderators on the website. - A list of users banned from feeds. - A list of feed moderators. With the new role-based system, I envision consolidating these into two primary roles: - `roleinfeed`: This role will manage permissions and access within individual feeds. - `roleonsite`: This role will manage permissions and access across the entire website. The `banned` status will remain as it is, separate from the role-based system. To support this new structure, we will need to create at least two, possibly three, new tables: 1. **Site Roles Table**: This table will store the various roles available at the site level. These roles will define the permissions and access levels for users across the entire website. 2. **Feed Roles Table**: This table will store the roles specific to each feed. Feed creators will have some autonomy in defining the roles within their feeds, but there will be a standard set of roles provided by default. This ensures consistency and ease of management. 3. **Role Attributes Table**: This optional table will define the specific attributes or permissions that can be assigned to each role. This will allow for more granular control over what each role can and cannot do. By implementing this role-based access control system, we aim to streamline the management of user permissions and enhance the overall moderation capabilities of the platform.
Aug 28, 2025 ยท 23:08
Collapse
Comments