=== K1ra is now known as Exio4 [11:01] Is there a document somewhere which explains in english "How to forward one channel to another"? [11:01] hold on, let me look [11:01] I found some lists of flags on freenode pages but nothing that gave "do this, now this" [11:02] "The suffix $#channel can be appended to any of the above ban masks to cause a user to be forwarded to #channel. The ban setter will only be able to set this ban if they are an op in #channel, or if #channel has channel mode +F set. In this case, in all situations where the user would previously have been told they could not join, they will instead join the channel named in the ban mask and be sent a 470 numeric describing the forward." [11:02] so, either set the receiving channel as +F, or op up there first [11:03] I am opped in source (#ubuntu-uk-podcast) and desitination (#uupc) [11:03] I didn't realise it had to be "ban forward"? [11:03] I thought just "forward" [11:04] /mode #channel1 +if #channel2 [11:05] "forward on uninvited" [11:05] +f only takes effect if you were unable to join "for some ok reason", e.g. +i, +r etc. [11:06] You'll probably want to mlock these so that they aren't lost when the channel empties. /msg chanserv help set mlock [11:06] yup [11:06] was just getting there, thanks Pricey [11:06] see, this is why i asked for documentation [11:06] Also, be careful not to confus channel MODES with chanserv FLAGS... it gets confusing [11:06] having an interactive conversation telling me about mlock isn't documentation ☻ [11:06] popey: http://freenode.net/using_the_network.shtml /msg chanserv help set mlock [11:06] it does indeed get confusing [11:06] yeah, i found that page [11:07] its not a friendly page for answering the question I had [11:07] "here, read about every single flag and mode first" [11:07] but that's what the staff members are here for, to answer questions ♥ [11:08] well indeed. sorry to take your time. [11:08] ctrl+f for 'forward', find the +f cmode, read: "This mode takes one parameter, a channel name. Users who cannot join the channel (because of +i, +j, +r, etc.) are instead sent to the channel given in +f. For example, /mode #channel1 +if #channel2" [11:08] yes. which I did [11:08] I've got a day off per Epiphany, so I've got time :-) [11:08] and it didnt work [11:08] hence me asking [11:09] * AlanBell nods, it kinda works unless chanserv does the mlock thing [11:09] so I set +if, and now if I join #ubuntu-uk-podcast I dont get forwarded [11:10] popey: Mind us joining to look? [11:10] knock yourself out [11:10] 11:10:13 [freenode] -!- mode/#ubuntu-uk-podcast [+cnstf] [11:10] no, you can't set +i because chanserv sets it back to -i [11:10] Yep, no 'i'. [11:10] because of mlock [11:11] 11:05 -!- mode/#ubuntu-uk-podcast [+if #uupc] by popey [11:11] 11:05 -!- mode/#ubuntu-uk-podcast [-i] by ChanServ [11:11] Something like /msg chanserv set #ubuntu-uk-podcast mlock +imnstf #somewhereelse [11:11] 11:11:40 set #ubuntu-uk-podcast mlock +imnstf #uupc [11:11] 11:11:40 -ChanServ(ChanServ@services.)- You are not authorized to perform this command. [11:12] Do you have +s in #uupc? [11:12] 11:12:28 -ChanServ(ChanServ@services.)- 1 popey +AFRfiorstv [modified ? ago] [11:12] Are you currently op in both channels? [11:12] yes [11:14] Do you have +s in #ubuntu-uk-podcast ? [11:15] 11:15:30 flags #ubuntu-uk-podcast [11:15] 11:15:30 -ChanServ(ChanServ@services.)- You are not authorized to perform this operation. [11:15] Bah I didn't even read your chanserv error... yeah you need +s in the first. [11:15] ☹ [11:16] Ok, I'm stuck now, I don't understand what the problem is and what to do. [11:17] Someone with +fs or +F on #ubuntu-uk-podcast's access list needs to give you +s. [11:17] how do I see who has that? [11:17] cied [11:17] /msg chanserv access #ubuntu-uk-podcast list [11:17] Or you can ask AlanBell to be a brute and tell me to give it to you. [11:18] cied isn't about, and popey is entirely the right person for this, so yes, Pricey can you +F popey in #ubuntu-uk-podcast please [11:18] AlanBell: Could you identify to your personal account please? [11:19] * AlanBell is me [11:20] Done. popey try "set #ubuntu-uk-podcast mlock +imnstf #uupc" again [11:20] 11:20:48 -ChanServ(ChanServ@services.)- The MLOCK for #ubuntu-uk-podcast has been set to +imnstf. [11:20] \o/ [11:21] That worked, many thanks Myrtti AlanBell Pricey [11:22] * AlanBell decides to write this down somewhere [11:22] so now do I boot everyone from the channel? [11:22] or just wait and let them organically move over? [11:22] popey: They aren't guarunteed to rejoin the new channel. [11:22] popey: I would ask them all to move over... [11:22] ok, thank you. [11:23] I gave you +imnstf earlier... that's quite a few modes including blocking all messages, invite only, forwarding, topic lock etc. [11:23] The +m for blocking all messages discourages people hanging on until their connection dies as they can't say anything so might as well move over. [11:23] oh of course. neat [11:24] BUGGER OFF YOU NITWITS [11:24] erm. [11:24] :-D [11:24] :D [11:24] popey: If you want, you could kick them all (more likely to trigger auto rejoin) or use chanserv's clear users. But that's messy. [11:24] https://wiki.ubuntu.com/IRC/MovingChannels is fairly reasonable now, I added the +F or +s bit [11:24] nice one. [11:24] I'll leave it for now. [11:25] popey: If you don't want cied to come along later and undo this, /msg chanserv flags #ubuntu-uk-podcast cied -* [11:25] or just -Fs [11:26] heh [11:31] https://wiki.ubuntu.com/IRC/MovingChannels is less a wall of text now [11:45] yay, thanks Pricey === cprofitt_ is now known as cprofitt === Exio4 is now known as E4xoi === E4xoi is now known as Exio4