Adin Schmahmann

@stebalien is this related to https://github.com/libp2p/go-libp2p-kad-dht/issues/729?

> Right now, `ipfs pin add` is actually faster than `ipfs get` at fetching data To be more precise `ipfs pin add` maybe be faster at download an entire DAG...

> while ipfs get is for full downloads. `ipfs get` doesn't output to your filesystem it sends responses over the HTTP API from the daemon to the client. In order...

@T0admomo since this is a client and UX change rather than a spec one mostly I would propose what the UX should be along with the various changes that would...

Agreed that there are issues with Snap. We could ask Canonical to get us approved for classic. If there are README updates you'd like to make to add clarity beyond...

Reopening just to track the snap switch to classic mode. Brief summary: - Snap confinement makes many CLI tools (from `jq` to `go-ipfs` essentially unusable) - Removing our blessing/CI deployment...

@TheTrueShadow can you be more precise about what you're trying to do and what your expectations are? For example, I can see you're running a go-ipfs node on that has...

Agreed, from a practical perspective I'd rather only have to maintain one tool. Happy to take PRs to ipfs-check. Will also allow some feedback from the other folks who have...

Ya, because the blockstore is now keyed by multihash checking is effectively done by multihash even when the API requests by CID.

@tysonzero I get your point and your pain here around wishing you could `ipfs get bafyabc` and have the data just get pulled from Filecoin. I think part of what...