Replicant » Replicant infrastructure

h1. IRC

h2. Introduction

See the "IRC section in the CommunityAndContact wiki page":https://redmine.replicant.us/projects/replicant/wiki/CommunityAndContact#IRC on the Replicant wiki for more details on how IRC is used.

h2. Freenode

This documentation was for when we used Freenode. It needs to be replaced with documentation for Libera Chat.

Now we migrated to Libera Chat instead. We also have a bridge that bridges the #replicant channels on Hackint, Libera Chat, and OFTC.

h3. How to make someone operator temporarily

Syntax: @/mode #replicant +o <nickname>@

Example: @/mode #replicant +o GNUtoo@

h3. How to make someone operator automatically

To get the help on Freenode, and with irssi, you could use: @/query ChanServ HELP FLAGS@

It will switch to the ChanServ window and show the help.

At the time of writing this gives:

<pre>

***** ChanServ Help *****

Help for FLAGS:

The FLAGS command allows for the granting/removal of channel

privileges on a more specific, non-generalized level. It

supports nicknames, groups and hostmasks as targets.

When only the channel argument is given, a listing of

permissions granted to users will be displayed.

Syntax: FLAGS <#channel>

Otherwise, an access entry is modified. A modification may be

specified by a template name (changes the access to the

template) or a flags change (starts with + or -). See the

TEMPLATE help entry for more information about templates.

If you are not a founder, you may only manipulate flags you

have yourself, and may not edit users that have flags you

don't have. For this purpose, +v grants the ability to grant

+V, +o grants the ability to grant +O, and +r grants the

ability to grant +b.

As of Atheme 7.0, there are now extended entity targets

which allow you to match chanacs against a situation instead

of against a nickname, hostmask or group.

Available exttargets are:

$chanacs:#channel - Any user with channel access in the given channel

                      (including hostmasks).

If you do not have +f you may still remove your own access

with -*.

Syntax: FLAGS <#channel> [nickname|hostmask|group template]

Syntax: FLAGS <#channel> [nickname|hostmask|group flag_changes]

Permissions:

    +v - Enables use of the voice/devoice commands.

    +V - Enables automatic voice.

    +o - Enables use of the op/deop commands.

    +O - Enables automatic op.

    +s - Enables use of the set command.

    +i - Enables use of the invite and getkey commands.

    +r - Enables use of the unban command.

    +R - Enables use of the recover, sync and clear commands.

    +f - Enables modification of channel access lists.

    +t - Enables use of the topic and topicappend commands.

    +A - Enables viewing of channel access lists.

    +S - Marks the user as a successor.

    +F - Grants full founder access.

    +b - Enables automatic kickban.

    +e - Exempts from +b and enables unbanning self.

The special permission +* adds all permissions except +b, +S, and +F.

The special permission -* removes all permissions including +b and +F.

Examples:

    /msg ChanServ FLAGS #foo

    /msg ChanServ FLAGS #foo foo!*@bar.com VOP

    /msg ChanServ FLAGS #foo foo!*@bar.com -V+oO

    /msg ChanServ FLAGS #foo foo!*@bar.com -*

    /msg ChanServ FLAGS #foo foo +oOtsi

    /msg ChanServ FLAGS #foo TroubleUser!*@*.troubleisp.net +b

    /msg ChanServ FLAGS #foo !baz +*

***** End of Help *****

</pre>

So to make @GNUtoo@ an operator we can use: @/msg ChanServ FLAGS #replicant GNUtoo +O@

h2. OFTC

TODO

h2. See also

* The "Infrastructure":https://redmine.replicant.us/projects/replicant/wiki/Infrastructure page on the Replicant wiki has many information on the IRC channel(s) too.