GitLab

Co-authored-by: Jessica Schilling <jessica@protocol.ai>

This adds docs in form of longer description that is displayed
when --help is passes on the CLI.

While at it, unified some language to match fields in the config file
and other places + included some tips and best practices which should
improve onboarding experience.

chore(deps): bump github.com/libp2p/go-libp2p-pubsub from 0.4.0 to 0.4.1

chore: update go-ipfs-pinner dep

Bumps [github.com/libp2p/go-libp2p-pubsub](https://github.com/libp2p/go-libp2p-pubsub) from 0.4.0 to 0.4.1.
- [Release notes](https://github.com/libp2p/go-libp2p-pubsub/releases)
- [Commits](https://github.com/libp2p/go-libp2p-pubsub/compare/v0.4.0...v0.4.1)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore(deps): bump github.com/ipfs/go-graphsync from 0.5.1 to 0.5.2

pin remote commands are comma delimited on the CLI only

fix: remote services ls always return a list

fix: improved error message on broken CIDv0

feat(gw): URI router for Web API navigator.registerProtocolHandler

Additional tests to ensure there are no regressions, as this will be
used by browser vendors in the future.

URL.Query() will already decode the query parameters

This makes ?uri= param able to process URIs passed by web browsers
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler

This commit adds support for requests produced by navigator.registerProtocolHandler on gateways. Now one can register `dweb.link` as an URI handler for `ipfs://`:

```
navigator.registerProtocolHandler('ipfs', 'https://dweb.link/ipfs/?uri=%s', 'ipfs resolver')
```

Then opening `ipfs://QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR` will produce an HTTP GET call to:

```
https://dweb.link/ipfs?uri=ipfs%3A%2F%2FQmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR
```

The query parameter `uri` will now be parsed and the given content identifier resolved via:

`https://dweb.link/ipfs/QmbWqxBEKC3P8tqsKc98xmWNzrzDtRLMiMPL8wBuTGsMnR`

feat(gw): DNSLink names on https:// subdomains

This kinda enables to run their custom DNS resolver with custom
tlds/names that are independent from the public DNS network.

Escape non-printable characters in user output

docs: fixed typos and commas in blocks/blockstoreutil's RemoveBlock comments

docs: update IPFS Desktop maintainer

Bumps [github.com/ipfs/go-graphsync](https://github.com/ipfs/go-graphsync) from 0.5.1 to 0.5.2.
- [Release notes](https://github.com/ipfs/go-graphsync/releases)
- [Changelog](https://github.com/ipfs/go-graphsync/blob/master/CHANGELOG.md)
- [Commits](https://github.com/ipfs/go-graphsync/compare/v0.5.1...v0.5.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

update go-libp2p to v0.13.0

As suggested in
https://github.com/ipfs/go-ipfs/pull/7847#discussion_r551933162

Closes #7792

Problem statement and rationale for doing this can be found under
"Option C" at: https://github.com/ipfs/in-web-browsers/issues/169

TLDR is:

`https://dweb.link/ipns/my.v-long.example.com` can be loaded from a
subdomain gateway with a wildcard TLS cert if represented as a single
DNS label: `https://my-v--long-example-com.ipns.dweb.link`

Replaces control characters and non-printable characters with escape sequences, in any fields that are printed by the CLI, which could have been user input.

Output from `ipfs cat` is unchanged.

Closes #7824

update version to 0.9.0-dev

chore(deps): bump go.opencensus.io from 0.22.4 to 0.22.5