Moderation

Moderation is the queue the reports people file are worked in, and it is open to staff alone. The account’s own cells decide it: an account holding the ticket-view cell sees Moderation in the hub bar and in the command palette, and every other account sees neither. Opening the screen without the cell says so and shows nothing else. The cells are read from the profile the server answers, never from a copy kept here, so a role granted or revoked takes effect the next time the profile is read.

One queue stands over four tables. Reports, copyright notices, appeals and feedback are one list, because a queue whose rows mean different things is not one queue. Each row says which of the four it is, the reason it was filed under, its severity, whether it is open or closed, who it is about and the day it arrived. A row past its due time is marked.

Four filters cut it: type, state, severity and age. Severity is the five words the server files a report at, in the order it sorts by: critical, high, legal, medium, low. Legal sits under high because a copyright notice is answered by reading the notice and the work, which is a day’s work rather than an interruption. Age means older than, and its three spans are the ones a backlog is worked by. Above the list a line counts what is shown against what the filters match, and the queue stops at fifty rows: past that, narrow the filters rather than scroll.

A set of tickets is worked in one go. Every row carries a checkbox and Select all takes the rows on screen. With a selection a bar appears above the list saying how many are held, and it offers Assign to me, Unassign, Escalate and Dismiss. Each opens a dialog naming the count, and Escalate and Dismiss take the reason that goes on the trail; Dismiss also takes the form whose statement every reporter in the set receives. Fifty is the ceiling: a larger selection is refused here before anything is sent, because a set that half happened is one nobody can undo by hand. An appeal is answered one at a time and is refused in a set for the same reason, and so is an assignment or an escalation on feedback, which carries neither. The answer is shown once under the bar: how many of those sent were acted on, since a ticket somebody else had already worked is skipped, or the tickets held back with the reason each met. A reader holding the ticket-view cell but not the act cell reads the queue with the bar disabled and the reason beside it.

Saved views are the filters kept under a name. Above the filters is a row of chips, one per view. Save view keeps the filters as they stand under a name you give; a chip puts its filters back on the queue; and Delete beside a chip asks first and then removes it. The views are the server’s and yours alone: nothing is kept on this device, so the same views are there on the next machine you sign in from, and twelve is the most one reader may hold.

A ticket carries what a decision is made from. Opening a row shows the reporter and the day, the due day, how many decisions already stand against the account it is about, what the reporter wrote, and the reported item read through its own route: the work with its summary, the guild with its motto, the account with its about text, or the message with the lines that stood beside it in its room. An item a decision has already taken down is marked as removed. An item that is no longer there says so rather than showing an empty box.

Five actions and a dismissal. Warn writes a decision with no end. Mute closes chat for an hour, a day or a week. Suspend closes community access for a day, a week, thirty days or for good, and the dialog states that the application keeps working and that paid licences are not refunded. Remove content is offered for a work and a guild and for nothing else. Dismiss closes the ticket and does nothing to anybody.

Every decision is written from a form or from your own words. The dialog lists the forms whose action is the action being taken, each carrying the statement the person will receive and the rule it is taken under, with this ticket’s facts already in it, so you read what they will read before deciding rather than after. Choosing Own reason writes the statement yourself instead. A form’s own length is used unless the action named one.

The internal note is not the statement. What you write in the note stays on the ticket, is never sent to anybody and never appears in what the person receives. That separation is the point of having both.

A ticket is worked once. After a decision the ticket reads closed and the actions are gone: two reviewers on one queue cannot both act on it. What happened is on the ticket’s history at the bottom, one line per decision with its day, who took it and the reason recorded.

Try: open Moderation from the hub bar, set Severity to Legal, and open the one ticket it leaves. Read the work under the report, then take Remove content and pick the form. The statement in the dialog is what the writer receives; the note under it is what only the queue sees.