Moderator Orientation - Revision history

Reality at 14:45, 28 May 2018

2018-05-28T14:45:42Z

← Older revision		Revision as of 09:45, 28 May 2018
Line 3:		Line 3:
	=Commands=		=Commands=

	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.		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.

			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 ==		== Checking a users status ==

Reality at 14:59, 16 May 2018

2018-05-16T14:59:37Z

← Older revision		Revision as of 09:59, 16 May 2018
Line 3:		Line 3:
	=Commands=		=Commands=

	Moderators have access to all commands described [~~here~~ https://wiki.tripsit.me/wiki/Guardian_Orientation], as well as the additional commands described below.		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.

	== Checking a users status ==		== Checking a users status ==

Reality at 14:56, 16 May 2018

2018-05-16T14:56:39Z

Show changes

Reality at 16:01, 14 May 2018

2018-05-14T16:01:57Z

← Older revision		Revision as of 11:01, 14 May 2018
Line 1:		Line 1:
	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.		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 ==		== Reports ==

Bjorn: /* As a Moderator */

2017-05-25T22:25:54Z

As a Moderator

← Older revision		Revision as of 17:25, 25 May 2017
Line 116:		Line 116:
	5. ~warn the user (if necessary) providing information about the encounter.		5. ~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~~.		:* 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 record.

	:* Occasionally public warnings will be issued to show to others what the rules are, but please don't "make an example" out of anyone.		:* Occasionally public warnings will be issued to show to others what the rules are, but please don't "make an example" out of anyone.

Bjorn: /* Remember to keep logs and documentation on tripsitmods.tripsit.me when necessary. */

2017-05-25T22:22:12Z

Remember to keep logs and documentation on tripsitmods.tripsit.me when necessary.

← Older revision		Revision as of 17:22, 25 May 2017
Line 126:		Line 126:
	:* You can use ~remindme <time> <reason> to set a reminder for yourself to unquiet.		:* You can use ~remindme <time> <reason> to set a reminder for yourself to unquiet.

	= Remember to keep logs and documentation on ~~tripsitmods.tripsit.me~~ when necessary. =		= Remember to keep logs and documentation on TripCloud when necessary. =

	Thanks for reading! <3		Thanks for reading! <3

	[[Category:TripSit]]		[[Category:TripSit]]

LucidityStill: Fixed typo

2017-05-22T03:08:43Z

Fixed typo

← Older revision		Revision as of 22:08, 21 May 2017
Line 18:		Line 18:
	/msg tripbot ~concerning <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 ~~~concering~~ 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.'''		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.'''

	== Warning ==		== Warning ==

Toasterlizard: Updated with changes made to commands, minor formatting

2016-04-09T19:11:25Z

Updated with changes made to commands, minor formatting

← Older revision		Revision as of 14:11, 9 April 2016
Line 1:		Line 1:
	~~Summing up the~~ responsibilities ~~of a Moderator~~ would be 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.		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.

	==== Reports ====		== Reports ==

	/msg TripBot ~report <user> <reason>		/msg TripBot ~report [#channel] <user> <reason>

			'''[#channel] is optional; defaults to the channel the command was used in.'''
	'''<reason> should be as descriptive as possible, and may even include a link to a pad of logs.'''		'''<reason> should be as descriptive as possible, and may even include a link to a pad of logs.'''

Line 19:		Line 20:
	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 ~concering 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.'''		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 ~concering 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.'''

	==== Warning ====		== Warning ==

	/msg TripBot ~warn <user> <reason> #note		/msg TripBot ~warn <user> <reason> #note
Line 29:		Line 30:
	Warnings are counted and permanently stored for staff to view past events. These should be utilised as much as possible, as it provides a good record for us when considering a ban. The user is notified of the warning when it is issued, and is considered a formal warning. However, a warning is not a replacement for actually speaking to the user to explain what they did and why it's not acceptable. People appreciate being talked to by a human, rather than just being notified from an automatic system. Verbal warnings suffice most of the time, but it does not hurt to apply a #note warning (silent, non-formal) so that we can look back on it if needed. Repeat behaviour should usually lead to a formal warning, and sourcing ''always'' leads to a warning/quiet.		Warnings are counted and permanently stored for staff to view past events. These should be utilised as much as possible, as it provides a good record for us when considering a ban. The user is notified of the warning when it is issued, and is considered a formal warning. However, a warning is not a replacement for actually speaking to the user to explain what they did and why it's not acceptable. People appreciate being talked to by a human, rather than just being notified from an automatic system. Verbal warnings suffice most of the time, but it does not hurt to apply a #note warning (silent, non-formal) so that we can look back on it if needed. Repeat behaviour should usually lead to a formal warning, and sourcing ''always'' leads to a warning/quiet.

	==== Quiet ====		== Quiet ==

	/msg TripBot ~quiet <~~time in minutes~~> <#room> <user> <reason> #warn		/msg TripBot ~quiet [time(<integer><units>)] [#room] <user> <reason> #warn

	'''<time ~~in minutes>~~ is optional if you intend to manually remove the quiet when the situation has passed.'''		'''[time] is optional if you intend to manually remove the quiet when the situation has passed, where <integer> is a number and <units> is either h or m, for hours or minutes respectively.'''

	'''<#room> is optional if you are using the command in the target room.'''		'''<#room> is optional if you are using the command in the target room.'''

	'''#warn is used to automatically apply a warning with the quiet reason.'''		'''#warn is used to automatically apply a warning with the quiet reason.'''

			'''Example: ~quiet 5m Teknos Being a jerk.'''

			This command can be given to users to give them a 'time out' in a room. This will prevent the user from talking, but only in this room. You can set the time limit to your discretion, but generally small issues don't need more than a 5-10 minute quiet to get the point across.

	As a Moderator, this command will be your secondary mode of recourse against a problem user, after verbal warning have failed, or the infraction is severe enough to merit a 'time out'. This command prevents the user from speaking in the channel or changing their nickname; and also sends a notify to staff in that channel. For example, a ~quiet in #drugs will alert all moderators to the quiet, while a ~quiet in #tripsit will alert all tripsitters to the quiet. 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.		As a Moderator, this command will be your secondary mode of recourse against a problem user, after verbal warning have failed, or the infraction is severe enough to merit a 'time out'. This command prevents the user from speaking in the channel or changing their nickname; and also sends a notify to staff in that channel. For example, a ~quiet in #drugs will alert all moderators to the quiet, while a ~quiet in #tripsit will alert all tripsitters to the quiet. 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.
Line 45:		Line 50:
	Should trying to change the topic fail, one quiet is usually enough to change the subject quickly.		Should trying to change the topic fail, one quiet is usually enough to change the subject quickly.

	==== Shadow Quiet ====		== Shadow Quiet ==

	/msg TripBot ~quiet <~~time in minutes~~> <#room> <user> <reason> #warn		/msg TripBot ~quiet [time(<integer><units>)] <#room> <user> <reason> #warn

	/mode <channel> +z		/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 ~~visable~~ 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.		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 ====		== Ban ==

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

	'''<~~hours~~> is ~~optional~~. If a time is not specified the ban will remain in place until manually removed by an operator or a sysop.'''		'''[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.'''		'''<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 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).
Line 65:		Line 72:
	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.		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.

	==== Notify ====		== Notify ==

	/msg TripBot ~notify <channel> <event>		/msg TripBot ~notify <channel> <event>
Line 73:		Line 80:
	= Rule Breaking Procedure =		= Rule Breaking Procedure =

	=== As a member ===		=== As a staff member/user ===

	1. ~report the user		1. ~report the user
Line 83:		Line 90:
	:* In the event of serious trolls, this may be skipped.		:* In the event of serious trolls, this may be skipped.

	2. ~quiet <time> <#channel> <username> <reason> to quiet problematic users in #tripsit.		2. ~quiet [time] <#channel> <username> <reason> to quiet problematic users in #tripsit.

	3. ~report <user> and discuss the problem with other staff in #teamtripsit.		3. ~report <user> and discuss the problem with other staff in #teamtripsit.
Line 121:		Line 128:
	= Remember to keep logs and documentation on tripsitmods.tripsit.me when necessary. =		= Remember to keep logs and documentation on tripsitmods.tripsit.me when necessary. =

	Thanks for reading!		Thanks for reading! <3

	[[Category:TripSit]]		[[Category:TripSit]]

Teknos at 00:56, 8 August 2015

2015-08-08T00:56:42Z

← Older revision		Revision as of 19:56, 7 August 2015
Line 11:		Line 11:
	==== Checking a users status ====		==== Checking a users status ====

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

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

	/msg tripbot ~concerning <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 ~concering 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.'''		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 ~concering 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.'''
Line 47:		Line 47:
	==== Shadow Quiet ====		==== Shadow Quiet ====

	/msg TripBot ~quiet <time in minutes> <#room> <user> <reason> #warn		/msg TripBot ~quiet <time in minutes> <#room> <user> <reason> #warn

	/mode <channel> +z		/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 visable 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.		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 visable 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.
Line 55:		Line 55:
	==== Ban ====		==== Ban ====

	/msg tripbot ~nban <time in hours> <user> <reason>		/msg tripbot ~nban <time in hours> <user> <reason>

	'''<hours> is optional. If a time is not specified the ban will remain in place until manually removed by an operator or a sysop.'''		'''<hours> is optional. If a time is not specified the ban will remain in place until manually removed by an operator or a sysop.'''

Teknos at 00:54, 8 August 2015

2015-08-08T00:54:46Z

Show changes