=== Logan_ is now known as Guest50062 === Logan__ is now known as Logan_ === PriceChild is now known as Pricey === cprofitt_ is now known as cprofitt === Darkwing_ is now known as Darkwing === guntbert is now known as Guest75644 === Zic_ is now known as Guest8512 === ashams is now known as Guest15032 [14:25] directhex called the ops in #ubuntu-uk () === plantigrade is now known as avelldiroll === Guest8512 is now known as Zic === ubott2 is now known as ubottu === LjL^ is now known as LjL === lubotu3` is now known as lubotu3 === funkyHat_ is now known as funkyHat === tiagoscd is now known as Guest15290 === Guest15290 is now known as tiagoscd === cprofitt_ is now known as cprofitt === init is now known as Exio === init is now known as Exio === ubott2 is now known as ubottu === Exio is now known as 16WAAGGVQ === 16WAAGGVQ is now known as Exio === elky` is now known as elky [20:30] can I have the same mask of ubotu-br for ubotu-br` ? [20:36] hggdh: Group them. === hggdh is now known as ubotu-br === ubotu-br is now known as ubotu-br` === ubotu-br` is now known as hggdh [20:42] ...Well I suppose technically that works. [20:43] Unit193: checking it now -- I thought I already had it grouped [20:44] 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] so I will wait for the next netsplit [20:48] Don't have SASL setup? [20:49] not for ubotu-br, still to look at it [20:50] and sasl does not protect against collision after a netsplit, anyway === PriceChild is now known as Pricey [21:05] hggdh: sasl will ensure you identify to an account irrespective of what nickname you connect with. Collisions shouldn't matter? [21:13] Pricey: collisions do not matter in general, but the bot runs on some restricted channeld [21:13] *channels [21:14] hggdh: How do you mean? [21:14] Is something going on that should be being solved with "+I $a:accountname" ? [21:15] currently some channels are invite-only. The bot runs on it and, on a nick change, loses access [21:15] ah [21:15] * hggdh goes to the chanserv docs [21:16] * Unit193 hopes it isn't +I ubotu-br!*@* [21:17] heh [21:17] no, it is not [21:19] hggdh: Ok well you should /mode +I $a:accountname [21:19] bah, the +I is correctly set, all I was missing was the group [21:19] hggdh: That means that as long as it identifies with sasl while connecting it'll get into the channel. [21:19] hggdh: The group? [21:20] Pricey: actually, setting SASL is the first priority right now [21:20] Pricey: since the bot had not grouped the possible nicks, I was not getting the cloak (so, a different issue) [21:20] hggdh: No.... that's wrong. [21:20] hggdh: You do not need to be using a nickname grouped to the account in order to identify. [21:21] yes, I know, if I use SASL [21:21] there are other options too [21:21] which? [21:21] 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] http://freenode.net/faq.shtml#identify - the server password can be "accountname:password" [21:22] That's probably far easier to set up than sasl in a bot that doesn't do sasl. [21:22] This is for a supybot, so certfp is out. [21:23] (Mine does SASL at least.) [21:23] Ubottu clone? [21:23] Pricey: I am only a bot, please don't think I'm intelligent :) [21:23] Pricey: indeed. But it seems that the supybot branch is not really up-to-date [21:24] sasl/server passwords and "+I $a:accountname" will ensure the bot can get in. [21:25] ack, will work on it [21:25] Pricey: But yes. [21:31] yeah, supibot seems to be failing auth when using an alternate nick. Will look at it [21:31] supybot, even [21:38] hggdh: How are you getting it to identify? [22:01] Pricey: I was just using supybot config, will have to look and find what it does === holstein_ is now known as holstein