00:00:00  * ircretaryquit (Remote host closed the connection)
00:00:08  * ircretaryjoined
00:00:28  * mirkokjoined
00:07:51  * jibayquit (Quit: Leaving)
00:09:47  * AvianFluquit (Ping timeout: 260 seconds)
00:11:50  * AvianFlujoined
00:15:49  <substack>youtube is trying to get me to watch "The illuminati Exposed By Muammar Gaddafi"
00:16:17  <substack>silly youtube, why do you recommend zany RT conspiracy theories at me
00:17:40  <Raynos>rvagg_: no it cant
00:17:43  <Raynos>thats what npm currently does
00:17:49  <Raynos>loads all of npm into memory
00:18:12  <Raynos>defunctzombie: setting up a private npm repo is on the todo list
00:18:53  <Raynos>rvagg_: what you need to do is re-index npm by search words then just do a range query on your input
00:19:21  <rvagg_>Raynos: the thing that slows npm search down is the initial resync
00:19:32  <Raynos>i doubt it
00:19:40  <Raynos>half the time is spend just doing a map reduce in memory in JS
00:21:09  * AvianFluquit (Read error: Connection reset by peer)
00:21:23  * AvianFlujoined
00:21:52  <Raynos>rvagg_: you make a good point though you can do an increment streaming search
00:21:56  <Raynos>where you get some results earlier
00:25:24  <rvagg_>Raynos: try this, depending on where your npm is, edit /usr/local/lib/node_modules/npm/node_modules/npm-registry-client/lib/get.js
00:25:50  <rvagg_>at about line 58, just above the requestAll_ call
00:25:59  <rvagg_>put this: return cb(er, data)
00:26:09  * Tim``quit (Quit: Page closed)
00:26:11  <rvagg_>then run an npm search and see the difference without the registry sync
00:27:27  <rvagg_>of course it makes a huge difference for me here on the other side of the world
00:31:50  * st_lukequit (Remote host closed the connection)
00:44:41  <substack>might be on the verge of a breakthrough getting mutual authentication to work over https
00:44:54  <substack>for git
00:44:59  <substack>which I can find exactly 0 information online about
00:45:12  <substack>0 libraries of congress worth of data
00:54:40  <Raynos>substack: idea!
00:54:50  <Raynos>You know how we have nodeup for node news
00:55:23  <Raynos>and paul irish does things like the breakpoint ( https://developers.google.com/live/shows/8954018/ )
00:55:37  <Raynos>we should set up something similar for browserify and browser-based npm modules
00:55:48  <Raynos>screencasts, podcasts, blog articles, etc.
00:58:44  * harrowquit (Read error: Operation timed out)
01:02:15  <Raynos>Mainly because there is no-one evangelizing the npm+browserify = awesome front end dev thing
01:03:06  * harrowjoined
01:05:41  <ralphtheninja>good idea raynos
01:06:01  <Raynos>if anyone is came I would love to do an audio or video session
01:06:12  <Raynos>thats basically an introduction to browserify+npm
01:07:16  <defunctzombie>closure compiler advanced optimizations mode is amazing
01:08:37  * dominictarrjoined
01:22:14  * dguttmanjoined
01:22:41  * yorickquit (Remote host closed the connection)
01:23:04  <defunctzombie>my life was darkness before testling... but now I can tread cautiously into the light
01:23:07  * mirkokquit (Quit: mirkok)
01:24:25  <substack>defunctzombie: tell your friends!
01:24:32  <defunctzombie>I am :)
01:24:43  <defunctzombie>trying to convince a friend I have at a company to use it
01:24:49  <substack>oh sweet
01:24:53  <defunctzombie>I think they use selenium currently
01:24:58  * ralphtheninjaquit (Ping timeout: 265 seconds)
01:25:04  <defunctzombie>but that is all manual and slow
01:25:22  <substack>using selenium doesn't preclude you from using testling-ci
01:25:38  <defunctzombie>yep
01:46:25  <defunctzombie>should .height() return the height of the element including padding?
01:46:43  <defunctzombie>why are there so many fucking element heights hahaha
01:49:27  * dguttmanquit (Quit: dguttman)
01:51:58  <substack>defunctzombie: sounds out of scope
01:52:17  <substack>you should write a library that just handles positioning calculators
01:52:20  <substack>*calculations
01:52:22  <defunctzombie>https://developer.mozilla.org/en-US/docs/Determining_the_dimensions_of_elements
01:52:26  <substack>and then if you want, dom can depend on that lib
01:52:34  <substack>then everybody wins yay!
01:52:43  <defunctzombie>the calculations are available
01:53:02  <defunctzombie>just the api is all over the place haha
01:53:11  <defunctzombie>jquery has height/outerheight/innerheight/scrollheight
01:53:18  <substack>jquery has a sprawling api
01:53:29  <substack>it's from before we had modules
01:53:38  <defunctzombie>what do you think of when you think of an element's height?
01:53:54  <defunctzombie>I would say it is the space it takes up on the page
01:54:01  <substack>just be explicit
01:54:25  <substack>if height means multiple things make multiple ways of getting that value
01:54:32  <defunctzombie>I agree
01:54:58  <defunctzombie>I was asking about the basic "height"
01:54:59  <defunctzombie>reading about what jquery made it mean
01:54:59  <defunctzombie>I am not so sure
01:55:30  <defunctzombie>if you go with matching css
01:55:40  <defunctzombie>then it would be the height inside the border (I think)
01:56:16  <substack>git has only a handful of curl opts ;_;
01:57:48  <defunctzombie>?
02:00:31  <substack>I want to tell git to set CURLOPT_SSLKEY
02:00:39  <substack>so I can do a mutual key exchange
02:00:42  <substack>ssh-style
02:00:53  <substack>cert-based auth is so painful
02:07:25  <substack>whoa!!! https://en.wikipedia.org/wiki/HTTPsec
02:09:34  <substack>haha multi-line headers
02:09:45  <dominictarr>https://npmjs.org/package/http-signature
02:10:28  <dominictarr>^ similar, but using key pairs
02:10:54  <substack>but not good enough
02:11:01  <substack>curl needs to natively understand it
02:11:15  <substack>so I can use this to authenticate git over http
02:11:20  <dominictarr>yes
02:11:37  <substack>git doesn't let me set CURLOPT_SSLKEY so I can't use http-signature
02:12:06  <dominictarr>so put a pr into libcurl... and then wait for everyone to install the new version...
02:12:07  <substack>deep into mad science territory
02:12:19  <substack>not ever going to do that
02:14:36  <substack>that's for people to bikeshed on mailing lists about
02:16:54  <substack>blarg it seems that curl doesn't support httpsec
02:19:50  <substack>I could just use secure-peer for this
02:24:51  <substack>oh that won't work since git won't let that work
02:27:52  <hij1nx>git-stream
02:28:06  <hij1nx>git is a bitch, and has too many deps
02:28:33  <hij1nx>using git is like using 25 different programs
02:31:31  <hij1nx>substack: you are hitting the exact same stuff that i hit when i was doing http://github.com/hij1nx/d
02:31:47  <hij1nx>substack: which is why i started git-stream
02:32:39  <hij1nx>wrapping git is like trying to put a collar on cthulhu
02:33:42  <substack>I'll give git-stream a spin!
02:33:46  <substack>good plan
02:34:19  <hij1nx>substack: its unstable, not finished
02:34:33  <hij1nx>substack: its very close though
02:34:46  <substack>npm ERR! 404 'git-stream' is not in the npm registry.
02:34:59  <hij1nx>substack: there's no stable branch yet
02:35:06  <hij1nx>i should publish though
02:35:09  <substack>yes
02:35:34  <substack>publish early, often, etc
02:35:55  <hij1nx>done
02:36:44  <substack>sweet!
02:36:50  <hij1nx>substack: but I warn you, its just been me and tmpvar hacking on it and so far we're not even finished with the push workflow; but like i said very little left to do
02:38:07  <hij1nx>substack: i would love to be able to stream git repos around and have arbitrary end points check them out and even stream the files to various places as they come out of the repo.
02:40:05  <substack>/home/substack/projects/legit/node_modules/git-stream/lib/remote.js:24 if (!opts.path || !) {
02:40:44  * lyaunzbequit (Read error: Connection reset by peer)
02:40:47  * lyaunzbe_joined
02:43:29  <hij1nx>substack: yeah, like i said, very unstable ;)
02:56:01  <hij1nx>dominictarr: https://github.com/hij1nx/git-stream/blob/master/docs/pack-protocol.md
02:57:41  * dguttmanjoined
02:57:43  * dguttmanquit (Client Quit)
03:05:28  * jez0990_quit (Ping timeout: 250 seconds)
03:34:02  <hij1nx>alright... shit. time for another git-stream sprint; this is a solvable problem.
05:00:04  <substack>whoa richard attenborough, the actor who played the old professor in jurassic park, is the elder brother of david attenborough
05:26:16  * mikealquit (Quit: Leaving.)
05:26:36  * mikealjoined
05:41:36  * AvianFluquit
06:15:45  <hij1nx>creating a git packfile is not trivial...
06:23:36  * mikealquit (Quit: Leaving.)
06:27:07  <substack>pow https://github.com/substack/subdir
06:27:14  <substack>got tired of writing that function over and over
06:27:20  <substack>and I put a testling badge on it why not
06:28:09  * shuaibquit (Quit: Textual IRC Client: http://www.textualapp.com/)
06:51:12  * stlsaintjoined
06:51:12  * stlsaintquit (Changing host)
06:51:12  * stlsaintjoined
07:03:29  * mikealjoined
07:51:43  * dominictarrquit (Ping timeout: 245 seconds)
08:03:01  * rvagg_quit (Read error: Connection reset by peer)
08:33:33  * rvagg_joined
09:02:15  * jibayjoined
09:02:41  * saijanai_joined
09:02:41  * saijanai_quit (Excess Flood)
09:16:27  <substack>defunctzombie: ignore the noise on http://ci.testling.com/shtylman/dom we're testing chroot stuff
09:16:38  <defunctzombie>substack: kk
09:17:18  <substack>soon you'll be able to run node programs alongside your browser tests
09:17:35  <defunctzombie>\o/
09:17:42  <defunctzombie>that will be great
09:17:57  <defunctzombie>will help in testing ajax libs to go along with this dom lib :)
09:22:50  <defunctzombie>I have also given up on trying to support anything < ie9
09:23:01  <defunctzombie>it is possible.. but holy crap is it annoying
09:39:16  * defunctzombiechanged nick to defunctzombie_zz
09:43:30  * xaqjoined
10:25:16  * ralphtheninjajoined
10:25:21  * mirkokjoined
10:44:16  * mirkokquit (Quit: mirkok)
11:24:03  * xaqquit (Remote host closed the connection)
11:34:12  * rvagg_quit (Ping timeout: 250 seconds)
12:13:27  * yorickjoined
12:23:45  * jez0990_joined
12:26:11  <ralphtheninja>a bit early for some of you guys, but in sweden we celebrate xmas today, so merry hacking xmas to y'all!
12:57:31  * saijanai_joined
12:57:31  * saijanai_quit (Excess Flood)
12:57:54  * saijanai_joined
13:15:16  * jez0990_quit (Ping timeout: 260 seconds)
13:15:35  * jez0990joined
13:15:35  * jez0990quit (Changing host)
13:15:35  * jez0990joined
13:25:19  * shuaibjoined
13:31:57  * jez0990quit (Read error: Operation timed out)
13:33:50  * jez0990joined
13:33:50  * jez0990quit (Changing host)
13:33:50  * jez0990joined
13:46:27  * mirkokjoined
13:58:16  * mirkokquit (Quit: mirkok)
14:09:12  * shuaibquit (Ping timeout: 252 seconds)
14:10:48  * shuaibjoined
14:19:18  * ITproquit (Ping timeout: 264 seconds)
14:20:34  * ITprojoined
14:21:42  <yorick>substack: in the seaport.connect, when you call s.createStream, you probably want to call stream.on('synced', s.emit.bind(s, 'synced')) on the created stream (unless you through() it somewhere, which also happens sometimes :/)
14:22:36  <yorick>substack: then, you can seaport.on('synced'), and on the second emitted sync after a connection is established (currently), it has your data.
14:22:58  <substack>yorick: want to send a pull req for that?
14:23:57  <yorick>substack: it's a bit of a hack, though. scuttlebutt-git has some changes to the sync event that are not yet in npm, too
14:24:47  <yorick>actually, I think they are
14:27:13  <yorick>oh, crdt still depends on ~5.0, while scuttlebutt is on ~5.3
14:28:44  <yorick>substack: I'll send a pull request
14:40:30  <paul_irish_>Raynos: yeah i dont think bower is working out. :/ npm + browserify is probably in a better position
14:44:12  <substack>there are still lots of experiments running right now but yeah npm is my favorite
14:44:30  <substack>paul_irish_: congrats on getting engaged too!
14:45:29  * substackis working on a git-server blog engine for browserify.org right now
14:45:42  <substack>finally putting up a dedicated site for it
14:46:05  <substack>with testling-ci powered search and featured module articles
14:47:28  <yorick>interesting :-)
14:49:43  <paul_irish_>substack: :D thx!!!
14:49:48  <paul_irish_>coolness
14:50:37  <substack>starting to get a lot of repos up in testling-ci
14:51:12  <substack>and we've just about got server-side parts of tests running in a chrooted environment
14:51:38  <substack>so folks can test stuff like xhr libs or ajax apis
14:51:46  <substack>or websocket libs especially
14:52:31  * chapelquit (Ping timeout: 245 seconds)
14:52:48  * sorensenquit (Ping timeout: 260 seconds)
14:53:02  * stlsaintquit (Ping timeout: 255 seconds)
15:11:27  * st_lukejoined
15:12:30  <substack>it works yay!
15:12:35  <substack>git push server blog
15:14:01  <substack>I'll make it pretty tomorrow
15:14:07  <substack>it's mostly just a lib though
15:22:22  <yorick>spawn('git', ['rev-parse', 'HEAD']).stdout.pipe(res) // yay
15:25:23  <pkrumins>paul_irish_: congrats from me too!
15:27:40  <pkrumins>testling is getting ie10 today
15:27:50  <pkrumins>then later this or next week browserling too
15:42:01  <yorick>substack: bouncy does not seem to emit res.on('finish') :/
15:46:27  * AvianFlujoined
15:52:26  <pkrumins>yes there are issues with bouncy
15:53:17  <substack>the new bouncy
15:53:39  <pkrumins>the new bouncy isn't finished is it?
15:55:14  <substack>yes it's been finished for a while
15:55:38  <substack>just published: https://github.com/substack/legit
15:55:41  <substack>git push blog engine
15:55:42  <pkrumins>oh and it works too?
15:55:57  <pkrumins>i thought you were having some issues with websockets
15:56:07  <substack>oh hmm I should test those more yes
15:56:51  <pkrumins>we can swap it out quickly in production see how it works
15:57:03  <pkrumins>if it doesnt work well put the old thing back
15:57:16  <substack>about to go to sleep here
15:57:24  <pkrumins>aight.
15:57:24  <substack>best to do that when we're both awake!
15:57:28  * substackzzz &
15:57:29  <pkrumins>good job on legit
15:58:20  <yorick>substack: be sure to check out my pull request, too :)
16:44:04  <pkrumins>just published a new blog post!
16:44:07  <pkrumins>http://www.catonmat.net/blog/chroot-su-sh-trick/
16:44:19  <pkrumins>^--> The `sudo chroot /chroot su - user sh -c "cmd args"` trick <--
16:45:02  <yorick>how do you bind to port 80?
16:45:46  <pkrumins>in what sense
16:45:59  <yorick>linux doesn't allow you to port 80 if you're not root
16:46:03  <pkrumins>at the moment i just run node as root
16:46:08  <yorick>oh dear
16:46:25  <pkrumins>well bouncy runs on port 80
16:46:35  <yorick>you trust bouncy with root? :O
16:46:38  <pkrumins>and forwards stuff to other processes running on like 8080 and 8081
16:46:59  <yorick>I've heard of iptables -t nat -I PREROUTING --src 0/0 --dst YOUR.IP.ADDRESS.HERE -p tcp --dport 80 -j REDIRECT --to-ports 8080
16:47:05  <pkrumins>better do i trust node with root? :)
16:47:17  <pkrumins>yes there is that trick and other tricks
16:47:34  <pkrumins>no time for all that, so much to do, just got to get it going then fix it later
16:47:47  <yorick>hmm
16:55:18  * rannmannchanged nick to ranndeer
16:59:00  * defunctzombie_zzchanged nick to defunctzombie
17:03:35  * jez0990quit (Ping timeout: 265 seconds)
17:11:47  <defunctzombie>substack: that browser range stuff won't work for things like firefox/3.6..17.0
17:12:07  <defunctzombie>when I first wrote the range I just did basic math ops
17:12:19  <defunctzombie>but now that the version list is passed in, I think that should be used instead
17:25:19  <Raynos>paul_irish_: pivot~
17:25:36  <Raynos>paul_irish_: pivot all of yeoman to npm
17:26:51  <defunctzombie>haha
18:08:25  <st_luke>yorick: I do the iptables thing
18:08:27  <st_luke>works fine
18:25:40  <defunctzombie>pkrumins yorick st_luke you can also bind to the port and then drop privs to a normal user, or check out something called authbind (http://en.wikipedia.org/wiki/Authbind)
18:30:26  <st_luke>defunctzombie: which do you do?
18:30:33  <st_luke>looks like authbind is really really simple on debian
18:30:53  <defunctzombie>currently, neither. I use haproxy
18:31:14  <defunctzombie>since I typically need to route based on some domain info as well on many of the things I run
18:31:28  <defunctzombie>on my internap box I do use iptables to forward to the internal virtual machines
19:26:21  <defunctzombie>anyone know of a good css/js effects module/lib for html elements?
19:26:45  <defunctzombie>things like slide up/down fade in/out ? etc?
19:49:32  * mikealquit (Quit: Leaving.)
19:52:12  <st_luke>defunctzombie: just saw a neat one earlier, let me find it
19:52:28  <st_luke>defunctzombie: http://daneden.me/animate/
19:52:47  <st_luke>I didn't look at the code tho
19:52:53  <defunctzombie>I saw that one.. doesn't have slide up/down tho
19:53:46  <defunctzombie>so the weird thing about transitions involving height
19:53:56  <defunctzombie>is that the starting height has to be known in the css as well
19:54:02  <defunctzombie>apparently it doesn't do so well with height: auto
19:55:20  <st_luke>defunctzombie: bounceInUp and bounceOutDown are pretty nice sliding entrances
19:55:50  <defunctzombie>st_luke: I am looking for something closer to jquery.slideUp/down
19:56:01  <defunctzombie>I am thinking I will just write a simple 'fx' module
19:56:33  <defunctzombie>to do some basic things :/ really the problem is that for transition height to work you have to set the starting height, then it is ok
19:57:30  <st_luke>there's so much browsery stuff to keep in mind when making something like that
19:57:33  <st_luke>not super fun
19:57:43  <defunctzombie>http://stackoverflow.com/questions/3149419/can-you-use-css3-to-transition-from-height0-to-the-variable-height-of-content
19:58:06  <defunctzombie>st_luke: I started making a simple jquery dom clone https://github.com/shtylman/dom/wiki
19:58:10  <defunctzombie>focused on just some dom basics
19:58:31  <defunctzombie>picked up where tj left off really
19:59:55  <st_luke>sort of like bonzo?
19:59:55  <st_luke>https://github.com/ded/bonzo
20:00:28  <defunctzombie>oh nice! let me check this out
20:02:07  <defunctzombie>yea.. sorta like bonzo except written with commonjs requires and code that ideally could be maintained :p
20:02:32  <defunctzombie>I also don't see any event stuff in bonzo
20:07:12  <st_luke>haven't really used it, I just remember coming across it while trying to get my previous team on board with something like ender
20:11:02  * stlsaintjoined
20:11:03  * stlsaintquit (Changing host)
20:11:03  * stlsaintjoined
20:12:34  <st_luke>I started working on that PR you pointed out to me the other week, thought it was gonna be like a 20 minute thing but docs don't build on my machine, heh
20:14:40  <defunctzombie>hahaha
20:16:55  <st_luke>I'm gonna try it on a linux box and see if it's just me, must not be defeated by build silliness
20:17:23  * shuaibquit (Quit: Textual IRC Client: http://www.textualapp.com/)
20:18:26  <defunctzombie>what didn't build?
20:19:08  <st_luke>I couldn't build the docs separately
20:20:20  <st_luke>`make doc`
20:20:26  <defunctzombie>iirc there is a make target for the docs
20:20:45  <st_luke>it starts off fine
20:20:47  <st_luke>Input file = doc/api/all.markdown
20:20:52  <st_luke>goes through the list
20:20:57  <st_luke>then
20:20:58  <st_luke> throw new Error('invalid list - text without current item\n' +
20:21:05  <st_luke>and then I was like, well I'm gonna go to bed now
20:21:18  <defunctzombie>yea, I am getting that as well
20:21:57  <st_luke>going to build on debian just because
20:22:25  <st_luke>I'm guessing it's just some weirdness that never came up before, didn't go through the issues to search for it yet though
20:23:10  <st_luke>also this way my laptop won't get really hot
20:27:59  <defunctzombie>st_luke: I pulled the latest upstream master and that seems to have built without issue
20:28:38  <st_luke>defunctzombie: cool, I just did the same
20:28:42  <st_luke>mine is still going
20:30:51  <st_luke>changelog part is taking like 20 years
20:32:15  <defunctzombie>get a faster computer
20:32:34  <st_luke>I'm doing it on a voxel vm
20:32:38  <st_luke>this step
20:32:38  <st_luke>bash tools/build-changelog.sh
20:32:44  <st_luke>wait4(-1,
20:32:47  <st_luke>lol
20:33:44  <defunctzombie>haha
20:35:39  <st_luke>so I guess this is why I write js
20:36:27  <st_luke>if this build finishes first on my 3 year old laptop I'm totally asking for a refund on this vm
20:36:48  <defunctzombie>haha
20:36:54  <defunctzombie>did you get one with SSD?
20:36:58  <defunctzombie>SSD is the way to go
20:37:35  <st_luke>probably not, it was free
20:39:17  <st_luke>the vm I mean
20:39:24  <st_luke>ssd in the laptop, build was pretty quick
20:40:04  <st_luke>anyway, doc build works fine with latest upstream master, I can try that PR now
20:43:13  * mikealjoined
20:44:52  * fotoveritejoined
20:53:35  * mikealquit (Ping timeout: 255 seconds)
21:33:14  * dguttmanjoined
21:36:03  * dguttmanquit (Client Quit)
21:38:04  * dguttmanjoined
21:47:45  * dguttmanquit (Quit: dguttman)
21:48:30  * mirkokjoined
21:49:32  * mikealjoined
21:54:07  * mikealquit (Ping timeout: 260 seconds)
21:56:14  * st_lukequit (Remote host closed the connection)
22:05:10  <defunctzombie>pretty quiet in here on christmas eve
22:05:18  <defunctzombie>is everyone waiting for jesus?
22:05:38  <fotoverite>Nope, waiting for my chinese food
22:05:49  <fotoverite>Which I will be doing tomorrow if anyone wants to join
22:05:54  <fotoverite>jewish tradition. :D
22:09:03  * jden_joined
22:11:02  * shuaibjoined
22:11:41  * xaqjoined
22:15:55  * dguttmanjoined
22:16:59  * dguttmanquit (Client Quit)
22:24:27  * st_lukejoined
22:33:38  * dguttmanjoined
22:40:14  * devaholicjoined
22:42:21  * mirkokquit (Quit: mirkok)
22:49:53  * mikealjoined
22:54:11  * mikealquit (Ping timeout: 245 seconds)
23:07:06  * sorensenjoined
23:12:06  * chapeljoined
23:17:02  * dguttmanquit (Quit: dguttman)
23:32:24  * devaholicquit (Ping timeout: 252 seconds)
23:35:22  <substack>https://github.com/substack/glog#http-api
23:37:50  <substack>all generated from `git tag -l` and `git show`
23:43:14  <substack>jjjjohnnny: https://en.wikipedia.org/wiki/Phlogiston_theory
23:43:35  * devaholicjoined
23:49:21  <yorick>substack: I submitted a pull request #seaport
23:49:29  <yorick>did you see it?
23:49:35  <substack>yep
23:50:13  * mikealjoined
23:51:40  <yorick>great :)
23:53:01  <substack>uh oh there is a syntax error in the latest crdt
23:53:14  <substack>or scuttlebutt
23:53:23  <substack>or something isn't working quite right with the latest version at least
23:54:49  <defunctzombie>disaster!
23:54:56  <yorick>uh oh. it works for me, but the travis builds are all broken
23:55:55  <substack>published
23:56:04  <substack>I just pegged the crdt version to 3.1.4
23:56:08  <substack>something is messed up with 3.1.8
23:56:23  <defunctzombie>this is why we peg versions ;)
23:56:33  <defunctzombie>developers cannot be trusted hahaha
23:56:51  <substack>only when proven otherwise
23:57:12  <defunctzombie>given enough time everyone will be proven otherwise
23:57:34  <defunctzombie>programming sucks
23:57:42  * st_lukequit (Remote host closed the connection)
23:57:53  <substack>anyways the release management in npm is pretty much the best large-scale open source release management being done right now
23:58:00  <defunctzombie>yes
23:58:43  <substack>it's so crazy how much *better* all the package tools and infrastructure is in node+npm than any other platforms I've used
23:58:59  <yorick>am I supposed to delete my fork now?
23:59:03  <substack>I feel pretty confident in letting the patch float
23:59:06  <substack>yorick: do whatever you like
23:59:14  <substack>I just leave my forks kicking around
23:59:32  <substack>other folks like to delete their forks for some reaosn
23:59:53  <yorick>you have enough repositories that you don't notice one or two more :P
23:59:55  <mbalho>you just cant trust developers from new zealand