(20 intermediate revisions by 8 users not shown)
Line 1: Line 1:
Summing up the responsibilities of a Moderator would be the word "guidance". Moderators with the power to manage users, their primary function is to enforce the rules and attempt to keep a positive environment! They represent our network and make sure that things are going smoothly. They don't have the responsibility of kick/banning people and their primary goal is to be helpful and positive. The following powers are granted to all moderators in all channels where TripBot has OP. Note: Just because TripBot has OP does not mean it's an official TripSit room. Whenever you have doubts/need advice/help, do not forget about ~teamtripsit!
+
Moderator responsibilities would be best summed up with the word "guidance". Moderators' primary function is to enforce the rules and attempt to keep a positive environment! They represent our network and make sure that things are going smoothly, as well as having some more input on rule formation and other TripSit activites. Moderators are able to perform moderator actions via TripBot in all channels where tripbot has op, i.e. nbans and quiets will only take effect in rooms where tripbot has the 'o' flag. Whenever you have doubts/need advice/help, do not forget about ~teamtripsit or ask in #moderators! New moderators are asked to watch the process and ask questions for a while to get a feel for how we moderate. Please also make sure you are familiar with our general [https://wiki.tripsit.me/wiki/Orientation staff orientation].
  
==== Reports ====
+
=Commands=
  
