search

bluesky-social / ozone

web interface for labeling content in atproto / Bluesky
https://atproto.com
Other
281 stars 24 forks source link

additional action state: "review" or "backburner" #15

Open bnewbold opened 1 year ago

bnewbold commented 1 year ago

The escalation mods requested an additional "queue" for escalated reports which need further review and feedback. The idea is to get them out of the "escalation" queue. The way things currently work, this would need to be a new action type, that reports can be updated to.

I'm not sure we actually want to do this now, we might want to wait until we refactor the report/action data model. And the mods said it wasn't an urgent request, just something to consider. But wanted to record the idea here in github.

foysalit commented 1 year ago

with snooze feature in prod for the last few weeks, is this still something we want to build? I know the snooze behavior is not global but at least it helps folks throw things in the "backburner" in a way, right?

bnewbold commented 1 year ago

I think this is pretty different from the snooze.

The motivation for snooze is when a subject is getting new reports like crazy, regardless of the resolution state. Eg, if we have "acknowledged" a report on an account, but there are still hundreds of reports coming in, each new report still needs to be "resolve with current action". This happens when, eg, a person is getting dogpiled for a bad take, but didn't violate any rules.

The motivation for a "review" or "backburner" action state is that there are often cases where we haven't decided if we should take action, and are waiting for review/consensus, which could take several days, spanning several on-call shifts of escalation agents. There is a desire to keep the escalation queue "inbox" cleared, especially at a shift rotation, instead of leaving things lingering in there. Marking as "review"/"backburner" makes it clear that it isn't a task needing attention for now. The way this is often handled now is that they just "acknowledge" out of the escalation queue and mention in Slack; then if there is a change in decision we go back and re-action. This means there is important state left in Slack, and things fall through the cracks easily (if we never follow-up, remains "acknowledge" forever).