| fo0bar | elky: hi | 00:37 |
|---|---|---|
| elky | hi let me get a look at what pieces we have | 00:37 |
| fo0bar | elky: as it stands now, there are 3 accounts (ubuntulog, ubuntulog2, ubuntulog3) | 00:37 |
| fo0bar | I can go into ubuntulog2 and re-identify with ubuntulog, but I can't group it because of the existing accounts apparently | 00:38 |
| elky | ok, so what you need to do is drop the 2 and 3 accounts before grouping | 00:38 |
| fo0bar | ah, I didn't notice DROP in the nickserv help | 00:39 |
| Unit193 | ubuntulog3 [ubuntulog] there it is. | 00:41 |
| fo0bar | excellent, thanks | 00:42 |
| elky | yep they're all together now | 00:42 |
| elky | now you only have to worry about one account | 00:42 |
| * fo0bar updates the backend configs and does yet one more global quit/join :( | 00:42 | |
| Unit193 | Sounds like they're using /msg nickserv on join.. | 00:43 |
| fo0bar | Unit193: yeah. I can probably change that to connection pass while I'm in there. I assume all three would be ":ubuntulog $PASS" now | 00:45 |
| fo0bar | (can you tell this is an irssi session which was cobbled together 10 years ago? :) | 00:46 |
| elky | if the irssi is up to date you should be able to use sasl | 00:46 |
| Unit193 | Yes I very much can tell. :P | 00:46 |
| Unit193 | irssi v0.8.19 so it says. | 00:47 |
| Unit193 | fo0bar: FWIW, for server pass it's actually account:pass | 00:48 |
| fo0bar | Unit193: interesting. my personal freenode's .irss/config has 'password = ":fo0bar $PASS";' for some reason | 00:49 |
| Unit193 | fo0bar: I have SASL (external script, with NIST256P support), and CertFP so if I ever join when services are split, as soon as they come back I'll be identified. | 00:50 |
| fo0bar | Unit193: that'd sounds nice, but I don't want to go that far right now (Friday right before EOD and all that, heh). but I'll file an internal ticket to look into that | 00:52 |
| Unit193 | fo0bar: Understandable, also why I only mentioned it when you said your personal account. | 00:52 |
| Unit193 | I presume 'internal' doesn't mean rt@ubu? | 00:53 |
| fo0bar | Unit193: we have another RT for company-specific ticket-tracking. that one's set up so we can better track intra-IS techdebt, whereas rt@u.c is always assumed to be a "customer" request and triaged appropriately | 00:55 |
| Unit193 | Figured as such, yep. Only asked because I can actually see the latter. | 00:55 |
| fo0bar | (which just happens to be at >110,000, while rt@u.c's around 30,000) | 00:56 |
| Unit193 | Ouch.. | 00:56 |
| fo0bar | > #65535: Add more bits to RT | 00:57 |
| fo0bar | This RT installation's approaching the limits of industry-standard | 00:57 |
| fo0bar | 16-bit computing. We should probably add three or four more bits, just | 00:57 |
| fo0bar | to be safe for the future. | 00:57 |
| * elky falls over laughing | 00:57 | |
| Unit193 | Well I was going to say that I'll be around for any irssi questions, but now I'm starting to wonder. :P | 00:59 |
| fo0bar | 01:02 -NickServ(NickServ@services.)- Information on ubuntulog3 (account ubuntulog): | 01:03 |
| fo0bar | 01:02 -NickServ(NickServ@services.)- Registered : Aug 19 00:41:22 2017 (21m 22s ago) | 01:03 |
| fo0bar | 01:02 -NickServ(NickServ@services.)- User reg. : Jul 19 05:10:41 2005 (12y 4w 5d ago) | 01:03 |
| fo0bar | \o/ | 01:03 |
| fo0bar | Unit193, elky: thanks for the help | 01:03 |
| Unit193 | fo0bar: Glad you've got it! | 01:03 |
| Unit193 | That's not good. | 01:10 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!