[19:35] <oldfred>     /msg nickserv register qwer5tQQ fpalmer19@comcast.net
[19:36] <Mikaela> you may want to try "/query NickServ" in order to avoid accidentally sending the commands to channel and when you do register, you may want to use different and more secure password.
[20:08] <oldfred> Thanks, Mikaela guess I did not realize NickServ was a channel and not a command.  How do I request a cloak. I am a member https://launchpad.net/~oldfred
[20:09] <IdleOne> Pici: ^
[20:09] <Mikaela> NickServ is a service/bot and /query opens private messaging window with it.
[20:09] <Mikaela> To request a cloak, you ask here (like you did) and wait for member of Ubuntu IRC council to appear and ping staffers
[20:09] <Fuchs> it is neither a channel nor a command, it's a service frontend. As for the cloak: asking in here, then waiting for both IRCC and staff.
[20:10]  * Pici looks
[20:16] <Pici> huzzah
[20:16] <Fuchs> congratulations, oldfred
[20:17] <Fuchs> now you might want to configure auto-authentication in your client, preferred way is http://freenode.net/sasl/
[20:17] <oldfred> Thanks, while in Forums for a while, first time in IRC
[20:18] <Fuchs> you'll either like it or run away screaming. Anyway, enjoy your stay. http://freenode.net/using_the_network.shtml has links to good primers / tutorials if interested, most things come by learning by doing, though.
[20:18] <Mikaela> You might also want to change your client. XChat is not developed anymore and it doesn't support anything newer than SSLv3 and because of poodle and servers removing support for it, you will be unable to connect using SSL in the future.
[20:18] <Fuchs> in that case you might want to go for hexchat, which is an xchat fork. Does the SASL I mentioned out of the box.
[20:19] <oldfred> I was suggested both xchar & hexchat If I logout & back in do I have to start over?
[20:19] <Mikaela> HexChat which should be available in Ubuntu repositories can take your current config http://hexchat.readthedocs.org/en/latest/faq.html#how-do-i-migrate-my-settings-from-xchat
[20:19] <Mikaela> and it also has SASL support https://freenode.net/sasl/sasl-hexchat.shtml/
[20:19] <Mikaela> the last link should be https://freenode.net/sasl/sasl-hexchat.shtml
[20:20] <oldfred> I already installed hexchat, just happened to use xchat first
[20:20] <Fuchs> oldfred: not really, no. Your cloak is now tied to your account, just don't drop the account, then you are fine.
[20:20] <Mikaela> oldfred: you are currently using xchat
[20:20] <Mikaela> 2014-12-23 22:17:33+0200 -- CTCP query to oldfred: VERSION
[20:20] <Mikaela> 2014-12-23 22:17:34+0200 -- CTCP reply from oldfred: VERSION xchat 2.8.8 Ubuntu
[20:20] <Mikaela> [
[20:23] <Mikaela> Fuchs: sorry :(
[20:23] <Fuchs> Mikaela: that wasn't terribly serious :)
[20:23] <Fuchs> more poking fun of sending a ctcp version when he actually said what client he is using. Ignore me, I'm silly.
[20:24]  * Mikaela specified new version reply
[20:24] <Mikaela> I versioned before client was mentioned
[20:25] <oldfred> Since I have not really done anything other than log in here with xchat, I will logout and then try hexchat. Wish me luck.
[20:25] <Fuchs> oldfred: shall keep paw crossed
[20:25] <Fuchs> aww
[20:30] <Fuchs> well, that looks good, and you are identified as well
[20:30] <oldfred> oldfred back, had a couple of issues as it first defaulted to second name and I did not get password in in time. But then found where to add password to default.
[20:32] <oldfred> I think I used wrong one again. signing off
[20:50] <oldfred> Not sure I am working
[20:50] <Mikaela> automatic identification is not currently working
[20:51] <Fuchs> it worked the first time you came back, mind.
[20:52] <oldfred> very first time I accidentally click on xchat, the with hexchat it came in as second choice or third choice as I did not have password set in hexchat
[20:53] <oldfred> This time I came in as oldfred but it said I was already used and went ot Nickserv to add password again
[20:53] <Fuchs> https://freenode.net/sasl/sasl-hexchat.shtml   << you followed these instructions?
[20:53] <Fuchs> because if you use SASL, you don't have to deal with nickserv.
[20:53] <Fuchs> just make sure to set oldfred as the username, set SASL as the method and put your password in the password field
[20:55] <oldfred> I thought that was what I did, could be system saw me trying too many times at once?
[20:56] <Fuchs> nah
[20:57] <Fuchs> if you put the right username in, the nick it uses shouldn't matter either. Try that again, as said, it initially did work. If it did put you on another nick: entirely possible, this (might not sound logical to you) doesn't have anything to do with whether you are identified or not
[20:57] <oldfred> I am going out and double check settings
[21:06] <oldfred_> I came back as oldfred_ not oldfred, double checked settings and changed a couple of check boxes
[21:07] <Fuchs> yes, but at least you are now identified
[21:07] <Fuchs> your old connection is still around though, so probably you left something open. You can remove it from the network with nickserv's ghost command if you want, then you can have your usual nick
[21:07] <Fuchs> see   /msg nickserv help ghost
[21:08] <Fuchs> there can only be one connection using the nick oldfred at a time, thus the second one uses the alt name. Identifying to nickserv does not automagically change your nick  (that is intended and correct)
[21:09] <oldfred_> I thought I had shutdown, do I have to detach before closing Hexchat?
[21:09] <Fuchs> no, shouldn't be needed. Not knowing hexchat in detail: some clients have an option to keep running in systray when you close the window, maybe it's that.
[21:11] <oldfred_> I will try logging out and come back after a few hours and see what happens, too much new user not sure what he is doing.