tabcat

@Independent-Eye2446 you can add and remove writers with the 'orbit-db' access controller. i think this can actually be closed.

This often happens when the two ipfs nodes are not able to communicate. Here is a testing library we use that includes minimal ipfs configuration for nodejs instances to talk....

He is an [example for browsers](https://github.com/orbitdb/orbit-db/blob/68971f4ad8e0d414fc6c57eec1401e774bc78d43/examples/browser/example.js#L48-L72).

@nichoth try removing the `.config.Addresses`'s `.API` and `.Gateway` properties

this ipfs config is persisted so u need to clear the indexeddb data for that site to reset it. the `this.events.off` error looks very odd.

so it seems like you bring up 2 issues; an issue with replicating a certain amount of dbs from other nodes into the browser and an issue with the `db.load`...

> When the db has no data that is locally synced, the db.load() line completes, but the database stays empty. (No synchronization.) If any data has already been locally synced...

if you close one store is another store able take its place and replicate/load after? > Replicating in nodejs always works. Regardless of whether the databases are hosted in the...

so just to be clear; the issue is with browser nodes using an ipfs http api that is talking to an instance of go-ipfs. is this correct?

@kottackalsulvin is this resolved?