00:33:00  * tilgoviquit (Ping timeout: 245 seconds)
00:33:11  * tilgovijoined
00:34:45  <dools>tanepiper: use xpath!
00:34:55  <dools>slash the dom
00:41:38  * ryan_stevensquit (Quit: Leaving.)
00:44:51  * wiwilliaquit (Ping timeout: 260 seconds)
00:58:45  <rowbit>Hourly usage stats: []
01:08:08  * wiwilliajoined
01:10:26  * devaholicjoined
01:13:58  * st_lukejoined
01:16:07  * st_lukequit (Remote host closed the connection)
01:22:51  <SubStack>dominictarr: sending some pull reqs to sockjs, things are bugging me about it that are pretty fixable
01:24:08  <chapel>like what?
01:24:16  <SubStack>turning off logging
01:24:22  <chapel>ah
01:24:39  <SubStack>one sec and I will possibly say another thing
01:25:11  <chapel>lol
01:30:24  <SubStack>oh sweet the stream already has readable and writable set!
01:41:09  * ryan_stevensjoined
01:42:44  <jesusabdullah>SubStack: I like it when modules emit log events and you can just catch them and do whatever the fuck
01:42:55  <SubStack>jesusabdullah: that doesn't scale at all
01:43:04  <SubStack>if you have a complicated app and you're trying to debug things
01:43:12  <SubStack>that AREN'T related to the spammy module
01:43:16  <SubStack>it's so much noise
01:43:23  <jesusabdullah>So you don't listen for the logging events
01:43:26  <SubStack>every module that does that needs to die in a fire
01:43:36  <SubStack>jesusabdullah: no no no I'm talking about things that spam stdout/stderr
01:43:40  <jesusabdullah>I mean thing.on('log')
01:43:40  <SubStack>by default
01:43:42  <jesusabdullah>Yeah I know
01:43:48  <SubStack>oh yeah .on('log') is great
01:43:50  <jesusabdullah>I'm saying I prefer thing.emit('log', 'msg')
01:43:51  <SubStack>I've no beefs with that
01:44:17  <SubStack>socket.io and socksjs both do this ;_;
01:44:47  <jesusabdullah>-_-
01:45:14  <SubStack>hey whoa
01:45:42  <SubStack>ah sockjs is still written in coffee but at least they had the good sense to .npmignore the src/
01:49:59  * wiwilliaquit (Ping timeout: 245 seconds)
01:54:19  <jesusabdullah>At least there's that
01:54:25  <jesusabdullah>I can accept coffee code if it's done smartly
01:54:31  <jesusabdullah>and the socksjs guys seemed to do, well
01:54:31  <jesusabdullah>okay
01:54:32  <jesusabdullah>at least
01:58:45  <rowbit>Hourly usage stats: []
01:58:48  * darshanshankarjoined
02:02:03  <jesusabdullah>yo darshanshankar
02:02:28  <darshanshankar>yo yo
02:02:59  <SubStack>darshanshankar: dnode's getting a .pipe() facelift
02:03:02  <SubStack>also weakrefs!
02:03:14  <SubStack>and I ripped out socket.io because it was making me ;_;
02:03:44  <SubStack>also: fuck EPIPE
02:03:53  <SubStack>I hate that error message so much.
02:06:25  <jesusabdullah>well stop epiping then
02:06:39  <darshanshankar>hehehe
02:06:56  <darshanshankar>i have to say, I'm a fan of the changes socket.io has made recently
02:07:07  <darshanshankar>there was a time last year where it was unbearable
02:07:08  <jesusabdullah>such as
02:07:13  * darshanshankarquit (Quit: darshanshankar)
02:07:19  <jesusabdullah>whaaaaat
02:07:26  <jesusabdullah>dagnabit darshan
02:07:31  * darshanshankarjoined
02:08:09  <jesusabdullah>Ope too late
02:08:16  <jesusabdullah>anyways: What's new with socket.io?
02:08:33  <darshanshankar>lol my bad. dc'd. one sec.
02:12:28  <darshanshankar>ill have to check the socket.io gh
02:12:39  <darshanshankar>but i recall checking in on their 0.9 release and feeling pleased
02:16:21  <jesusabdullah>I see
02:16:30  <jesusabdullah>Conceptually, I think I like the goals behind engine.io
02:17:26  <jesusabdullah>but what I really want is something that simply exposes node's streaming api
02:17:34  <jesusabdullah>just a readable/writable stream to the client
02:17:41  <jesusabdullah>and then you should be able to build an abstraction on top of that
02:18:10  <SubStack>engine.io isn't even on npm!
02:19:39  <jesusabdullah>whaaaaat
02:19:42  <jesusabdullah>weak
02:19:46  <jesusabdullah>you should snipe it
02:20:12  <jesusabdullah>just put the current master on npm, easiest thing
02:20:26  <jesusabdullah>also then you look like a nice person even though you're really just trolling
02:20:38  <jesusabdullah>so when they *do* want to publish you play the avoidance game
02:21:36  <SubStack>http://browserling.com:9999/
02:21:44  <SubStack>working dnode over sockjs
02:22:49  <jesusabdullah>browrstleng!
02:22:59  <jesusabdullah>I approve
02:24:32  <SubStack>the next order of business
02:24:45  <darshanshankar>we've been using sockjs with bridge
02:24:50  <SubStack>is submitting a pull request to sockjs-client for browserify support
02:24:53  <darshanshankar>tis good in langs != node
02:25:08  <SubStack>sockjs is nice because it only tries to make streams work
02:25:12  <SubStack>not a bunch of other things
02:25:12  <darshanshankar>also engine.io
02:25:14  <darshanshankar>what is?
02:25:34  <darshanshankar>https://github.com/LearnBoost/engine.io ?
02:26:01  <SubStack>engine.io is supposedly a slimmed down version of socket.io but it's not on npm or anything yet
02:26:40  * ryan_stevensquit (Quit: Leaving.)
02:26:41  <darshanshankar>interesting. i haven't seen this before
02:28:02  <rowbit>SubStack, pkrumins: Encoders down:
02:32:33  * ryan_stevensjoined
02:37:26  * tilgoviquit (Ping timeout: 260 seconds)
02:53:40  * darshanshankarquit (Quit: darshanshankar)
02:58:45  <rowbit>Hourly usage stats: []
03:03:11  <SubStack>pow https://github.com/sockjs/sockjs-client/pull/76
03:20:20  <SubStack>https://github.com/sockjs/sockjs-node/pull/77
03:30:35  <SubStack>https://gist.github.com/2963645
03:57:19  * tilgovijoined
03:58:45  <rowbit>Hourly usage stats: []
04:00:33  * devaholicquit (Read error: Operation timed out)
04:13:49  <chapel>SubStack: actually sockjs makes sense to use with dnode
04:14:13  <chapel>since socket.io transitioned to a more rpc style api, and added a bunch of stuff, it was just too heavy
04:14:16  <chapel>and painful to use
04:14:38  <chapel>sockjs on the other hand is more simple and something that would fit well under dnode
04:14:39  <SubStack>feature creepin
04:15:21  <chapel>feature creep is just a new module to you :)
04:17:33  <SubStack>yes
04:17:35  <SubStack>it's the only way
04:17:55  <SubStack>keep the creepers at bay
04:18:01  <SubStack>build torches
04:23:35  <jesusabdullah>and stone walls
04:23:40  <jesusabdullah>because soil ones are too soft
04:26:56  * ryan_stevensquit (Quit: Leaving.)
04:31:31  * wiwilliajoined
04:49:53  * shykeschanged nick to zz_shykes
04:50:24  * saijanai_quit (Quit: saijanai_)
04:58:45  <rowbit>Hourly usage stats: []
05:22:21  * wiwilliaquit (Ping timeout: 265 seconds)
05:38:23  <SubStack> 71 files changed, 822 insertions(+), 1801 deletions(-)
05:38:47  <dominictarr>SubStack, just realized you could use weakrefs to pull off hot code updates.
05:39:14  <SubStack>3 2 1
05:39:15  <dominictarr>and know that it worked cleanly.
05:39:20  <SubStack>http://github.com/substack/dnode
05:39:23  <SubStack>v1.0.0
05:39:55  <SubStack>waiting for travis to report back before I npm publish
05:40:11  <dominictarr>sweet
05:40:19  <SubStack>especially: https://github.com/substack/dnode#using-socksjs-in-the-browser
05:40:23  <dominictarr>reading readme
05:41:13  <SubStack>it passes!
05:41:20  <SubStack>published
05:46:14  <SubStack>dominictarr: https://github.com/dominictarr/rpc-stream/commit/e463fd678ff1108d25ecb96bbbe543dc4dcffbe1
05:47:17  <dominictarr>I'll fix that shortly.
05:48:43  <SubStack>I really hope my sockjs patches land
05:48:50  <SubStack>they're pretty small and they make everything awesome
05:49:21  <guybrush>waaah 1.0.0
05:49:40  <SubStack>tanepiper: ^^^
05:50:52  <dominictarr>SubStack, did you make the client side into a node stream?
05:51:01  <SubStack>yes
05:51:23  <SubStack>https://github.com/substack/dnode/blob/master/example/sockjs/client.js
05:51:35  <SubStack>https://github.com/substack/dnode/blob/master/example/sockjs/client.js#L15
05:51:39  <dominictarr>it's quite arkward how they have a different api on the server and client.
05:51:48  <SubStack>oh you mean in sockjs
05:51:55  <dominictarr>yeah
05:52:04  <SubStack>yeah the browserified version of sockjs is a node stream
05:52:19  <SubStack>I put it there so when you do require('sockjs') it will work browser-side
05:52:54  <SubStack>that's game-over for websocket libs
05:53:01  <SubStack>sockjs wins
05:53:04  <guybrush>lol
05:53:41  <SubStack>they just need to `npm publish` the new stuff
05:57:20  <dominictarr>but i just see onmessage = fun...
05:57:32  <dominictarr>that isn't gonna work with pipe. am I missing something?
05:57:45  <SubStack>dominictarr: are you looking at the right branch?
05:57:57  <SubStack>https://github.com/sockjs/sockjs-node/pull/77
05:58:06  <SubStack>https://github.com/substack/sockjs-node/commit/3b017913b7054b421c6722e3677bbeb1cba28cd8
05:58:45  <rowbit>Hourly usage stats: []
06:01:40  <dominictarr>I found it.
06:02:08  <guybrush>dnode now installs much faster without socketio :DD
06:02:08  <dominictarr>with this I can refactor browser-stream into a stream multiplexer.
06:02:36  <dominictarr>it will just send multiple object streams down one byte stream.
06:02:54  <dominictarr>so, will work over tcp or stdio or whatever
06:03:52  <SubStack>YES
06:04:01  <chapel>SubStack is excited!
06:04:08  <SubStack>dominictarr: why just for browsers though?
06:04:15  <SubStack>I want a multiplexer server-side too
06:04:25  <SubStack>mux/demux
06:06:19  <guybrush>so ready events are gone?
06:07:34  <SubStack>they're still around but deprecated
06:07:38  <SubStack>just listen on 'remote'
06:07:40  <guybrush>kk
06:07:47  <guybrush>really like all the changes
06:07:53  <SubStack>I'll drop those in the next minor point release
06:15:32  <guybrush>reconnect is gone too?
06:16:32  <dominictarr>hmm, flow control will be more complicated with mux-demux
06:17:02  <dominictarr>probably, will be wanting some sort of control point stream, and to apply control theory
06:17:09  <dominictarr>with feedback, etc.
06:17:13  <SubStack>wouldn't you just need to stuff in the channel id in with the message payload?
06:17:27  <dominictarr>pause/resume is too simplistic.
06:17:29  <SubStack>and a framing protocol
06:18:15  <SubStack>you could implement qos too
06:18:31  <dominictarr>yes, you probably want to do that, but need a way to control the flow of the inner streams, and the carrier stream.
06:18:42  <SubStack>oh right
06:19:14  <dominictarr>also, since transmitting the pause, resume calls are async, then by the time they arrive they are old.
06:19:55  <dominictarr>if someone is transmitting too much, and you need to pause, it will be harder for your pause message to arrive.
06:20:09  <dominictarr>which will make for an unstable system.
06:20:52  <dominictarr>probably will want something like in tcp, where the sender slows exponentially,
06:21:15  <dominictarr>on pause, and speeds up linearly on resume
06:22:04  <dominictarr>so it searches for the correct throughput safely despite latency.
06:22:50  <chapel>implement tcp over websocket (which is like tcp) over http over tcp
06:23:11  <dominictarr>chapel, you got it.
06:23:19  <chapel>:)
06:26:15  <dominictarr>hmm, it would be great to have a better sandbox than a browser to run applications on.
06:26:43  <dominictarr>then you could really flex your mussels on the (so-called) "client"
06:27:17  <dominictarr>just have a highly configurable sandbox...
06:27:38  <dominictarr>you need this for a PaaS aswell.
06:27:58  <dominictarr>this would just be putting the Platform on the Client
06:58:45  <rowbit>Hourly usage stats: []
07:20:32  <rowbit>SubStack, pkrumins: Encoders down:
07:22:32  <rowbit>SubStack, pkrumins: Encoders down:
07:24:32  <rowbit>SubStack, pkrumins: Encoders down:
07:41:02  <rowbit>SubStack, pkrumins: Encoders down:
07:41:42  <guybrush>SubStack: how can i do reconnect? https://gist.github.com/2964418
07:41:57  <guybrush>piping the new stream into the same dnode-client does not work
07:42:12  <guybrush>i would have to make a new dnode-client isnt it?
07:42:32  <rowbit>SubStack, pkrumins: Encoders down:
07:46:14  <guybrush>oh i did it wrong
07:49:32  <rowbit>SubStack, pkrumins: Encoders down:
07:55:27  <tanepiper>guybrush: share your gist of what you're doing :) I might re-write my stuff for my talk and just use the new stuff
07:56:15  <guybrush>im struggling somehow, have to read the code
07:56:25  <guybrush>its very little code now, awesome :D
07:56:32  <rowbit>SubStack, pkrumins: Encoders down:
07:58:45  <rowbit>Hourly usage stats: []
07:58:51  <guybrush>well i got it working, but i dont like how i did it
08:00:04  <tanepiper>i need to work out how i'll do it with express
08:00:06  <guybrush>https://gist.github.com/2964418 that way it works
08:00:17  <tanepiper>I suppose i'd have to pipe it through a res object inside a route?
08:00:23  <guybrush>i mean this is only reconnect-stuff i need
08:01:33  <guybrush>it thought i can just pipe the new stream into the already initialized dnode-object
08:01:51  <guybrush>but somehow im wrong
08:02:35  <guybrush>like connecting to a server and pipe the stream into dnode, after the connection drops and i reconnect - just pipe the new stream into the old dnode-object
08:03:15  <guybrush>will let it go for now and do real work haha
08:04:04  <guybrush>socketio depends on a really old redis which didnt shim the require('sys') thing properly and now it fucks everything in node07x :D
08:04:48  <guybrush>maybe i just drop socketio and switch to sockjs since its really much thinner and i think with a sticky-balancer it should also be ok when a project needs to scale
08:06:56  <tanepiper>fuu, new dnode breaks dnode-session :/ Going to have to re-write it myself then
08:10:38  <guybrush>all the node stuff is such a fast moving target :D
08:11:15  <guybrush>you are on the bleeding edge all the time
08:11:30  <guybrush>though with n its really easy to keep old stuff running :)
08:23:03  * dominictarrquit (Ping timeout: 246 seconds)
08:27:48  <tanepiper>hmm, so in a 'middleware' `this` isn't dnode :/ i.e. d.on('local', require('dnode-session')({store: instance.sessions}));
08:28:08  <tanepiper>suppose i could just pass d as a parameter
08:29:34  <tanepiper>duh of course it isn't
08:46:23  * devaholicjoined
08:54:58  <guybrush>http://opalang.org/ haha opa means grandfather in german :)
08:55:15  <tanepiper>gahh, /dnode.js is not available now via express
08:57:38  <tanepiper>well that's why, but also still breaks when I try d.listen(instance.express)
08:58:45  <rowbit>Hourly usage stats: []
09:03:54  <SubStack>tanepiper: yes, that api went away
09:04:01  <SubStack>you can generate a bundle with browserify
09:04:41  <tanepiper>yea, looking through that - so i just have to ignore express now and use purely as my static app server
09:06:09  <SubStack>you just set up a stream somehow
09:06:52  <tanepiper>within express that would mean doing it inside a path (e.g. d.pipe(res).pipe(d) ) i suppose ?
09:07:18  <tanepiper>eh, no just get sockjs to listen on it...duh
09:07:26  * tanepiperneeds moar coffee
09:07:46  <SubStack>that's the easy way
09:07:56  <SubStack>it's also possible with socketio and browser-stream
09:08:00  <SubStack>but harder
09:08:27  <tanepiper>yea, i want easy :D
09:13:57  * dominictarrjoined
09:15:50  <tanepiper>dominictarr: when will those sockjs changes get merged in that SubStack submitted?
09:21:21  * dominictarrquit (Ping timeout: 255 seconds)
09:22:07  <tanepiper>hmff: https://gist.github.com/bb53fffee5a19e0a450b
09:23:37  <tanepiper>i take it this is why the patch is needed?
09:26:45  * devaholicquit (Ping timeout: 245 seconds)
09:35:33  <tanepiper>right i need to get on with work so i'll come back to this later
09:58:45  <rowbit>Hourly usage stats: []
10:04:53  <SubStack>tanepiper: use these: https://github.com/substack/dnode/blob/master/example/sockjs/package.json#L5-L6
10:05:39  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
10:05:39  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
10:06:04  <SubStack>rawk
10:06:09  * tilgoviquit (Read error: Connection reset by peer)
10:34:02  <rowbit>SubStack, pkrumins: Encoders down:,,,,,,,,,,
10:34:44  * dominictarrjoined
10:37:47  <tanepiper>SubStack: cool, will do
10:58:45  <rowbit>Hourly usage stats: []
11:34:16  <SubStack>oh geez, stream haters https://github.com/sockjs/sockjs-node/pull/77 and https://github.com/sockjs/sockjs-node/issues/67
11:34:20  <SubStack>dominictarr: ^^^
11:42:28  * dominictarrquit (Ping timeout: 272 seconds)
11:53:58  * dominictarrjoined
11:58:45  <rowbit>Hourly usage stats: []
12:27:33  <tanepiper>haters gonna hate
12:29:31  <SubStack>streamers gonna stream
12:32:08  <tanepiper>hmm, should i not be able to do: npm install git://github.com/substack/sockjs-node.git#browserify-npm ?
12:33:15  <SubStack>I'm not sure
12:33:57  <SubStack>well the npm install help page says that should work
12:34:42  <tanepiper>mehh, doesn't - i'll just clone and ping isaacs later
12:44:16  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
12:44:16  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
12:46:30  <SubStack>sweeet
12:58:45  <rowbit>Hourly usage stats: []
13:03:26  <guybrush>tanepiper: i think git+ssh://[email protected]/substack/sockjs-node#browserify-npm works
13:03:52  <guybrush>but ye git:// should work too
13:04:32  <guybrush>note that there were some changes lately (like between 1.1.25 and 1.1.30)
13:04:57  <guybrush>basically now npm eats everything (scp-style and normal git-url style)
13:05:39  <tanepiper>bahh - dnode-session won't work now :/
13:05:57  <tanepiper>it uses conn.stream.socketio.manager.handshaken[id]
13:10:32  <tanepiper>basically socketio binds the current request in some way, so you can access req.session - not sure how i'd do this with sockjs
13:14:37  <tanepiper>dominictarr: do you know any way i could get the http request that sockjs is bound to?
13:42:42  * ikjoined
13:58:45  <rowbit>Hourly usage stats: []
14:06:45  <tanepiper>hrmm got a weird one SubStack - on my server side, my .on('remote') never seems to get fired
14:07:25  <tanepiper>i've been moving code about so the sockjs/dnode stuff is only instanced on one route
14:07:40  <tanepiper>that way i can access the req object with the session data for oauth
14:12:10  <tanepiper>local is getting fired though, and no error :/
14:12:39  * dominictarrquit (Read error: Connection reset by peer)
14:13:08  <tanepiper>https://gist.github.com/f5072d6086635c6003b7
14:23:01  * xaqjoined
14:32:34  <rowbit>SubStack, pkrumins: Encoders down:
14:33:48  * wiwilliajoined
14:53:34  <tanepiper>nope, nothing i do can get on remote to fire on the server side :/ no error or fails either, and local works fine - i can call my function from the browser end
14:56:40  <tanepiper>(but from what i have seen, man sockjs is FAAAAASSSSTTTT!)
14:56:56  <tanepiper>practically 0 delay in calling my simple function and getting a return
14:58:45  <rowbit>Hourly usage stats: []
15:00:44  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
15:00:45  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
15:01:07  <tanepiper>infact, first value is after the function is called, second is when i started on teh client side, third is the server side time in the cb:
15:01:15  <tanepiper>1340290791306 [1340290791300, 1340290791302]
15:02:14  <tanepiper>so on my local machine, 6ms :D
15:11:59  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
15:11:59  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
15:12:34  <tanepiper>oh nice!
15:14:28  <isaacs>maxogden, dominictarr, substack, mikeal: Should .pipe() call .resume() right away?
15:14:31  <isaacs>https://github.com/joyent/node/issues/3484
15:21:28  <tanepiper>isaacs: npm install git+ssh://[email protected]/substack/sockjs-node#browserify-npm
15:21:30  <tanepiper>zsh: no matches found: git+ssh://[email protected]/substack/sockjs-node#browserify-npm
15:22:43  <tanepiper>any idea why git npm installs like this might be broken?
15:23:20  <isaacs>tanepiper: npm -v?
15:23:31  <isaacs>Better .pipe()/.resume() issue: https://github.com/joyent/node/issues/3503
15:23:41  <isaacs>maxogden, dominictarr, mikeal, SubStack: ^
15:25:24  <isaacs>tanepiper: i'm getting a failure because it wants sockjs-client 0.x, which is not published
15:25:33  <isaacs>tanepiper: only 0.1 versions seem to be up
15:25:38  <isaacs>tanepiper: er, wants 0.0.x
15:25:54  <tanepiper>ahh so can't to branch names?
15:26:04  <tanepiper>(fyi 1.1.21)
15:27:32  <rowbit>SubStack, pkrumins: Developers waiting in the queue for ie9 (Queue length: 1 on 1 servers. Total servers: 5)
15:28:42  <isaacs>tanepiper: you should upgrade, there've been some improvements
15:29:01  <isaacs>tanepiper: oh! haha. # is a comment on the shell :)
15:30:52  <tanepiper>ahh yea, making it a string does do something, although it complains about versions again
15:31:46  <tanepiper>got to install client first, then server
15:31:46  <isaacs>tanepiper: yep.
15:31:48  <tanepiper>works fine
15:31:52  <isaacs>tanepiper: kewl :)
15:32:31  <tanepiper>yea, need to write a test case for this dnode stuff, cos i can't get the new on.('remote' to work in my app :/
15:33:40  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
15:33:40  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
15:42:01  <ik>pkrumins: hi hello
15:42:30  <ik>pkrumins: gonna need you to do a thing for all turtle-kind
15:43:12  <ik>pkrumins: /msg chanserv access #stackvm add CAPSLOCKBOT +O
15:45:09  <tanepiper>hmm yea SubStack i can't get teh stream stuff to work at all in these test cases now :/
15:46:37  <tanepiper>https://github.com/tanepiper/dnode-stream-testcase
15:56:46  <tanepiper>i tried your example SubStack - it did work, but still no on remote on teh server side :/
15:58:46  <rowbit>Hourly usage stats: []
16:04:53  * devaholicjoined
16:07:35  <rowbit>SubStack, pkrumins: Encoders down:
16:10:11  * xaqquit (Read error: Connection reset by peer)
16:10:41  * xaqjoined
16:20:36  <tanepiper>twitter down for you guys?
16:26:43  * tilgovijoined
16:28:02  <guybrush>tanepiper: yes
16:32:07  <SubStack>tanepiper: is your remote listener on the same tick?
16:35:28  <tanepiper>you mean, i should define it in the sock.on('connection ?
16:35:41  <tanepiper>i did it with your example code as well, didn't output the remote either
16:36:02  * dominictarrjoined
16:36:23  <tanepiper>SubStack: https://gist.github.com/52f10c705c6477e86f69
16:36:46  <tanepiper>that;s your server example, doesn;t output the remote
16:37:08  <tanepiper>i also tried d = dnode({...}).on('remote') as well
16:38:18  <guybrush>tanepiper: shouldnt it be stream.pipe(d).pipe(stream) ?
16:38:22  <guybrush>im not sure though :D
16:39:56  <tanepiper>guybrush: don't think it matters actually
16:40:00  <guybrush>mhhh actually stream.pipe(d).pipe(stream) and d.pipe(stream).pipe(d) are equivalent?
16:40:18  <tanepiper>yea, works just as fine
16:41:10  <tanepiper>the dnode thing is bugging me though because it works perfectly fine on the client side, but on the server side nup :/ and my app relies on sending data to client side functions since it's streaming data
16:41:41  <tanepiper>and i'm demoing it tuesday in my talk :/ I might just have to stick with the old dnode for now
16:42:14  <guybrush>the new one is way cooler! its streams man! haha
16:42:31  <tanepiper>yea, i know :D
16:43:04  * ryan_stevensjoined
16:44:29  <tanepiper>at least it's got me digging through the dnode source code to see if i can find why
16:45:00  <guybrush>good, then i can ask you when i am stuck :D
16:46:06  <guybrush>AH! FUTURAMA HAS STARTED AGAIN
16:47:31  <guybrush>funny how twitter is dead and i can still read it via google-reader
16:50:29  <tanepiper>better not die when i do my demo LD
16:50:35  <tanepiper>it's a streaming twitter app
16:50:40  <guybrush>nice
16:51:34  <tanepiper>ahh, i had a bad thought! luckly i did commit my code last night before i started messing round with the new dnode
16:52:57  <tanepiper>shitting myself about it too - look who i'm speaking with http://scotlandjs.com/speakers.html
16:53:09  <tanepiper>Jim Weirich!
16:53:22  <guybrush>lol that reminds me of the cat-pic you tweeted some time ago :D "code refactoring"
16:53:25  <tanepiper>http://scotlandjs.com/schedule.html
16:54:12  <guybrush>if i had some money i would go there and watch you!
16:55:18  <tanepiper>and since it's tuesday and dnode is changing (for the better) it reminds me of an IT Crowd quote:
16:55:20  <tanepiper>"Jiminy! Jones! Look, the nature of the thing that is happening has changed slightly, rendering it yet more interesting! "
16:58:45  <rowbit>Hourly usage stats: []
17:01:27  <tanepiper>it's cool thought that i'll get to show off dnode to over 100 new people though LD
17:01:41  <tanepiper>and i get to use it in my next 3 apps (two are mine, one is a client)
17:02:02  <tanepiper>new stream stuff shall make my irc client awesome :D
17:11:02  <rowbit>SubStack, pkrumins: Encoders down:
17:22:01  <dominictarr>tanepiper, what sort of apps do you build?
17:26:36  * nrfjoined
17:30:11  * devaholicquit (Quit: Leaving)
17:58:45  <rowbit>Hourly usage stats: []
18:04:02  * tilgoviquit (Remote host closed the connection)
18:13:03  * tilgovijoined
18:13:59  <guybrush>looool `mocha -r nyan` is just hilarious :D
18:21:51  * dominictarrquit (Remote host closed the connection)
18:38:08  * ryan_stevensquit (Quit: Leaving.)
18:46:55  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
18:46:56  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
18:52:27  * ryan_stevensjoined
18:58:45  <rowbit>Hourly usage stats: []
19:31:48  * _sorensenjoined
19:40:30  * mikealjoined
19:53:01  * mikealquit (Quit: Leaving.)
19:58:45  <rowbit>Hourly usage stats: []
19:58:45  <rowbit>Daily usage stats: []
20:13:32  <rowbit>SubStack, pkrumins: Encoders down:
20:14:19  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
20:14:19  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
20:18:33  <rowbit>SubStack, pkrumins: Developers waiting in the queue for ie9 (Queue length: 1 on 1 servers. Total servers: 5)
20:24:05  <rowbit>SubStack, pkrumins: Developers waiting in the queue for ie9 (Queue length: 1 on 1 servers. Total servers: 5)
20:25:32  <rowbit>SubStack, pkrumins: Encoders down:
20:37:05  <rowbit>SubStack, pkrumins: Encoders down:
20:58:46  <rowbit>Hourly usage stats: []
21:05:05  <rowbit>SubStack, pkrumins: Encoders down:
21:12:43  * mikealjoined
21:16:34  <rowbit>SubStack, pkrumins: Encoders down:
21:31:51  <jesusabdullah>maxogden: I have need of your couchdb expertise!
21:32:07  <jesusabdullah>maxogden: Ping me when you have a few minutes so I can PICK YOUR BRAIN if you may be so kind ^__^
21:34:11  <rowbit>/!\ ATTENTION: (default-local) [email protected] successfully signed up for developer browserling plan ($20). Cash money! /!\
21:34:12  <rowbit>/!\ ATTENTION: (default-local) paid account successfully upgraded /!\
21:34:40  <jesusabdullah>maxogden: I asked in #couchdb
21:40:52  <chapel>jesusabdullah: whats the question?
21:41:41  <jesusabdullah>chapel: historical versions of couchdb views
21:41:48  <jesusabdullah>chapel: like, "what this view looked like a month ago"
21:41:55  <chapel>oh hmm
21:42:09  <chapel>yeah sorry I can't help there, what do you need it for?
21:42:21  <jesusabdullah>historical user data
21:42:49  <jesusabdullah>I could pull the changes feed and assemble it myself I suppose
21:50:35  * mikealquit (Quit: Leaving.)
21:58:02  <rowbit>SubStack, pkrumins: Encoders down:
21:58:45  <rowbit>Hourly usage stats: []
22:12:32  <rowbit>SubStack, pkrumins: Encoders down:
22:13:32  <rowbit>SubStack, pkrumins: Encoders down:
22:33:16  * zz_shykeschanged nick to shykes
22:35:15  <SubStack>tanepiper: are you building the client bundle with browserify?
22:36:03  <SubStack>also var dnode = require('../../');
22:36:09  <SubStack>make sure you change that to 'dnode' !
22:36:22  <SubStack>unless you're running it from the dnode/example/sockjs directory
22:42:00  <SubStack>wowsy socket.io now works with browserify! https://github.com/LearnBoost/socket.io-client/pull/428#issuecomment-6493084
22:47:54  * wiwilliaquit (Ping timeout: 240 seconds)
22:50:15  * mikealjoined
22:50:47  * st_lukejoined
22:53:53  * shykeschanged nick to zz_shykes
22:58:45  <rowbit>Hourly usage stats: []
23:00:50  * st_lukequit (Quit: Leaving)
23:02:15  * wiwilliajoined
23:12:11  * wiwillia2joined
23:26:20  * xaqquit (Remote host closed the connection)
23:43:10  * wiwillia2quit (Ping timeout: 244 seconds)
23:47:23  * wiwilliaquit (Ping timeout: 248 seconds)
23:48:17  * nrfquit (Ping timeout: 264 seconds)
23:56:21  * ryan_stevensquit (Quit: Leaving.)
23:58:42  * mikealquit (Quit: Leaving.)
23:58:45  <rowbit>Hourly usage stats: []