Steven Allen

I've edited the issue to: 1. Make it clear that this is just a proposal. 2. Explain the motivation.

> Is there some timeline in which we think we can back off of the second point? Never, unfortunately. > For instance, is there a future date at which I...

Based on https://github.com/ipld/specs/blob/master/IPLD-Data-Model-v1.md, we should be using the canonical encoding. The data model doesn't distinguish between different float/int types at the _encoding_ level.

I take it that's just everything concatenated? Works for me! Also note: utf8(`/`) is the multicodec for "paths" (:trollface:), so _every_ part of this is multicodec prefixed. Also related: https://github.com/multiformats/multiformats/pull/55.

Wait, so you're not just concatenating a CID and a path? You're suggesting a new object type, stored as an "inline/identity" CID? I mean, that works, but it seems like...

I guess... My concerns are: 1. Unless handled "specially", these links will appear to be new blocks and would have to be handled at a _higher_ layer (e.g., ADL). I...

> Both Browse and Lookup return immediately. The go routines started by these methods (including the Go routine that reads from the connection) is stopped eventually after the context is...

> Although the API seems to suggest otherwise, it's only possible to call Lookup / Browse once per Resolver instance, as both of them start reading from the UDPConn (and...

Docker uses a separate user namespace unless you disable that (with, e.g., `--userns=host`).

It has never been marketed as censorship proof or uncensorable. Making the IPFS _protocol_ itself uncensorable is a non-starter. If you wish to discuss this, please make a post on...