00:21:58  * pfrazeejoined
00:52:06  * savantgardejoined
00:56:47  * savantgardequit (Ping timeout: 264 seconds)
01:00:43  * savantgardejoined
01:06:15  * savantgardequit (Ping timeout: 252 seconds)
01:30:31  * blobaumjoined
01:59:15  * ekristenquit (Quit: ekristen)
02:00:58  * phatedjoined
03:03:04  * savantgardejoined
03:08:00  * savantgardequit (Ping timeout: 276 seconds)
03:26:19  * phatedquit (Remote host closed the connection)
03:29:18  * contrahaxquit (Quit: Sleeping)
03:42:32  * contrahaxjoined
03:58:14  * blobaumquit (Quit: Leaving)
04:03:52  * savantgardejoined
04:08:38  * savantgardequit (Ping timeout: 255 seconds)
04:51:32  * phatedjoined
04:55:49  * contrahaxquit (Quit: Sleeping)
05:04:33  * savantgardejoined
05:08:03  * pfrazeequit (Remote host closed the connection)
05:09:11  * savantgardequit (Ping timeout: 240 seconds)
06:05:19  * savantgardejoined
06:10:08  * savantgardequit (Ping timeout: 255 seconds)
06:42:20  * phatedquit (Remote host closed the connection)
06:52:37  * phatedjoined
06:57:05  * phatedquit (Ping timeout: 248 seconds)
07:06:32  * savantgardejoined
07:11:45  * savantgardequit (Ping timeout: 276 seconds)
07:29:26  <emilbayes>ogd: Just saw toiletdb, ha! Does .writeFile actually guarantee that the Buffer has been flushed to disk before the callback is invoked?
07:29:48  <ogd>emilbayes: nope
07:29:54  <ogd>emilbayes: unless node does
07:30:30  <emilbayes>ogd: Oh, just got the impression from the readme that you guaranteed that, and went looking for fsyncs :p
07:30:39  <ogd>emilbayes: oh oops
07:31:01  <ogd>emilbayes: was just making flush puns sorry
07:31:06  <emilbayes>ogd: No worries, I've just been thinking about how to use fsync efficiently without thrashing IOPS
07:31:18  <emilbayes>ogd: ;) haha
07:31:24  <ogd>emilbayes: i dont care about iops so if you know how to make this safer feel free to pr
07:31:41  <emilbayes>ogd: I don't :( Want to learn how though
07:38:47  <emilbayes>Always thought the B in B-Tree was for Block
08:07:04  * savantgardejoined
08:11:28  * savantgardequit (Ping timeout: 240 seconds)
08:40:55  * phatedjoined
08:45:09  * phatedquit (Ping timeout: 240 seconds)
09:07:48  * savantgardejoined
09:12:23  * savantgardequit (Ping timeout: 255 seconds)
09:26:33  * pfrazeejoined
09:31:17  * pfrazeequit (Ping timeout: 255 seconds)
10:08:34  * savantgardejoined
10:13:13  * savantgardequit (Ping timeout: 258 seconds)
10:29:01  * phatedjoined
10:33:42  * phatedquit (Ping timeout: 255 seconds)
10:52:57  * phatedjoined
10:57:09  * phatedquit (Ping timeout: 240 seconds)
11:09:18  * savantgardejoined
11:13:49  * savantgardequit (Ping timeout: 240 seconds)
11:26:02  * mylesborinsquit (Quit: farewell for now)
11:26:32  * mylesborinsjoined
12:10:09  * savantgardejoined
12:15:32  * savantgardequit (Ping timeout: 255 seconds)
13:02:10  * savantgardejoined
13:03:14  * pfrazeejoined
13:07:28  * pfrazeequit (Ping timeout: 240 seconds)
15:22:48  * pfrazeejoined
15:51:58  * savantgardequit (Remote host closed the connection)
16:09:39  * savantgardejoined
16:17:23  * savantgardequit (Remote host closed the connection)
16:26:42  * lmatteisjoined
17:18:28  * savantgardejoined
17:23:09  * savantgardequit (Ping timeout: 240 seconds)
18:19:33  * savantgardejoined
18:23:48  * savantgardequit (Ping timeout: 240 seconds)
18:40:04  * akivajoined
19:03:13  * contrahaxjoined
19:20:14  * savantgardejoined
19:24:28  * savantgardequit (Ping timeout: 240 seconds)
20:01:12  * lmatteisquit (Quit: Connection closed for inactivity)
20:21:02  * savantgardejoined
20:26:01  * savantgardequit (Ping timeout: 256 seconds)
20:34:45  * pfrazeequit (Remote host closed the connection)
20:55:49  * phatedjoined
21:07:24  * pfrazeejoined
21:21:44  * savantgardejoined
21:26:06  * savantgardequit (Ping timeout: 240 seconds)
22:22:28  * savantgardejoined
22:26:11  * phatedquit (Remote host closed the connection)
22:27:23  * savantgardequit (Ping timeout: 264 seconds)
23:07:50  <noffle>mafintosh: that strange chrome<->firefox webrtc issue turned out to be me using browserify 9.x.x. Upgraded to latest and it went away; unsure of the root cause, but it was in hyperlog: made protocol buffers decode differently on chrome vs firefox
23:08:08  <mafintosh>whoa
23:09:37  <substack>maybe a buffer issue?
23:12:51  <noffle>old me it a browserify bug in the past, which is why I used an older browserify: https://github.com/noffle/hyperpad/commit/be457d945a209c41c2fbb7ebba0d471de9be1ebc
23:13:03  <noffle>because I use npm link a lot: https://github.com/substack/node-browserify/issues/1359
23:13:25  <noffle>maybe
23:13:47  <noffle>I think on FF it just did passthrough: no decoding happened
23:14:46  <noffle>mafintosh: sorry in protocol-buffers, not hyperlog
23:23:13  * savantgardejoined
23:28:17  * savantgardequit (Ping timeout: 255 seconds)
23:57:18  * phatedjoined