***: Tsesarevich has quit IRC (*.net *.split)
acf_ has quit IRC (*.net *.split)
Tsesarevich has joined #arpnetworks
acf_ has joined #arpnetworks
mhoran has joined #arpnetworks
card.freenode.net sets mode: +o mhoran
trobotham has joined #arpnetworks
acf_ has quit IRC (Ping timeout: 252 seconds)
Tsesarevich has quit IRC (Ping timeout: 252 seconds)
Tsesarevich has joined #arpnetworks
ziyourenxiang has quit IRC (Ping timeout: 244 seconds)
JC_Denton has quit IRC (Quit: The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts.)
JC_Denton has joined #arpnetworks
m0unds has quit IRC (Quit: derp)
m0unds has joined #arpnetworks
mhoran_ has joined #arpnetworks
ChanServ sets mode: +o mhoran_ mhoran_: Is this thing broken?
Weird. ***: mhoran has quit IRC (*.net *.split) maxp: you successfully posted a message to this channel mhoran_ mhoran_: I can't /whois the existing mhoran, which is odd. And I can't take the nick back.
Oh there we go. ***: mhoran_ is now known as mhoran mhoran: Never seen a /whois hang so I figured maybe something else was going on like a ton of lag. ***: ziyourenxiang has joined #arpnetworks mercutio: if /whois is hanging it usually means the server you're connected to itself is lagged mhoran: That’s why I sent a message and it went through immediately.
Pretty weird. mercutio: yeah danopia: some clients map `/whois nick` as `WHOIS nick nick` which asks the local server to route the WHOIS to one server, specifically, the server that <nick> is connected to. supposedly your client did that and the server never responded since it was about to netsplit anyway
by routing to the server that the remote user is on, you often get more information back mercutio: ah interesting
i've seen that other whois but i thought it was the server name then the nick
undernet used to tell you how long someone had been idle on the server they were on but not remote or something iirc
hmm if i do /quote whois danopia and /quote whois danopia danopia then i get idle time with both
i also get idle time with normal /whois, so it seems weechat is doing the latter
hmm if i do /quote whois wolfe.freenode.net danopia then it also works
so it seems your nick is a way to shortcut remote server danopia: i don't get idle time for you unless i specify your nick twice
so supposedly we're seeing different things :D
mercutio: you're right about arg order btw - it's just that the first arg (which is now server) can be a nick instead, and it acts as a server lookup mercutio: yeah
i wrote an irc client in late 90s
so i'm sligtly familiar with things
well /quote lets you send raw content through
are you using weechat? danopia: i'm currently using one i wrote myself. but i definitely forgot that it wasn't an optional second arg, so you still got me, heh mercutio: oh cool danopia: no, a homebrew web-based client :p mercutio: sweet mine was cli
used gnu readline
but other than that was real basic
used hardly any resources compared to others though
great when i only had 24mb ram danopia: heh, so like the opposite of Slack
i never figured out readline so my CLI clients were always super crappy
i think most people i know on irc wrote a client before... the question is how long they managed to stick to it mkb: I don't know about a usable human client but a lot of people have written bots... mercutio: readline is much easier than doing your own :)
i am not sure where the source is now but it wasn't terribly complicated
i think readline uses callbacks m0unds: i have a crappy python bot on another net that does url shortening, weather, etc