/msg TripBot ~report <user> <reason>
+
Moderators have access to all commands described [https://wiki.tripsit.me/wiki/Guardian_Orientation here], as well as the additional commands described below. See the [https://wiki.tripsit.me/wiki/Rule_Breaking_Procedure rule breaking procedure] for more information on how to react to a situation.
  
<reason> should be as descriptive as possible, and may even include a link to a pad of logs.  
+
When using commands, remember to be descriptive - the commands are recorded, and are often looked upon when judging a user's history in its entirety, or when reviewing a particular event. In these cases, it's very helpful for the command reasons to provide context as to why it was used. As a rule of thumb, the reason for a warning, quiet, or timeout should include the rule(s) that have been broken. If you feel that there's more important context necessary, you can make a document on the Cloud, and add a note with a link to it. If you forget to add a descriptive reason to a command, or did not have time to do so, you can use the ~addnote command to add a reason subsequently.
  
Moderators will make heavy use of the ~report command to keep records of events on the network, and should be used every time you have to verbally warn a user. Moderators will also receive notifications of user 'reports' which take place in a certain room. If you're around, please respond to these reports and follow up with a ~notify stating you have dealt with the situation. This is something that is sometimes abused by people. When a report is filed wrongfully, explain to the issuer that it is not something to abuse; repeat offenders should be ~warn 'ed.
+
== Checking a users status ==
  
==== Warning ====
+
/msg tripbot ~ustatus <user>
  
Syntax: /msg TripBot ~warn <user> <reason>  
+
/msg tripbot ~sustatus <user>
  
You can provide an automatic warn when placing a ~quiet by including #warn in the reason.
+
  /msg tripbot ~concerning <user>
   
+
You can also see a user's previous warnings with ~warnings username.
+
+
Warnings are counted and permanently stored online for staff to view past events. These should be used as much as possible, as it provides a good record for us when considering a ban. The user is not notified of the warning when it is issued; it is only used for internal record keeping. Verbal warnings suffice most of the time, but when there is repeat behavior or serious offenses such as sourcing it is good to make a note of it.
+
  
==== Quiet ====
+
The ~ustatus command is great for getting the current status of a user (banned, unbanned, number of quiets, reports and warnings). For a listing of all reports, quiets, and warnings a user has accumulated, the commands ~sustatus is used. ~ustatus will provide a simple count of each, while ~sustatus will print the full reasons for reports, quiets, and warnings a user has been issued. Further, using the ~concerning command, you can get a user's history from when they have seeked help in #tripsit. '''As this is considered sensitive material, ~ustatus and ~sustatus can only be run in #tripsit.me, #tripbot, #moderators or in PM. ~concerning can be used only in #teamtripsit, #tripsitters, #tripsit.me and PM.'''
  
Syntax: /msg TripBot ~quiet <time in minutes> <#room> <user> <reason> #warn
+
== Shadow Quiet ==
  
<time in minutes> is optional if you intend to manually remove the quiet when the situation has passed.
+
/msg TripBot ~quiet [time(<integer><units>)] <#room> <user> <reason> #warn
  
<#room> is optional if you are using the command in the target room.
+
/mode <channel> +z
  
#warn is used to automatically apply a warning with the quiet reason.
+
While not used very often, this method has worked against repeat trolls who use free-VPN to get around a kline. After applying the quiet on a user, mode +z allows the messages from the user to still enter the channel, but are only visible by people with the +o flag. In effect, the user still thinks they're talking, but are not inconveniencing anyone by doing so. Changing modes in a channel requires an Operator's approval, so this is not a tactic to jump to right away, but it's possible in the event that it's agreed to be used.  
  
As a Moderator, this command will be your primary mode of recourse against a problem user.
+
== Ban ==
This command prevents the user from speaking in that channel or changing their nickname; and also sends a notify to staff in that channel.
+
It is an excellent tool for trolls and rowdy users who need a small break to cool off.
+
It's usually better to employ a timed quiet rather than a permanent one, since this is difficult to follow up and is more of a 'permanent' solution, which isn't generally the intended use of a quiet.
+
  
Often a good method of 'moderation' is simply to attempt to guide a channel into a reasonable conversation.
+
/msg tripbot ~nban [time<integer><units>] <user> <reason>
It's almost always better to try and defuse a situation with your words, than to immediately move towards silencing or warning a user.
+
Most people listen to reason, and simply changing the subject is often an effective tactic in ceasing any buffoonery.
+
~question can be used to try to pull in a random conversation topic. 
+
Should trying to change the topic fail, one quiet is usually enough to change the subject quickly.
+
  
= Rule Breaking Procedure =
+
'''[time] is optional, where <integer> is a number and <units> is either h or m, for hours or minutes respectively. If a time is not specified the ban will remain in place until manually removed by an operator or a sysop.'''
  
=== As a member ===
+
'''<reason> should be a summary of the accumulated offenses. It should not, however, include direct links to any pads, as the reason is stated in any channel the user is kicked from. Please post pad links in #tripsit.me when requesting ban authorization.'''
  
*~report the user
+
'''Example: ~nban 3h toasterlizard Excessive shenanigans filling channels with spam.'''
  
=== As a TripSitter ===
+
This command can be used to remove users that have been causing repeated issues, and are unresponsive to quiets and warnings. Before a ban is issued, it should be discussed in #tripsit.me and should receive the approval of at least one other moderator, operator or sysop. (If another staff member is unavailable, certain cases do not require approval. Examples include: blatant sourcing, spamming/flooding, or extreme cases of trolling).
  
* Verbal warning to please chill out or leave the room.  
+
This command prevents a user from joining any offical TripSit Channel (channel tripbot is opped in). It will also kick the user from any channel the ban is applied in. Note that the user will still be able to access the network, PM people, and join non-TripSit channels. These abilities can be removed by requesting a kline from an operator.  
** In the event of serious trolls, this may be skipped.
+
* ~quiet <time> <#channel> <username> <reason> to quiet problematic users in #tripsit.
+
* ~report <user> and discuss the problem with other staff in #teamtripsit.
+
* Join #tripsit.me and say ~teamtripsit
+
  
=== As a Moderator ===
+
[[Category:TripSit]]
 
+
When you receive a ~report about a user, or witness the activity yourself:
+
* Verbal warning to please chill out.
+
* If user is doing a serious infraction, this may be skipped, and you may immediately:
+
* ~quiet the user for a specified time limit.
+
** For minor infractions 10 minutes is a pretty good number.
+
* Talk to the user.
+
** This may be the most important step. A user needs to know what they did wrong and should hear it from a human rather than a robot.
+
* ~warn the user (if necessary) providing information about the encounter.
+
** Warning will be sent via PM on most occasions as to avoid drama in the main channels and a note will be added to their file on Titan pad.
+
** Occasionally public warnings will be issued.
+
* If a ~warn is not necessary, ~notify #tripsit.me of the outcome of the interaction.
+
* If the above ~quiet was not timed, remember to undo the quiet.
+
 
+
== Remember to keep logs and documentation on Titan pad. ==
+

Latest revision as of 14:45, 28 May 2018

Moderator responsibilities would be best summed up with the word "guidance". Moderators' primary function is to enforce the rules and attempt to keep a positive environment! They represent our network and make sure that things are going smoothly, as well as having some more input on rule formation and other TripSit activites. Moderators are able to perform moderator actions via TripBot in all channels where tripbot has op, i.e. nbans and quiets will only take effect in rooms where tripbot has the 'o' flag. Whenever you have doubts/need advice/help, do not forget about ~teamtripsit or ask in #moderators! New moderators are asked to watch the process and ask questions for a while to get a feel for how we moderate. Please also make sure you are familiar with our general staff orientation.

Commands

Moderators have access to all commands described here, as well as the additional commands described below. See the rule breaking procedure for more information on how to react to a situation.

When using commands, remember to be descriptive - the commands are recorded, and are often looked upon when judging a user's history in its entirety, or when reviewing a particular event. In these cases, it's very helpful for the command reasons to provide context as to why it was used. As a rule of thumb, the reason for a warning, quiet, or timeout should include the rule(s) that have been broken. If you feel that there's more important context necessary, you can make a document on the Cloud, and add a note with a link to it. If you forget to add a descriptive reason to a command, or did not have time to do so, you can use the ~addnote command to add a reason subsequently.

Checking a users status

/msg tripbot ~ustatus <user>
/msg tripbot ~sustatus <user>
/msg tripbot ~concerning <user>

The ~ustatus command is great for getting the current status of a user (banned, unbanned, number of quiets, reports and warnings). For a listing of all reports, quiets, and warnings a user has accumulated, the commands ~sustatus is used. ~ustatus will provide a simple count of each, while ~sustatus will print the full reasons for reports, quiets, and warnings a user has been issued. Further, using the ~concerning command, you can get a user's history from when they have seeked help in #tripsit. As this is considered sensitive material, ~ustatus and ~sustatus can only be run in #tripsit.me, #tripbot, #moderators or in PM. ~concerning can be used only in #teamtripsit, #tripsitters, #tripsit.me and PM.

Shadow Quiet

/msg TripBot ~quiet [time(<integer><units>)] <#room> <user> <reason> #warn
/mode <channel> +z

While not used very often, this method has worked against repeat trolls who use free-VPN to get around a kline. After applying the quiet on a user, mode +z allows the messages from the user to still enter the channel, but are only visible by people with the +o flag. In effect, the user still thinks they're talking, but are not inconveniencing anyone by doing so. Changing modes in a channel requires an Operator's approval, so this is not a tactic to jump to right away, but it's possible in the event that it's agreed to be used.

Ban

/msg tripbot ~nban [time<integer><units>] <user> <reason>

[time] is optional, where <integer> is a number and <units> is either h or m, for hours or minutes respectively. If a time is not specified the ban will remain in place until manually removed by an operator or a sysop.

<reason> should be a summary of the accumulated offenses. It should not, however, include direct links to any pads, as the reason is stated in any channel the user is kicked from. Please post pad links in #tripsit.me when requesting ban authorization.

Example: ~nban 3h toasterlizard Excessive shenanigans filling channels with spam.

This command can be used to remove users that have been causing repeated issues, and are unresponsive to quiets and warnings. Before a ban is issued, it should be discussed in #tripsit.me and should receive the approval of at least one other moderator, operator or sysop. (If another staff member is unavailable, certain cases do not require approval. Examples include: blatant sourcing, spamming/flooding, or extreme cases of trolling).

This command prevents a user from joining any offical TripSit Channel (channel tripbot is opped in). It will also kick the user from any channel the ban is applied in. Note that the user will still be able to access the network, PM people, and join non-TripSit channels. These abilities can be removed by requesting a kline from an operator.

Top Contributors