Winterhuman

@lidel Any update on getting `classic`? It seems https://forum.snapcraft.io/t/ipfs-classic-request/28516/9?u=lidel hasn't progressed

It's a shame there's no Flatpak, last time it was discussed that I know of was https://github.com/ipfs/ipfs-desktop/issues/686

@Stebalien Doesn't Bitswap use multihashes now, or should this issue still be open?

Leaving a comment to state my support for this. The project I'm part of (IPNS-Link: https://github.com/ipns-link/ipns-link) could definitely benefit from this, especially the fact that IPFS Gateways can shorten the...

What about constructing CIDv2 like this: Example CIDv1: ``` multibase: base32 multicodec: CIDv1 multicodec: DAG-PB multihash: sha2-256 256 ``` Alternate CIDv2: ``` multibase: base32 multicodec: CIDv2 multicodec: DAG-CBOR multihash: identity...

@sharp2448 go-ipfs v0.13 will have a ResourceManager so rate limiting will be possible pretty soon.

@Stebalien Any chance this could be re-opened? Kubo is one of the few applications which doesn't store config files in `~/.config` in my case (specifically to check for `~/.config/ipfs` first,...

@Jorropo Using `IPFS_PATH` wouldn't be the same, it's about making `~/.config/ipfs` be detected by default alongside `~/.ipfs` (basically the equivalent to `IPFS_PATH=.config/ipfs,.ipfs` as the default mode)

That could work as well, an alias would be a lot easier than removing `ipfs refs` (and it would be more backwards compatible as well)

After looking at `ipfs refs`'s functionality closer, moving the whole thing under `ipfs repo` would make no sense. I think Jorropo's idea is the best moving forward