Additional Channel Founders - Revision history

Nero at 17:03, 8 February 2025

2025-02-08T17:03:46Z

← Older revision		Revision as of 17:03, 8 February 2025
Line 10:		Line 10:

	1. Create the group		1. Create the group
	<pre>		<pre>/msg GroupServ REGISTER !MyChannelFounders</pre>
	/msg GroupServ REGISTER !MyChannelFounders
	</pre>
	- This registers a group named '''!MyChannelFounders'''.		- This registers a group named '''!MyChannelFounders'''.
	- You will automatically be set as the group's founder.		- You will automatically be set as the group's founder.

	2. Add additional users to the group		2. Add additional users to the group
	<pre>		<pre>/msg GroupServ FLAGS !MyChannelFounders Nickname +Amc</pre>
	/msg GroupServ FLAGS !MyChannelFounders Nickname +Amc
	</pre>
	- Replace '''Nickname''' with the username of the person you want to add.		- Replace '''Nickname''' with the username of the person you want to add.
	- The `+Amc` flags grant them '''channel founder access''', but they '''cannot modify the group itself''' (i.e., they cannot add or remove other users from the group).		- The `+Amc` flags grant them '''channel founder access''', but they '''cannot modify the group itself''' (i.e., they cannot add or remove other users from the group).
Line 48:		Line 44:

	1. Grant all channel flags (except founder flags) to the group		1. Grant all channel flags (except founder flags) to the group
	<pre>		<pre>/msg ChanServ FLAGS #Channel !MyChannelFounders +*</pre>
	/msg ChanServ FLAGS #Channel !MyChannelFounders +*
	</pre>
	- This ensures that all members of the group get full channel access, except founder privileges.		- This ensures that all members of the group get full channel access, except founder privileges.

	2. Assign founder status to the group		2. Assign founder status to the group
	<pre>		<pre>/msg ChanServ FLAGS #Channel !MyChannelFounders +F</pre>
	/msg ChanServ FLAGS #Channel !MyChannelFounders +F
	</pre>
	- This makes the group an '''official channel founder''', granting all members of the group full channel access, including founder privileges.		- This makes the group an '''official channel founder''', granting all members of the group full channel access, including founder privileges.

Line 63:		Line 55:
	To confirm that the group is now the channel founder, use the following command:		To confirm that the group is now the channel founder, use the following command:

	<pre>		<pre>/msg ChanServ INFO #Channel</pre>
	/msg ChanServ INFO #Channel
	</pre>

	You should see '''!MyChannelFounders''' listed as the channel founder including your own nickname.		You should see '''!MyChannelFounders''' listed as the channel founder including your own nickname.
