[20:30] <hggdh> can I have the same mask of ubotu-br for ubotu-br` ?
[20:36] <Unit193> hggdh: Group them.
[20:42] <Unit193> ...Well I suppose technically that works.
[20:43] <hggdh> Unit193: checking it now -- I thought I already had it grouped
[20:44] <hggdh> but -- going thru the motions again, it seems I did not have it really grouped (perhaps it was just a dream I had...)
[20:47] <hggdh> so I will wait for the next netsplit
[20:48] <Unit193> Don't have SASL setup?
[20:49] <hggdh> not for ubotu-br, still to look at it
[20:50] <hggdh> and sasl does not protect against collision after a netsplit, anyway
[21:05] <Pricey> hggdh: sasl will ensure you identify to an account irrespective of what nickname you connect with. Collisions shouldn't matter?
[21:13] <hggdh> Pricey: collisions do not matter in general, but the bot runs on some restricted channeld
[21:13] <hggdh> *channels
[21:14] <Pricey> hggdh: How do you mean?
[21:14] <Pricey> Is something going on that should be being solved with "+I $a:accountname" ?
[21:15] <hggdh> currently some channels are invite-only. The bot runs on it and, on a nick change, loses access
[21:15] <hggdh> ah
[21:15]  * hggdh goes to the chanserv docs
[21:16]  * Unit193 hopes it isn't +I ubotu-br!*@*
[21:17] <hggdh> heh
[21:17] <hggdh> no, it is not
[21:19] <Pricey> hggdh: Ok well you should /mode +I $a:accountname
[21:19] <hggdh> bah, the +I is correctly set, all I was missing was the group
[21:19] <Pricey> hggdh: That means that as long as it identifies with sasl while connecting it'll get into the channel.
[21:19] <Pricey> hggdh: The group?
[21:20] <hggdh> Pricey: actually, setting SASL is the first priority right now
[21:20] <hggdh> Pricey: since the bot had not grouped the possible nicks, I was not getting the cloak (so, a different issue)
[21:20] <Pricey> hggdh: No.... that's wrong.
[21:20] <Pricey> hggdh: You do not need to be using a nickname grouped to the account in order to identify.
[21:21] <hggdh> yes, I know, if I use SASL
[21:21] <Pricey> there are other options too
[21:21] <hggdh> which?
[21:21] <Pricey> certfp... server passwords, even a correctly formatted "/msg nickserv identify" can identify you to an account even if you'r enot using a grouped nickname
[21:22] <Pricey> http://freenode.net/faq.shtml#identify - the server password can be "accountname:password"
[21:22] <Pricey> That's probably far easier to set up than sasl in a bot that doesn't do sasl.
[21:22] <Unit193> This is for a supybot, so certfp is out.
[21:23] <Unit193> (Mine does SASL at least.)
[21:23] <Pricey> Ubottu clone?
[21:23] <hggdh> Pricey: indeed. But it seems that the supybot branch is not really up-to-date
[21:24] <Pricey> sasl/server passwords and "+I $a:accountname" will ensure the bot can get in.
[21:25] <hggdh> ack, will work on it
[21:25] <Unit193> Pricey: But yes.
[21:31] <hggdh> yeah, supibot seems to be failing auth when using an alternate nick. Will look at it
[21:31] <hggdh> supybot, even
[21:38] <Pricey> hggdh: How are you getting it to identify?
[22:01] <hggdh> Pricey: I was just using supybot config, will have to look and find what it does