| 00:12.36 | DocScrutinizer05 | note: I'm not sure how compatible maemo xchat's script API is to the genuine xchat, since it has e.g. no python support built in |
| 00:27.06 | *** join/#qi-hardware wpwrak (~werner@154-164-231-201.fibertel.com.ar) |
| 00:28.52 | DocScrutinizer05 | http://askubuntu.com/questions/151224/how-to-get-xchat-to-automatically-ghost-the-old-session-on-provider-forced-r |
| 00:36.39 | DocScrutinizer05 | note that even https://github.com/Sepero/xchat_auto_ghost/blob/master/auto_ghost.py lacks the delay between the ghost-cmd and the nick-cmd I mentioned above |
| 00:42.44 | DocScrutinizer05 | you can easily solve that whole thing when you use "/msg nickserv id $accountname $password <ctrl-sh-a-u> /msg nickserv ghost $primary_nick $password <ctrl-sh-a-u> /timer 6 nick $primary_nick" in Server's "connect command", I guess |
| 00:44.17 | DocScrutinizer05 | I probably used a command like "cmd auto-login.xsh" instead |
| 00:44.54 | DocScrutinizer05 | or s/cmd/source/, or script, or exec or dunno what's the right reserved word to run a script |
| 00:45.57 | DocScrutinizer05 | I don't use this stuff anymore on xchat since I installed ZNC |
| 00:49.42 | DocScrutinizer05 | HAHA!!! >> I changed the second command to /timer 5 nick nickname.<< ( Izzy Jun 18 '12 at 21:31 ) |
| 00:52.18 | DocScrutinizer05 | s@auto-login.xsh@/home/user/.xchat2/xchat-login.xsh @ |
| 01:07.26 | DocScrutinizer05 | wpwrak: another nice one, re >>does that wait until i have sorted out the nick situation << : https://freenode.net/recommended/xchat/kludges/cloak-before-join.pl.txt |
| 01:40.07 | *** join/#qi-hardware kristianpaul (~kristianp@181.137.231.189) |
| 01:40.08 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 01:54.09 | *** join/#qi-hardware kristianpaul (~kristianp@181.137.231.189) |
| 01:54.09 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 01:54.59 | *** join/#qi-hardware kristianpaul (~kristianp@181.137.231.189) |
| 01:54.59 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 02:00.01 | wpwrak | ah yes, that looks like the level of complexity i expected |
| 02:00.12 | DocScrutinizer05 | huh? |
| 02:00.41 | DocScrutinizer05 | "/msg nickserv id $accountname $password <ctrl-sh-a-u> /msg nickserv ghost $primary_nick $password <ctrl-sh-a-u> /timer 6 nick $primary_nick" doesn't sound like any level of complexity |
| 02:01.42 | DocScrutinizer05 | and again, as long as you don't run into a collision (due to your login being more than 5 minutes after you left server with ping timeout), nothing at all will show up as a problem |
| 02:02.16 | DocScrutinizer05 | when however you encounter the smoker issue, you will easily fix it with "/msg nickserv id $accountname $password <ctrl-sh-a-u> /msg nickserv ghost $primary_nick $password <ctrl-sh-a-u> /timer 6 nick $primary_nick" and nobody will get hurt |
| 02:02.56 | DocScrutinizer05 | when you refer to https://freenode.net/recommended/xchat/kludges/cloak-before-join.pl.txt - I don't see you using a cloak |
| 02:04.45 | DocScrutinizer05 | I guess your concerns are due to incomplete understanding of the true nature of the problem |
| 02:06.06 | DocScrutinizer05 | >> Though the connection usually is re-established within seconds, due to the changed IP the "old session" is invalidated. XChat automatically joins the network(s), but then my nick gets refused as it "is already in use". I can manually solve that by "/nickserv ghost MyUser MyPass" << |
| 02:06.40 | DocScrutinizer05 | http://askubuntu.com/questions/151224/how-to-get-xchat-to-automatically-ghost-the-old-session-on-provider-forced-r |
| 02:07.16 | DocScrutinizer05 | wpwrak_ is simply the alternative user nickname you configured in your xchat, which gets used when the primary one is "in use" |
| 02:08.52 | DocScrutinizer05 | yes, you might join channels with nick wpwrak_ and then everybody sees when the script changes your nick to wpwrak, but what's the real problem in that, other than cosmetic? |
| 02:09.55 | DocScrutinizer05 | note however that this only happens when you actually run into a nick collision |
| 02:10.42 | DocScrutinizer05 | and even then I'm not sure if xchat doesn't do "the right thing" and postpones channel autojoin until any server-connect-cmd finished |
| 02:11.18 | DocScrutinizer05 | which would completely avoid any nick changes visible in channels |
| 02:12.11 | DocScrutinizer05 | <-- wpwrak (~werner@154-164-231-201.fibertel.com.ar) has left this server and --> wpwrak (~werner@154-164-231-201.fibertel.com.ar) has joined this channel. will show up nevertheless, inevitably |
| 02:14.24 | DocScrutinizer05 | anyway such is IRC, such is the problem, and those are the tools to mitigate/fix it. Nothing else you can do about it, so either you accept smoker or you do sth about it to fix the issue |
| 02:21.06 | *** join/#qi-hardware xiangfu (~xiangfu@118.186.138.201) |
| 02:35.20 | DocScrutinizer05 | should feel less annoyed when providing a oneliner solution and receiving complaints about the perceived complexity in such solution |
| 02:35.47 | DocScrutinizer05 | seems it's a recurring pattern at wpwrak's side |
| 02:36.46 | DocScrutinizer05 | I just fail to clearly decide if that's sarcasm, irony, or just kidding |
| 02:38.30 | *** join/#qi-hardware Textmode (~boneidle@adsl-1-au-2-174.ozonline.com.au) |
| 02:47.15 | *** join/#qi-hardware atommann (~atommann@116.24.10.15) |
| 02:50.56 | DocScrutinizer05 | with script it will look like: |
| 02:50.59 | DocScrutinizer05 | 01:52 DocScrutinizer05 has quit [Disconnected by services] |
| 02:51.00 | DocScrutinizer05 | 01:52 DocScrutinizer05 has joined #qi-hardware |
| 02:53.42 | wpwrak | naw, no reason to get excited :) i was commenting on that perl script. and it wasn't a complaint either, just me saying that the complexity of the script looked like what i'd expect, considering the complexity of the task (to be honest, i'm not entirely sure it covers all the corner cases, e.g., multiple disconnects and such. but it may still fail "nicely" even in cases it doesn't handle properly, which would be good enough in this co |
| 02:53.42 | wpwrak | ntext.) |
| 02:55.02 | DocScrutinizer05 | I don't know how multiple disconnects look for a client that usually has only one connect per server |
| 02:55.04 | wpwrak | xiangfu: i have a fun question for you: our beloved president is visiting china these days. at the beginning of her trip, she said nice things about Mao. now i wonder if that was a good or a bad idea :) |
| 02:55.27 | wpwrak | DocScrutinizer05: i mean over time |
| 02:55.52 | DocScrutinizer05 | I don't see why that's an issue |
| 02:56.44 | DocScrutinizer05 | also please note that worst case(!!!) a reconnect with ghost script but without client waiting for server-reconnect-script to finish would look like: |
| 02:56.51 | DocScrutinizer05 | 01:43 dos11 has joined #qi-hardware |
| 02:56.52 | DocScrutinizer05 | 01:43 dos11 is now known as dos1 |
| 02:56.54 | wpwrak | well, does the script get terminated and restarted ? or does it keep on running, waiting for an event that was never scheduled in the new session ? |
| 02:57.18 | DocScrutinizer05 | I don't bother checking that script |
| 02:57.31 | DocScrutinizer05 | it's completely unrelated basically |
| 02:59.07 | DocScrutinizer05 | it's meant to enforce a delay in joining channels until nickserv authenticated you and applied cloak, since otherwise you'd expose your IP to channels |
| 02:59.34 | DocScrutinizer05 | _you_ expose your IP all the time since you don't use a cloak |
| 02:59.44 | DocScrutinizer05 | so please forget about that script |
| 03:00.45 | wpwrak | naw, the script looks useful. that's a starting point. and yes, those "cosmetics" are important to me |
| 03:01.11 | DocScrutinizer05 | I just linked to it to give a hint what to do when you're really concerned about that visible nick change |
| 03:01.45 | wpwrak | yup. thanks ! |
| 03:02.00 | DocScrutinizer05 | but again, I *think* xchat just behaves and defers chan autojoin until server connect script/cmd returns |
| 03:03.09 | DocScrutinizer05 | would be quite weird when they started a concurrent child process for executing server connect command |
| 03:03.53 | DocScrutinizer05 | after all such command is supposed to run in parent process' environment |
| 03:04.01 | wpwrak | depends a bit on what you expect it to be used for |
| 03:04.45 | wpwrak | or, rather, expected at the time of implementation. it's not uncommon to find some mechanism whose function overlaps with another one added at a different time |
| 03:05.05 | DocScrutinizer05 | please simply open xchat server list config, freenode network, and add >>"/msg nickserv id $accountname $password <ctrl-sh-a-u> /msg nickserv ghost $primary_nick $password <ctrl-sh-a-u> /timer 6 nick $primary_nick"<< to server's "Connect Command" |
| 03:05.48 | DocScrutinizer05 | as elaboreated upon in http://askubuntu.com/questions/151224/how-to-get-xchat-to-automatically-ghost-the-old-session-on-provider-forced-r |
| 03:06.17 | DocScrutinizer05 | which funnily enough is *exactly* what I implemented a 2 or 3 years before |
| 03:07.03 | DocScrutinizer05 | then when you actually encounter a |
| 03:07.05 | DocScrutinizer05 | 01:43 dos11 has joined #qi-hardware |
| 03:07.07 | DocScrutinizer05 | 01:43 dos11 is now known as dos1 |
| 03:07.21 | DocScrutinizer05 | alike problem, you can have a look into that script |
| 03:09.19 | DocScrutinizer05 | http://i.stack.imgur.com/N1j0b.png |
| 03:10.35 | DocScrutinizer05 | again: server password is what you should use, and for freenode it's "<useraccountname>:<password>" |
| 03:11.47 | DocScrutinizer05 | according to nickserv your account name is identical to your preferred nick |
| 03:11.48 | DocScrutinizer05 | [Notice] -NickServ- Information on wpwrak (account wpwrak) |
| 03:13.39 | DocScrutinizer05 | using nickserv password would do a second authentication, and the 1st command in my suggested connect-command is a third authentication |
| 03:14.42 | DocScrutinizer05 | you probably get away with using just one, ideally server password |
| 03:15.44 | wpwrak | xchat says that i have to use a script for multiple commands |
| 03:16.04 | DocScrutinizer05 | hmm, interesting. That's prolly why I actually did ;-) |
| 03:16.11 | wpwrak | and /load complains that it can't find my script. hmm. |
| 03:16.29 | DocScrutinizer05 | FQN? |
| 03:16.33 | wpwrak | ah, was a typo :) |
| 03:17.23 | DocScrutinizer05 | never really wrapped my head around that <ctrl-sh-a-u> stuff either |
| 03:17.33 | wpwrak | whatever it is :) |
| 03:17.36 | DocScrutinizer05 | yep |
| 03:17.56 | wpwrak | okay, xchat is armed :) we'll see at the next disconnect if it also works :) |
| 03:18.15 | DocScrutinizer05 | either ctrl-sh-A;U or ctrl-sh-alt-U |
| 03:18.40 | DocScrutinizer05 | sinply kill xchat and restart it |
| 03:19.13 | wpwrak | (ctrl-shit-and-so-on) it looks like the sort of thing that's best avoided :) |
| 03:19.26 | DocScrutinizer05 | *nod* |
| 03:19.52 | DocScrutinizer05 | particularly since it seems to depend on gtk version |
| 03:20.24 | DocScrutinizer05 | http://xchat.org/faq/#q214 |
| 03:21.39 | DocScrutinizer05 | OUUUUUUUCH!!! >>You can create two UserCommands, with the same name, and then execute the UserCommand. It will be executed in the same order as it's written in the UserCommands GUI.<< took a while til I even got what they meant |
| 03:22.45 | DocScrutinizer05 | note the -e parameter for /load ! |
| 03:23.17 | DocScrutinizer05 | otherwise I guess it expects a script to get interpreted by the shebang interpreter |
| 03:25.38 | DocScrutinizer05 | btw you don't even need to kill xchat. a simple "reconnect" should do |
| 03:25.54 | wpwrak | begin with #!/usr/bin/xchat then wait for what happens ;-) |
| 03:25.55 | DocScrutinizer05 | menu -> "server" -> "reconnect" |
| 03:26.03 | wpwrak | naw, don't want to produce all that nosie |
| 03:26.15 | DocScrutinizer05 | that shall not be much noise |
| 03:26.46 | DocScrutinizer05 | and when there's more noise than you expected, you at least can do sth about it when you test it under close supervision |
| 03:27.56 | DocScrutinizer05 | go figure you inserted a typo that makes xchat hang in an endless loop on next reregister ;-P |
| 03:28.20 | DocScrutinizer05 | THAT would create *too much* noise |
| 03:29.54 | DocScrutinizer05 | for a start you can invoke the script manually (/LOAD -e <yourscript>) |
| 03:30.55 | DocScrutinizer05 | you should see a few "you're already authenticated" and "you can't ghost yourself", while nobody else will notice anything |
| 03:31.09 | xiangfu | wpwrak: (nice things about Mao): It is bad for your own country. it is good for her in China public place but it is bad when people talking private like me. |
| 03:31.36 | DocScrutinizer05 | hehe, good answer |
| 03:39.52 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 03:40.26 | DocScrutinizer05 | [2015-02-02 Mon 04:39:43] [Notice] -NickServ- This nickname is registered. Please choose a different nickname, or identify via /msg NickServ identify <password>. |
| 03:40.28 | DocScrutinizer05 | [2015-02-02 Mon 04:39:43] [Notice] -NickServ- You are now identified for jOERG_rw. |
| 03:40.29 | DocScrutinizer05 | [2015-02-02 Mon 04:39:49] [Notice] -NickServ- You are already logged in as jOERG_rw. |
| 03:40.31 | DocScrutinizer05 | [2015-02-02 Mon 04:39:49] [Notice] -NickServ- You may not ghost yourself. |
| 03:40.32 | DocScrutinizer05 | [2015-02-02 Mon 04:39:50] [Notice] -NickServ- You may not ghost yourself. |
| 03:44.33 | *** join/#qi-hardware archang (~archang@148.109.128.122.static.ximdns.com) |
| 03:45.15 | DocScrutinizer05 | ^^^ been a "reconnect" |
| 04:32.38 | *** join/#qi-hardware porchao (~quassel@218.231.148.105.eo.eaccess.ne.jp) |
| 04:34.57 | *** join/#qi-hardware archang (~archang@60.10.200.118) |
| 04:40.41 | *** join/#qi-hardware dos1 (~dos1@unaffiliated/dos1) |
| 04:56.09 | wpwrak | xiangfu: heh, that's about what i tought after having a look at what wikipedia has to say about how mao is perceived in china today. ah well, she also thinks that venezuela is a great example. ah well, let's just hope the chinese government has been properly briefed on what sort of president is visiting them - and how much longer that president will stay in power. |
| 05:06.25 | xiangfu | wpwrak: the chinese government changed recently. |
| 05:07.28 | wpwrak | will that mean a significant change in policies ? i picture china as a country where successive governments maintain a fairly constant style |
| 05:07.38 | xiangfu | because the new president of China. ï¼ https://en.wikipedia.org/wiki/Xi_Jinping |
| 05:10.18 | xiangfu | hmm... no. start from the chinese government inside first. |
| 05:13.09 | wpwrak | the current argentine government is left-populist, basically cleptocratic, and not very competent at actually running its country |
| 05:13.29 | wpwrak | however, it has proven great skills at ruining it ... |
| 05:15.32 | wpwrak | unfortunately, there are lots of uneducated people who like left-populism. so it's not sure yet whether argentina will get a decent government at the next elections, which are august-november this year. |
| 05:16.28 | wpwrak | (primaries to select among candidates within parties are in august, then the main election in october and - if needed - another round between the winners of the main election in november) |
| 06:21.14 | *** join/#qi-hardware jekhor (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 06:22.26 | xiangfu | https://www.youtube.com/watch?v=aThCr0PsyuA |
| 06:26.24 | DocScrutinizer05 | well, just another AR goggles. "holograms" is pretty misleading. BTW google glass relaunch i aiming at exactly same direction |
| 06:26.44 | DocScrutinizer05 | s/ i / is / |
| 06:26.46 | qi-bot | DocScrutinizer05 meant: "well, just another AR goggles. "holograms" is pretty misleading. BTW google glass relaunch is aiming at exactly same direction" |
| 06:40.56 | xiangfu | Yes. |
| 06:58.14 | *** join/#qi-hardware fengling (~fengling@49.5.133.149) |
| 07:19.59 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 07:35.52 | *** join/#qi-hardware bellow (43d519a6@gateway/web/cgi-irc/kiwiirc.com/ip.67.213.25.166) |
| 07:35.57 | bellow | Hello |
| 07:35.57 | bellow | I am trying to reconnect my Magnavox MBP 5120 blu-ray player to my Linksys routers wifi (which I have done before without trouble) and I am getting DHCP cannot be acquired. I have change the IP Address to manual on the blu-ray player without changing the IP address itself and no error. I have checked the routers settings and DHCP is enabled. Is the |
| 07:35.58 | bellow | re a way to fix this? I had it connected just fine so I added the ip/mac address to the DHCP Reservation think that would help it did not. |
| 07:44.34 | *** join/#qi-hardware bellow (43d519a6@gateway/web/cgi-irc/kiwiirc.com/ip.67.213.25.166) |
| 07:52.06 | eintopf | wpwrak: there was some KiCAD talk at FOSDEM but I wasn't there :( |
| 07:56.46 | *** join/#qi-hardware xiangfu (~xiangfu@114.54.18.141) |
| 08:03.03 | eintopf | wpwrak: https://lh5.googleusercontent.com/-YHwWlURyobA/VMuzjrkVteI/AAAAAAAAAOg/WJ7LLtljGko/w536-h876-no/MDP_Module_3.jpg |
| 08:03.20 | eintopf | I think that's the modular google smartphone which jamal mentioned |
| 08:29.56 | bellow | I am trying to reconnect my Magnavox MBP 5120 blu-ray player to my Linksys routers wifi (which I have done before without trouble) and I am getting DHCP cannot be acquired. I have change the IP Address to manual on the blu-ray player without changing the IP address itself and no error. I have checked the routers settings and DHCP is enabled. Is the |
| 08:29.56 | bellow | re a way to fix this? I had it connected just fine so I added the ip/mac address to the DHCP Reservation think that would help it did not. |
| 08:53.38 | *** join/#qi-hardware newcup (newcup@peruna.fi) |
| 09:44.59 | *** join/#qi-hardware wolfspraul (~wolfsprau@x2f76afc.dyn.telefonica.de) |
| 10:46.34 | *** join/#qi-hardware jekhor (~jek@port-13-adslby-pool42.infonet.by) |
| 10:53.34 | *** join/#qi-hardware jekhor (~jek@port-13-adslby-pool42.infonet.by) |
| 11:07.56 | *** join/#qi-hardware wolfspraul (~wolfsprau@x2f76afc.dyn.telefonica.de) |
| 11:12.58 | *** join/#qi-hardware jekhor_ (~jek@port-13-adslby-pool42.infonet.by) |
| 11:14.49 | *** join/#qi-hardware jekhor__ (~jek@port-13-adslby-pool42.infonet.by) |
| 11:21.27 | *** join/#qi-hardware pcercuei (~paul@p4FC46732.dip0.t-ipconnect.de) |
| 11:21.28 | *** join/#qi-hardware jekhor__ (~jek@port-8-adslby-pool36.infonet.by) |
| 11:26.36 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 11:53.56 | *** join/#qi-hardware jekhor_ (~jek@port-8-adslby-pool36.infonet.by) |
| 11:58.24 | *** join/#qi-hardware jekhor (~jek@port-8-adslby-pool36.infonet.by) |
| 13:22.12 | *** join/#qi-hardware jekhor_ (~jek@port-8-adslby-pool36.infonet.by) |
| 14:34.33 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 15:05.30 | *** join/#qi-hardware jekhor__ (~jek@port-8-adslby-pool36.infonet.by) |
| 15:14.02 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 15:27.47 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 15:34.02 | *** join/#qi-hardware xiangfu (~xiangfu@60.10.97.218) |
| 15:37.23 | *** join/#qi-hardware jluis (~jpddb@83.247.136.72) |
| 15:40.32 | *** join/#qi-hardware jekhor__ (~jek@port-43-adslby-pool43.infonet.by) |
| 16:11.06 | *** join/#qi-hardware wej (~j@2001:1af8:4010:a027:21::4e) |
| 17:19.58 | *** join/#qi-hardware Luke-Jr (~luke-jr@unaffiliated/luke-jr) |
| 17:36.50 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 17:40.56 | *** join/#qi-hardware wolfspraul (~wolfsprau@x2f76afc.dyn.telefonica.de) |
| 17:57.44 | *** join/#qi-hardware jwhitmore (~jwhitmore@host86-154-190-165.range86-154.btcentralplus.com) |
| 18:08.17 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 18:12.47 | *** join/#qi-hardware lrockhq (~AOv2@2601:c:9200:e8e:e086:4fc9:8fb0:985b) |
| 18:12.47 | *** join/#qi-hardware lrockhq (~AOv2@unaffiliated/sirlongrock) |
| 18:25.29 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 19:10.35 | *** join/#qi-hardware pcercuei (~pcercuei@2a02:810d:1b40:1118:1af4:6aff:fec5:1c8f) |
| 19:46.01 | *** join/#qi-hardware jekhor__ (~jek@nat-minsk-pool-46-53-200-14.telecom.by) |
| 20:51.21 | *** join/#qi-hardware methril (~methril@200.49.35.42) |
| 21:14.21 | *** join/#qi-hardware methril (~methril@200.49.35.42) |
| 22:50.39 | *** join/#qi-hardware dandon (~dandon@88.151.75.119) |
