added irc-how-to.org
This commit is contained in:
notnull
parent
0d67ff01c1
commit
045c299f81
229
md/irc-how-to.md
Normal file
229
md/irc-how-to.md
Normal file
@ -0,0 +1,229 @@
|
||||
Anarchy Planet IRC how to
|
||||
=========================
|
||||
|
||||
How to Connect
|
||||
--------------
|
||||
|
||||
### web
|
||||
|
||||
<https://irc.anarchyplanet.org>
|
||||
|
||||
### using a client
|
||||
|
||||
irc.anarchyplanet.org port 6667 irc.anarchyplanet.org port 6697 (SSL)
|
||||
km3jy7nrj3e2wiju.onion port 6667 || 6697
|
||||
|
||||
### using tor
|
||||
|
||||
<https://irc.anarchyplanet.org/pad/p/connect-to-apirc-with-tor>
|
||||
|
||||
Basic Commands
|
||||
--------------
|
||||
|
||||
/nick nickname Changes your nick.
|
||||
|
||||
/list Lists all channels on the current network.
|
||||
|
||||
/join \#channel Joins the specified channel.
|
||||
|
||||
/part \#channel Leaves the specified channel.
|
||||
|
||||
/quit \[message\] Disconnects from current server with optional leaving
|
||||
message.
|
||||
|
||||
/names \#channel Shows the nicks of all users on \#channel.
|
||||
|
||||
/msg nickname message Sends a private message to a user.
|
||||
|
||||
/query nickname message Sends a private message to a user and opens a
|
||||
private chat window.
|
||||
|
||||
/me action Prints "yourname action"
|
||||
|
||||
/notice nickname message Sends a notice to the specified user. Like a
|
||||
/msg, but usually makes a sound.
|
||||
|
||||
/whois nickname Shows information about the specified user. This action
|
||||
is not visible to the specified user.
|
||||
|
||||
/whowas nickname Shows information about a user who has quit.
|
||||
|
||||
Managing Nicknames (Nickserv)
|
||||
-----------------------------
|
||||
|
||||
/msg nickserv register password \[email\] Registers your current nick
|
||||
with NickServ with the chosen password and binds it to an e-mail address
|
||||
(optional).
|
||||
|
||||
/msg nickserv identify password Identifies your nick to NickServ using
|
||||
the password you set.
|
||||
|
||||
/msg nickserv recover nickname password Kills (forcibly disconnects)
|
||||
someone who has your registered nick.
|
||||
|
||||
/msg nickserv ghost nickname password Terminates a "ghost" IRC session
|
||||
that's using your nickname.
|
||||
|
||||
/msg nickserv set password yournewpassword Changes your password. NOTE:
|
||||
Under no circumstances should you change your nick to the letter O
|
||||
followed by 8 digit
|
||||
|
||||
Managing Channels (ChanServ)
|
||||
----------------------------
|
||||
|
||||
/msg chanserv register \#channel password description Registers the
|
||||
current channel to you with ChanServ and sets its password and
|
||||
description.
|
||||
|
||||
/msg chanserv set \#channel mlock modes Locks the channel's modes.
|
||||
|
||||
to unlock all of a channel's modes, use /msg chanserv set \#channel
|
||||
mlock +
|
||||
|
||||
Advanced Commands for the uberl337 **\***
|
||||
-----------------------------------------
|
||||
|
||||
### Advanced NickServ commands
|
||||
|
||||
1. User modes
|
||||
|
||||
*mode nickname +*-attributes \[data\] Setting people's modes (for
|
||||
current channel only). To set a user's mode outside of a channel,
|
||||
use *mode nickname \#channel +*- attributes
|
||||
|
||||
Some of the more important ones are: +q: User is owner of the
|
||||
current channel (prefix \~ or @) +a: User is an admin (SOP) on the
|
||||
current channel (prefix & or @). +o: User is an operator (AOP) on
|
||||
the current channel (prefix @). +h: User is a half-op on the current
|
||||
channel (prefix %). +v: User has voice on the current channel
|
||||
(prefix +).
|
||||
|
||||
For a complete list of user modes visit
|
||||
<https://wiki.inspircd.org/User_Modes>
|
||||
|
||||
### Advanced Chanserv commands
|
||||
|
||||
1. Commands
|
||||
|
||||
/msg chanserv set \#channel secure \[on|off\] Keeps everyone except
|
||||
aops, sops, and the founder from becoming ops.
|
||||
|
||||
/msg chanserv set \#channel keeptopic \[on|off\] Maintains the topic
|
||||
even if everyone leaves.
|
||||
|
||||
/msg chanserv set \#channel enforce \[on|off\] Restores
|
||||
op/halfop/voice if a person with op/halfop/voice
|
||||
gets de-opped/halfopped/voiced.
|
||||
|
||||
/msg chanserv set \#channel leaveops \[on|off\] Whether or not to
|
||||
allow the first person who join the channel to get ops.
|
||||
|
||||
/msg chanserv drop \#channel \[dropcode\] Un-registers the current
|
||||
channel to you with ChanServ.
|
||||
|
||||
/msg chanserv set \#channel founder \[nickname\] Sets the current
|
||||
channel's founder.
|
||||
|
||||
/msg chanserv set \#channel desc \[description\] Changes the current
|
||||
channel's description.
|
||||
|
||||
/msg chanserv set \#channel url \[address\] Associates a URL with
|
||||
the channel.
|
||||
|
||||
/msg chanserv set \#channel \[email@address\] Associates an email
|
||||
address with the channel.
|
||||
|
||||
2. Channel modes
|
||||
|
||||
Set a mode with: *mode \#channel +*-attribute \[data\]
|
||||
|
||||
/mode \#channel +k channelkey gives a channel a password
|
||||
|
||||
For a full list of Inspircd's channel modes visit
|
||||
<https://wiki.inspircd.org/Channel_Modes>
|
||||
|
||||
/kick \#channel nickname \[reason\] temporarily remove user from
|
||||
channel
|
||||
|
||||
### Moderating Channels
|
||||
|
||||
/kick nickname!userid@hostname removes user from channel, but does not
|
||||
ban them. They are able to join immediately.
|
||||
|
||||
/ban nickname!userid@hostname bans user from channel, but does not kick
|
||||
them. They are prevented from speaking but can still see the channel.
|
||||
|
||||
/kickban nickname!userid@hostname
|
||||
|
||||
Use /whois, /whowas or /who to find the information necessary for a ban.
|
||||
note: \* is a wildcard and can replace nickname, userid, parts of
|
||||
nickname or userid, hostname or a segment of a hostname.
|
||||
|
||||
/mode \#channel +b nickname!userid@hostname the same as /ban
|
||||
|
||||
1. Ban Examples:
|
||||
|
||||
joe!\*@* Will prevent anyone with the nick joe from joining.
|
||||
|
||||
**myg0t**!\* Will prevent anyone whose nick contains myg0t
|
||||
from joining.
|
||||
|
||||
mark!\*elc@\* Will prevent anyone with the nick mark and the userid
|
||||
elc from joining.
|
||||
|
||||
\*!\*@c-123-24-76-213.ga.isp.net Will prevent anyone with the host
|
||||
c-123-24-76-213.ga.isp.net from joining.
|
||||
|
||||
\*!\*@* Bans everyone. Don't do that.
|
||||
|
||||
### Access lists
|
||||
|
||||
/msg chanserv access \#channel add \[nickname\] \[level\] Adds nickname
|
||||
to the channel's access list at the specified level. /msg chanserv
|
||||
access channel del \[nickname\] Removes nickname from the channel's
|
||||
access list. /msg chanserv access \#channel list Displays the channel's
|
||||
access list. /msg chanserv access \#channel count Displays how many
|
||||
entries are in the channel's access list.
|
||||
|
||||
### Access levels
|
||||
|
||||
These may vary from network to network. For example, some networks do
|
||||
not go by tens and use 3, 4, 5, 10, etc.
|
||||
|
||||
Founder Full access to ChanServ functions, automatic opping upon
|
||||
entering channel. 100+ Makes the person an SOP, automatic opping upon
|
||||
entering channel. 50 Makes the parson an AOP, automatic opping upon
|
||||
entering channel. 40 Automatic half-opping. 30 Automatic voicing. 0 No
|
||||
special privileges. -1 May not be opped. -100 May not join the channel.
|
||||
Any nick not on the access list has an access level of 0.
|
||||
|
||||
\#AOPs and SOPs
|
||||
|
||||
\#\#AOPs Are automatically ops and can give themselves ops. Can
|
||||
give/take op/halfop/voice to/from other channel members. Can unban
|
||||
themselves. Receive memos sent to the whole channel. Can invite
|
||||
themselves to the channel.
|
||||
|
||||
\#\#SOPs Can do everything AOPs can. Can give and take AOP privileges.
|
||||
Receive memos sent to the channel's SOPs. Can add (but not remove)
|
||||
AKICKs. \#\#Viewing and setting privileges
|
||||
|
||||
Viewing AOP and SOP lists /msg chanserv aop \#channel list /msg chanserv
|
||||
sop \#channel list adding a AOP or SOP /msg chanserv \[AOP|SOP\] channel
|
||||
\[ADD|DEL|LIST|CLEAR\] \[nick | entry-list\]
|
||||
|
||||
\#\#AKICKs People on the AKICK list are automatically kicked and banned
|
||||
when they enter the channel. Bans made as a result of AKICK must be
|
||||
removed manually. /msg chanserv akick \#channel add host \[reason\] Adds
|
||||
host to \#channel's AKICK list \[for reason\]. /msg chanserv akick
|
||||
\#channel del host Removes host from the AKICK list. /msg chanserv akick
|
||||
\#channel list /msg chanserv akick \#channel view Displays the AKICK
|
||||
list. Color codes it's possible to color your text in irc. in most
|
||||
clients you can use control c then foreground,background (background is
|
||||
optional). examples: red text ^c4^. black text on a blue background
|
||||
^c1^,2. here's a full list of the color codes:
|
||||
|
||||
Number Name 00 white 01 black 02 blue (navy) 03 green 04 red 05 brown
|
||||
(maroon) 06 purple 07 orange (olive) 08 yellow 09 light green (lime) 10
|
||||
teal (a green/blue cyan) 11 light cyan (cyan / aqua) 12 light blue
|
||||
(royal) 13 pink (light purple / fuchsia) 14 grey 15 light grey (silver)
|
||||
263
org/inspircdathemelimnoria.org.html
Normal file
263
org/inspircdathemelimnoria.org.html
Normal file
@ -0,0 +1,263 @@
|
||||
Nbasic IRC commands to get you started: http://pad.anarchistnews.org/p/irc-how-to
|
||||
|
||||
|
||||
Questions
|
||||
|
||||
Q: will you leave the channel? I want to see what hpapens to ops, e.g., can I take them
|
||||
A: One needs to leave and join again to take over an empty channel.
|
||||
|
||||
Q: How do i identify the bot automatically using SASL or certificates?
|
||||
A: http://doc.supybot.aperio.fr/en/latest/use/identifying_to_services.html
|
||||
^ f you get an error about “Insufficient parameters for CERT”, CertFP is supported, and if you get an error about unknown command, it’s not supported.
|
||||
^ this is why I was trying to figure out how to enable SASL...
|
||||
|
||||
Inspircd
|
||||
inspircd user modes: https://wiki.inspircd.org/User_Modes
|
||||
inspircd channel modes: https://wiki.inspircd.org/Channel_Modes
|
||||
|
||||
to become an IRC pro, do these tasks!
|
||||
register a nick
|
||||
get a hostmask
|
||||
group another nick
|
||||
Register a channel
|
||||
set MLOCK
|
||||
set entry msg
|
||||
make private, secret, keyword-enabled
|
||||
Add people to access lists
|
||||
Fantasy Mode
|
||||
atheme flags: https://chanop.wordpress.com/2011/03/12/atheme-service-commands/
|
||||
|
||||
|
||||
Limnora (i.e. Novatore)
|
||||
register with novatore
|
||||
create an alias
|
||||
add an RSS
|
||||
|
||||
Register a Channel
|
||||
<notnull>This IRC is two different things: Inspircd and Atheme. Athme provides "services" which the best way to think about them is that they are bots that take commands.
|
||||
<notnull> chanserv, nickserv, memoserv, all are Atheme Services
|
||||
<notnull> when you register a channel you are sending a command to ChanServ to keep track of it
|
||||
<notnull> similiarly w/ your nick and nickserv
|
||||
<notnull> channels have properties that are set with flags
|
||||
<notnull> can you op me rfa?
|
||||
<notnull> do !op notnull
|
||||
<rfa> !op notnull
|
||||
/* ChanServ gives channel operator status to notnull
|
||||
<notnull> the ! is called 'fantasy mode'
|
||||
<notnull> it is an alias for /msg chanserv
|
||||
<notnull> you can set it to be whatever you want, but yes ! is atheme default for chanserv
|
||||
<notnull> !info
|
||||
-ChanServ- Information on #poetry:
|
||||
-ChanServ- Founder : rfa
|
||||
-ChanServ- Successor : (none)
|
||||
-ChanServ- Registered : Jan 01 19:30:41 2019 -0800 (1h 33m 11s ago)
|
||||
-ChanServ- Mode lock : +nt-lk
|
||||
-ChanServ- Flags : VERBOSE GUARD FANTASY
|
||||
-ChanServ- Prefix : ! (default)
|
||||
-ChanServ- *** End of Info ***
|
||||
<notnull> so channels have 'flags' that give them properties
|
||||
<notnull> the channel info shows the Mode lock: +nt-lk shows that this channel has the n and t flags locked as being on, and the l and k flags locked as being off
|
||||
<notnull> so I can never remember what these stupid flags are, but I'll just start with k, which is 'keyword'
|
||||
<notnull> this channel is 'locked' to have a -k flag, which means you can' tset a keyword (i.e. password) for it because chanserv is guarding it
|
||||
/* notnull sets channel keyword to paswd
|
||||
/* ChanServ removes channel keyword
|
||||
/* Channel #poetry modes: +nst
|
||||
/* Channel #poetry created on Tue Jan 1 22:29:50 2019
|
||||
<rfa> yikes
|
||||
<notnull> so if you want to fix that you have to remove it from the mlock
|
||||
<notnull> sooo the way to do that is
|
||||
<notnull> !set mlock k
|
||||
-ChanServ- You may only alter +OP modes.
|
||||
<rfa> !set mlock k
|
||||
<notnull> I got this result: -ChanServ- You may only alter +OP modes.
|
||||
<rfa> "ChanServ:The MLOCK for #poetry has been removed."
|
||||
/* notnull sets channel keyword to passwd
|
||||
/* Channel #poetry modes: +knst passwd
|
||||
/* Channel #poetry created on Tue Jan 1 22:29:50 2019
|
||||
<rfa> only ops can do this right?
|
||||
<notnull> so you'll have to go through all the flags, I cna never remeber what they all are, but you can, e.g.,make channels private, invite only, all kinds of stuff.
|
||||
<notnull> yes and there are also different access levels
|
||||
<rfa> and there's no need to lock a normal, open channel, right?
|
||||
<notnull> !access list
|
||||
-ChanServ- Entry Nickname/Host Role
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- 1 rfa <Custom>
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
<notnull> so, access lists are actually just 'templates' of flag groups
|
||||
<notnull> there are channel flags and user flags
|
||||
<Fauvenoir> flags... set... mode.... what's the difference?
|
||||
<notnull> good question ;)
|
||||
<notnull> !help flags
|
||||
-ChanServ- ***** ChanServ Help *****
|
||||
-ChanServ- Help for FLAGS:
|
||||
-ChanServ-
|
||||
-ChanServ- The FLAGS command allows for the granting/removal of channel
|
||||
-ChanServ- privileges on a more specific, non-generalized level. It
|
||||
-ChanServ- supports nicknames, groups and hostmasks as targets.
|
||||
-ChanServ-
|
||||
-ChanServ- When only the channel argument is given, a listing of
|
||||
-ChanServ- permissions granted to users will be displayed.
|
||||
-ChanServ-
|
||||
-ChanServ- Syntax: FLAGS <#channel>
|
||||
-ChanServ-
|
||||
-ChanServ- Otherwise, an access entry is modified. A modification may be
|
||||
-ChanServ- specified by a template name (changes the access to the
|
||||
-ChanServ- template) or a flags change (starts with + or -). See the
|
||||
-ChanServ- TEMPLATE help entry for more information about templates.
|
||||
-ChanServ-
|
||||
-ChanServ- If you are not a founder, you may only manipulate flags you
|
||||
-ChanServ- have yourself, and may not edit users that have flags you
|
||||
-ChanServ- don't have. For this purpose, +v grants the ability to grant
|
||||
-ChanServ- +V, +h grants the ability to grant +H, +o grants the ability
|
||||
-ChanServ- to grant +O, and +r grants the ability to grant +b.
|
||||
-ChanServ-
|
||||
-ChanServ-
|
||||
-ChanServ-
|
||||
-ChanServ- If you do not have +f you may still remove your own access
|
||||
-ChanServ- with -*.
|
||||
-ChanServ-
|
||||
-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group template]
|
||||
-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group flag_changes]
|
||||
-ChanServ-
|
||||
-ChanServ- Permissions:
|
||||
-ChanServ- +v - Enables use of the voice/devoice commands.
|
||||
-ChanServ- +V - Enables automatic voice.
|
||||
-ChanServ- +h - Enables use of the halfop/dehalfop commands.
|
||||
-ChanServ- +H - Enables automatic halfop.
|
||||
-ChanServ- +o - Enables use of the op/deop commands.
|
||||
-ChanServ- +O - Enables automatic op.
|
||||
-ChanServ- +a - Enables use of the protect/deprotect commands.
|
||||
-ChanServ- +q - Enables use of the owner/deowner commands.
|
||||
-ChanServ- +s - Enables use of the set command.
|
||||
-ChanServ- +i - Enables use of the invite and getkey commands.
|
||||
-ChanServ- +r - Enables use of the kick, kickban, ban and unban commands.
|
||||
-ChanServ- +R - Enables use of the recover, sync and clear commands.
|
||||
-ChanServ- +f - Enables modification of channel access lists.
|
||||
-ChanServ- +t - Enables use of the topic and topicappend commands.
|
||||
-ChanServ- +A - Enables viewing of channel access lists.
|
||||
-ChanServ- +F - Grants full founder access.
|
||||
-ChanServ- +b - Enables automatic kickban.
|
||||
-ChanServ- +e - Exempts from +b and enables unbanning self.
|
||||
-ChanServ-
|
||||
-ChanServ- The special permission +* adds all permissions except +b and +F.
|
||||
-ChanServ- The special permission -* removes all permissions including +b and +F.
|
||||
-ChanServ-
|
||||
-ChanServ- Examples:
|
||||
-ChanServ- /msg ChanServ FLAGS #foo
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com VOP
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com -V+oO
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com -*
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo +oOtsi
|
||||
-ChanServ- /msg ChanServ FLAGS #foo TroubleUser!*@*.troubleisp.net +b
|
||||
-ChanServ- /msg ChanServ FLAGS #foo !baz +*
|
||||
-ChanServ- ***** End of Help *****
|
||||
<rfa> oh do i need to set auto op for me so if i log out i don't lose it?
|
||||
<notnull> no you would always be op as founder of the channel
|
||||
/* rfa (rfa@nihilist.abyss) has left
|
||||
/* rfa (rfa@nihilist.abyss) has joined
|
||||
/* ChanServ sets mode +q on #poetry rfa
|
||||
/* ChanServ gives channel operator status to rfa
|
||||
<notnull> hehee
|
||||
<rfa> yikes
|
||||
<notnull> !set mlock + will remove all of the mlock flags, but only founders can do it.
|
||||
<notnull> !set mlock +
|
||||
-ChanServ- You may only alter +OP modes.
|
||||
<rfa> !set mlock +
|
||||
<rfa> ChanServ:The MLOCK for #poetry has been removed.
|
||||
<notnull> there are some other things like
|
||||
<notnull> !set topiclock on
|
||||
-ChanServ- You are not authorized to perform this command.
|
||||
<notnull> that keeps the topic even when you leave
|
||||
<rfa> !set topiclock on
|
||||
-ChanServ/#poetry- rfa enabled the TOPICLOCK flag
|
||||
<notnull> and !set guard on/off controls whether chanserv hangs out
|
||||
<rfa> nice
|
||||
<notnull> also, if you don't want ChanServ you can make a custom bot!
|
||||
<rfa> oh yes
|
||||
<rfa> if cs leaves that's bad, right?
|
||||
<notnull> if you do /bs assign milieu #poetry
|
||||
<rfa> why would i ever want no cs?
|
||||
<notnull> it will be milieu instead of chanserv
|
||||
<notnull> just a cooler name :P
|
||||
<rfa> what's bs stand for?
|
||||
<rfa> !set guard on
|
||||
<rfa> ah botserv
|
||||
<notnull> so your whole hostmask is hex3@anarchy-planete17.kfm.ujrisk.IP
|
||||
<notnull> hex = nick, hex3 = ident, all that other shit = hostname
|
||||
<notnull> a vhost changes the hostname to something custom.
|
||||
<notnull> to get a vhost, you request it from me.
|
||||
<hex> Oh ok, I see, give me a moment to think of my new hostname.
|
||||
<notnull> hehe I can just make something temporary for you?
|
||||
<hex> Violence.solves.everything?
|
||||
<notnull> LOL love it.
|
||||
<notnull> the bots 'recognize' you by your hostmask: that's the whole thing (nick!ident@hostname)
|
||||
<notnull> so now, when you come here, if you aren't 'logged in', ChanServ won't recognize you.
|
||||
<notnull> next: group a nick.
|
||||
<notnull> you just change your nick to whatever, and then you /ns group
|
||||
<notnull> you might wanna group hex_afk for example
|
||||
<abyss> next: access lists.
|
||||
<abyss> do this:
|
||||
<abyss> !access add notnull aop
|
||||
-ChanServ- You are not authorized to perform this operation.
|
||||
<hex> !access add notnull aop
|
||||
-ChanServ/#hexchannel- hex added notnull to the access list (with role: aop).
|
||||
<abyss> sweet
|
||||
<hex> What is the aop?
|
||||
<abyss> so now I will be auto-opped every time I enter this channel
|
||||
<abyss> !help access
|
||||
-ChanServ- ***** ChanServ Help *****
|
||||
-ChanServ- Help for ACCESS:
|
||||
-ChanServ-
|
||||
-ChanServ- The following subcommands are available:
|
||||
-ChanServ- ADD Add an access list entry.
|
||||
-ChanServ- DEL Delete an access list entry.
|
||||
-ChanServ- INFO Display information on an access list entry.
|
||||
-ChanServ- LIST List channel access entries.
|
||||
-ChanServ- SET Update an access list entry.
|
||||
-ChanServ-
|
||||
-ChanServ- For more information, use /msg ChanServ HELP ACCESS command.
|
||||
-ChanServ- ***** End of Help *****
|
||||
<abyss> "AOP" in this context is a template of permissions.
|
||||
<abyss> !access list
|
||||
-ChanServ- Entry Nickname/Host Role
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- 1 hex <Custom>
|
||||
-ChanServ- 2 notnull AOP
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- End of #hexchannel ACCESS listing.
|
||||
<abyss> there I am, AOP-tastic!
|
||||
<abyss> you can remove it too using !access del notnull
|
||||
<abyss> !access del notnull
|
||||
-ChanServ- notnull was removed from the AOP role in #hexchannel.
|
||||
<abyss> so you can get veeerrry precise about what kind of access you give others. I don't use it that much, the server is just too small. auto-op is one of the main ones that's important.
|
||||
<hex> I assume you'd do that by adding and removing them from various lists?
|
||||
<abyss> yes but ... you can actually put individual flags on people. access lists are just templates.
|
||||
<abyss> so for example you can !flags notnull +F
|
||||
<abyss> ;)
|
||||
<hex> !flags notnull +F
|
||||
-ChanServ/#hexchannel- hex set flags +Ff on notnull
|
||||
<abyss> MWAHAHAHA
|
||||
<abyss> !info
|
||||
<abyss> - Founder : hex, notnull
|
||||
<hex> What does that do?
|
||||
<abyss> hehe
|
||||
<abyss> it gives me Founder access which is basiclally the highest level
|
||||
<abyss> !access add plast aop
|
||||
-ChanServ/#hexchannel- abyss (notnull) added plast to the access list (with role: aop).
|
||||
/* ChanServ gives channel operator status to plast
|
||||
<abyss> see, now I can do shit like that
|
||||
<abyss> oh yes, novatore
|
||||
<abyss> novatore is a python-based IRC bot, but the best way to think about it is that it's v. similar to the way services work.
|
||||
<abyss> so she takes commands, her fantasy prefix is @
|
||||
<abyss> but
|
||||
<abyss> you have to register with her, just like you register with nickserv
|
||||
<abyss> it doesn't have to be the same nick or anything
|
||||
<hex> Is it helpful to use the same nick?
|
||||
<abyss> kind of... but only slightly
|
||||
<abyss> nov recognizes you through your hostname
|
||||
<abyss> whereas the Services bots authenticate your nick as well
|
||||
<abyss> @help register
|
||||
<novatore> (register <name> <password>) -- Registers <name> with the given password <password> and the current hostmask of the person registering. You shouldn't register twice; if you're not recognized as a user but you've already registered, use the hostmask add command to add another hostmask to your already-registered user, or use the identify command to identify just for a session. This command (and all other (1 more message)
|
||||
<abyss> @list
|
||||
<novatore> Admin, Alias, Anonymous, AttackProtector, AutoMode, Channel, Conditional, Config, Games, Google, Later, LinkRelay, MessageParser, Misc, Network, NickAuth, Note, Owner, PluginDownloader, Quote, RSS, Reply, SedRegex, Seen, User, Utilities, and Web
|
||||
<abyss> those are all of novatore's modules.
|
||||
250
org/irc-how-to.org
Normal file
250
org/irc-how-to.org
Normal file
@ -0,0 +1,250 @@
|
||||
* Anarchy Planet IRC how to
|
||||
** How to Connect
|
||||
*** web
|
||||
https://irc.anarchyplanet.org
|
||||
|
||||
*** using a client
|
||||
irc.anarchyplanet.org port 6667
|
||||
irc.anarchyplanet.org port 6697 (SSL)
|
||||
km3jy7nrj3e2wiju.onion port 6667 || 6697
|
||||
|
||||
*** using tor
|
||||
https://irc.anarchyplanet.org/pad/p/connect-to-apirc-with-tor
|
||||
** Basic Commands
|
||||
|
||||
/nick nickname
|
||||
Changes your nick.
|
||||
|
||||
/list
|
||||
Lists all channels on the current network.
|
||||
|
||||
/join #channel
|
||||
Joins the specified channel.
|
||||
|
||||
/part #channel
|
||||
Leaves the specified channel.
|
||||
|
||||
/quit [message]
|
||||
Disconnects from current server with optional leaving message.
|
||||
|
||||
/names #channel
|
||||
Shows the nicks of all users on #channel.
|
||||
|
||||
/msg nickname message
|
||||
Sends a private message to a user.
|
||||
|
||||
/query nickname message
|
||||
Sends a private message to a user and opens a private chat window.
|
||||
|
||||
/me action
|
||||
Prints "yourname action"
|
||||
|
||||
/notice nickname message
|
||||
Sends a notice to the specified user. Like a /msg, but usually makes a sound.
|
||||
|
||||
/whois nickname
|
||||
Shows information about the specified user. This action is not visible to the specified user.
|
||||
|
||||
/whowas nickname
|
||||
Shows information about a user who has quit.
|
||||
|
||||
** Managing Nicknames (Nickserv)
|
||||
|
||||
/msg nickserv register password [email]
|
||||
Registers your current nick with NickServ with the chosen password and binds it to an e-mail address (optional).
|
||||
|
||||
/msg nickserv identify password
|
||||
Identifies your nick to NickServ using the password you set.
|
||||
|
||||
/msg nickserv recover nickname password
|
||||
Kills (forcibly disconnects) someone who has your registered nick.
|
||||
|
||||
/msg nickserv ghost nickname password
|
||||
Terminates a "ghost" IRC session that's using your nickname.
|
||||
|
||||
/msg nickserv set password yournewpassword
|
||||
Changes your password. NOTE: Under no circumstances should you change your nick to the letter O followed by 8 digit
|
||||
|
||||
** Managing Channels (ChanServ)
|
||||
|
||||
/msg chanserv register #channel password description
|
||||
Registers the current channel to you with ChanServ and sets its password and description.
|
||||
|
||||
/msg chanserv set #channel mlock modes
|
||||
Locks the channel's modes.
|
||||
|
||||
to unlock all of a channel's modes, use /msg chanserv set #channel mlock +
|
||||
|
||||
** Advanced Commands for the uberl337 ***
|
||||
*** Advanced NickServ commands
|
||||
**** User modes
|
||||
|
||||
/mode nickname +/-attributes [data]
|
||||
Setting people's modes (for current channel only). To set a user's mode outside of a channel, use /mode nickname #channel +/- attributes
|
||||
|
||||
Some of the more important ones are:
|
||||
+q: User is owner of the current channel (prefix ~ or @)
|
||||
+a: User is an admin (SOP) on the current channel (prefix & or @).
|
||||
+o: User is an operator (AOP) on the current channel (prefix @).
|
||||
+h: User is a half-op on the current channel (prefix %).
|
||||
+v: User has voice on the current channel (prefix +).
|
||||
|
||||
For a complete list of user modes visit https://wiki.inspircd.org/User_Modes
|
||||
|
||||
*** Advanced Chanserv commands
|
||||
**** Commands
|
||||
/msg chanserv set #channel secure [on|off]
|
||||
Keeps everyone except aops, sops, and the founder from becoming ops.
|
||||
|
||||
/msg chanserv set #channel keeptopic [on|off]
|
||||
Maintains the topic even if everyone leaves.
|
||||
|
||||
/msg chanserv set #channel enforce [on|off]
|
||||
Restores op/halfop/voice if a person with op/halfop/voice gets de-opped/halfopped/voiced.
|
||||
|
||||
/msg chanserv set #channel leaveops [on|off]
|
||||
Whether or not to allow the first person who join the channel to get ops.
|
||||
|
||||
/msg chanserv drop #channel [dropcode]
|
||||
Un-registers the current channel to you with ChanServ.
|
||||
|
||||
/msg chanserv set #channel founder [nickname]
|
||||
Sets the current channel's founder.
|
||||
|
||||
/msg chanserv set #channel desc [description]
|
||||
Changes the current channel's description.
|
||||
|
||||
/msg chanserv set #channel url [address]
|
||||
Associates a URL with the channel.
|
||||
|
||||
/msg chanserv set #channel [email@address]
|
||||
Associates an email address with the channel.
|
||||
**** Channel modes
|
||||
|
||||
Set a mode with: /mode #channel +/-attribute [data]
|
||||
|
||||
/mode #channel +k channelkey
|
||||
gives a channel a password
|
||||
|
||||
For a full list of Inspircd's channel modes visit https://wiki.inspircd.org/Channel_Modes
|
||||
|
||||
/kick #channel nickname [reason]
|
||||
temporarily remove user from channel
|
||||
|
||||
*** Moderating Channels
|
||||
|
||||
/kick nickname!userid@hostname
|
||||
removes user from channel, but does not ban them. They are able to join immediately.
|
||||
|
||||
/ban nickname!userid@hostname
|
||||
bans user from channel, but does not kick them. They are prevented from speaking but can still see the channel.
|
||||
|
||||
/kickban nickname!userid@hostname
|
||||
|
||||
Use /whois, /whowas or /who to find the information necessary for a ban.
|
||||
note: * is a wildcard and can replace nickname, userid, parts of nickname or userid, hostname or a segment of a hostname.
|
||||
|
||||
/mode #channel +b nickname!userid@hostname
|
||||
the same as /ban
|
||||
|
||||
**** Ban Examples:
|
||||
|
||||
joe!*@*
|
||||
Will prevent anyone with the nick joe from joining.
|
||||
|
||||
*myg0t*!*
|
||||
Will prevent anyone whose nick contains myg0t from joining.
|
||||
|
||||
mark!*elc@*
|
||||
Will prevent anyone with the nick mark and the userid elc from joining.
|
||||
|
||||
*!*@c-123-24-76-213.ga.isp.net
|
||||
Will prevent anyone with the host c-123-24-76-213.ga.isp.net from joining.
|
||||
|
||||
*!*@*
|
||||
Bans everyone. Don't do that.
|
||||
|
||||
*** Access lists
|
||||
|
||||
/msg chanserv access #channel add [nickname] [level]
|
||||
Adds nickname to the channel's access list at the specified level.
|
||||
/msg chanserv access channel del [nickname]
|
||||
Removes nickname from the channel's access list.
|
||||
/msg chanserv access #channel list
|
||||
Displays the channel's access list.
|
||||
/msg chanserv access #channel count
|
||||
Displays how many entries are in the channel's access list.
|
||||
|
||||
*** Access levels
|
||||
|
||||
These may vary from network to network. For example, some networks do not go by tens and use 3, 4, 5, 10, etc.
|
||||
|
||||
Founder
|
||||
Full access to ChanServ functions, automatic opping upon entering channel.
|
||||
100+
|
||||
Makes the person an SOP, automatic opping upon entering channel.
|
||||
50
|
||||
Makes the parson an AOP, automatic opping upon entering channel.
|
||||
40
|
||||
Automatic half-opping.
|
||||
30
|
||||
Automatic voicing.
|
||||
0
|
||||
No special privileges.
|
||||
-1
|
||||
May not be opped.
|
||||
-100
|
||||
May not join the channel.
|
||||
Any nick not on the access list has an access level of 0.
|
||||
|
||||
#AOPs and SOPs
|
||||
|
||||
##AOPs
|
||||
Are automatically ops and can give themselves ops.
|
||||
Can give/take op/halfop/voice to/from other channel members.
|
||||
Can unban themselves.
|
||||
Receive memos sent to the whole channel.
|
||||
Can invite themselves to the channel.
|
||||
|
||||
##SOPs
|
||||
Can do everything AOPs can.
|
||||
Can give and take AOP privileges.
|
||||
Receive memos sent to the channel's SOPs.
|
||||
Can add (but not remove) AKICKs.
|
||||
##Viewing and setting privileges
|
||||
|
||||
Viewing AOP and SOP lists
|
||||
/msg chanserv aop #channel list
|
||||
/msg chanserv sop #channel list
|
||||
adding a AOP or SOP
|
||||
/msg chanserv [AOP|SOP] channel [ADD|DEL|LIST|CLEAR] [nick | entry-list]
|
||||
|
||||
##AKICKs
|
||||
People on the AKICK list are automatically kicked and banned when they enter the channel. Bans made as a result of AKICK must be removed manually.
|
||||
/msg chanserv akick #channel add host [reason]
|
||||
Adds host to #channel's AKICK list [for reason].
|
||||
/msg chanserv akick #channel del host
|
||||
Removes host from the AKICK list.
|
||||
/msg chanserv akick #channel list
|
||||
/msg chanserv akick #channel view
|
||||
Displays the AKICK list.
|
||||
Color codes
|
||||
it's possible to color your text in irc. in most clients you can use control c then foreground,background (background is optional). examples: red text ^c4. black text on a blue background ^c1,2. here's a full list of the color codes:
|
||||
|
||||
Number Name
|
||||
00 white
|
||||
01 black
|
||||
02 blue (navy)
|
||||
03 green
|
||||
04 red
|
||||
05 brown (maroon)
|
||||
06 purple
|
||||
07 orange (olive)
|
||||
08 yellow
|
||||
09 light green (lime)
|
||||
10 teal (a green/blue cyan)
|
||||
11 light cyan (cyan / aqua)
|
||||
12 light blue (royal)
|
||||
13 pink (light purple / fuchsia)
|
||||
14 grey
|
||||
15 light grey (silver)
|
||||
264
org/ircwalkthrough.org
Normal file
264
org/ircwalkthrough.org
Normal file
@ -0,0 +1,264 @@
|
||||
* Anarchy Planet IRC Walkthrough Tutorial
|
||||
basic commands: http://pad.anarchistnews.org/p/irc-how-to
|
||||
|
||||
|
||||
** Questions
|
||||
|
||||
Q: will you leave the channel? I want to see what hpapens to ops, e.g., can I take them
|
||||
A: One needs to leave and join again to take over an empty channel.
|
||||
|
||||
Q: How do i identify the bot automatically using SASL or certificates?
|
||||
A: http://doc.supybot.aperio.fr/en/latest/use/identifying_to_services.html
|
||||
^ f you get an error about “Insufficient parameters for CERT”, CertFP is supported, and if you get an error about unknown command, it’s not supported.
|
||||
^ this is why I was trying to figure out how to enable SASL...
|
||||
|
||||
Inspircd
|
||||
inspircd user modes: https://wiki.inspircd.org/User_Modes
|
||||
inspircd channel modes: https://wiki.inspircd.org/Channel_Modes
|
||||
|
||||
to become an IRC pro, do these tasks!
|
||||
register a nick
|
||||
get a hostmask
|
||||
group another nick
|
||||
Register a channel
|
||||
set MLOCK
|
||||
set entry msg
|
||||
make private, secret, keyword-enabled
|
||||
Add people to access lists
|
||||
Fantasy Mode
|
||||
atheme flags: https://chanop.wordpress.com/2011/03/12/atheme-service-commands/
|
||||
|
||||
|
||||
Limnora (i.e. Novatore)
|
||||
register with novatore
|
||||
create an alias
|
||||
add an RSS
|
||||
|
||||
Register a Channel
|
||||
<notnull>This IRC is two different things: Inspircd and Atheme. Athme provides "services" which the best way to think about them is that they are bots that take commands.
|
||||
<notnull> chanserv, nickserv, memoserv, all are Atheme Services
|
||||
<notnull> when you register a channel you are sending a command to ChanServ to keep track of it
|
||||
<notnull> similiarly w/ your nick and nickserv
|
||||
<notnull> channels have properties that are set with flags
|
||||
<notnull> can you op me rfa?
|
||||
<notnull> do !op notnull
|
||||
<rfa> !op notnull
|
||||
/* ChanServ gives channel operator status to notnull
|
||||
<notnull> the ! is called 'fantasy mode'
|
||||
<notnull> it is an alias for /msg chanserv
|
||||
<notnull> you can set it to be whatever you want, but yes ! is atheme default for chanserv
|
||||
<notnull> !info
|
||||
-ChanServ- Information on #poetry:
|
||||
-ChanServ- Founder : rfa
|
||||
-ChanServ- Successor : (none)
|
||||
-ChanServ- Registered : Jan 01 19:30:41 2019 -0800 (1h 33m 11s ago)
|
||||
-ChanServ- Mode lock : +nt-lk
|
||||
-ChanServ- Flags : VERBOSE GUARD FANTASY
|
||||
-ChanServ- Prefix : ! (default)
|
||||
-ChanServ- *** End of Info ***
|
||||
<notnull> so channels have 'flags' that give them properties
|
||||
<notnull> the channel info shows the Mode lock: +nt-lk shows that this channel has the n and t flags locked as being on, and the l and k flags locked as being off
|
||||
<notnull> so I can never remember what these stupid flags are, but I'll just start with k, which is 'keyword'
|
||||
<notnull> this channel is 'locked' to have a -k flag, which means you can' tset a keyword (i.e. password) for it because chanserv is guarding it
|
||||
/* notnull sets channel keyword to paswd
|
||||
/* ChanServ removes channel keyword
|
||||
/* Channel #poetry modes: +nst
|
||||
/* Channel #poetry created on Tue Jan 1 22:29:50 2019
|
||||
<rfa> yikes
|
||||
<notnull> so if you want to fix that you have to remove it from the mlock
|
||||
<notnull> sooo the way to do that is
|
||||
<notnull> !set mlock k
|
||||
-ChanServ- You may only alter +OP modes.
|
||||
<rfa> !set mlock k
|
||||
<notnull> I got this result: -ChanServ- You may only alter +OP modes.
|
||||
<rfa> "ChanServ:The MLOCK for #poetry has been removed."
|
||||
/* notnull sets channel keyword to passwd
|
||||
/* Channel #poetry modes: +knst passwd
|
||||
/* Channel #poetry created on Tue Jan 1 22:29:50 2019
|
||||
<rfa> only ops can do this right?
|
||||
<notnull> so you'll have to go through all the flags, I cna never remeber what they all are, but you can, e.g.,make channels private, invite only, all kinds of stuff.
|
||||
<notnull> yes and there are also different access levels
|
||||
<rfa> and there's no need to lock a normal, open channel, right?
|
||||
<notnull> !access list
|
||||
-ChanServ- Entry Nickname/Host Role
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- 1 rfa <Custom>
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
<notnull> so, access lists are actually just 'templates' of flag groups
|
||||
<notnull> there are channel flags and user flags
|
||||
<Fauvenoir> flags... set... mode.... what's the difference?
|
||||
<notnull> good question ;)
|
||||
<notnull> !help flags
|
||||
-ChanServ- ***** ChanServ Help *****
|
||||
-ChanServ- Help for FLAGS:
|
||||
-ChanServ-
|
||||
-ChanServ- The FLAGS command allows for the granting/removal of channel
|
||||
-ChanServ- privileges on a more specific, non-generalized level. It
|
||||
-ChanServ- supports nicknames, groups and hostmasks as targets.
|
||||
-ChanServ-
|
||||
-ChanServ- When only the channel argument is given, a listing of
|
||||
-ChanServ- permissions granted to users will be displayed.
|
||||
-ChanServ-
|
||||
-ChanServ- Syntax: FLAGS <#channel>
|
||||
-ChanServ-
|
||||
-ChanServ- Otherwise, an access entry is modified. A modification may be
|
||||
-ChanServ- specified by a template name (changes the access to the
|
||||
-ChanServ- template) or a flags change (starts with + or -). See the
|
||||
-ChanServ- TEMPLATE help entry for more information about templates.
|
||||
-ChanServ-
|
||||
-ChanServ- If you are not a founder, you may only manipulate flags you
|
||||
-ChanServ- have yourself, and may not edit users that have flags you
|
||||
-ChanServ- don't have. For this purpose, +v grants the ability to grant
|
||||
-ChanServ- +V, +h grants the ability to grant +H, +o grants the ability
|
||||
-ChanServ- to grant +O, and +r grants the ability to grant +b.
|
||||
-ChanServ-
|
||||
-ChanServ-
|
||||
-ChanServ-
|
||||
-ChanServ- If you do not have +f you may still remove your own access
|
||||
-ChanServ- with -*.
|
||||
-ChanServ-
|
||||
-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group template]
|
||||
-ChanServ- Syntax: FLAGS <#channel> [nickname|hostmask|group flag_changes]
|
||||
-ChanServ-
|
||||
-ChanServ- Permissions:
|
||||
-ChanServ- +v - Enables use of the voice/devoice commands.
|
||||
-ChanServ- +V - Enables automatic voice.
|
||||
-ChanServ- +h - Enables use of the halfop/dehalfop commands.
|
||||
-ChanServ- +H - Enables automatic halfop.
|
||||
-ChanServ- +o - Enables use of the op/deop commands.
|
||||
-ChanServ- +O - Enables automatic op.
|
||||
-ChanServ- +a - Enables use of the protect/deprotect commands.
|
||||
-ChanServ- +q - Enables use of the owner/deowner commands.
|
||||
-ChanServ- +s - Enables use of the set command.
|
||||
-ChanServ- +i - Enables use of the invite and getkey commands.
|
||||
-ChanServ- +r - Enables use of the kick, kickban, ban and unban commands.
|
||||
-ChanServ- +R - Enables use of the recover, sync and clear commands.
|
||||
-ChanServ- +f - Enables modification of channel access lists.
|
||||
-ChanServ- +t - Enables use of the topic and topicappend commands.
|
||||
-ChanServ- +A - Enables viewing of channel access lists.
|
||||
-ChanServ- +F - Grants full founder access.
|
||||
-ChanServ- +b - Enables automatic kickban.
|
||||
-ChanServ- +e - Exempts from +b and enables unbanning self.
|
||||
-ChanServ-
|
||||
-ChanServ- The special permission +* adds all permissions except +b and +F.
|
||||
-ChanServ- The special permission -* removes all permissions including +b and +F.
|
||||
-ChanServ-
|
||||
-ChanServ- Examples:
|
||||
-ChanServ- /msg ChanServ FLAGS #foo
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com VOP
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com -V+oO
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo!*@bar.com -*
|
||||
-ChanServ- /msg ChanServ FLAGS #foo foo +oOtsi
|
||||
-ChanServ- /msg ChanServ FLAGS #foo TroubleUser!*@*.troubleisp.net +b
|
||||
-ChanServ- /msg ChanServ FLAGS #foo !baz +*
|
||||
-ChanServ- ***** End of Help *****
|
||||
<rfa> oh do i need to set auto op for me so if i log out i don't lose it?
|
||||
<notnull> no you would always be op as founder of the channel
|
||||
/* rfa (rfa@nihilist.abyss) has left
|
||||
/* rfa (rfa@nihilist.abyss) has joined
|
||||
/* ChanServ sets mode +q on #poetry rfa
|
||||
/* ChanServ gives channel operator status to rfa
|
||||
<notnull> hehee
|
||||
<rfa> yikes
|
||||
<notnull> !set mlock + will remove all of the mlock flags, but only founders can do it.
|
||||
<notnull> !set mlock +
|
||||
-ChanServ- You may only alter +OP modes.
|
||||
<rfa> !set mlock +
|
||||
<rfa> ChanServ:The MLOCK for #poetry has been removed.
|
||||
<notnull> there are some other things like
|
||||
<notnull> !set topiclock on
|
||||
-ChanServ- You are not authorized to perform this command.
|
||||
<notnull> that keeps the topic even when you leave
|
||||
<rfa> !set topiclock on
|
||||
-ChanServ/#poetry- rfa enabled the TOPICLOCK flag
|
||||
<notnull> and !set guard on/off controls whether chanserv hangs out
|
||||
<rfa> nice
|
||||
<notnull> also, if you don't want ChanServ you can make a custom bot!
|
||||
<rfa> oh yes
|
||||
<rfa> if cs leaves that's bad, right?
|
||||
<notnull> if you do /bs assign milieu #poetry
|
||||
<rfa> why would i ever want no cs?
|
||||
<notnull> it will be milieu instead of chanserv
|
||||
<notnull> just a cooler name :P
|
||||
<rfa> what's bs stand for?
|
||||
<rfa> !set guard on
|
||||
<rfa> ah botserv
|
||||
<notnull> so your whole hostmask is hex3@anarchy-planete17.kfm.ujrisk.IP
|
||||
<notnull> hex = nick, hex3 = ident, all that other shit = hostname
|
||||
<notnull> a vhost changes the hostname to something custom.
|
||||
<notnull> to get a vhost, you request it from me.
|
||||
<hex> Oh ok, I see, give me a moment to think of my new hostname.
|
||||
<notnull> hehe I can just make something temporary for you?
|
||||
<hex> Violence.solves.everything?
|
||||
<notnull> LOL love it.
|
||||
<notnull> the bots 'recognize' you by your hostmask: that's the whole thing (nick!ident@hostname)
|
||||
<notnull> so now, when you come here, if you aren't 'logged in', ChanServ won't recognize you.
|
||||
<notnull> next: group a nick.
|
||||
<notnull> you just change your nick to whatever, and then you /ns group
|
||||
<notnull> you might wanna group hex_afk for example
|
||||
<abyss> next: access lists.
|
||||
<abyss> do this:
|
||||
<abyss> !access add notnull aop
|
||||
-ChanServ- You are not authorized to perform this operation.
|
||||
<hex> !access add notnull aop
|
||||
-ChanServ/#hexchannel- hex added notnull to the access list (with role: aop).
|
||||
<abyss> sweet
|
||||
<hex> What is the aop?
|
||||
<abyss> so now I will be auto-opped every time I enter this channel
|
||||
<abyss> !help access
|
||||
-ChanServ- ***** ChanServ Help *****
|
||||
-ChanServ- Help for ACCESS:
|
||||
-ChanServ-
|
||||
-ChanServ- The following subcommands are available:
|
||||
-ChanServ- ADD Add an access list entry.
|
||||
-ChanServ- DEL Delete an access list entry.
|
||||
-ChanServ- INFO Display information on an access list entry.
|
||||
-ChanServ- LIST List channel access entries.
|
||||
-ChanServ- SET Update an access list entry.
|
||||
-ChanServ-
|
||||
-ChanServ- For more information, use /msg ChanServ HELP ACCESS command.
|
||||
-ChanServ- ***** End of Help *****
|
||||
<abyss> "AOP" in this context is a template of permissions.
|
||||
<abyss> !access list
|
||||
-ChanServ- Entry Nickname/Host Role
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- 1 hex <Custom>
|
||||
-ChanServ- 2 notnull AOP
|
||||
-ChanServ- ----- ---------------------- ----
|
||||
-ChanServ- End of #hexchannel ACCESS listing.
|
||||
<abyss> there I am, AOP-tastic!
|
||||
<abyss> you can remove it too using !access del notnull
|
||||
<abyss> !access del notnull
|
||||
-ChanServ- notnull was removed from the AOP role in #hexchannel.
|
||||
<abyss> so you can get veeerrry precise about what kind of access you give others. I don't use it that much, the server is just too small. auto-op is one of the main ones that's important.
|
||||
<hex> I assume you'd do that by adding and removing them from various lists?
|
||||
<abyss> yes but ... you can actually put individual flags on people. access lists are just templates.
|
||||
<abyss> so for example you can !flags notnull +F
|
||||
<abyss> ;)
|
||||
<hex> !flags notnull +F
|
||||
-ChanServ/#hexchannel- hex set flags +Ff on notnull
|
||||
<abyss> MWAHAHAHA
|
||||
<abyss> !info
|
||||
<abyss> - Founder : hex, notnull
|
||||
<hex> What does that do?
|
||||
<abyss> hehe
|
||||
<abyss> it gives me Founder access which is basiclally the highest level
|
||||
<abyss> !access add plast aop
|
||||
-ChanServ/#hexchannel- abyss (notnull) added plast to the access list (with role: aop).
|
||||
/* ChanServ gives channel operator status to plast
|
||||
<abyss> see, now I can do shit like that
|
||||
<abyss> oh yes, novatore
|
||||
<abyss> novatore is a python-based IRC bot, but the best way to think about it is that it's v. similar to the way services work.
|
||||
<abyss> so she takes commands, her fantasy prefix is @
|
||||
<abyss> but
|
||||
<abyss> you have to register with her, just like you register with nickserv
|
||||
<abyss> it doesn't have to be the same nick or anything
|
||||
<hex> Is it helpful to use the same nick?
|
||||
<abyss> kind of... but only slightly
|
||||
<abyss> nov recognizes you through your hostname
|
||||
<abyss> whereas the Services bots authenticate your nick as well
|
||||
<abyss> @help register
|
||||
<novatore> (register <name> <password>) -- Registers <name> with the given password <password> and the current hostmask of the person registering. You shouldn't register twice; if you're not recognized as a user but you've already registered, use the hostmask add command to add another hostmask to your already-registered user, or use the identify command to identify just for a session. This command (and all other (1 more message)
|
||||
<abyss> @list
|
||||
<novatore> Admin, Alias, Anonymous, AttackProtector, AutoMode, Channel, Conditional, Config, Games, Google, Later, LinkRelay, MessageParser, Misc, Network, NickAuth, Note, Owner, PluginDownloader, Quote, RSS, Reply, SedRegex, Seen, User, Utilities, and Web
|
||||
<abyss> those are all of novatore's modules.
|
||||
Loading…
Reference in New Issue
Block a user