tabcat

i think it would be worth to encode data ourselves using one of the dag encoding libraries like `@ipld/dag-cbor`. having control of the storage format would mean using the ipfs...

@CSDUMMI I dont have any others in mind, but i know users do and it could be made easier.

I think separating the manifest into its own new class/data type would be good. Meaning it would be similar to the db address data type and would be used to...

`open` seems best imo. you are opening a local replica, which may or may not exist yet, for a manifest that was created or fetched. it seems like you might...

Interesting idea for a new address format: `//orbitdb/` and the corresponding manifest structure from cid root would be: `{ orbitdb: { : { type, access, [meta] } } }` Currently...

@chrispanag yes we now traverse the next field as well although im not sure we are done refactoring the replicator :smile: there is also some work from haad that could...

> We should stick to // format as this is the standard convention in the IPFS/libp2p (and others) ecosystem. We can drop the /name part from the end and put...

You could still build massive bundled manifests if you wanted, they would just need to be separate blocks, so they each get their own cid and then refer to each...

After reading about multiaddrs a bit im assuming the convention is more to do with prefixes like `/ipfs/`, `/ipld/`, and `/ipns/`.

I'm not sure of the reason but I'd like it to handle any datatype that can be encoded in CBOR which may already be the case; the CBOR codec used...