Haad

Thanks for the suggestions @joelamouche! I like them and agree these points should be emphasized in the docs. Leaving this open for contributions and to get to it at some...

@mistakia thank you for opening this discussion! This is indeed something we should look at and see how we can improve the current implementation. Great thinking here @mistakia as to...

I think so, yeah 👍 It was added back in the day, when es5->es6 transition was still happening. We're past that.

> Too many messages in the same channel makes it slow. We know. No need to specify which known issues there are. Pointing the user to the known issues is...

Thanks @Andlinks-Yourturn for opening the issue! I'm not sure what exactly you mean by "have nodes synced by default", perhaps you can elaborate what problems you're having? As for getting...

Got it. So there's couple of things you need to do: First, we currently don't have a support for running a separate IPFS daemon to be used with OrbitDB, but...

@dibu28 thanks for reporting the issue! This should now be fixed in master and release [0.0.15 on npm](https://www.npmjs.com/package/orbit-db-cli). Latest ipfs and orbit-db contains the fix. Re. the other error mentioned...

I think @mistakia's answer is a good one as one first needs to consider the underlying storage and transport systems (IPFS vs. Dat) as that's more the defining factor for...

Related to: orbitdb/orbit-db#342, orbitdb/orbit-db#474, orbitdb/orbit-db#212

@fazo96 has already done great job at explaining the persistency, but I wanted to add a note that currently js-ipfs doesn't have GC, so nothing gets removed meaning everything is...