Evidence
Attach screenshots and video to a case file, view them, take them off, destroy them, what the audit log records about them, the three evidence permissions, and the upload limits in Settings.
Evidence is the screenshots and video attached to a case file. It sits in the Evidence section of the case file page.
Before anyone can attach evidence, whoever runs your Modbot has to choose where the files are kept. See Storage buckets.
The three evidence permissions
| Permission | What it allows |
|---|---|
| View evidence | Open the screenshots and video attached to a case file. |
| Upload evidence | Attach screenshots and video to a case file, and take them off it. |
| Destroy evidence | Permanently remove the files. The record that they existed stays. |
View evidence is separate from reading case files on purpose. Knowing somebody was banned for harassment is not the same as needing to watch it happen. Without it, the Evidence section says You do not have permission to view evidence.
Attaching a screenshot or video
You see Attach a screenshot or video when all of these are true:
- you have Upload evidence;
- you wrote the case file, or you have Ban;
- the case file has not been withdrawn.
Beside the button, Modbot lists the accepted formats and the size limit per file.
Press Attach a screenshot or video
Choose one file. To attach several, do them one after another.
Wait for the upload
You may see Checking the file… first, then a progress bar with how much has been sent and how fast, then Attaching…. A large video on a home connection can take minutes.
Check it arrived
The line says Attached and the file name, and the file appears in the list.
Nothing is attached until the upload has finished. If your connection drops, the file is not attached; try again. If a file is over the size limit, Modbot says so before sending anything.
The same file can be on several case files. Attach it on each one and Modbot keeps a single copy in storage, and each case file shows it under the name you gave it there. Attaching a file that is already on the case file changes nothing.
Accepted formats
| Kind | Formats |
|---|---|
| Images | PNG, JPEG, WebP, GIF |
| Video | MP4, WebM |
Modbot decides what a file is from its contents, not from its name. A file that is really something else is refused, whatever it is called. SVG and HTML files are never accepted, because they can carry code that would run in a moderator's browser.
Modbot stores the file exactly as you uploaded it. It does not shrink, convert or clean it, so a photo keeps any hidden details saved inside it (such as when or where it was taken).
Clips saved in the companion
A moderator whose companion is set to Tell the group's Modbot when I save a clip tells Modbot each time they save a clip in one of your group's instances — when, where, and the file's fingerprint, never the clip itself. The case file of anybody who was in that instance at the time lists each such clip under Evidence, until the case file holds it:
Clip saved on Alex's PC at 9:14 PM · The Black Cat #98874 · 48.2 MB · not uploaded Attach
Clips are listed from a week before the ban (or before the case file was written, when it has no ban) to a day after it. The list is of instances the person was in, by the companions' reports; whether the clip shows them is for you to see.
Attach opens the file picker. Choose the clip on the PC that saved it: its file name has the world, the instance and the time in it. Modbot checks the file's fingerprint against the one the companion sent. The right file is attached and its line says clip saved on Alex's PC, with when and where. Any other file is refused with That file is not the clip saved on Alex's PC, and nothing is attached. The audit log's Evidence attached entry says it was a clip and which one.
The same three rules as any other upload apply: Upload evidence, your own case file or Ban, and a case file that has not been withdrawn.
Clips Modbot asked the companion for
When a moderator's companion has Send clips for my actions automatically ticked, Modbot can ask it for a clip of a ban, kick or warning that moderator made, if the group has switched that on in Settings. The clip arrives without anyone attaching it and is kept as evidence on the action, marked as a clip, with where and when it was saved, whose PC it came from and its fingerprint. Each action that was asked shows a status such as Clip attached or Companion didn't answer. The Clips page lists them all.
If uploads are refused
When the storage is not set up or not reachable, the button is greyed out and a line says Uploads are refused right now: with the reason. Ask whoever runs your Modbot to check Settings, Evidence.
Viewing evidence
Each attached file shows:
- Images inline. Click one to open it full size in a new tab.
- Video in a player on the page. Seeking works when the storage supports reading part of a file (Settings, Evidence, Partial downloads).
- The file name, its type, its size, the date it was attached and who attached it. A file attached as a companion clip also says whose PC saved it, when and in which instance.
- Download, to save the file.
- Take off and Destroy, when you are allowed them (see below).
- Its
sha256fingerprint. This is a code worked out from the file's exact contents. If a downloaded file gives the same fingerprint, it is byte for byte the file that was stored.
To show an attached image inside the written reason, copy its fingerprint and write
. Only evidence attached to the same case file
works. See Formatting the written reason.
Taking a file off a case file
Take off shows on a file when you could attach one: you have Upload evidence, you wrote the case file or you have Ban, and the case file has not been withdrawn. Modbot asks Take it off this case file? and you press Take off.
Taking a file off ends that case file's hold on it and nothing more. The file stays in storage, and
so does every other case file that has it. The case file keeps one line where the file was, with its
name, who took it off and the date: old.png taken off by sam, 29 Sep. A case file never looks as
though it never had the file.
To put it back, attach the same file again. The line stays as the record that it was taken off, and the file shows again in its place.
Destroying evidence
Destroying removes a file's contents from storage for good. There is no undo: none of the storage types Modbot supports could bring it back.
Destroy shows on a file, and on the line a taken-off file leaves behind, when you have Destroy evidence. It works on any case file, including a withdrawn one. Modbot asks for a reason, which is kept with who destroyed the file and when. Destroying from a case file takes the file off that case file first, so it is one step.
If another case file still has the file, Modbot refuses and says which: This file is still on the case file for the person it is about. Nothing is taken off or destroyed. Take the file off that case file first, or destroy it from a case file that is the last to have it. Modbot also refuses while the storage's state is in doubt.
What stays is the record that the file existed: its fingerprint, size and type, who destroyed it and why. In the case file, the line for the file says destroyed, with who did it, the date and the reason. A case file never looks as though it had no evidence.
What the audit log records about evidence
Every change to evidence, and every time somebody looks at it, is written to the audit log, against the account that did it. Each entry names the case file, the file and who.
| Entry | When |
|---|---|
| Evidence attached | A file is put on a case file. |
| Evidence taken off | A file is taken off a case file. |
| Evidence viewed | Somebody looks at a file on the case file page. Written at most once for each person and file every 10 minutes, so reloading the page or skipping through a video does not fill the log. |
| Evidence downloaded | Somebody downloads a file. Written every time, except that a request which says it is only showing the file (as the case file page does) is written as viewed, at most once every 10 minutes. |
| Evidence destroyed | A file's contents are destroyed, with the reason. |
The entries are about the case file, so purging a person from Modbot leaves them where they are, and they are kept for as long as the log is.
When the storage hands your browser a link instead of sending the file through Modbot, the entry records that a link was handed out. The fetch itself goes to the storage and never reaches Modbot.
To read these entries you need View evidence as well as View audit log: an entry names the file, and a file's name can say what it shows.
Upload limits in Settings
Anyone with Change settings can set limits in Settings, Evidence, File Upload Limits, then press Save limits.
| Field | Meaning | Default |
|---|---|---|
| Per file (MB) | The largest single file anyone can attach. Checked in the browser before sending, and again by the server while the file arrives. | 100 MB |
| Per report (MB) | The most one case file may hold in total. 0 means no limit. If set, it cannot be smaller than the per-file limit. | 0 (no limit) |
| Whole install (MB) | The most your whole Modbot may hold. 0 means no limit. | 0 (no limit) |
All three are checked when a file is attached: before it is sent, from the size the browser declares, and again when it arrives, from the size that was stored. A file that would take a case file or your whole Modbot over its limit is refused with a sentence saying what is held and what the limit is. A file the case file already holds is not counted twice, and neither is one that is already stored for another case file. A file taken off a case file stops counting toward that case file's limit, but it still counts toward the whole install until it is destroyed; destroyed files count for nothing.
The What this store is doing card in the same tab shows Delivery (Straight from the store or Through Modbot), Partial downloads, Evidence held (how many files and how much space), Destroyed and Accepted formats. When delivery is straight from the store, opening a file sends your browser a link that works for 5 minutes.
Appeals and the yearly report
Write down each appeal against a ban, mark it upheld or turned down, and read or download a year of warnings, kicks, bans, unbans and appeals. Staff only.
Reviews and repeat offenders
The list of people acted on more than once, the Past actions block on a person, and the Reviews page that asks the team to look when a moderator's pattern seems unusual or a moderation rule flags somebody.