Line 71:		Line 61:
	If you wish to '''remain hidden''' and remove yourself as an individual founder, use:		If you wish to '''remain hidden''' and remove yourself as an individual founder, use:

	<pre>		<pre>/msg ChanServ FLAGS #Channel MyNickname -* </pre>
	/msg ChanServ FLAGS #Channel MyNickname -*
	</pre>
	This will remove your personal founder access, but you'll still have control via the '''!MyChannelFounders''' group.		This will remove your personal founder access, but you'll still have control via the '''!MyChannelFounders''' group.

Nero: /* Important Advisory */

2025-02-08T15:28:31Z

Important Advisory

← Older revision		Revision as of 15:28, 8 February 2025
Line 104:		Line 104:
	== Important Advisory ==		== Important Advisory ==

	Be cautious when adding multiple channel founders. The more founders you have, the '''higher the risk of a takeover''', as any founder can add new users to the access list and modify channel settings. However, ops can be notified of changes via the following command:		Be cautious when adding multiple channel founders. The more founders you have, the '''higher the risk of a takeover''', as any founder can add new users to the access list and modify channel settings.

			However, operators (ops) can be notified of any changes via a notice using the following command:

	<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>		<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>

Nero: /* Example Usage */

2025-02-08T15:26:49Z

Example Usage

← Older revision		Revision as of 15:26, 8 February 2025
Line 86:		Line 86:
	/msg GroupServ FLAGS !ExampleFounders Charlie +Amc		/msg GroupServ FLAGS !ExampleFounders Charlie +Amc
	/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +*		/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +*
	/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +F		/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +F
	</pre>		</pre>

Line 92:		Line 92:

	* They '''cannot''' modify the group itself (i.e., they cannot add or remove group members).		* They '''cannot''' modify the group itself (i.e., they cannot add or remove group members).
	* They '''can''' add other users to the channel's access list, including vop, aop, sop, custom flags, and akicks.		* They '''can''' add other users to the channel's access list, including vop, aop, sop, custom flags, adding/removing other channel founders, and managing akicks.

	== Advantages of Using GroupServ for Founders ==		== Advantages of Using GroupServ for Founders ==

Nero at 15:24, 8 February 2025

2025-02-08T15:24:35Z

← Older revision		Revision as of 15:24, 8 February 2025
Line 96:		Line 96:
	== Advantages of Using GroupServ for Founders ==		== Advantages of Using GroupServ for Founders ==

	* You can have up to 100 founders instead of just 5.		* You can have up to '''100 founders''' instead of just 5.
	* You can manage founders more easily using a single group.		* You can manage founders more easily using a '''single group'''.
	* It keeps the channel founder list hidden, improving security.		* It keeps the '''channel founder list hidden''', improving security.
	* You can easily send memos to other group members using:		* You can easily send '''memos''' to other group members using:
	<pre>/msg Memoserv send !ExampleFounders message</pre>		<pre>/msg Memoserv send !ExampleFounders message</pre>

Nero: /* Example Usage */

2025-02-08T15:23:34Z

Example Usage

← Older revision		Revision as of 15:23, 8 February 2025
Line 86:		Line 86:
	/msg GroupServ FLAGS !ExampleFounders Charlie +Amc		/msg GroupServ FLAGS !ExampleFounders Charlie +Amc
	/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +*		/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +*
	/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +Ff		/msg ChanServ FLAGS #ExampleChannel !ExampleFounders +F
	</pre>		</pre>

Nero: /* Assigning the Group as a Channel Founder */

2025-02-08T15:23:26Z

Assigning the Group as a Channel Founder

← Older revision		Revision as of 15:23, 8 February 2025
Line 55:		Line 55:
	2. Assign founder status to the group		2. Assign founder status to the group
	<pre>		<pre>
	/msg ChanServ FLAGS #Channel !MyChannelFounders +Ff		/msg ChanServ FLAGS #Channel !MyChannelFounders +F
	</pre>		</pre>
	- This makes the group an '''official channel founder''', granting all members of the group full channel access, including founder privileges.		- This makes the group an '''official channel founder''', granting all members of the group full channel access, including founder privileges.

Nero: /* Important Advisory */

2025-02-08T15:13:02Z

Important Advisory

← Older revision		Revision as of 15:13, 8 February 2025
Line 108:		Line 108:
	<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>		<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>

	Only grant founder access to those you completely trust.		Only grant founder access to those you '''completely trust'''.

	== Additional Settings ==		== Additional Settings ==

Nero: /* Important Advisory */

2025-02-08T15:12:08Z

Important Advisory

← Older revision		Revision as of 15:12, 8 February 2025
Line 104:		Line 104:
	== Important Advisory ==		== Important Advisory ==

	Be cautious when adding multiple channel founders. The more founders you have, the higher the risk of a takeover, as any founder can add new users to the access list and modify channel settings. However, ops can be notified of changes via the following command:		Be cautious when adding multiple channel founders. The more founders you have, the '''higher the risk of a takeover''', as any founder can add new users to the access list and modify channel settings. However, ops can be notified of changes via the following command:

	<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>		<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>

Nero: /* Important Advisory */

2025-02-08T15:11:39Z

Important Advisory

← Older revision		Revision as of 15:11, 8 February 2025
Line 104:		Line 104:
	== Important Advisory ==		== Important Advisory ==

	Be cautious when adding multiple channel founders. The more founders you have, the ~~'''~~higher the risk of a takeover~~'''~~, as any founder can add new users to the access list.		Be cautious when adding multiple channel founders. The more founders you have, the higher the risk of a takeover, as any founder can add new users to the access list and modify channel settings. However, ops can be notified of changes via the following command:

	Only grant founder access to those you ~~'''~~completely trust~~'''~~.		<pre>/msg ChanServ SET #Channel VERBOSE OPS</pre>

			Only grant founder access to those you completely trust.

	== Additional Settings ==		== Additional Settings ==

Nero at 15:09, 8 February 2025

2025-02-08T15:09:18Z

← Older revision		Revision as of 15:09, 8 February 2025
Line 96:		Line 96:
	== Advantages of Using GroupServ for Founders ==		== Advantages of Using GroupServ for Founders ==

	* You can have up to ~~'''~~100 founders~~'''~~ instead of just 5.		* You can have up to 100 founders instead of just 5.
	* You can manage founders more easily using a ~~'''~~single group~~'''~~.		* You can manage founders more easily using a single group.
	* It keeps the ~~'''~~channel founder list hidden~~'''~~, improving security.		* It keeps the channel founder list hidden, improving security.
	* You can easily send ~~'''~~memos~~'''~~ to other group members using /msg ~~memoserv~~ send !ExampleFounders message		* You can easily send memos to other group members using:
			<pre>/msg Memoserv send !ExampleFounders message</pre>

	== Important Advisory ==		== Important Advisory ==