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.
(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.