00:00:09  * knownasilyaquit (Quit: Connection closed for inactivity)
00:01:36  * pfrazequit (Ping timeout: 250 seconds)
00:11:56  * TatumCreative_joined
00:12:48  * ngoldman_joined
00:13:22  * wa7son_joined
00:15:08  * TatumCreativequit (Ping timeout: 240 seconds)
00:15:08  * juliangruberquit (Ping timeout: 240 seconds)
00:15:08  * ngoldmanquit (Ping timeout: 240 seconds)
00:15:08  * wa7sonquit (Ping timeout: 240 seconds)
00:15:09  * juliangruberjoined
00:15:09  * TatumCreative_changed nick to TatumCreative
00:15:35  * wa7son_changed nick to wa7son
00:15:49  * ngoldman_changed nick to ngoldman
00:46:37  <noffle>mafintosh: substack: I wrote ipfs-hyperlog today (https://github.com/noffle/ipfs-hyperlog)! It's a drop-in hyperlog replacement that creates nodes and hash links that are binary-compatible with ipfs. I'm planning to use the hyperlog ecosystem of modules (hyperkv, swarmlog) on top to build out a pubsub protoype for ipfs. :)
01:38:02  * dguttmanquit (Quit: dguttman)
01:42:00  * dguttmanjoined
02:05:00  * dguttmanquit (Quit: dguttman)
02:30:33  <substack>noffle: excellent!
02:32:26  * gildeanquit (Ping timeout: 272 seconds)
02:32:45  * gildeanjoined
02:35:39  <substack>noffle: and it passes the existing test suite O_O
02:39:45  * phatedquit (Remote host closed the connection)
02:47:07  <substack>noffle: cannot find module 'ipfs-blocks' in ipfs-merkle-dag
02:47:20  <substack>aside from that, it works!
02:47:55  * dguttmanjoined
02:58:26  * py1honquit (Ping timeout: 240 seconds)
03:03:39  * py1honjoined
03:17:43  * shamaquit (Quit: (╯°□°)╯︵ɐɯɐɥs)
03:24:48  * domanicjoined
03:34:43  <noffle>ungh, I see: it's a dev dep for some reason
03:40:02  <noffle>next piece is a hyperlog pull-only peer that replicates the nodes it sees to ipfs, to bridge the two worlds
03:40:40  <noffle>until js-ipfs gets further, this will require an ipfs api daemon somewhere to publish to
03:44:16  * dguttmanquit (Quit: dguttman)
03:44:31  * py1honquit (Ping timeout: 245 seconds)
03:47:09  * py1honjoined
04:15:03  * phatedjoined
04:19:16  * phatedquit (Ping timeout: 248 seconds)
05:47:39  * serapathjoined
05:57:00  * pfrazejoined
06:03:08  * phatedjoined
06:07:22  * phatedquit (Ping timeout: 240 seconds)
06:40:23  * phatedjoined
06:44:50  * phatedquit (Ping timeout: 252 seconds)
07:08:16  * warbrettquit (Quit: Connection closed for inactivity)
07:11:21  * pfrazequit (Remote host closed the connection)
08:28:26  * foreigneyequit (Quit: No Ping reply in 180 seconds.)
08:29:52  * foreigneyejoined
09:20:44  * drptbljoined
09:25:07  * drptbl_joined
09:28:04  * drptblquit (Ping timeout: 248 seconds)
09:38:57  * djcoinjoined
09:41:54  * contrahaxquit (Quit: Sleeping)
09:53:22  * drptbl_quit (Quit: My MAC has gone to sleep. zZz..)
09:53:23  * fotoveritequit (Quit: fotoverite)
10:12:25  * fotoveritejoined
10:19:53  * fotoveritequit (Quit: fotoverite)
10:31:37  <mafintosh>noffle: wow great work :)
11:09:52  * djcoinquit (Quit: WeeChat 1.0.1)
12:17:22  * domanicquit (Ping timeout: 240 seconds)
12:30:19  * peutetrejoined
12:40:25  * serapathquit (Quit: Connection closed for inactivity)
13:21:45  * pfrazejoined
14:03:20  * serapathjoined
14:58:31  * fotoveritejoined
15:27:22  * pfrazequit (Remote host closed the connection)
15:34:12  * knownasilyajoined
15:47:22  * pfrazejoined
16:07:24  * dguttmanjoined
16:39:33  * peutetrequit (Quit: ...)
16:42:37  * phatedjoined
16:44:06  * peutetrejoined
17:14:40  * shamajoined
17:26:25  * McJesusquit (Quit: ZNC - http://znc.in)
17:31:17  * McJesusjoined
17:31:19  * McJesuschanged nick to Guest33309
17:36:05  * peutetrequit (Quit: ...)
17:40:39  <noffle>mafintosh: your extensive test suite helped a lot!
17:41:50  <noffle>I wish ipfs-hyperlog could layer on top of hyperlog instead -- I don't want to rebase hyperlog changes/fixes for the rest of eternity
17:43:48  <noffle>mafintosh: maybe this means allowing the hash method to be provided?
17:47:19  <mafintosh>noffle: feel free to add that :)
17:48:13  <noffle>perfect!
17:49:16  <noffle>aside: for comparing buffers in tests, is there some nice way (or module) to create a buffer from readable text? something like 'var buf = Buffer.fromLiteral("<Buffer 12 20 50 ee 82>")'
17:49:29  <noffle>this MUST be a module, but I can't find it
17:49:52  <mafintosh>noffle: new Buffer(string, 'hex')?
17:50:35  <noffle>mafintosh: perfect
18:10:26  * foreigneyequit (Ping timeout: 240 seconds)
18:36:18  * peutetrejoined
19:51:13  <thealphanerd>ogd oh hey
19:51:46  <thealphanerd>I figured we could move the chat here if you were interested in figuring out what I was trying to say in so few characters :p
19:52:10  <ogd>thealphanerd: haha ok. i think i just need a gist or something, i dont know what the words you were using meant :P
19:52:21  <thealphanerd>hehe
19:52:22  <ogd>thealphanerd: also i dont know how react works
19:52:24  <thealphanerd>so we had this happen at famous
19:52:29  <thealphanerd>the famous engine was a singleton
19:52:41  <thealphanerd>and you would register trees to be rendered
19:52:59  <thealphanerd>so when you created a new element, that registered in a global registry (which was a singleton)
19:52:59  <ogd>thealphanerd: do you mean global?
19:53:07  <thealphanerd>but it wasn't a global
19:53:14  <thealphanerd>it was as singleton that was exposed via require
19:53:21  <ogd>thealphanerd: ive never used the term 'singleton' when talking about modules before
19:53:31  <thealphanerd>so if you end up with two instances in your tree than you end up with two singletons
19:53:49  <ogd>thealphanerd: do you have an example?
19:53:53  <ogd>preferably on github
19:54:01  <thealphanerd>i think it depends on the way you are using it... if the module you are requiring has state, and you are relying on that state being shared between multiple requires... singleton
19:54:03  <thealphanerd>imho
19:54:25  <thealphanerd>I can make a quick one
19:54:29  <ogd>nah thats ok
19:54:33  <ogd>sounds like globals to me
19:54:38  <ogd>not globals in the sense of js scope
19:54:47  <thealphanerd>oh yeah
19:54:47  <thealphanerd>totally
19:54:54  <ogd>but i am curious why you would ever need that, it basically makes you write plugins
19:54:58  <thealphanerd>I got into massive arguments that any singleton should be a global
19:55:08  <thealphanerd>it is definitely an anti pattern
19:55:10  <thealphanerd>but it exists
19:55:16  <ogd>well i would recommend not doing that then :)
19:55:21  <thealphanerd>:D
19:55:23  * ogdretreats back to moduletopia
19:55:27  <thealphanerd>hehe
19:55:32  <thealphanerd>mah modules are functions with no state
19:55:42  <thealphanerd>STATE IS THE ENEMY
19:55:48  <ogd>ooh
19:56:01  <ogd>npm install denzel
20:00:25  * serapathquit (Quit: Connection closed for inactivity)
20:03:13  <thealphanerd>lol
20:11:10  * peutetrequit (Read error: Connection reset by peer)
20:12:01  * peutetrejoined
20:37:26  * peutetrequit (Ping timeout: 240 seconds)
20:50:16  <substack>noffle: I think a storage/hash layer in hyperlog might help with building a scuttlebot bridge too
20:51:25  <noffle>substack: yeah I was thinking how nice it'd be if hyperlog was easily generalizable at that level
20:55:46  <noffle>substack: then we populate the networks with bridge nodes
20:56:11  <noffle>substack: not sure how it'll work for ipfs->hyperlog though, since ipfs has no way to really aggregate dags
20:56:17  <noffle>but other direction is easy enough
20:57:21  <ogd>daggregate
20:59:13  <noffle>hah
21:22:08  * pfrazequit (Remote host closed the connection)
21:22:21  * contrahaxjoined
21:45:34  * domanicjoined
21:51:59  * contrahaxquit (Quit: Sleeping)
22:09:29  * contrahaxjoined
22:16:08  * contrahaxquit (Quit: Sleeping)
22:19:14  * contrahaxjoined
22:24:20  * contrahaxquit (Ping timeout: 276 seconds)
22:25:02  * contrahaxjoined
22:25:07  * pfrazejoined
22:26:16  * contrahaxquit (Client Quit)
22:36:37  * dguttmanquit (Quit: dguttman)
22:44:32  * contrahaxjoined
22:47:12  <substack>ok I'm thinking hyperboot should run as a background service, since it will be seeding html torrents
22:52:45  * pfrazequit (Remote host closed the connection)
23:14:23  * domanicquit (Ping timeout: 276 seconds)
23:33:15  <joepie91>thealphanerd: "modules should export functionality, not state or data" is a thing I have to repeat in #Node.js on a near-daily basis...
23:36:21  <thealphanerd>joepie91 tell that to react
23:36:40  <joepie91>thealphanerd: I find React amusing
23:37:02  <joepie91>"everything should be a modular component!"
23:37:17  <joepie91>... most popular data propagation architecture has a single global namespace with no way to isolate components
23:37:22  <ogd>"we are using separate files therefore they are modules"
23:37:41  <thealphanerd>they call me kindle
23:37:43  <thealphanerd>I start the flame
23:37:44  <thealphanerd>:D
23:37:48  <joepie91>another reason I like Riot more, it seems to make it a lot easier to write actually modularized components
23:38:05  <joepie91>and wiring up each component as its own event emitter *during usage*
23:39:28  <ogd>feross: you should make a bumper sticker for standard that says ONE LESS BIKESHED
23:39:41  <ogd>feross: as a joke on the ONE LESS CAR bicycle bumper stickers for bikes
23:52:22  <substack>actually existing modular components
23:58:21  * contrahaxquit (Quit: Sleeping)