Steven Allen

Recommended maximum block size: 1MiB. This isn't a philosophical question, its a question of what's likely to work and what isn't. We have to pick a number and we should...

Really, I think we need both. * For browsers: `ipld://Cid/path`. This is technically incorrect as the "Cid" isn't an "authority". However, we already have to use this format for `ipfs://`...

# Proposal: Simplicity over UX Given that others are, hopefully at least, *not* using this format, we could just say that all paths must use link *indices*. We'll need to...

# Proposal: Named xor Unnamed If we require that all links in an object either be named or unnamed, we can redefine the structure to either have a map of...

> Is this a new standard or is this CIDv2? I'd say it's a new thing. Really, it's just a binary format for `/ipld/Qm.../a/b/c`. > What do we do about...

> Do you mean something like resolve('/hamt//deep/path') and then the resolver will take care of it? If that's a yes, I'm in favour of that. Yes (although we might want...

> So you swap out the IPLD Resolvers depending on your needs/new development. I just want to make it clear that, no matter *what* we do, `/ipld/Qm../a/b/c` *must* mean the...

Use-cases: * Queue that starts at an arbitrary offset. Currently, this offset will force a minimum depth of `log(offset)`. This is a problem for pretty much all of our epoch-based...

This could be useful for automatic prefetching: select a file and recursively execute the prefetch selector embedded in the file's metadata.

It's clearly marked as experimental and I doubt many users are using it. Mostly just users who're also using the "raw leaves" feature.