You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
(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.
The text was updated successfully, but these errors were encountered: