00:31:03  * yangwaoquit (Ping timeout: 250 seconds)
00:55:16  * pfrazequit (Remote host closed the connection)
01:00:04  * pfrazejoined
01:08:04  * vweeversquit (Ping timeout: 240 seconds)
01:41:48  * pfrazequit (Remote host closed the connection)
01:43:21  * pfrazejoined
01:49:29  * pfrazequit (Remote host closed the connection)
01:51:18  * pfrazejoined
02:37:51  * yangwaojoined
03:44:26  * pfrazequit (Remote host closed the connection)
03:58:53  * pfrazejoined
04:49:00  * TatumCreativequit (Read error: Connection reset by peer)
04:49:27  * TatumCreativejoined
04:49:29  * creationixquit (Ping timeout: 240 seconds)
04:53:04  * dlmanningquit (Ping timeout: 268 seconds)
04:54:18  * rfquit (Ping timeout: 268 seconds)
04:54:32  * rfjoined
04:54:55  * trevnorrisquit (Ping timeout: 268 seconds)
04:56:14  * creationixjoined
04:59:29  * dlmanningjoined
04:59:46  * trevnorrisjoined
05:02:03  * pfrazequit (Remote host closed the connection)
06:40:56  * fotoveritequit (Quit: fotoverite)
07:00:58  * contrahaxjoined
07:44:56  * pfrazejoined
08:24:21  * pfrazequit (Remote host closed the connection)
10:50:16  <substack>finally got this working https://github.com/substack/hyperlog-seed
11:22:03  <substack>https://github.com/substack/hyperlog-webtorrent-seed
11:39:13  <substack>http://www.newsweek.com/clifford-stoll-why-web-wont-be-nirvana-185306
11:39:27  * vweeversjoined
11:48:49  <rom15044>I bet he's still saying that
11:50:31  <rom15044>Well Wikipedia says he's not ^^
12:56:07  * fotoveritejoined
14:29:56  <emilbayes>substack: Looking at swarmlog, why is it smart to have the swarm in a hyperlog? Isn't peers in a swarm very volatile? Any what do the properties of a hyperlog help with?
16:32:07  * pfrazejoined
17:01:16  * contrahaxquit (Quit: Sleeping)
18:05:53  * jhermsjoined
19:16:44  <substack>emilbayes: hyperlogs are not volatile, they save everything
19:17:00  <substack>so if there are any peers in the swarmlog, you will be able to replicate the data that they have
19:35:23  * vweeversquit (Ping timeout: 244 seconds)
19:55:51  * vweeversjoined
20:40:00  <emilbayes>substack: that's what I was wondering about. The peers themselves are(might be?) volatile, but the hyperlog will remember them forever?
21:18:18  <substack>the peers aren't important
21:18:27  <substack>each peer replicates the data feed
21:18:37  <substack>so you can get the data from any peer
21:28:44  <noffle>emilbayes: I think I see the source of confusion. The peers aren't being stored in the hyperlog. Rather, a [potentially volatile] swarm of peers locate each other via a signalhub (or futurey webrtc dht) to collaborate on replicating a single hyperlog between themselves.
21:30:54  <noffle>emilbayes: the base hyperlog module doesn't concern itself with the transport used for replication: it just hands you read/write streams. swarmlog takes over the transport piece using one (of many) possible transports: webrtc (/w signalhub for peer discovery)
21:44:25  <yangwao>mm, peers are volatile thing, I think. Till we don't have full ipv6 homing thing :x
22:48:06  * contrahaxjoined
23:18:29  * jhermsquit (Ping timeout: 240 seconds)
23:18:54  * pfrazequit (Remote host closed the connection)
23:28:28  * pfrazejoined
23:34:03  * pfrazequit (Remote host closed the connection)
23:57:16  * pfrazejoined