#qi-hardware IRC log for Sunday, 2015-02-01

wpwrak_hmm .. putty ... brand name "sicko". http://articulo.mercadolibre.com.ar/MLA-543789996-sicko-masilla-putty-para-modelismo-y-maquetas-50g-_JM02:00
wpwrak_grmbl. and why does freenode think i'm a smoker ?02:11
DocScrutinizer05wpwrak: (smoker) you should check your xchat config/scripts. auto-rejoin without using '/msg nickserv ghost' will inevitably result in your client using next alternative nickname, on every netsplit or connectivity loss11:37
DocScrutinizer05.xchat2/xchat-login.xsh ::11:40
DocScrutinizer05nick Docscrutemp11:40
DocScrutinizer05msg nickserv ghost DocScrutinizer51  MyPasswd11:40
DocScrutinizer05timer 6 nick DocScrutinizer5111:40
DocScrutinizer05msg nickserv id joerg_rw  MyPasswd11:41
DocScrutinizer05http://wiki.maemo.org/User:Joerg_rw/xchat/11:44
wpwrakhmm. how would xchat know to execute xchat-login.xsh ? and what language is .xsh ? i can see lots of stuff about perl and python scripting, but you seem to be the only one on the planet who uses that xchat-login.xsh script :)14:22
whitequarkxchat script?14:47
wpwraki guess it's a variant of the things described here: http://xchatdata.net/Scripting/HomePage15:16
rjeffrieswpwrak your anelok case work boggles my mind. With the CNC approach what do you consider the practical upper bound on number of cases made that (tedious) way?20:09
rjeffriesI assume that a soft tool (aluminum mold, I think..)  for injection molding would be logical way for moderate production. But is n=100 doable the hard way?20:11
DocScrutinizer05wpwrak: no idea, al that stuff is 5 years old. I guess there's a well defined script name xchat executes on start. Or the whole thing got deactivated by me when I switched to ZNC20:34
DocScrutinizer05quite possible that the thing been named xchat-login.sh before I renamed it to disable it20:36
DocScrutinizer05and it looks like plain xchat commands without leading "/"20:36
DocScrutinizer05prolly Raster instructed me back in TPE20:38
DocScrutinizer05or shortly after, when I bought my N81020:39
DocScrutinizer05without Raster's N800 (N770?) I'd possibly never had noticed maemo and thus xchat. Definitely Raster told me about xchat20:40
DocScrutinizer05anyway I recall I learned about timers via '/help timer' cmd, and that stuff once kinda worked20:49
DocScrutinizer05the cmds are only a 4 lines, you should be capable to grok the idea even without a POSIX standard scripting language being used ;-D20:58
DocScrutinizer05maybe one of the 250 scripts provided on http://xchatdata.net/Scripting/HomePage even offers a smarter approach, like the one I do on Konversation where I wait for regex pattern "DocScrutinizer05.*has.*been.*ghosted" | "DocScrutinizer05.*is.*not.*online" to autorespond "/nick DocScrutinizer05". Smarter than a "sleep 6"21:02
wpwrakrjeffries: n=100 may be easier the hard way, yes. a mold is hard to make with my mill. so by the time i'd have one made and fully debugged, i'd probably be done with the 100 directly milled cases21:34
wpwrakDocScrutinizer05: interesting .. didn't know of the raster angle :)21:35
wpwrak(concept) yes, that's clear enough. but i'd like to avoid the temporary name. and to do that i'll need to understand more of what's underneath21:36
DocScrutinizer05you need a temporary name anyway, since you can't log in to IRC with a nick that's already in use21:38
DocScrutinizer05recently your temporary name is smoker21:39
DocScrutinizer05;-)21:39
wpwrakwell, i only need a temp name if there's actually a conflict21:49
DocScrutinizer05you need one to even find out *if* there is a conflict22:13
DocScrutinizer05your client tries to log in with your primary nickname (wpwrak). If that fails, the client usually tries the secondary/alternative nickname (in your case wpwrak_). Whatever the result of this, next steps are: authenticate to nickserv (/msg nickserv <ACCOUNTnam> <PassWD>), ghost primary nickname (answer either "can't ghost yourself [when using your primary nick] or "has.*been.*ghosted" resp ".*is.*not.*online" [when using secondary 22:19
DocScrutinizer05nick]), then _try_ to change nick to primary nick, ideally on receiving (one of) the reply(s) as mentioned before from nickserv (since sometimes nickserv takes 'ages' to complete the ghost command)22:19
DocScrutinizer05oops s/ /msg nickserv <ACCOUNTnam> <PassWD> / /msg nickserv ID <ACCOUNTnam> <PassWD> /22:20
DocScrutinizer05changing nick to <primary_nick> is a NUL operation when your nick already is the primary one. And "/msg nickserv ghost <primary_nick>" will fail when you already use primary nick ("can't ghost yourself"). So the above sequence doesn't need any tests and conditional branches. It simply "just works"22:27
DocScrutinizer05NB your alternative (temporary) nick is completely arbitrary, you don't even need to know it22:29
DocScrutinizer05wpwrak: ^^^22:30
wpwrakmy concern would be auto-joining of channels. does that wait until i have sorted out the nick situation ? if not, any temporary nick is still a problem22:33
DocScrutinizer05that depends on client22:33
wpwrakxchat :)22:33
DocScrutinizer05I dunno about xchat22:33
eintopfwho use xchat here22:33
wpwrakme ! :)22:34
eintopfi am shocked22:34
eintopfso a crazy fvwm2rc with xchat22:34
wpwrakguess you would have expected that i use a strictly tty-type interface. no cursor positioning ;)22:34
DocScrutinizer05*usually* any login script should complete before chan-autojoin runs22:35
eintopfwpwrak: yes22:36
DocScrutinizer05wpwrak: also note please that any such "problem" with alternative nick only ever shows when you actually run into a collision22:36
eintopfwpwrak: I would expected something like this: http://www.zsh.org/mla/users/2006/msg00582.html22:36
wpwrakDocScrutinizer05: doesn't make you script always produce the problem, given that it always uses the temp nick ?22:37
DocScrutinizer05when xchat can log in with primary_nick, all the script with all the ghosting etc will be completely invisible to IRC22:37
DocScrutinizer05sorry, that script is a tad old and loaded with cruft22:37
wpwrak(zirc) yeah, that looks decently hardcore ;-)22:38
wpwraknow do it in traditional Bourne, for the veterans :)22:39
DocScrutinizer05log in to IRC ideally using server password (or SASL) to authenticate during log in. To be on the failsafe side, do /ns id accountname password. Then /ns ghost primary_nick. Then /nick primary_nick22:39
DocScrutinizer05simple as that22:40
DocScrutinizer05hint: on freenode use "accountname:password" for server password22:41
DocScrutinizer05hint: I repeat the above for 3 times, to deal with delays in nickserv22:45
DocScrutinizer05well, step 2,3,4 of above ;-)22:45
DocScrutinizer05/ns id accountname password;  /ns ghost primary_nick password; /nick primary_nick22:46
DocScrutinizer05password should be expendable on ghost command, I nevertheless use it in case the previous ID command didn't complete yet22:47
DocScrutinizer05but I do this because I _always_ use DocScrutinizer06 (SIC!) as login nick, on this client. Otherwise you mayve ghost yourself, dunno22:48
DocScrutinizer05you can't ghost anybody when you're not authenticated and don't use password in ghost command22:50
DocScrutinizer05so up to you if you use ghost with password or without22:50
DocScrutinizer05BEWARE! don't use this scheme on two concurrent clients with same primary_nick, or they will start lick-ass pingpong22:52
DocScrutinizer05kick*22:52
DocScrutinizer05;-P22:53
DocScrutinizer05same applies for multiple connections to same IRC network from same client, unless you make sure that script only runs for first server connection but not for second+22:54
wpwrakheh :) you've already convinced me that this problem doesn't have an easy solution and that debugging any solution it probably considerably more annoying to people than the occasional manual change22:58
wpwraklet's just hope freenode keeps the number of such renames reasonably low also in the future ...22:58
DocScrutinizer05no, this problem is extremely simple to solve (see above), doesn't need much debugging particularly since the solution runs since several years on my clients, and you're running into this problem on *every* reconnect caused by whatever reason23:06
DocScrutinizer05unless the disconnect time is long enough to make IRC servers auto-'ghost' the stale login23:06
DocScrutinizer05honestly, how hard can it be to add a >>/ns id accountname password;  /ns ghost primary_nick password; /nick primary_nick<< to some reconnect hook in your irc client?23:08
DocScrutinizer05but meh, not _my_ problem23:11
DocScrutinizer05((auto-'ghost')) "...has left this server (Quit: No Ping reply in 180 seconds.)."23:18
DocScrutinizer05freenode changed that from 12 to 3 minutes some years ago, probably to mitigate exactly this problem23:20
DocScrutinizer05I discussed with freenode stuff why they don't do auto-ghost on re-login, but they had some compelling reason why they don't want this - alas I forgot the details23:21
DocScrutinizer05actually I think they changed ping period from 600s to 90s23:32
DocScrutinizer05or sth like that23:33
DocScrutinizer05http://bugs.quassel-irc.org/issues/50023:37
DocScrutinizer05((debug)) you can enter all those commands manually, after killing and restarting your IRC client. One tip I found during automating the manually tested commands: you need a delay of several seconds between the ghost-cmd and the nick-change (if you don't wait to go nifty and wait for the response to ghost-cmd, sth I did in Konversation with "highlight" on above mentioned regex)23:46
DocScrutinizer05that's why my xchat script uses that timer 23:47
--- Mon Feb 2 201500:00

Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!