tabcat

no

The manifest in the address is not able to be fetched, this most likely means a connectivity issue between the ipfs nodes. We are likely to change the api a...

It's possible the manifest is not being resolved from the address which would hide the second issue of trying to open a docstore as a keyvalue store.

Its from not being able to resolve the manifest from the address. The machine with the manifest data cannot be reached. https://github.com/orbitdb/orbit-db/issues/919#issuecomment-932414698 I'll add a better error message.

It should happen automatically. Are you reproducing this behavior on a regular basis?

Hi Zorinik, replicating stores has always been somewhat difficult (at least for me). It's good that you know the nodes can transfer files/talk to each other. I think the issue...

Hi @aspironical When is this the case? My thought is that if there is an identity that doesn't fit this convention it, then it should be changed so it does....

Connection errors logged to console in the browser are pretty common with ipfs/libp2p and most of the time arent the root issue. Not being able to fetch the manifest is...

The only person I remember hearing trying this would be @holmesworcester im sure this has been brought up in libp2p issues

In #967 the error seems to originate from https://github.com/ipfs/js-ipfs/blob/1082fce9b2b027b6e176b8807d84b21f1358f296/packages/ipfs-http-client/src/block/put.js#L22-L38 as a result of https://github.com/orbitdb/orbit-db-io/blob/736bb888f991e436be32033412f1a84d9a0745f5/index.js#L96-L103 it needs to be handled in one of the two places. I'd rather it handled in...