phillmac

On your consumer, take the Id output here by the producer: https://github.com/ohager/orbitdb-remote-poc/blob/master/producer.js#L34 and run this on the consumer: `await ipfs.swarm.connect('/ipfs/')` I see you are using `js-ipfs`, possibly try using go-ipfs...

Try this version of the demo. I think it's slightly more up to date: https://ipfs.io/ipfs/Qma4jzYSZkzUt4Tz4Pxr7KGupHCViaFNZh13bsEhovPkZp/

***WARNING*** I'm no longer recomending upgrading to > 0.4.23 because of broken p2p-circuit relay functionality In fact I recommend sticking with 0.4.23 as the last working version. see https://github.com/ipfs/go-ipfs/issues/7433

@Zorinik For nodejs, you need to enable listening on TCP ports in your config. e.g. ``` "Addresses": { "Swarm": [ "/ip4/0.0.0.0/tcp/4001" ] } ``` This will enable the TCP transport...

Afaik, I could be wrong, there are no plans for chalenge/response type authentication, it would be exceptionaly hard to implement via ipfs. Any encryption of the data is left as...

> This change is really major.But it could really help people to understand some part of the internals of OrbitDB. > > I have a question: > What functions should...

Try the latest version, i.e. `v0.21.3`. This seems to be fixed.

Something like this would be useful imo. I'm using this in the http api: https://github.com/phillmac/orbit-db-managers/blob/develop/src/DBManager.js If you want to formally specify an interface as a SCP I'm 1000% down to...

The assumption is you have cloned the repo, run `npm install` and `npm run build`. Then those files should exist in those specific paths.

Just out of curiosity, are you using the same ipfs instance to run both of the orbitdb instances? This tends to be buggy as pubsub doesn't work well in this...