Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: granular access control #258

Open
rudyfraser opened this issue Dec 9, 2024 · 3 comments
Open

Feature request: granular access control #258

rudyfraser opened this issue Dec 9, 2024 · 3 comments

Comments

@rudyfraser
Copy link

To keep moderators focused on certain work streams, it would be great to give them access to subjects based on report type. So if a mod handles the "misleading" queue, they would only see unreviewed subjects with a recent "misleading" report.

To prevent moderators from using labels like !hide, !warn, or sexual, etc that are accessible by default in Ozone, should be able to choose which labels a mod has access to apply.

@SteveTownsend
Copy link

SteveTownsend commented Dec 9, 2024 via email

@rudyfraser
Copy link
Author

The Events view can already be filtered on Report Reason - you could configure a macro for use by your "Misleading" queue handler person. Would that work? [image: image.png]

Macros are per user, per device and can't be filtered to say "misleading and unresolved, order by last in first out". Even if they could be, it wouldn't stop someone from wandering into a "violation" post and taking an action nor would it address the controls needed on a per label basis.

@foysalit
Copy link
Contributor

thanks for bringing this up. this has been a necessity for us at bluesky for a while now and im working on an advanced tag filter that should help with this. we recently started tagging subjects with report reasons which will allow mods to view subjects reported for a certain reason although it doesn't really address issues with users sending reports with unrelated/wrong reasons.

we have thought about finer grain ACL for labels and current config API may be able to solve this quickly but isn't a great replacement for proper ACL implementation unfortunately. I'll try to get a config based proposal out soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants