00:02:02  <txdv_>gods shouldn't ask mortals questions
00:02:17  <tjfontaine>ryah: what's the context of the question?
00:03:45  <TooTallNate>txdv_: but what if god was one of us?
00:03:52  * tjfontainegroans
00:04:03  <TooTallNate>hahaha
00:16:08  <ryah>lol
00:37:27  * ryahshakes gyp violently
00:37:31  <ryah>WORK
00:51:20  * EhevuTovquit (Quit: This computer has gone to sleep)
00:54:04  <ryah>shaking software does fix things...
00:55:42  <TooTallNate>ryah: what are you trying to do?
00:56:54  * ericktquit (Ping timeout: 240 seconds)
01:01:08  * TooTallNatequit (Quit: Computer has gone to sleep.)
01:18:28  <tjfontaine>ryah: I'm curious as well, are you trying to do the xcode thing? if so https://github.com/joyent/node/pull/4022
01:18:40  <tjfontaine>ryah: you're fighting with the fact that there's a dependency missing in the tree
01:41:19  * Raltquit (Remote host closed the connection)
01:41:52  * Raltjoined
01:43:32  <ryah>no different project
01:46:08  * Raltquit (Ping timeout: 245 seconds)
01:54:45  * lohkeypart
01:55:57  * lohkeyjoined
02:00:08  * lohkeyquit (Ping timeout: 255 seconds)
02:09:36  * ericktjoined
02:46:02  * TooTallNatejoined
02:55:02  <ryah>https://twitter.com/gevent/status/251870755187478529 <-- :)
02:55:36  <ryah>it would be so great to have gevent on libuv
03:01:28  <tjfontaine>TooTallNate: those commits do make stricttype work with arguments, I just need to make StrictType(Struct()) work and I should be ready for you to review
03:02:19  <TooTallNate>tjfontaine: kewl :)
03:02:29  <TooTallNate>tjfontaine: ya it feels much cleaner no calling ref()
03:02:33  <TooTallNate>it was such a hack
03:02:44  <TooTallNate>and in retrospect completely unnecessary :D
03:02:52  <tjfontaine>heh
03:03:14  <TooTallNate>correctness > speed anyways
03:04:50  * brsonquit (Quit: leaving)
03:05:01  <TooTallNate>i'm trip pin on why this one node-ffi test takes 2 second to complete...
03:05:09  <TooTallNate>fuck you autocomplete
03:05:18  <tjfontaine>heh, ya I noticed that the past couple days
03:05:49  <TooTallNate>it's suspiciously the same length as the mocha timeout
03:31:04  * AvianFluquit (Remote host closed the connection)
03:48:26  * bnoordhuisquit (Ping timeout: 260 seconds)
04:03:56  * loladiro_joined
04:05:43  * loladiroquit (Ping timeout: 260 seconds)
04:05:43  * loladiro_changed nick to loladiro
04:16:48  * stagasjoined
04:44:59  * TooTallNatequit (Quit: Computer has gone to sleep.)
04:50:50  * philips_quit (Excess Flood)
04:55:10  * philips_joined
05:09:40  * Raynosquit (Ping timeout: 246 seconds)
05:11:04  * Raynosjoined
05:44:19  * stagasquit (Quit: ChatZilla 0.9.89-rdmsoft [XULRunner 1.9.0.17/2009122204])
06:32:31  <creationix>If anyone wants to have fun and test out my node-powered sandbox check out http://luvit.io:133
06:32:44  <creationix>if you add ?debug to the url, it will console.log the smith rpc messages
06:33:16  <creationix>It's running as a user with read-only access to the fs and under a cgroup https://github.com/luvit/try.luvit.io/blob/master/config.js#L18-19
06:34:38  * TooTallNatejoined
06:34:54  <indutny>creationix: doesnt' seem to be working...
06:35:16  <creationix>indutny, requires binary websockets
06:35:19  <creationix>what browser are you using?
06:35:37  <indutny>oh
06:35:51  <creationix>Chrome works fine for me
06:35:55  <creationix>even on Android!
06:35:59  <indutny>odd
06:36:06  <indutny>I've even tried it in canary
06:36:32  <creationix>does your isp block them or something?
06:36:53  <indutny>hah
06:36:55  <indutny>idk
06:37:03  <indutny>I'll check it once again in a bit
06:37:10  <indutny>probably I've some DNS problem
06:37:14  <indutny>connected through VPN now
06:37:22  <indutny>though, luvit.io works fine
06:37:25  <creationix>oh heh
06:37:27  <creationix>port 1337
06:37:30  <creationix>not 133
06:37:41  <creationix>http://luvit.io:1337/
06:37:51  <creationix>I guess my copy paste failed the first time
06:38:05  <indutny>ah
06:38:09  <indutny>that's much better
06:38:16  <creationix>how's the latency for you?
06:38:19  <creationix>the server is in Texas
06:38:29  <indutny>nice!
06:38:31  <creationix>I assume you're in either Europe or Russia
06:38:32  <indutny>well, it's fine
06:38:44  <indutny>I'm russia, but in europe zone
06:38:58  <creationix>do I dare tweet this?
06:39:06  <creationix>each live session uses about 3mb of ram
06:39:18  <indutny>creationix: sure :)
06:39:23  <creationix>my box can handle about 400mb more
06:39:36  <indutny>I'm doing make -j4 16 now :D
06:39:40  <indutny>it's really fun
06:39:56  <creationix>good luck getting to bash
06:40:01  <indutny>haha
06:40:05  <creationix>I guess child_process.spawn with custom fd would work
06:40:10  <creationix>I think luvit supports that
06:40:32  <creationix>the cgroup sandbox kills you if you use too much ram or cpu
06:40:47  <creationix>try "while true do print 'hi' end"
06:40:48  <indutny>ok
06:40:53  <indutny>2100 rps on 16 core server
06:41:32  <indutny>that's https
06:41:42  <creationix>progress!
06:41:47  <creationix>I wonder how luvit's ssl compares
06:41:51  <creationix>I think pquerna did it
06:42:43  <creationix>wow, that strange, my master node process is stuck at 100% cpu
06:42:44  <indutny>hm...
06:42:47  <indutny>may be it's not as good
06:42:51  <indutny>ah
06:42:53  <indutny>no it is!
06:42:54  <indutny>so
06:43:09  <indutny>I get 628 req/sec with one thread and https module
06:43:21  <indutny>and 914 req/sec with one thread and tlsnappy module
06:43:26  <indutny>woot!
06:48:32  <creationix>what's it mean when my node process is consuming 100% cpu and strace toggles between epoll_wait and clock_gettime?
06:49:43  <creationix>hmm, the website is super reponsive
06:49:48  <creationix>as is the other process on that server
06:49:54  <indutny>aha
06:49:57  <indutny>that's the problem
06:50:02  <indutny>checkout active handles
06:50:09  <indutny>but
06:50:13  <indutny>it should not eat 100% cpu
06:50:22  <indutny>you should probably try connecting with gdb to it
06:50:27  <creationix>how do I do that?
06:50:28  <indutny>and inspecting each thread's bt
06:50:33  <indutny>gdb -p processid
06:51:01  <creationix>heh, first need to install gdb
06:51:08  <creationix>fresh box
06:51:23  <indutny>heh
06:51:26  <indutny>is it ubuntu?
06:51:34  <creationix>yep
06:51:40  <creationix>alright, attached to process, now what?
06:52:46  <creationix>bt shows it calling uv_hrtime
06:53:11  <creationix>from uv_update_time from uv__run from uv_run
06:54:30  <creationix>on another run it broke on uv__poll -> epoll_poll -> epoll_wait
07:14:32  <indutny>creationix: sorry
07:14:34  <indutny>I was afk
07:14:41  <indutny>creationix: i threads
07:14:50  <indutny>creationix: then "t [thread num]" and "bt"
07:14:55  <indutny>creationix: for each thread
07:17:14  <creationix>https://gist.github.com/ca9145ce8f0df9af94de
07:17:54  <indutny>creationix: and while you have opened gdb
07:17:58  <indutny>creationix: is cpu usage 0% ?
07:18:43  <indutny>creationix: from what I see, there're no actions in event loop at all (so it should not eat CPU at all)
07:19:03  <indutny>creationix: btw, what program can geek use to create nice plot?
07:19:16  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
07:19:38  <creationix>it's 0% cpu while gdb has the process paused
07:19:44  <indutny>creationix: interesting
07:19:46  <creationix>but it's back to 100% as soon as I cont
07:19:58  <creationix>I am using the pty.js C addin
07:20:01  <indutny>creationix: and if you break (^C) ?
07:20:05  <indutny>pty.js addon
07:20:06  <indutny>hm...
07:20:06  <creationix>maybe he's doing something wrong
07:20:09  <indutny>link?
07:20:22  <creationix>https://github.com/chjj/pty.js/
07:20:39  <creationix>I kinda wish it was built into node
07:20:45  <creationix>but I guess it's not a common enough need
07:21:23  <indutny>are you using fork?
07:22:01  <creationix>I'm using his spawn
07:22:03  <creationix>whatever that does
07:22:18  <creationix>says it's a wrapper for forkpty(3)
07:23:00  <indutny>hm..
07:23:02  <indutny>idk
07:23:18  <creationix>it doesn't seem to hurt anything other than maxing our one of my 4 cores
07:23:20  <indutny>so only epoll_wait and getclocktime syscalls and nothing more?
07:23:24  <creationix>everything stays super snappy
07:23:35  <indutny>and breaking in gdb doesn't reveal any interesting stacktrace?
07:23:35  * loladiropart
07:24:58  <creationix>nothing that makes sense to me
07:25:07  <creationix>and it quit doing it when I closed gsb
07:25:11  <creationix>*gdb
07:25:17  <creationix>I wonder if I killed the process somehow
07:25:23  <creationix>upstart restarts it automatically
07:25:35  <creationix>yeah, the pid changed
07:26:59  <creationix>I should make a nodejs version of this
07:27:05  <creationix>it would be a pretty trivial change
07:27:13  <creationix>except node uses a ton of ram
07:27:17  <creationix>10mb per session is expensive
07:29:01  <creationix>alright, I'm off to bed, hopefully my server is still running in the morning
07:38:07  * ericktquit (Quit: erickt)
07:46:40  * hzjoined
07:50:53  * Raltjoined
07:56:43  * AvianFlujoined
08:03:22  * rendarjoined
08:15:36  <indutny>ok
08:15:41  <indutny>creationix: sleep tight
08:19:27  * TooTallNatejoined
08:19:27  * TooTallNatequit (Client Quit)
08:19:36  <indutny>oh nice
08:19:40  <indutny>fork is not really good with tlsnappy
08:19:43  <indutny>ryah: ^
08:19:49  <indutny>ryah: I mean cluster.fork
08:20:14  <indutny>that's because event-loop isn't busy enough and only half of forks was really accepting connections
08:20:24  <creationix>http://howtonode.org:1337/ -> require('tetris') -> :)
08:20:31  <creationix>now I'm really going to bed
08:24:27  <indutny>creationix: ++
08:24:41  <indutny>creationix: odd thing
08:24:50  <indutny>creationix: cluster is really bad at balancing :)
08:24:58  <indutny>creationix: I suppose it's due to it's not-round-robin nature
08:28:50  * TheJHjoined
08:36:05  * kristatejoined
08:59:38  <ryah>indutny: oh okay
09:02:23  * kristatequit (Ping timeout: 245 seconds)
09:15:46  * mmaleckijoined
09:23:03  <indutny>ryah: it works fine with 16 threads and one process, though :D
09:23:32  <indutny>and js is still isn't full saturated, since it can handle ~6000 rps
09:23:54  <indutny>probably hybrid combinations, like 4 forks with 4 threads each may work better
09:23:58  <indutny>haven't tested this yet
09:24:28  * Raltquit (Remote host closed the connection)
09:25:00  * Raltjoined
09:29:30  * Raltquit (Ping timeout: 252 seconds)
09:44:57  * Raltjoined
09:46:12  * Raltquit (Read error: Connection reset by peer)
09:46:16  * Ralt_joined
09:47:14  * mmaleckiquit (Ping timeout: 255 seconds)
09:51:19  * mmaleckijoined
09:59:02  * Ralt_quit (Remote host closed the connection)
09:59:38  * Raltjoined
10:03:58  * Raltquit (Ping timeout: 252 seconds)
10:06:22  * Raltjoined
10:13:42  * Raltquit (Remote host closed the connection)
10:14:18  * Raltjoined
10:18:25  * Raltquit (Read error: Connection reset by peer)
10:18:43  * Raltjoined
10:31:17  * rendarquit
10:35:11  * Raltquit (Remote host closed the connection)
10:35:44  * Raltjoined
10:38:46  * mmaleckiquit (Ping timeout: 244 seconds)
10:40:18  * Raltquit (Ping timeout: 245 seconds)
10:48:41  * mmaleckijoined
10:49:28  * rendarjoined
11:08:05  * mmaleckiquit (Quit: Reconnecting)
11:18:06  * mmaleckijoined
11:20:21  * mmalecki_joined
11:20:28  * mmaleckiquit (Client Quit)
11:20:44  * TheJHquit (Quit: goodbye)
11:24:10  * TheJHjoined
11:26:29  * bnoordhuisjoined
11:50:06  * mmalecki_quit (Quit: Reconnecting)
11:55:31  * mmaleckijoined
12:19:32  * Raltjoined
12:56:13  * TheJHquit (Ping timeout: 246 seconds)
12:56:30  * TheJHjoined
13:03:47  * mmaleckiquit (Ping timeout: 260 seconds)
13:06:24  * mmaleckijoined
13:26:15  <indutny>bnoordhuis: hey man
13:26:21  <indutny>bnoordhuis: wanna see tlsnappy benchmarks?
13:38:27  <deoxxa>so uh
13:38:30  <deoxxa>nodejs.org has expired
13:38:43  <deoxxa>ping isaacs ryah
13:40:02  <mmalecki>huh? I'm getting ECONNREFUSED on https
13:40:44  <mmalecki>also, Bert is just giving a talk about libuv
13:40:54  <deoxxa>Domain Name:NODEJS.ORG
13:40:54  <deoxxa>Created On:29-Sep-2009 14:50:55 UTC
13:40:54  <deoxxa>Last Updated On:29-Sep-2012 12:50:48 UTC
13:40:54  <deoxxa>Expiration Date:29-Sep-2012 14:50:55 UTC
13:41:03  <mmalecki>ah. domain.
13:41:04  <mmalecki>whoops.
13:41:16  <mmalecki>I can grab [0] and have him call isaac
13:41:22  * deoxxanods
13:41:24  <mmalecki>or mikeal
13:41:28  <mmalecki>or Bert
13:41:37  <mmalecki>okay, will do
13:43:25  <mmalecki>his talk should end in 10 mins
13:44:02  <mmalecki>don't registrars do recurring payments tho?
13:44:19  <bnoordhuis>indutny: ho man
13:44:20  <bnoordhuis>sure
13:44:40  <mmalecki>bnoordhuis: can *you* call Ryan or Isaac?
13:45:19  <indutny>bnoordhuis: shared with you google doc
13:45:21  <deoxxa>looks like something's happening with it, but there's somethign weird going on
13:45:29  <deoxxa>like, it was last updated today
13:45:35  <indutny>basically tlsnappy is able to handle almost 2200
13:45:36  <indutny>rps
13:45:52  <indutny>and nginx ~2450
13:45:53  <mmalecki>yeah, exactly
13:46:09  <indutny>not as bad, actually
13:46:56  <bnoordhuis>mmalecki: what's up?
13:47:01  <mmalecki>bnoordhuis:
13:47:02  <mmalecki>Last Updated On:29-Sep-2012 12:50:48 UTC
13:47:02  <mmalecki>Expiration Date:29-Sep-2012 14:50:55 UTC
13:47:10  <mmalecki>nodejs.org ^
13:47:29  <bnoordhuis>oh, the cert expired?
13:47:33  <deoxxa>no, the domain
13:47:33  <mmalecki>domain
13:47:43  <bnoordhuis>ah, i see
13:48:02  <indutny>oooh
13:48:14  <indutny>this's a serious shit
13:48:21  <bnoordhuis>i'll mail them
13:48:55  <indutny>bnoordhuis: https://github.com/indutny/tlsnappy/blob/master/benchmark/index.md
13:48:58  <indutny>that's webpage
13:49:01  <indutny>if you're lazy :)
13:50:12  <bnoordhuis>spiffy infographics
13:50:27  <indutny>bnoordhuis: yeah
13:50:31  <bnoordhuis>so you're outperforming nginx?
13:50:33  <indutny>bnoordhuis: there're data below
13:50:47  <indutny>no, I don't
13:50:53  <bnoordhuis>on request time, i mean
13:51:03  <indutny>no
13:51:04  <indutny>I don't
13:51:05  <indutny>:)
13:51:05  <bnoordhuis>oh wait, higher is slower
13:51:10  <indutny>but I'm very close
13:51:12  <bnoordhuis>graphs are hard
13:51:33  <bnoordhuis>nice
13:51:36  <indutny>I'm outperforming tls module
13:51:41  <indutny>:)
13:51:44  <indutny>for sure
13:51:57  * piscisaureus_joined
13:52:07  <piscisaureus_>isaacs: ryah: dude
13:52:16  <piscisaureus_>isaacs: you let nodejs.org expire :-(
13:52:35  <indutny>piscisaureus_: https://github.com/indutny/tlsnappy/blob/master/benchmark/index.md
13:53:00  <indutny>piscisaureus_: hangouts are bad for domain names
13:54:10  <bnoordhuis>http://news.ycombinator.com/newest <- quick! upvote the libuv link
13:55:30  <piscisaureus_>oh it's not expired yet
13:55:34  <piscisaureus_>we have 1 hour :-)
14:00:46  <indutny>haha
14:00:50  <indutny>I'll buy it
14:01:11  <mmalecki>then sell it to ryah for $ kk
14:01:25  <indutny>ok
14:01:43  <mmalecki>(kidding, obviously)
14:01:48  * piscisaureus_quit (Ping timeout: 256 seconds)
14:01:49  <indutny>50 m 55sec
14:01:50  <indutny>ahhaha
14:02:33  <bnoordhuis>naming your window manager 'awesome' sure as hell doesn't improve googleability...
14:02:35  <mmalecki>indutny: I think Bert will be buying it if Ryan doesn't get on top of it
14:02:52  <mmalecki>but he's out for a cigarett
14:02:57  <indutny>hahaha
14:03:01  <indutny>also
14:03:04  <indutny>it's on ycombinator
14:03:10  <indutny>so probably a lot of people will try to buy it
14:03:18  <mmalecki>oh fuck...
14:03:22  <indutny>http://news.ycombinator.com/item?id=4589563
14:03:25  <indutny>I've flagged it
14:03:43  <indutny>:)
14:03:53  <mmalecki>people are idiots
14:09:19  <deoxxa>it's not a huge problem
14:09:33  <deoxxa>there's still plenty of time to buy it back
14:09:48  <deoxxa>it'll just be inoperational for a couple of days or whatever in the very worst case
14:10:03  <deoxxa>like, that's pretty bad on its own, but it's not unrecoverable
14:15:18  <Ralt>bnoordhuis: always google awesome wm, I usually get good results this way
14:21:13  <bnoordhuis>Ralt: ah, good tip - thanks
14:21:52  <bnoordhuis>i was adding 'window manager' the whole time but that gets old (and rsi inducing) fast
14:22:29  <txdv_>3
14:48:47  * mmaleckiquit (Quit: Reconnecting)
14:48:58  * mmaleckijoined
14:52:40  <indutny>mmalecki: I can't buy it
14:52:41  <indutny>:(
14:53:19  <bnoordhuis>they don't accept rubles?
14:53:25  * bnoordhuisducks
14:53:57  <bnoordhuis>indutny: you can't buy it because it's entered the grace period
14:54:19  <bnoordhuis>it won't be for sale for a few more days at the least
14:54:38  <indutny>bnoordhuis: har har
14:54:39  <indutny>:)
14:54:54  <indutny>bnoordhuis: so any ideas how we can make tlsnappy as fast as nginx is?
14:55:19  <bnoordhuis>indutny: yes, maybe - but i'm off to dinner
14:55:25  <indutny>ok
14:55:26  <indutny>see ya
14:55:27  <bnoordhuis>i'll ping you in a couple of hours
14:59:58  <mmalecki>indutny: yeah, neither can I
15:38:36  <tjfontaine>ircretary: tell TooTallNate https://github.com/tjfontaine/ref-strict
15:38:36  <ircretary>tjfontaine: I'll be sure to tell tootallnate
15:42:42  * lohkeyjoined
16:06:45  <txdv_>I love cookies
16:12:15  <mmalecki>indutny: you had that thing for distributed locking?
16:14:21  * Raltquit (Remote host closed the connection)
16:14:55  * Raltjoined
16:19:28  * Raltquit (Ping timeout: 248 seconds)
16:35:27  * loladirojoined
16:40:41  <txdv_>bnoordhuis: please do uv_file_t
16:43:11  * mmalecki_joined
16:46:09  * rendarquit
16:46:42  * mmaleckiquit (Ping timeout: 256 seconds)
16:58:17  * ericktjoined
17:01:02  * rendarjoined
17:10:36  * mmalecki_changed nick to mmalecki
17:19:17  * stagasjoined
17:25:55  * mmaleckiquit (Ping timeout: 246 seconds)
17:28:48  <txdv_>dis ppl
17:28:57  <txdv_>at least reddit never rests
17:30:25  * Ariajoined
17:41:52  * Raltjoined
17:45:10  * Raltquit (Remote host closed the connection)
17:45:47  * Raltjoined
17:50:18  * Raltquit (Ping timeout: 260 seconds)
18:02:23  * stagasquit (Ping timeout: 245 seconds)
18:06:05  * avalanche123|hjoined
18:11:24  * avalanche123|hquit (Quit: Computer has gone to sleep.)
18:12:01  * TooTallNatejoined
18:30:54  * Raltjoined
18:38:51  * Raltquit (Remote host closed the connection)
18:39:23  * Raltjoined
18:43:54  * Raltquit (Ping timeout: 240 seconds)
18:44:45  <TooTallNate>isaacs: this made me lol http://cl.ly/image/1e2I1Y2N030J
18:45:22  <isaacs>TooTallNate: ugh.
18:45:26  <isaacs>TooTallNate: it should be updated now.
18:45:38  <isaacs>TooTallNate: you may need to clear chrome's cache
18:45:43  <TooTallNate>grrrrr dns propagation
18:45:45  <TooTallNate>ya maybe that
18:47:08  <isaacs>chrome caches dns longer than the ttls say to. that's a big part of why it's so "fast"
18:48:18  <TooTallNate>still a parked domain for me after clearing cache and restarting chrome
18:50:39  * lohkeyquit (Quit: lohkey)
18:50:41  <Aria>Hm. I see the parking too.
18:51:18  <Aria>Google's public DNS still has the old IP with a TTL of 449 for me.
18:51:25  <isaacs>oh, wtf.
18:52:40  <Aria>(dig nodejs.org @8.8.8.8)
18:52:53  <isaacs>Aria: what ip address?
18:53:01  <isaacs>it should be 8.12.44.238
18:53:19  <Aria>Yeah, that's the new. I see 199.x.x.x.
18:53:33  <Aria>nodejs.org. 443 IN A 199.59.166.108
18:53:39  <isaacs>ok... must jsut be propagating still?
18:53:51  <Aria>Yeah.
18:53:55  <Aria>279 seconds now.
18:54:57  <isaacs>one chimpanzee... two chimpanzee...
19:00:02  * hzquit
19:01:03  <TooTallNate>now i get nginx 504 gateway timeout
19:01:11  * loladiroquit (Quit: loladiro)
19:01:36  <isaacs>hmm.
19:01:37  <isaacs>that's weir
19:01:42  <isaacs>TooTallNate: what ip address?
19:01:55  <isaacs>TooTallNate: do you get that error from browser, or curl?
19:01:56  <TooTallNate>199.59.166.108
19:02:01  <TooTallNate>isaacs: browser
19:02:09  <TooTallNate>and curl
19:02:26  <isaacs>TooTallNate: that's the wrong address
19:02:30  <isaacs>TooTallNate: wait :)
19:03:34  <Aria>Hrm. Google just refreshed with the wrong IP again
19:03:54  <isaacs>that's annoying.
19:04:23  * kristatejoined
19:04:40  <Aria>Isn't it?
19:04:42  <isaacs>Aria: works in CA, and in indiana
19:04:48  <Aria>That's really weird. They're usually fast.
19:04:54  <Aria>And your SOA record did bump.
19:06:38  <isaacs>i'm not super happy with namecheap
19:07:02  <isaacs>they seem to not be updating everywhere internally, or something
19:08:00  <Aria>Hm. They did pass up to the .org servers properly.
19:08:04  <Aria>So I don't think it's namecheap.
19:08:18  <Aria>though their soa record is weirdly formatted for the expired domains, but not in a way that a DNS server should have a problem with.
19:08:22  <Aria>'cept maybe Google's.
19:10:39  <isaacs>sure
19:10:47  <isaacs>Aria: but google's DNS in CA is working fine, apparelty
19:12:34  <Aria>Yeah. It's anycast, so it'll vary by region, depending on the network topology.
19:12:51  <Aria>Makes me hopeful that the east coast will catch up shortly.
19:18:14  <TooTallNate>wheew, it's back up for me
19:18:43  * isaacsaway for a few
19:25:23  <ryah>yo
19:26:27  <ryah>isaacs: glad that got taken care of :)
19:26:33  <ryah>isaacs: did you talk to emily?
19:26:43  <ryah>i texted her frantically this morning
19:28:28  * lohkeyjoined
19:28:49  * Raltjoined
19:31:10  <indutny>hoya
19:31:16  <indutny>ryah: what about nodejs.org?
19:31:25  <indutny>oh
19:31:26  <indutny>2013
19:31:27  <indutny>good
19:31:57  <ryah>indutny: i think it's fixed now
19:32:03  <indutny>yes, I see
19:36:18  <isaacs>ryah: yeah, should be fixed now
19:36:33  <isaacs>ryah: Aria reports that boston still sees the namecheap page.
19:36:39  <isaacs>but the dns is crawling along
19:37:14  <ryah>isaacs: getting 504 from nodejs.org
19:37:31  <ryah>is there a backend server now?
19:37:49  <ryah>im trying to ssh in.. but can't
19:38:27  <isaacs>ryah: which ip address you getting for it?
19:39:02  <isaacs>$ ssh node@nodejs.org ifconfig external0:3
19:39:02  <isaacs>external0:3: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 3
19:39:05  <isaacs> inet 8.12.44.238 netmask fffffe00 broadcast 8.12.45.255
19:39:38  <ryah>199.59.166.108
19:40:16  <ryah>oh, wrong one
19:40:16  <isaacs>ryah: edit your hosts file
19:40:26  <ryah>sorry - nm
19:40:34  * Raltquit (Remote host closed the connection)
19:40:41  <ryah>i guess namecheap also uses ngninx
19:40:58  <Aria>Heh. Oy.
19:41:10  * Raltjoined
19:41:11  * lohkeyquit (Quit: lohkey)
19:45:36  * Raltquit (Ping timeout: 245 seconds)
19:59:33  * ericktquit (Quit: erickt)
20:01:11  <isaacs>ryah: we should have done this readable stream read() method approach 2 years ago
20:01:17  <isaacs>ryah: back when it was ok to break all nodes
20:03:45  <isaacs>would have prevented a lot of modules depending on weirdo edge cases.
20:14:32  * ericktjoined
20:26:04  * ericktquit (Quit: erickt)
20:26:32  * Raltjoined
20:27:17  * brsonjoined
20:29:39  * Raltquit (Remote host closed the connection)
20:29:55  * Ariaquit (Remote host closed the connection)
20:30:12  * Raltjoined
20:33:47  * Raltquit (Read error: Operation timed out)
20:43:45  * Raltjoined
20:57:41  * kristatequit (Ping timeout: 245 seconds)
21:09:26  * TooTallNatequit (Quit: ["Textual IRC Client: www.textualapp.com"])
21:12:41  <ryah>isaacs: c'est la vie
21:12:54  <isaacs>ryah: yep.
21:12:59  <isaacs>it's almost done.
21:13:19  <isaacs>the hacks are pretty disgusting, but at least theyr'e relatively well factored, and will be easy to remove in 50 years when we can actually remove them
21:13:23  <isaacs>:)
21:13:53  * Raltquit (Remote host closed the connection)
21:14:26  * Raltjoined
21:19:22  * Raltquit (Ping timeout: 260 seconds)
21:24:24  * Raltjoined
21:29:43  <ryah>man 8.8.8.8 isn't timing out nodejs.org
21:35:16  <ryah>oh well
21:35:29  <ryah>looks like there are many people on the site so i guess it's just me
21:40:25  * Ariajoined
21:43:47  * Raltquit (Remote host closed the connection)
21:44:22  * Raltjoined
21:44:59  * Ariaquit (Ping timeout: 250 seconds)
21:48:46  * Raltquit (Ping timeout: 246 seconds)
21:49:52  * rendarquit
22:09:46  <bnoordhuis>indutny: ping
22:11:43  * loladirojoined
22:14:16  * Ariajoined
22:31:53  <indutny>bnoordhuis: pong
22:36:35  <indutny>ryah: wfm
22:59:24  <bnoordhuis>indutny: so about tlsnappy
23:04:22  * lohkeyjoined
23:13:34  * ericktjoined
23:19:11  * lohkeyquit (Quit: lohkey)
23:42:24  * Ariaquit (Remote host closed the connection)