|
| |
|
Sunday, 03 September 2006 |
19:25 <@ nenolod> Recently, we have switched to a new ircd software called Charybdis.
19:26 <@ nenolod> We also switched to an updated version of Services, version 1.5.
19:26 <@ nenolod> Both applications have new features, which we will cover here. :)
19:27 <@ nenolod> jacob is primarily in charge of services at present, you'll have a chance to request any features after the end of this class.
19:27 <@ nenolod> Now, to explain how the class works
19:27 <@ nenolod> Basically, we're going to go through a few topics at a time, then have a few moments for questions regarding those topics.
19:28 <@ nenolod> Then we will go through some more topics, etcetera.
19:28 <@ nenolod> So, lets start off with a few channel modes.
19:28 <@ nenolod> First of all, we have made some changes to the behaviour of channel mode +c.
19:29 <@ nenolod> Instead of blocking colours to the channel like it used to, it now removes the colours from the messages sent to the channel.
19:29 <@ nenolod> You can toggle this feature via /mode #channel +c or /mode #channel -c.
19:29 <@ nenolod> This will turn the feature on and off, respectively.
19:30 <@ nenolod> +c also blocks bold, underline, beep and inverse.
19:30 <@ nenolod> Many of you have been wondering about the changes we have made to /cs invite, I will cover this next.
19:30 <@ nenolod> The new ircd has ban exceptions and invite exceptions (+e and +I masks, respectively).
19:31 <@ nenolod> Masks which are in the +e list, will be able to join through a ban.
19:31 <@ nenolod> Masks which are in the +I list will be able to join through +i without having to use /cs invite.
19:31 <@ [twisti]> thats a capital i, for those with odd fonts ;)
19:32 <@ nenolod> You can set an exception, via /mode #channel +e mask
19:32 <@ nenolod> for example, /mode #opschool +e *!*@*.ipt.aol.com
19:32 <@ nenolod> to set a ban exception on AOL users.
19:32 <@ nenolod> For an invite exception, it is the same syntax, but you use +I instead of +e, or +b.
19:33 <@ nenolod> Next, we'll cover quiets.
19:33 <@ nenolod> Quiets can be used to selectively moderate specific hostmasks in a channel.
19:33 <@ nenolod> They are useful for discouraging troublemakers without increasing drama in the channel.
19:33 <@ nenolod> Quiets were implemented in the previous ircd software, as +b $q:mask
19:34 <@ nenolod> Now, you will need to do /mode +q mask instead.
19:34 <@ nenolod> You can set a client by /mode #channel +q mask. For example:
19:34 <@ Phrea> check
19:35 <@ nenolod> /mode #opschool +q zyzychyn!*@*, would quiet zyzychyn.
19:35 <@ nenolod> Those who are voiced or opped can talk through a quiet.
19:35 <@ nenolod> We're going to pause for a moment now to allow people to ask questions over this material.
19:35 <@ nenolod> Yeah.
19:36 <@ nenolod> A mask is a collection of wildcards and seperators which describe a client.
19:36 <@ nenolod> Masks are described as nick!user@host.
19:36 <@ [twisti]> it should be mentioned that +q still allows people to join, but not to change their nickname
19:36 <@ nenolod> Yeah, +q will allow people to still join.
19:36 <@ nenolod> Anyhow, going to open the channel up for questions now.
19:36 <@ nenolod> 12:44 < FurrySaint> So Quiet is a singular +m then? <- Yes
19:37 <@ nenolod> 12:45 < Ryoga> so +q also preventsfrom nick changes? <- Yes, but it isn't intended for that.
19:37 <@ Lockwood> +q will act as a form of moderation, but +z will not work with it
19:37 <@ jilles> or /quote help cmode
19:38 <@ nenolod> 12:46 < Rize> can you +q let's say all aol users, or is it meant only for individual users? <- Yes. *!*@*.ipt.aol.com
19:38 <@ jilles> +q'ed users can still join
19:38 <@ Lockwood> +z allows messages in a moderated channel to go to the voices & ops in a channel
19:39 <@ jilles> Silva, yeah you can /mode #channel q like you can /mode #channel b
19:39 <@ nenolod> 12:47 < Silva> can other uses see who is +q ? <- Yes. /mode #channel q will bring up the list.
19:40 <@ nenolod> Ok, carrying on, I gues.s
19:40 <@ nenolod> 12:48 < Ehlanna> nenolod: did you mean q for listing. I did a -1 (by mistake?) and it listed
19:41 <@ nenolod> ^- Passing anything without an argument will display the list.
19:41 <@ nenolod> Linkshot: ^G, \007
19:41 <@ Lockwood> I stand corrected
19:41 <@ nenolod> ok
19:42 <@ nenolod> The next thing we're going to go over is stuff you've already seen before.
19:42 <@ nenolod> Charybdis (and sorircd, and unreal) have an extended ban system.
19:42 <@ nenolod> These `extended bans', or `ban conditionals', allow you to define special criteria for bans to work on.
19:43 <@ nenolod> These criteria can be applied to bans (+b), exceptions (+e), invites (+I) and quiets (+q).
19:44 <@ nenolod> The first one I am going to go over is $a.
19:44 <@ nenolod> $a is actually new.
19:44 <@ nenolod> It will let you ban by the nickname the user is identified to.
19:44 <@ nenolod> You can set it by /mode #channel +b $a:whatevernick
19:45 <@ nenolod> For example, /mode #channel +b $a:Milambar would ban anybody identified to Milambar's nick from #channel.
19:45 <@ nenolod> jacob: ok
19:46 <@ nenolod> The next one we're going to go over is $g.
19:46 <@ nenolod> $g lets you ban by "gecos", or the realname information sent to the IRC server by your client.
19:46 <@ nenolod> You can set it by /mode #channel +b $g:whoever.
19:46 <@ [twisti]> this one is very useful for people who keep changing their nick and their ip via dialin to avoid bans
19:47 <@ nenolod> For instance, /mode #opschool +b $g:Jacob*Herpin would ban our good friend jacob from #opschool ;)
19:47 <@ jacob> or, if you don't like people named william, you'd /mode #opschool +b $g:*William*
19:47 <@ nenolod> You can see the gecos information of a client, via /whois
19:47 <@ [twisti]> the gecos field is the field often referred to as 'real name' field
19:47 <@ nenolod> you can also use ? instead of * in these masks.
19:48 <@ nenolod> (? will match against only one character, while * matches against many)
19:48 <@ [twisti]> if you write /whois nenolod, it would be the part that says "William Pitcock"
19:48 <@ nenolod> ok
19:48 <@ nenolod> we're going to cover $r next
19:48 <@ jacob> and that would be why i don't like people named william ;p
19:48 <@ Lockwood> Real*Name would catch "Real name" and "Really good name", Real?Name won't
19:48 <@ nenolod> $r bans let you ban by who is or is not in a channel.
19:49 <@ nenolod> If you set /mode #channel +b $~r:#somechannel, you must be in #somechannel to join #channel.
19:50 <@ [twisti]> this is especially useful for those role playing channels that have an OOC channel
19:50 <@ nenolod> If you set /mode #channel +b $r:#somechannel, you can't be in #somechannel if you want to join #channel.
19:50 <@ nenolod> ok
19:50 <@ nenolod> we're going to go over Lockwood's favourite one
19:50 <@ Phrea> :D
19:50 <@ Lockwood> The Lockyban?
19:51 <@ Phrea> YES !!
19:51 <@ Lockwood> Yay
19:51 <@ jacob> +gay?
19:51 <@ Lockwood> +q jacob!*@*
19:51 <@ Phrea> Lockwood: you made me puke through my nose just now
19:51 <@ Phrea> :\
19:51 <@ jacob> no offense to all you gay people out there by comparing you to locky :(
19:51 <@ nenolod> ok
19:51 <@ [twisti]> we forgive you
19:51 <@ Phrea> jacob: last warning
19:51 <@ nenolod> The $x ban combines the $g ban with a standard banmask.
19:52 <@ nenolod> It's syntax is:
19:52 <@ nenolod> /mode #channel +b $x:nick!user@host#realname
19:52 <@ nenolod> This is useful if you want to only do $g banning against some ranges.
19:53 <@ nenolod> Alright.
19:53 <@ nenolod> That covers extbans.
19:53 <@ nenolod> Opening back up for questions.
19:53 <@ Lockwood> Why did you make it $x and not $l?
19:54 <@ Lockwood> :P
19:54 <@ nenolod> Sure.
19:54 <@ Phrea> haha
19:54 <@ nenolod> 13:02 < Ehlanna> nenolod: please ... examples for +x? I am having a brain fail! :) <- /mode #opschool +b $x:*!*@*.ntl.com#*Brandy*Sauce* would ban Milambar.
19:54 <@ Lockwood> like /mode #opschool +b $x:ehlanna!
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
#Ehlanna
19:55 <@ nenolod> 13:03 < Spider> it should probably be noted that users can change their real name, so this is by no means a permanent solution <- he is correct
19:55 <@ Lockwood> and nenolod's ban wouldn't hit me, as my realname is different
19:55 <@ Lockwood> <Calivion> what if they don't have there real name listed? For instance they have "I am me" as there name <- $g:I?am?me
19:56 <@ Lockwood> It's what they set as their real name, not what their real name really is
19:56 <@ nenolod> You would use $x to restrict it to a specific hostmask.
19:56 <@ nenolod> 13:04 < Calivion> What would you use if you have many "Bob Smith"s
19:56 <@ Lockwood> <Calivion> What would you use if you have many "Bob Smith"s <- you'd use $-
19:56 <@ jacob> nenolod: others couldn't see his question ;p
19:56 <@ Lockwood> what he said
19:56 <@ nenolod> (got that backwards :P)
19:57 <@ nenolod> 13:05 < Crowley> Your examples show the ban "*!*@*.ntl.com" affecting Milambar, but that it's his hostmask as far as I can see. Do the banmask get around the
19:57 <@ nenolod> masking of the actuall user hostmask?
19:57 <@ nenolod> ^- Both the realhost and fakehost are matched.
19:57 <@ nenolod> 13:05 < Ehlanna> Pardon my denseness, but isn't /mode #opschool +b $x:ehlanna!
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
#Ehlanna in effect the same as /mode
19:57 <@ jacob> 12:57 < Ehlanna> Pardon my denseness, but isn't /mode #opschool +b $x:ehlanna!
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
#Ehlanna in effect the same as /mode #opschool +b
19:57 <@ nenolod> #opschool +b Ehlanna!
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
?
19:57 <@ jacob> Ehlanna!
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
?
19:57 <@ nenolod> :P
19:57 <@ nenolod> ^- Yes
19:57 <@ jacob> ehlana: yes it is.
19:57 <@ jacob> he was just trying to show how it worked ;p
19:58 <@ Lockwood> no
19:58 <@ nenolod> 13:06 < Stray> would people know WHY they were banned? ie, if someone banned asdf in the real name, would i know that that was why i couldn't get into a
19:58 <@ nenolod> channel?
19:58 <@ Lockwood> <Stray> would people know WHY they were banned? ie, if someone banned asdf in the real name, would i know that that was why i couldn't get into a channel? <- no
19:58 <@ jacob> Stray: it will just say 'you are banned', otherwise it's too easy to ban evade.
19:58 <@ jilles> Stray, they don't get anything special when trying to join, but they can see the ban list
19:58 <@ jilles> let me add that most of these extbans can be used in +q, +e, +I as well
20:00 <@ nenolod> Any further questions before we continue?
20:00 <@ nenolod> Alrighty.
20:01 <@ nenolod> The next segment will actually be fairly small, as the next feature after these two require in-depth explaination.
20:01 <@ nenolod> A commonly requested feature was the ability to deny unregistered users from joining the channel.
20:01 <@ nenolod> We now have this feature implemented.
20:02 <@ nenolod> To restrict unregistered users from joining a channel, you can set +r on your channel.
20:02 <@ nenolod> The syntax to do this is: /mode #channel +r
20:02 <@ nenolod> Users who are unregistered will be told that they can't join because the channel is +r.
20:03 <@ nenolod> The next feature we're going to cover is the new join throttle.
20:04 <@ nenolod> The join throttle allows you to limit the amount of people who can join at a single moment.
20:05 <@ nenolod> It is set by /mode #channel +j amount-of-joins:time-limit
20:05 <@ nenolod> For instance, /mode #opschool +j 1:3 would limit #opschool to 1 join, per every 3 seconds
20:05 <@ nenolod> These are actual seconds, e.g. 60 seconds = 1 minute
20:06 <@ nenolod> Ok, going to open it up to intermission again.
20:06 <@ jacob> nenolod: what do people see if they can't join because of a throttle, or how does it stop it?
20:06 <@ [twisti]> <TheDude2> i assume netsplits wont trigger that? <- no, they wont
20:06 <@ nenolod> jacob: Cannot join channel (throttle exceeded).
20:06 <@ jacob> 13:06 < TheDude2> i assume netsplits wont trigger that? <-- no, you're already in the channel.
20:07 <@ nenolod> 13:15 < Rize> will the people that +r blocks be shows how to register there nick so they actually could join the channel? <- no
20:07 <@ Lockwood> Nickserv tells you that on conenct
20:07 <@ jilles> TheDude2, server restarts will count against +j though
20:07 <@ Lockwood> sorry, infoserv does
20:08 <@ Lockwood> "You might want to look at registering your nick while you're here - just type "/msg NickServ HELP" for more information."
20:08 <@ nenolod> Anything else?
20:08 <@ Lockwood> so there's no need for you to be told on join, reallu
20:08 <@ Phrea> time is limited, speak now of forever hold your peace
20:08 <@ nenolod> 13:16 < Ehlanna> I presume to turn off throttle, just -j? <- Yes
20:08 <@ [twisti]> mind you, +j doesnt ban you, you can just try to join again after a few moments
20:09 <@ [twisti]> <Rize> IMO, it would be helpful since a lot of people joining our channel are new to irc and may not know how to read the information. <- a welcome message can take care of that
20:09 <@ nenolod> 13:16 < Rize> IMO, it would be helpful since a lot of people joining our channel are new to irc and may not know how to read the information. <- We do have a solution for this, stay tuned. :)
20:09 <@ Lockwood> <Rize> IMO, it would be helpful since a lot of people joining our channel are new to irc and may not know how to read the information.
20:09 <@ Lockwood> Umm
20:09 <@ [twisti]> lol
20:09 <@ Lockwood> then why give them information telling them to register?
20:09 <@ Lockwood> Thjey don't read information
20:09 <@ nenolod> ok
20:09 <@ nenolod> this is the big feature everyone should be interested in
20:10 <@ junics> if you have missed anything a realtime log can be found here: http://www.maniacs.se/~junics/opschool.txt
20:10 <@ Lockwood> the +f eature?
20:10 <@ nenolod> we have received many many many requests for this system
20:10 <@ Phrea> everybody who's new to irc and are joining an excisting channel: educate them yourselv
20:10 <@ nenolod> so, we're going to cover it now
20:10 <@ Phrea> we dont do these classes for nothing
20:11 <@ nenolod> The channel forwarding system allows you to specify an alternate channel to send rejected users to.
20:11 <@ nenolod> This system will trigger if the channel is invite-only, join throttled, limited or restricted to registered users.
20:11 <@ nenolod> You can enable it by setting /mode #channel +f #other-channel
20:11 <@ Phrea> also: let them KNOW there is a #help channel
20:11 <@ [twisti]> channel requirements/restrictions too, no ?
20:11 <@ nenolod> You must be an op on the target channel, or the channel must be +F
20:11 <@ Lockwood> and it will NOT make infinite loops if you forward to the same channel
20:12 <@ Lockwood> before you try
20:12 <@ nenolod> You must be an op on the target channel, or the channel must be +F.
20:12 <@ nenolod> The channel *must* exist or the forward will be ignored.
20:12 <@ nenolod> The channel *must* not be +Q or the forward will be ignored.
20:12 <@ nenolod> I am going to have a very detailed example at the end of this segment, so stay tuned.
20:13 <@ nenolod> The +Q channel mode will allow a channel to say "I don't want to be forwarded to."
20:13 <@ nenolod> If you are concerned that your channel will be disrupted by users using this feature, that will allow you to opt out of it.
20:14 <@ nenolod> Inversely, you can also tell the world that you don't care if people forward to your channel.
20:14 <@ nenolod> To do so, you can set the channel +F
20:14 <@ nenolod> To set +Q or +F on a channel, you do /mode #channel +Q or /mode #channel +F respectively.
20:14 <@ nenolod> Ok, time for the example.
20:15 <@ nenolod> Lets imagine that we are a user named 'Moogle', and that we have just registered #ilovechocobos, and #ilovemoogles.
20:15 <@ nenolod> Moogle wants users to be in #ilovemoogles before they can join #ilovechocobos.
20:15 <@ [twisti]> nobody loves chocobos
20:16 <@ nenolod> Therefore, Moogle sets the following:
20:16 <@ nenolod> /mode #ilovechocobos +iI $r:#ilovemoogles
20:16 <@ nenolod> /mode #ilovechocobos +f #ilovemoogles
20:16 <@ nenolod> When users join #ilovechocobos, they will be sent to #ilovemoogles instead.
20:17 <@ nenolod> The next time they join #ilovechocobos, they will be able to join like normal (unless they parted #ilovemoogles.)
20:17 <@ Lockwood> If I part #ilovemoogles after joining #ilovechocobos, what will happen?
20:17 <@ nenolod> Now, lets say some jerk named Turk decides he hates Moogle and wants to make them cry.
20:18 <@ nenolod> Lockwood: nothing
20:18 <@ nenolod> anyway
20:18 <@ nenolod> Now, lets say some jerk named Turk decides he hates Moogle and wants to make them cry.
20:18 <@ nenolod> Turk registers #ihatemoogles.
20:18 <@ nenolod> He does /mode #ihatemoogles +if #ilovechocobos
20:18 <@ nenolod> Because #ilovechocobos is forwarding to #ilovemoogles, #ilovemoogles gets joinflooded by people that are spammed to #ihatemoogles.
20:19 <@ nenolod> Moogle cries for a while and contacts a help operator, which tells them to set +Q on their channel.
20:19 <@ nenolod> At this point, Moogle sets #ilovechocobos +Q to stop people from forwarding to it.
20:19 <@ nenolod> Moogle's forwarding rule still works, but Turk's does not.
20:20 <@ nenolod> Everyone lives happily ever after, of course.
20:20 <@ nenolod> ok. That covers channel forwarding.
20:20 <@ nenolod> Opening the floor up to questions.
20:20 <@ [twisti]> mind you, to do this, the evil Turk would have needed to have op on #ilovemoogles, so our friend Moogle was stupid to give out op to a jackass
20:20 <@ [twisti]> <RagingMonk> Are we protected against circular refrences? <- yes
20:21 <@ [twisti]> <Stray> will that send them to the second chan if they are banned from the first chan, will that trigger the forward? <- anything that stops you from joining will send you to the forwarded chan
20:21 <@ nenolod> 13:29 < RagingMonk> Why does the +Q stop Turk and not Moogle? <- Because Moogle set it at the entrypoint.
20:21 <@ [twisti]> bans, invite only, $a's, etc
20:22 <@ nenolod> 13:29 < Ehlanna> nenolod: surely your example re Turk and Moogle would only work if Turk had Ops in Moogles channels? <- We're assuming that he was allowed to somehow.
20:22 <@ nenolod> Either via +F or by having ops.
20:23 <@ [twisti]> <xarexerax> Do ops in the forwarding channel recieve a message about those who failed to join their channel? <- no
20:23 <@ nenolod> 13:30 < xarexerax> Do ops in the forwarding channel recieve a message about those who failed to join their channel? <- no, but we may look into adding that
20:23 <@ nenolod> 13:31 < MissSylvia> and if the channel does not wish to participate in the forwrding options at all, what are the procedures we should implement? <- /mode #channel +Q
20:25 <@ nenolod> 13:32 < RagingMonk> The answer 'Because Moogle set it at the entrypoint' confused me. Can you elaborate? <- Turk set the forward to #ilovechocobos, where Moogle set the +Q, therefore Moogle's rules to forward FROM #ilovechocobos still work, but not Turk's rules TO #ilovechocobos.
20:25 <@ nenolod> 13:32 < MissSylvia> is there an op level requirement? <- services do not play any role in forwarding at this time, but when they do, there will be a requirement.
20:25 <@ nenolod> 13:33 < Keina> What happens if Turk's forward switches to #ilovemoogles, assuming he gets it to work and isn't stopped otherwise, of course? Moogle's forward
20:25 <@ nenolod> would be broken by a +Q, but the channel would still get flooded without it, wouldn't it?
20:26 <@ nenolod> Keina: Moogle would be screwed, yes.
20:26 <@ nenolod> Keina: Moogle would have to set both channels +Q and hope for the best.
20:26 <@ nenolod> 13:34 < Spyke> Would De-Opping Turk in #ILoveChocobos remove his ability to forward from #IHateMoogles to #ILoveChocobos as well, or will the forward remain
20:26 <@ nenolod> unaltered until it is set +Q?
20:26 <@ nenolod> Spyke: if the forward has already been set then it will remain until it is removed or until the target channel is +Q'ed.
20:27 <@ [twisti]> <Spider> but you do have to be an op in the target channel initially? <- yes, but only to set the forward, you dont have to stay opped
20:27 <@ nenolod> 13:35 < RagingMonk> Does a forward stop working if ops are removed? <- no
20:28 <@ nenolod> 13:36 < RagingMonk> How are forwards removed? <- /mode #channel -f
20:28 <@ jacob> 13:28 < Rize> can any lvl op use forward? <-- yes, as it's just a channel mode.
20:28 <@ [twisti]> <Rize> can any lvl op use forward? <- yes, unless MLOCK is set to on
20:29 <@ nenolod> 13:37 < Linkshot> What happens if Turk registers #ilovechocobos before Moogle does (because he does love them), but lets Moogle forward to it?
20:29 <@ nenolod> ^- then Moogle would need to find another channel to own
20:29 <@ nenolod> ;p
20:30 <@ Lockwood> #ireallylovechocobos
20:30 <@ jacob> nenolod: fix your system clock. you're 8 minutes ahead
20:30 <@ jacob> Thu Aug 31 13:30:10 CDT 2006
20:30 <@ jacob> ;p
20:30 <@ Lockwood> or #ilovechocobosmorethanturkdoes
20:30 <@ [twisti]> that turk dude is one devious fellow
20:31 <@ nenolod> anything else?
20:32 <@ [twisti]> <Spyke> Sorry if I missed this being answered earlier, but is there a way to set a channel so that it can only be forwarded to by a specific channel (or channels)? <- sorry, there is not
20:32 <@ [twisti]> but you can always restrict the op list
20:32 <@ [twisti]> remember, you need op on a channel to set a forward to it (or the channel has to be +F)
20:33 <@ nenolod> By the way, forwards work for +r, +l and +j too. Not just invite-only channels.
20:33 <@ nenolod> Ok.
20:33 <@ [twisti]> the advanced ban modes too
20:33 <@ [twisti]> like $a
20:33 <@ nenolod> 13:41 < Miri> oh, a question... is there any way to hide +q being set on a user to level 0 users? since it's to deal with troublemakers, to do it quietly and
20:33 <@ nenolod> effectively, not having zillion users asking us "what's that mode"?
20:33 <@ Lockwood> <Miri> oh, a question... is there any way to hide +q being set on a user to level 0 users? since it's to deal with troublemakers, to do it quietly and effectively, not having zillion users asking us "what's that mode"?
20:33 <@ Lockwood> no
20:34 <@ nenolod> ^- no
20:34 <@ Lockwood> you got it in stereo!
20:34 <@ nenolod> ok
20:34 <@ nenolod> We're now going to go over user-modes.
20:35 <@ nenolod> Charybdis supports two forms of server-side ignore for private messages.
20:35 <@ nenolod> CALLERID, usermode +g, and Soft CALLERID, usermode +R.
20:35 <@ nenolod> To set a usermode, you do /mode yournickhere mode
20:35 <@ nenolod> For instance, I would do /mode nenolod +g to set usermode +g on my client.
20:35 <@ nenolod> Now, lets go over CALLERID and Soft CALLERID.
20:36 <@ nenolod> CALLERID is a full ignore, where the only people who can PM you are users who are explicitly on a whitelist.
20:36 <@ nenolod> Soft CALLERID is like CALLERID, but only applies to those who are not registered with services.
20:37 <@ nenolod> To add a nickname to your allow list, do /accept nick (or /quote accept nick based on what your client is)
20:37 <@ nenolod> To delete, do /accept -nick
20:37 <@ nenolod> and to list your PM whitelist, do /accept *
20:38 <@ nenolod> This is useful with scripts.
20:38 <@ nenolod> You can also opt out of channel forwarding on a personal level.
20:39 <@ nenolod> To do so, set +Q on your usermode, i.e. /mode yournickhere +Q
20:39 <@ nenolod> That's all for now (we're not going to cover /monitor, because it's only really useful to scripters)
20:40 <@ nenolod> If you're interested in more info, check out the ircd manual.
20:40 <@ nenolod> http://www.nexus.sorcery.net/download/ircd/charybdis-oper-guide.pdf
20:40 <@ nenolod> http://www.stack.nl/~jilles/irc/charybdis-oper-guide/
20:40 <@ [twisti]> Miri: that bugs me too :(
20:40 <@ nenolod> Ehlanna: yes
20:41 <@ [twisti]> Spider: go right ahead
20:41 <@ nenolod> We're also looking for other things to cover in #opschool... mail
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
if you have a suggestion.
20:42 <@ nenolod> Miri:
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
or
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
20:42 <@ [twisti]> miri: #gaycafe
20:42 <@ [twisti]> its not my channel rize
20:42 <@ nenolod> Spider: we don't have those here
20:42 <@ junics> if you have missed anything a log can be found here: http://www.maniacs.se/~junics/opschool.txt
|
|
Last Updated ( Sunday, 03 September 2006 )
|
|
|
|
|
Newsflash |
Did you know we have a glossary? Visit it here
|
|
|
Quote |
|
<skumwerk> IRCing from work is bad
* skumwerk coughs
<skumwerk> it leads to lower productivity overall
<skumwerk> i swear if i found out any of my coworkers were IRCing at work
<skumwerk> ... i'd have to hang out with them :\ ...
|
|
|
