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

[0005] "Infrastructure" vs. "community" moderation #66

Open
imax9000 opened this issue Oct 18, 2024 · 0 comments
Open

[0005] "Infrastructure" vs. "community" moderation #66

imax9000 opened this issue Oct 18, 2024 · 0 comments

Comments

@imax9000
Copy link

(Carried over from https://connect.iftas.org/groups/ozone-moderators/forum/discussion/ozone-moderation-history-api-proposal/)

Lumping “infrastructure” moderation (i.e., takedowns) with the rest feels like bad design: concerns and abilities of infra moderation and community moderation are substantially different, trying to treat them the same way will inevitably lead to conflicting requirements (and the confusion in implementations).

N.B.: this applies to reporting flow too – report reason options are hardcoded and make no sense for most moderation services.

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

1 participant