GitLab

(I plan on adding support to the http client, at least)

We just changed ID/"id" to IDENTITY/"identity" to match the multicodec table and
avoid confusion with peer IDs, CIDs, etc.

Unfortunately, this breaks the `--hash=id` flag. Luckily, I'm pretty sure
nobody's actually using this. As putting a block with an identity hash is
useless. If they are users, we can go about adding in backwards compatibility
hacks later.

And fix for peer ID formatting changes.

fixes https://github.com/ipfs/go-ipfs/pull/6222#issuecomment-483479039

See https://github.com/ipfs/go-ipfs-http-client/pull/10/files#r269268326

Otherwise, we can get random panics form dereferencing nil pointers.

This can be trivially implemented by the end-user if desired. The best the
CoreAPI can do is name the file with it's own hash so this isn't really all that
helpful either.

Note: This differs from js-ipfs because _there_, all files have paths (even
outside directories).

It's complicated. We need to carefully think through how sizes work.

(path can't represent relative paths)

(also, fix some error versus fatal nits)

1. Avoid `ipld.Link`. This is a protodag specific thing that will go away in
   future IPLD versions.
2. Avoid exposing the underlying file types. The user shouldn't care if they're
   dealing with a hamt, etc.
3. Add a field for a symlink's target.
4. Rename LsLink to DirEntry to better this type's role.

License: MIT
Signed-off-by: Łukasz Magiera <magik6k@gmail.com>

License: MIT
Signed-off-by: Łukasz Magiera <magik6k@gmail.com>

Switch _back_ to the 0.4.18 style of peer IDs while we figure things out. See
https://github.com/libp2p/specs/issues/138.

License: MIT
Signed-off-by: Steven Allen <steven@stebalien.com>