Bansharesexpand_more Submitting Guide
This is the lifecycle of a banshare:
A banshare is submitted to the banshare form. It is posted to and reviewed by the observer team.
Once it is approved, an observer will publish it and it will be posted to all TCN servers that have banshares set up, as well as the TCN Hub. The bot will also automatically ban the user(s) in servers where autoban is enabled.
We strive to avoid this from happening, but if a banshare is found to be invalid for any reason, we will rescind it with a reason and perform a postmortem to see why a faulty banshare was approved.
This may also be done if the user's behavior improves substantially and we retroactively agree to un-banshare them. Just as servers are not required to ban banshared users, they are not required to unban users in these cases either.
When the bot performs automated actions, either through autoban or the ban button, it will log the action in your logging channel(s) if you set it up. Here's what the log message looks like:
This is probably most appropriate for the channel in which your mods use commands rather than the mod actions audit log, but you are of course welcome to put it wherever you want.
To set up the banshare system, first invite the bot using this link.
You must grant the bot read and write access to any channels receiving the banshares or where you want the bot to post logs.
/banshares subscribeto register a channel to receive banshares (
/banshares unsubscribeto revert).
/banshares log enableto register a channel to send log output (
/banshares log disableto revert).
/banshares settingsto modify your server's settings, including enabling autoban.
Banshares are categorized into three severity levels and a special category. These are not strictly defined, and observers can adjust the severity before publishing. These are primarily used for autoban thresholds, should be primarily based on threat level, and do not indicate how "bad" we believe a user is. Here are our guidelines:
expand_less P0 (Critical)
The offense is extremely severe and all servers should immediately ban them for safety.
- A user spamming NSFW or NSFL content should be P0, as this violates all servers' rules and Discord's Terms of Service and constitutes an immediate and grave threat to member safety.
- Hacked or raid accounts posting spam or scam links should be P0, as despite the offense not being very severe, they are likely to become a nuisance in many other TCN servers and there is likely no reason a server would not want them banned.
remove P1 (Medium)
The offense is somewhat severe and the majority of servers, if not all of them, will want to ban them; however, individual servers may have other considerations and choose not to ban them.
- A user using slurs enough times to be banned with a reasonable amount of warnings (i.e. they are aware that what they are saying is wrong or were being deliberately malicious from the start) should be P1, as this violates all servers' rules and most will just immediately ban them unless they have enough positive contributions to be potentially given a last chance.
expand_more P2 (Low)
The offense is not extreme and some servers may not wish to ban the user. Do note that very minor offenses should not be banshared at all — this is for more nuanced cases but still cases where the user presents a threat to other servers.
- A user repeatedly stirring up trouble or randomly attacking members should be P2, as some servers will want to pre-emptively eliminate a potential disturbance but some other servers may want to give them a chance and only ban them if their behavior repeats there.
message DM Scam
The offense is a DM scam. These are categorized separately as some servers do not wish to receive these banshares.
Note that spamming scam links within a server should be P0 and other offenses within DMs such as harassment should be evaluated separately. This only applies to accounts attempting to scam users by DMing them, e.g. steam scams, fake nitro scams, art scams, etc.
To post a banshare, go to this form. All fields should be fairly intuitive, but here is a usage guide for each.
- IDs: The IDs of the offending users. Please post this as an actual list of IDs. If it is too long, it will be automatically uploaded as a
document, but if you paste a link, autoban will not work. If it is so long that the form rejects it, then you may need to post it as a link
- Once you paste your IDs, click Check IDs to fetch all of the users' tags to make sure you are bansharing the right people.
- Reason: Summarize why the users should be banned. This is used as the audit log reason for automated bans, so please write a detailed reason and leave notes in the evidence.
- Evidence: Include enough evidence to prove that your reasons are valid and for other mods to make an informed decision on what to do.
- Server: Choose the server from which you are submitting this banshare. If the incident is not bound to a particular server or is not from one you staff, you should pick your "main" server or the one in which you feel you have the most prominent position. If you do not see a particular server here, reach out to the server owner and direct them to this page.
- Severity: See above.
- Urgency: If you check the urgent box, this will ping all observers to review it immediately.
If the ID list is very long, you may want to use Submit Without Validation to skip checking if the IDs are valid, which will take a long time. Do not use Submit Without Checking IDs unless you had to submit it using a link in the ID field and there was no way around it. Skipping this check prevents automated banning from working.
The regular submission option will validate that all of your IDs correspond to valid users. Submitting without validation will only verify that the IDs look like the correct format and will parse them such that autoban will work.
The purpose of the banshare system is as a pre-emptive safety measure. Banshares should be used to eliminate threats from the network and ensure server safety, not as a punishment.
link Banshare Requirements
The following are required of banshares at a minimum, but meeting these requirements does not necessarily ensure a banshare is good enough:
- Demonstrable Threat: The offense must be severe enough that the user should be considered a threat to any other servers they join, and
there must be sufficient reason to believe that the user may join TCN servers.
- Spamming NSFW in a TCN server satisfies both conditions.
- Being banned for repeat minor offenses in one server does not satisfy the first condition unless their behavior repeats again elsewhere.
- Spamming NSFW in a random server not associated with the TCN or the Genshin Impact community does not satisfy the second condition as there is no demonstrable threat to the network unless the user is already in any TCN or Genshin Impact servers.
- Descriptive Reason: The reason must clearly explain what the offense was. A moderator should be able to understand why they were banned
by just looking at the ban reason on its own.
- "Spamming NSFW images in XYZ Mains" is a good reason.
- "Typical steam scammer" is an acceptable reason.
- "Troll" is not a good reason.
- Sufficient Evidence: The provided evidence must prove that the offense happened as described in the ban reason and all listed users were involved. Exceptions are granted in the case of large raids as it is both impractical to attach evidence for every single user and for the team to review that much evidence. In those cases, trust is placed on the author to ensure that the list of users is correct.