<ipfsbot>
[go-ipfs] chriscool pushed 1 new commit to fix-toolkit_upgrade-removal: https://git.io/vrG9R
<ipfsbot>
go-ipfs/fix-toolkit_upgrade-removal 12cdbe6 Christian Couder: README: points to Windows doc...
<slothbag>
Hey guys.. im trying to communicate with a ipfs node on port 4001, if im the client I get "/multistream/1.0.0\n" response, but if I reply I get nothing, same if I act as the server, no reponses.. how does the protocol proceed?
<Kubuxu>
slothbag: protocol is quite complex, I don't know if you want to communicate with it by hand.
Oatmeal has quit [Ping timeout: 252 seconds]
<slothbag>
i'm trying to implement a minimal node, just trying to understand how it works.. can't seem to get past this initial handshake
<ipfsbot>
[go-ipfs] whyrusleeping deleted fix-toolkit_upgrade-removal at 12cdbe6: https://git.io/vrGHb
arpu has quit [Ping timeout: 276 seconds]
ppham has quit [Remote host closed the connection]
chriscool has quit [Quit: Leaving.]
chriscool has joined #ipfs
arpu has joined #ipfs
MadcapJake is now known as MadcapJake_zZz
Oatmeal has joined #ipfs
cryptix has joined #ipfs
herzmeister has quit [Ping timeout: 246 seconds]
pfraze has quit [Remote host closed the connection]
herzmeister has joined #ipfs
cryptix has quit [Ping timeout: 244 seconds]
Dhole has quit [Read error: Connection reset by peer]
Dhole has joined #ipfs
erde74 has joined #ipfs
eaxdigitalhash has joined #ipfs
eaxdigitalhash has quit [Remote host closed the connection]
<daviddias>
slothbag: you can run an ipfs daemon with --disable-transport-encryption
<slothbag>
why is it important to encrypt public data?
<slothbag>
i get that it can provide some anonymity as to who is sending what
<slothbag>
but yes, its for testing
<slothbag>
daviddias: thanks
eaxdigitalhash has joined #ipfs
<cryptix>
imho: if you host OSM on ipfs, sure that's public. i still might want to keep private which areas i'm interested in (meaning requesting) - personal pain-point of current ipfs design for me is that it it's very easy to see who hosts what but we don't need to get into that right now, don't have the time anyway
<Kubuxu>
Is the sprint finally today or tommorow?
<Kubuxu>
s/tommorow/tomorrow/
<rendar>
cryptix: hmm, OSM?
<cryptix>
openstreetmap
<rendar>
ok
<Kubuxu>
If keychain is implemented you could make OSM with private areas.
<Kubuxu>
And store everything on IPFS
eaxdigitalhash has quit [Ping timeout: 246 seconds]
corvinux has joined #ipfs
<Kubuxu>
There is problem of damage control in case key leaks but apart from that.
<cryptix>
Kubuxu: i know :) that's why I said _current_
<Kubuxu>
true :P
<cryptix>
though.. if you still have the global swarm.. you can't use plain convergent crypto schemes. you need to drop the deduplication and use nonce seeds if you want privacy
<cryptix>
oor have something like a WoT or friends only swarm
<cryptix>
but yea.. revolves around the keychain
<Kubuxu>
True, you can't use convergent crypto, but you would still get dedup inside encrypted blocks.
<Kubuxu>
With one symmetric key.
Qwertie has joined #ipfs
Qwertie has quit [Changing host]
Qwertie has joined #ipfs
<cryptix>
yup
herzmeister has quit [Ping timeout: 276 seconds]
ulrichard has joined #ipfs
Senji has joined #ipfs
* ansuz
makes a GUI in visual basic
eaxdigitalhash has joined #ipfs
ygrek has joined #ipfs
ylp has quit [Ping timeout: 260 seconds]
eaxdigitalhash has quit [Ping timeout: 244 seconds]
<cryptix>
ansuz: dim dim dim dim
<cryptix>
that's the crazy-pants bell ringing
herzmeister has joined #ipfs
eaxdigitalhash has joined #ipfs
ylp has joined #ipfs
<ansuz>
lol
cemerick has quit [Ping timeout: 260 seconds]
eaxdigitalhash has quit [Ping timeout: 250 seconds]
<slothbag>
is there any doco around the different multistream identifiers and the order in which two peers would use them to go through a 'connection lifecycle' if I can call it that :)
zootella_ has quit [Quit: zootella_]
ylp has quit [Ping timeout: 260 seconds]
uzyn has quit [Quit: uzyn]
<cryptix>
ansuz: oooooh that was a csi reference...? slow penny is falling slow
ylp has joined #ipfs
ygrek has quit [Ping timeout: 246 seconds]
TheOneLaw has joined #ipfs
cmeik has quit [Ping timeout: 250 seconds]
cmeik has joined #ipfs
ygrek has joined #ipfs
TheOneLaw has quit [Remote host closed the connection]
rgrinberg has joined #ipfs
eaxdigitalhash has joined #ipfs
eaxdigitalhash has quit [Remote host closed the connection]
eaxdigitalhash has quit [Remote host closed the connection]
Suwandi has quit [Ping timeout: 265 seconds]
andoma has quit [Ping timeout: 244 seconds]
andoma has joined #ipfs
ppham has quit [Remote host closed the connection]
corvinux has joined #ipfs
Combined2857 has quit [Quit: Leaving]
Encrypt has joined #ipfs
redfish has quit [Ping timeout: 260 seconds]
pfraze has joined #ipfs
zorglub27 has joined #ipfs
corvinux has quit [Ping timeout: 260 seconds]
<ipfsbot>
[js-ipfs] dignifiedquire deleted greenkeeper-aegir-3.0.4 at 300ce69: https://git.io/vrZKu
computerfreak has quit [Quit: Leaving.]
ylp has joined #ipfs
vijayee has joined #ipfs
Combined2857 has joined #ipfs
<vijayee>
happy monday
<daviddias>
happy monday vijayee :)
<vijayee>
until they are abolished
<dignifiedquire>
daviddias, haad_, noffle, richardlitt and everyone else, do you have something you want to talk about during apps on IPFS later today?
<dignifiedquire>
haad_: any updates on orbit you want to share?
Qwertie has quit [Ping timeout: 276 seconds]
Qwertie has joined #ipfs
<daviddias>
If no one has stuff to share, I propose that we do a JS Task Force Hangout today
<daviddias>
during libp2p + js-ipfs
<daviddias>
and talk about what is on the map to get js-ipfs out the door
cketti has joined #ipfs
cketti has quit [Changing host]
cketti has joined #ipfs
<daviddias>
orbit on js-ipfs
<daviddias>
and what each one is focusing
<daviddias>
and what other people on the team can tackle to help
Combined2857 has quit [Quit: Leaving]
<haad_>
dignifiedquire: have couple of updates on orbit but those will be really quick.
<voxelot>
Task Force JS, murica
zorglub27 has quit [Ping timeout: 250 seconds]
ylp has quit [Ping timeout: 260 seconds]
zorglub27 has joined #ipfs
ylp has joined #ipfs
<ipfsbot>
[js-ipfs-api] dignifiedquire deleted greenkeeper-aegir-3.0.3 at 4d9c4e6: https://git.io/vrZMu
PrinceOPeeves has joined #ipfs
PrinceOfPeeves has quit [Read error: Connection reset by peer]
<daviddias>
Ok, I'll go ahead and merge libp2p+js-ipfs syncs and leave the apps on IPFS, so that haad_ can share his updates
Encrypt has quit [Quit: Quitte]
Encrypt has joined #ipfs
ashark has joined #ipfs
<ipfsbot>
go-ipfs/feature/spruce-upstat 8ee399f Richard Littauer: Add helptext, default logic to `ipfs stats`...
<ipfsbot>
[go-ipfs] RichardLitt force-pushed feature/spruce-upstat from 1523ae3 to 8ee399f: https://git.io/vrmf2
<richardlitt>
I have nothing to talk about during apps on IPFS
<ipfsbot>
[js-ipfs-api] dignifiedquire deleted greenkeeper-aegir-3.0.4 at c912090: https://git.io/vrZ9y
jryans has quit [Read error: Connection reset by peer]
jryans has joined #ipfs
pfraze has quit [Remote host closed the connection]
pfraze has joined #ipfs
pfraze has quit [Remote host closed the connection]
Oatmeal has quit [Ping timeout: 240 seconds]
pfraze has joined #ipfs
zootella has joined #ipfs
OutBackDingo has joined #ipfs
<haad_>
daviddias: "Unhandled rejection TypeError: node.encoded is not a function" js-ipfs@0.4.10 :(
libman has quit [Remote host closed the connection]
<daviddias>
we now check client side if the hash that go-ipfs returns is the one that should have been and if they don't match, we callback with an error
<haad_>
what does that mean?
<daviddias>
it means that the hash that you get now, should be the right one, comparing to the old version
ylp has joined #ipfs
<daviddias>
I noticed while doing tests that a lot of old object API code could sometimes lead to different hashes, because of how the data was being sent
<haad_>
daviddias: I'm not sure I follow. the hash I get from js-ipfs-api@3.x is the same as the go-ipfs CLI gives me. how can they be different in js-ipfs-api@4.x?
<haad_>
you mean there's now a difference in the encoding of the data in object.put?
cryptix has quit [Ping timeout: 244 seconds]
<haad_>
oh wait
<haad_>
SUCCESS!!
<daviddias>
I mean that now, you can be sure that the object that you create in JS, is the one that gets stored in go-ipfs
<daviddias>
byte by byte
<daviddias>
wooo :D
<haad_>
the problem was the object.put arg1, needs to be: ipfs.object.put(new Buffer(JSON.stringify(node.asJson)))
<richardlitt>
This is the IPFS biweekly sync. During this time, we will flood the channel a bit; please keep chatter to a minimum so we can focus on what we've done this week.
<richardlitt>
For more, see github.com/ipfs/pm
<noffle>
daviddias: thanks for getting the ball rolling with interface-ipfs-core
<ipfsbot>
[js-ipfs] dignifiedquire force-pushed core/object from c58ad06 to 034d0e7: https://git.io/vrZhm
<ipfsbot>
js-ipfs/core/object 034d0e7 dignifiedquire: feat: make core/object satisfy interface-ipfs-core
<richardlitt>
Since lgierth seems to be a bit late (which he warned us of, :D! ++), let's start with the next person. Who is me.
<daviddias>
:)
<richardlitt>
====== @RichardLitt ======
<richardlitt>
Last week I broke down ipfs/go-ipfs#2484 into around thirty small PRs. This involved overhauling pretty much every option with a default possibility in the go-ipfs codebase. Most of these have been merged now, and I have also been actively trying to keep the http-api up-to-date in respect to this. Besides that, I also worked on the blog with @jbenet,
<richardlitt>
Finally, I did a lot of work this week on standard-readme: there is now a full spec that I want feedback on, with what I think a good README should have. Extra IPFS-related rules can be found here (feedback also wanted). After talking with @noffle a lot, I also made a yeoman standard-readme generator that works well for scaffolding out your READMEs. Use it!
<richardlitt>
published Weekly 10, organized some hangouts, and updated the READMEs for js-ipfs-api and go-ipfs-api.
<ipfsbot>
[js-ipfs] dignifiedquire force-pushed core/object from 034d0e7 to 96013bb: https://git.io/vrZhm
<ipfsbot>
js-ipfs/core/object 96013bb dignifiedquire: feat: make core/object satisfy interface-ipfs-core
<richardlitt>
Also, I just renamed the Weekly to the NEwsletter. If you see Weekly anywhere, let me know.
<richardlitt>
=================
<richardlitt>
@dignifiedquire stop making IPFS bot talk. :P
<dignifiedquire>
lol
<noffle>
richardlitt: good progress on standard-readme
<daviddias>
whyrusleeping: got it, that came from the http-api spec :)
<richardlitt>
* [go-ipfs](//github.com/ipfs/go-ipfs): The logic surrounding defaults in go-ipfs has been clarified somewhat by the inclusion of a standard way to mark defaults, and greater enforcement of making them overtly declared. @RichardLitt went through the codebase making a lot of small PRs to make sure this worked: thanks @whyrusleeping and @Kubuxu for helping out
<richardlitt>
daviddias: not really. It came from me noticing that it wasn't clear.
<richardlitt>
(Please, put stuff in that collection. We're posting a newsletter today, kapisch?
<richardlitt>
Alright! Let's move on
<richardlitt>
Unless anyone has any questions for me? I am blocked on standard-readme until you all check the spec and the IPFS reqs and tell me that you like them.
ylp has joined #ipfs
<dignifiedquire>
richardlitt: is there an issue to collect all the people you are waiting on a thumbs up for?
<dignifiedquire>
or should we just tell you in irc?
<richardlitt>
ok, dignifiedquire I think you're next
HostFat has joined #ipfs
<dignifiedquire>
====== @dignifiedquire ======
<dignifiedquire>
The past week I have been exclusively working on js-ipfs. There were two main things that happened, the first one being the [merge of bitswap](https://github.com/ipfs/js-ipfs/pull/195) into js-ipfs and the second one being the [update of `ipfs object`](https://github.com/ipfs/js-ipfs/pull/219) to the newly formed
<daviddias>
I've been working solely focused on js-ipfs. There was a bunch of fixes, CR and debugging. The major/quantifiable things were:
<daviddias>
- Create [`interface-ipfs-core`], write the Object API spec (plus the foundations to write the remaining api specs), create a batch of tests and upgrade js-ipfs-api (now 4.x.x release) with the new interface. This unblocks the possibility of swapping js-ipfs-api with js-ipfs for Orbit.
<daviddias>
- Finish the multistream spec revision
<daviddias>
- Update js-multistream to the latest revision of the multistream spec. I also started working on refreshing the API of the module to make it less wonky.
<daviddias>
Other things involved the passing of the torch of ICWE to @dignifiedquire and giving a talk at require('lx'), the Node.js and JavaScript meetup.
* dignifiedquire
is impressed with richards fast writing of the newsletter in between
<vijayee>
daviddias: has anyone been able to webpack or browserify the js-ipfs module?
<vijayee>
repo packs up nicely
<daviddias>
vijayee: it is webpacked everytime we run the tests
<vijayee>
but js-ipfs gets angry when run in the browser
<daviddias>
and each time we publish
<vijayee>
intersting
<dignifiedquire>
vijayee: not when I run it through the tests
<vijayee>
I'll look through the test cases
<daviddias>
a dist version (so you can import with a script tag) is published to npm
<richardlitt>
daviddias: Are there notes // videos from those events?
<richardlitt>
*that event
zorglub27 has quit [Ping timeout: 244 seconds]
<daviddias>
richardlitt: there are some pics and tweets, videos were also recorded by me but won't appear anytime soon with all the things going on
<richardlitt>
daviddias: where is the multistream spec?
<daviddias>
writting down all that interface, upgrading js-ipfs-api, leverage what js-ipfs-api already had build and try to not break it, and then run the same batch of tests in both js-ipfs and js-ipfs-api and see them all pass, is awesome :D
<daviddias>
plus, now we have the foundation to build up the rest of the core-api spec
<dignifiedquire>
it is :)
<daviddias>
voxelot: has even submitted a PR for the Files API
<dignifiedquire>
next step rip js-ipfs-core out of js-ipfs
<voxelot>
yeah it's nice to have docs :)
<richardlitt>
daviddias: What is next?
<richardlitt>
ls?
<daviddias>
richardlitt: I mean that, it requires a lot of domain knowledge to use multistream and it always feels unnatural (aka need to read the docs) to use it. I want to change that, specially now that we have good patterns around things like connections and we know exactly in what points multistream appears, so it is easier now, looking backwards, to design a
<daviddias>
better API
<daviddias>
richardlitt: what's next? all the other calls :)
<richardlitt>
Cool.
arajakul2 has joined #ipfs
<richardlitt>
Ok, thanks daviddias
<richardlitt>
haad_: You still here buddy?
<haad_>
yup
<richardlitt>
your turn. gogogog
<haad_>
incoming:
<daviddias>
my pleasure richardlitt :)
<haad_>
### @haadcode sprint end report - 3 May - 15 May
<haad_>
#### Summary
<haad_>
I planned to work on putting Orbit into the browser but ended up fixing and optimizing orbit-db for the most of the sprint. Good news is, the fixes & optimizations in orbit-db were absolutely worth it: orbit-db's write throughput performance is now at ~100ops/s (~33% improvement) and the code base has been fully modularized. Orbit now uses the following modules as datastores: orbit-db-eventstore, orbit-db-feedstore, orbit-db-kvstore, orbit-db-counterstore. I'm
<haad_>
...I'm still in the process of updating all the documentation, though. Orbit also got some love and I've been integrating the new orbit-db version into it. Spent time also on code review & feedback for two new features to Orbit, implemented and PRed by two newcomers to the community: username auto-complete on 'tab' (by @masadeus) and emoji auto-complete and preview (by @shamb0t).
<haad_>
...Emoji auto-complete is not merged yet but will be in the next couple of days. I also spent some time on giving feedback to whyrusleeping's pubsub PR. Also tried to integrate js-ipfs to orbit-db (WIP).
<richardlitt>
haad_: that's awesome. Thank you!
<whyrusleeping>
haad_: great feedback thanks :)
arajakul has quit [Ping timeout: 260 seconds]
<haad_>
whyrusleeping: good to hear!
<haad_>
looking forward to the next version :)
<richardlitt>
Woot.
<richardlitt>
Anyone else for haad_ ?
<dignifiedquire>
haad_: looking forward to using orbit in the browser ; )
<haad_>
Me too :)
<Kubuxu>
My turn?
<richardlitt>
@Kubuxu yep
<richardlitt>
Go!
<Kubuxu>
### @Kubuxu sprint summary
<Kubuxu>
Not much as I just started coding go-ipfs again, this time I hope that for longer and more actively. I've reviewed many PRs, started going through some old and possibly outdated issues. My main focus was getting offline mode go-ipfs node up and running but it looks a tad harder that I thought it would be. While going through issues I picked up some small but old bugs that are still not fixed and started working
<Kubuxu>
on the also.
<Kubuxu>
s/the/them
<richardlitt>
Good job on refactoring and bugs
<richardlitt>
And thanks so much for the code review
<richardlitt>
You are awesome. :)
<richardlitt>
Also the long description thing, sweet move.
<Kubuxu>
Thanks ;D
* haad_
is still a fan :)
<Kubuxu>
I don't think anyone has questions to me, just joined back.
<voxelot>
This week I did a bit of js-ipfs documentation work. Updated the unixfs-engine readme, started 'files' core-api documentation on interface-ipfs-core. Made dignifiedquire draw a flow chart :)
<voxelot>
I updated the exporter part of the engine a bit and now will be working to make the export a duplex object stream. Also working on tar archiving and gzip compression options. I continued to work on js-ipfs http and updating the core, more work needs to be done to get the interfaces compatible for js-ipfs-api and core. Going to test loading a video to a page
<voxelot>
with js-ipfs core 'cat' in the browser this week.
<voxelot>
============EOF=============
<Kubuxu>
daviddias: ipfs daemon --offline - runs HTTP API but doesn't connect the swarm
<richardlitt>
+1 for compression options.
<daviddias>
Kubuxu: got it, that is sweet :D (we do a similar thing in js-ipfs, but call the core code directly instead)
<richardlitt>
Would you like help on 'files' in core-api?
<richardlitt>
I would like to have something to point people to if they want to help out.
<richardlitt>
Sweet. I'll point to that issue.
<voxelot>
made some updates but haven't pushed, waiting to update core a bit
Foxcool has quit [Ping timeout: 276 seconds]
<Kubuxu>
if you want to use locally available block (via gateway) but don't want to ipfs connect remotely
<richardlitt>
Are you going to go with the bunny or Sintel?
ljhms has quit [Read error: Connection reset by peer]
arajakul2 has quit [Ping timeout: 252 seconds]
<richardlitt>
Ok. Two more. @whyrusleeping are you ready?
<voxelot>
ohh bunny
<whyrusleeping>
ya, sure, you betcha
<richardlitt>
go
<whyrusleeping>
## whyrusleeping update
<whyrusleeping>
This last week I spent a lot of time debugging and fixing the hanging issue with yamux. This is the issue that causes (in at least 90% of observed cases) the gateways and other nodes to hang when simple requests are made on them. I have a patch in place and am waiting on upstream code review to get it pushed in officially.
<whyrusleeping>
During that process I also did a bunch of gx work, I refactored the dependency tree of go-stream-muxer to be more flat, making updating that area of the code easier, and also made `gx deps --tree` much more visually pleasing.
<whyrusleeping>
I also fixed and pushed up a perf improvement on go-multiaddr. Previously to create a multiaddr from some bytes, we converted it into a string, and called `NewMultiaddr` on it which converted it back into bytes. This was eating up an unecessary amount of CPU time on the gateways.
<whyrusleeping>
This week I plan to continue on with go-libp2p fixes, and I also am planning on doing some light bitswap work. Next week I will be out on vacation so make sure you poke me soon if you need anything done before june.
<richardlitt>
whyrusleeping: where is the CR you are waiting for?
<richardlitt>
Are you waiting for someone in particular, like jbenet?
<noffle>
Berlin travel and being sick consumed a lot of my time this sprint. I still managed to review some go-libp2p PRs and make progress on some go-ipfs bugfixes. I also wrote an IPFS resolver that uses Twitter as a transient record store (ipfs-twitter-resolver). I also collaborated with @RichardLitt a bit on his standard-readme project and my own [common-readme](https://github.com/noffle/common-readme) project. This
<noffle>
sprint is more helping out on go-ipfs and js-ipfs where ever help is needed.
<richardlitt>
ipfs-twitter-resolver is awesome
<richardlitt>
You should write a blogpost, or we could write one together
<richardlitt>
Thanks a ton for the std-rm.md help
<daviddias>
Are common-readme and standard-readme converging together?
<noffle>
richardlitt: thanks and you're welcome
<daviddias>
or two different projects with different goals?
<richardlitt>
No. Philosopical differences.
<noffle>
daviddias: they have different goals
<noffle>
ha
<richardlitt>
common-readme could be a subset of some of the standard-readme stuff, though
<noffle>
we're trying to make them as compatible as we can
<richardlitt>
yep.
<noffle>
std-readme wants to be a rigid format for all langs and all projects, and common-readme wants to be for node modules in particular
<noffle>
I can elaborate more after sync if you want
<noffle>
richardlitt: yeah we can arrange a blog post thing -- let's chat post-sync
<whyrusleeping>
That failure has been around for a while...
<whyrusleeping>
i'm honestly not sure what causes it
<whyrusleeping>
i think it might be resource consumption related
<haad_>
omg!
<haad_>
I just got ipfs-log running in the browser (and nodejs) with js-ipfs!
<haad_>
hooray daviddias dignifiedquire voxelot and everyone who's been working on this
<daviddias>
wowowowow :D :D :D
<haad_>
that is amazing!
<vijayee>
slow clap
<richardlitt>
Woow!
<dignifiedquire>
woooooo
<richardlitt>
haad_: Add that to the newslette rpls
<richardlitt>
:D
<voxelot>
haad_: grats. is your browser on fire?
<dignifiedquire>
whyrusleeping: any progress on browser things on teamcity?
<daviddias>
and it really worked 'almost at first try', been chatting with haad_ for the last 30 minutes and other than a minor change here and there (webpack conf, etc), it seems it was straight forward
herzmeister has quit [Quit: Leaving]
<dignifiedquire>
haad_: you have to show us in the apps hangout
<haad_>
richardlitt: not yet. there's still some "hacks" around.
<dignifiedquire>
haad_: is it using a single instance or multiple?
<daviddias>
yeah, save that for next newsletter
<daviddias>
dignifiedquire: single
<whyrusleeping>
dignifiedquire: nope, i have no idea about getting that working
<dignifiedquire>
:'(
<whyrusleeping>
dignifiedquire: if you can get your tests running in a docker image, i can work from there
<noffle>
does go-ipfs' t0030-mount.sh pass locally for anyone? I've always had this fail locally (unable to mount, since it can't find my test node's pubkey on the dht)
herzmeister has joined #ipfs
jaboja64 has joined #ipfs
rendar has joined #ipfs
<Kubuxu>
noffle: do you have FUSE up and running?
<noffle>
Kubuxu: yes
<noffle>
Kubuxu: ipfs mount in day to day use works fine
<lgierth>
i think we skip fuse tests in ci
ygrek has quit [Ping timeout: 246 seconds]
<lgierth>
NOFUSE
<noffle>
ah ha
<noffle>
surely everyone isn't just not running sharness tests locally
Protocol_under has quit [Quit: Teleported with a cheezecake]
Proto_type has left #ipfs ["Teleported with a cheezecake"]
<ipfsbot>
[go-ipfs] noffle created local-mount-test (+1 new commit): https://git.io/vrnHv
<ipfsbot>
go-ipfs/local-mount-test 305cf12 Stephen Whitmore: Make t0030 use iptb for consistent test passing....
<whyrusleeping>
Kubuxu: your node was storing a large amount of provider entries and wantlists
<whyrusleeping>
lol
<whyrusleeping>
we should probably flush some of that to disk, or something
<ipfsbot>
[go-ipfs] noffle opened pull request #2707: Make t0030 use iptb for consistent test passing. (master...local-mount-test) https://git.io/vrnHP
<Kubuxu>
It still is :p
Bat`O has joined #ipfs
ashark has joined #ipfs
<ipfsbot>
[go-ipfs] Kubuxu pushed 1 new commit to feature/MFSStatsHashOnly: https://git.io/vrnQ7
<ipfsbot>
go-ipfs/feature/MFSStatsHashOnly 7e71d4b Jakub Sztandera: Incorporate better moreThanOne function...
<ipfsbot>
[go-ipfs] Kubuxu force-pushed feature/MFSStatsHashOnly from 7e71d4b to 94f1922: https://git.io/vrn73
<ipfsbot>
go-ipfs/feature/MFSStatsHashOnly 94f1922 Jakub Sztandera: Incorporate better moreThanOne function...