| 00:26.48 | *** join/#qi-hardware dandon (~dandon@88.151.75.119) |
| 00:36.40 | *** join/#qi-hardware atommann (~atommann@58.250.80.106) |
| 00:53.36 | *** join/#qi-hardware arhuaco (~arhuaco__@181.61.62.24) |
| 01:37.12 | *** join/#qi-hardware arhuaco_ (~arhuaco__@181.61.62.24) |
| 01:39.32 | *** join/#qi-hardware wpwrak_ (~werner@154-164-231-201.fibertel.com.ar) |
| 01:41.47 | *** join/#qi-hardware dos11 (~dos1@unaffiliated/dos1) |
| 01:43.45 | *** join/#qi-hardware ysionneau (~fallen@37.59.58.85) |
| 01:44.55 | *** join/#qi-hardware uwe_mobile__ (~uwe@static.88-198-8-117.clients.your-server.de) |
| 01:48.06 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |
| 01:48.06 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 01:48.06 | *** join/#qi-hardware DocScrutinizer51 (~lagrange@openmoko/engineers/joerg) |
| 01:48.06 | *** join/#qi-hardware larsc (~lars@eisbaer.ursus-maritimus.org) |
| 01:48.06 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 01:48.56 | *** join/#qi-hardware Nik05 (~Nik05@s559686af.adsl.online.nl) |
| 01:48.56 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 01:49.23 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |
| 01:52.12 | *** join/#qi-hardware 77CAAI591 (~saturn@ppp-188-174-147-192.dynamic.mnet-online.de) |
| 01:52.12 | *** join/#qi-hardware 77CAAI591 (~saturn@openmoko/engineers/joerg) |
| 01:52.34 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 01:52.54 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 01:53.13 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 02:00.53 | wpwrak_ | hmm .. putty ... brand name "sicko". http://articulo.mercadolibre.com.ar/MLA-543789996-sicko-masilla-putty-para-modelismo-y-maquetas-50g-_JM |
| 02:11.20 | wpwrak_ | grmbl. and why does freenode think i'm a smoker ? |
| 03:33.28 | *** join/#qi-hardware atommann (~atommann@58.250.80.106) |
| 03:59.52 | *** part/#qi-hardware rozzin (rozzin@2600:3c00::f03c:91ff:fe56:7619) |
| 07:17.15 | *** join/#qi-hardware atommann (~atommann@58.250.80.106) |
| 08:02.07 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-d9ba44ef.pool.mediaWays.net) |
| 08:37.00 | *** join/#qi-hardware dandon_ (~dandon@88.151.75.119) |
| 08:37.26 | *** join/#qi-hardware dos11 (~dos1@unaffiliated/dos1) |
| 08:38.29 | *** join/#qi-hardware viric_ (~viric@unaffiliated/viric) |
| 08:40.00 | *** join/#qi-hardware uwe___ (~uwe_@dslb-088-067-009-230.088.067.pools.vodafone-ip.de) |
| 08:40.18 | *** join/#qi-hardware tumdedum_ (~tumdedum@unaffiliated/espiral) |
| 09:02.35 | *** join/#qi-hardware mth_ (wnlpnakf@88.159.34.112) |
| 09:03.11 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-d9ba44ef.pool.mediaWays.net) |
| 09:03.19 | *** join/#qi-hardware atommann (~atommann@58.250.80.106) |
| 09:06.02 | *** join/#qi-hardware viric_ (~viric@unaffiliated/viric) |
| 10:57.32 | *** join/#qi-hardware zcrc (~yaaic@cable-46.253.165.166.coditel.net) |
| 11:29.12 | *** join/#qi-hardware atommann (~atommann@116.24.82.221) |
| 11:37.48 | DocScrutinizer05 | wpwrak: (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 loss |
| 11:40.28 | DocScrutinizer05 | .xchat2/xchat-login.xsh :: |
| 11:40.34 | DocScrutinizer05 | nick Docscrutemp |
| 11:40.46 | DocScrutinizer05 | msg nickserv ghost DocScrutinizer51 MyPasswd |
| 11:40.55 | DocScrutinizer05 | timer 6 nick DocScrutinizer51 |
| 11:41.13 | DocScrutinizer05 | msg nickserv id joerg_rw MyPasswd |
| 11:44.32 | DocScrutinizer05 | http://wiki.maemo.org/User:Joerg_rw/xchat/ |
| 11:47.33 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 11:49.36 | *** join/#qi-hardware arossdotme (~butler@79-69-205-12.dynamic.dsl.as9105.com) |
| 13:24.16 | *** join/#qi-hardware jekhor (~jek@port-13-adslby-pool42.infonet.by) |
| 14:22.41 | wpwrak | hmm. 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:47.17 | whitequark | xchat script? |
| 15:16.20 | wpwrak | i guess it's a variant of the things described here: http://xchatdata.net/Scripting/HomePage |
| 15:56.56 | *** join/#qi-hardware jekhor (~jek@91.215.176.168) |
| 18:00.31 | *** join/#qi-hardware wolfspraul (~wolfsprau@brln-d9ba44ef.pool.mediaways.net) |
| 18:01.10 | *** join/#qi-hardware FDCX_ (~fdcx@84.232.210.81) |
| 20:06.27 | *** join/#qi-hardware rjeffries (~rjeffries@pool-108-40-199-126.snloca.fios.verizon.net) |
| 20:09.37 | rjeffries | wpwrak 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:11.17 | rjeffries | I 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:22.10 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 20:34.23 | DocScrutinizer05 | wpwrak: 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 ZNC |
| 20:36.13 | DocScrutinizer05 | quite possible that the thing been named xchat-login.sh before I renamed it to disable it |
| 20:36.53 | DocScrutinizer05 | and it looks like plain xchat commands without leading "/" |
| 20:38.07 | DocScrutinizer05 | prolly Raster instructed me back in TPE |
| 20:39.03 | DocScrutinizer05 | or shortly after, when I bought my N810 |
| 20:40.21 | DocScrutinizer05 | without Raster's N800 (N770?) I'd possibly never had noticed maemo and thus xchat. Definitely Raster told me about xchat |
| 20:49.42 | DocScrutinizer05 | anyway I recall I learned about timers via '/help timer' cmd, and that stuff once kinda worked |
| 20:58.31 | DocScrutinizer05 | the cmds are only a 4 lines, you should be capable to grok the idea even without a POSIX standard scripting language being used ;-D |
| 21:02.40 | DocScrutinizer05 | maybe 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:34.16 | wpwrak | rjeffries: 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 cases |
| 21:35.17 | wpwrak | DocScrutinizer05: interesting .. didn't know of the raster angle :) |
| 21:36.56 | 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 underneath |
| 21:38.42 | DocScrutinizer05 | you need a temporary name anyway, since you can't log in to IRC with a nick that's already in use |
| 21:39.15 | DocScrutinizer05 | recently your temporary name is smoker |
| 21:39.17 | DocScrutinizer05 | ;-) |
| 21:49.42 | wpwrak | well, i only need a temp name if there's actually a conflict |
| 21:50.54 | *** join/#qi-hardware lrockhq (~AOv2@unaffiliated/sirlongrock) |
| 22:13.57 | DocScrutinizer05 | you need one to even find out *if* there is a conflict |
| 22:19.43 | DocScrutinizer05 | your 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.45 | DocScrutinizer05 | nick]), 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:20.57 | DocScrutinizer05 | oops s/ /msg nickserv <ACCOUNTnam> <PassWD> / /msg nickserv ID <ACCOUNTnam> <PassWD> / |
| 22:27.50 | DocScrutinizer05 | changing 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:29.52 | DocScrutinizer05 | NB your alternative (temporary) nick is completely arbitrary, you don't even need to know it |
| 22:30.40 | DocScrutinizer05 | wpwrak: ^^^ |
| 22:33.25 | wpwrak | my 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 problem |
| 22:33.36 | DocScrutinizer05 | that depends on client |
| 22:33.42 | wpwrak | xchat :) |
| 22:33.51 | DocScrutinizer05 | I dunno about xchat |
| 22:33.57 | eintopf | who use xchat here |
| 22:34.07 | wpwrak | me ! :) |
| 22:34.16 | eintopf | i am shocked |
| 22:34.37 | eintopf | so a crazy fvwm2rc with xchat |
| 22:34.57 | wpwrak | guess you would have expected that i use a strictly tty-type interface. no cursor positioning ;) |
| 22:35.01 | DocScrutinizer05 | *usually* any login script should complete before chan-autojoin runs |
| 22:36.16 | eintopf | wpwrak: yes |
| 22:36.37 | DocScrutinizer05 | wpwrak: also note please that any such "problem" with alternative nick only ever shows when you actually run into a collision |
| 22:36.46 | eintopf | wpwrak: I would expected something like this: http://www.zsh.org/mla/users/2006/msg00582.html |
| 22:37.23 | wpwrak | DocScrutinizer05: doesn't make you script always produce the problem, given that it always uses the temp nick ? |
| 22:37.36 | DocScrutinizer05 | when xchat can log in with primary_nick, all the script with all the ghosting etc will be completely invisible to IRC |
| 22:37.58 | DocScrutinizer05 | sorry, that script is a tad old and loaded with cruft |
| 22:38.42 | wpwrak | (zirc) yeah, that looks decently hardcore ;-) |
| 22:39.22 | wpwrak | now do it in traditional Bourne, for the veterans :) |
| 22:39.57 | DocScrutinizer05 | log 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_nick |
| 22:40.36 | DocScrutinizer05 | simple as that |
| 22:41.38 | DocScrutinizer05 | hint: on freenode use "accountname:password" for server password |
| 22:45.08 | DocScrutinizer05 | hint: I repeat the above for 3 times, to deal with delays in nickserv |
| 22:45.26 | DocScrutinizer05 | well, step 2,3,4 of above ;-) |
| 22:46.23 | DocScrutinizer05 | /ns id accountname password; /ns ghost primary_nick password; /nick primary_nick |
| 22:47.28 | DocScrutinizer05 | password should be expendable on ghost command, I nevertheless use it in case the previous ID command didn't complete yet |
| 22:48.59 | DocScrutinizer05 | but I do this because I _always_ use DocScrutinizer06 (SIC!) as login nick, on this client. Otherwise you mayve ghost yourself, dunno |
| 22:50.06 | DocScrutinizer05 | you can't ghost anybody when you're not authenticated and don't use password in ghost command |
| 22:50.31 | DocScrutinizer05 | so up to you if you use ghost with password or without |
| 22:52.37 | DocScrutinizer05 | BEWARE! don't use this scheme on two concurrent clients with same primary_nick, or they will start lick-ass pingpong |
| 22:52.53 | DocScrutinizer05 | kick* |
| 22:53.01 | DocScrutinizer05 | ;-P |
| 22:54.53 | DocScrutinizer05 | same 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:58.08 | wpwrak | heh :) 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 change |
| 22:58.35 | wpwrak | let's just hope freenode keeps the number of such renames reasonably low also in the future ... |
| 23:06.07 | DocScrutinizer05 | no, 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 reason |
| 23:06.46 | DocScrutinizer05 | unless the disconnect time is long enough to make IRC servers auto-'ghost' the stale login |
| 23:08.00 | DocScrutinizer05 | honestly, 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:11.16 | DocScrutinizer05 | but meh, not _my_ problem |
| 23:18.44 | DocScrutinizer05 | ((auto-'ghost')) "...has left this server (Quit: No Ping reply in 180 seconds.)." |
| 23:20.05 | DocScrutinizer05 | freenode changed that from 12 to 3 minutes some years ago, probably to mitigate exactly this problem |
| 23:21.47 | DocScrutinizer05 | I 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 details |
| 23:32.51 | DocScrutinizer05 | actually I think they changed ping period from 600s to 90s |
| 23:33.08 | DocScrutinizer05 | or sth like that |
| 23:37.19 | DocScrutinizer05 | http://bugs.quassel-irc.org/issues/500 |
| 23:46.44 | 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:47.36 | DocScrutinizer05 | that's why my xchat script uses that timer |