tabcat

Testing this out in https://github.com/orbitdb/orbit-db-io/issues/33

js-ipfs doesnt currently garbage collect, and the error you see is not behavior seen if the entries were garbage collected. i dont know the issue here unfortunately and everything given...

https://github.com/orbitdb/orbit-db-control-center i thought the github link on the site would lead to the repo but it leads to the main orbit-db repo.

The errors on load seem fine. There can be a lot of errors from ipfs about connections failing. Also everything seems to be working for me. I created a database...

the cid encoding is different, as well as the actual encoded hash in this case. a different manifest is being created with differing configuration. you need to open the db...

the hash is a dag object and is not an ipfs file. they are a bit different and some tools that can read from ipfs can only read ipfs files...

You bring up an excellent point about opening addresses that use different encoding! I believe how our discovery system works currently they will never find each other! We need to...

> Got it, so it's the discovery system that is restricted to the z prefix only. not quite, its that only peers using the same base encoding for the address...

i would try splitting up the database up into smaller databases in a deterministic manor, so their addresses can be known.

https://github.com/orbitdb/orbit-db/blob/main/API.md#orbitdbcreatename-type-options > What if i "create" a database that already exists locally? this is will error without the overwrite option present. use orbitdb.open to open existing databases. > What if...