I spent too long to figure out I was putting mainnet addresses to regtest node, errors weren't helpful at getaddressinfo and validateaddress.

Seems like a good first issue to augment the error messages when prefix/hrp don't match current network.

Right now, Syncthing seems to always use LF for line endings in config.xml and .stignore. This is a problem in Windows when trying to edit those using the built-in Notepad, which until very recently had no support for other line endings than CRLF. Support for them has only been added in the very recent versions of Windows 10.

The problem is that when opening those files in Notepad under old

If we config the cache options in the config file, then it will be overwritten.

**Describe

Summa

Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Forking ipfs/js-ipfs#3252 (comment) into separate issue.

Looks like some of our API calls return values that refer to same ArrayBuffer, which in turn causes one of the encoder functions https://github.com/ipfs/js-ipfs/tree/master/packages/ipfs-message-port-protocol/src to add it to the transfer list twice and error on postMessage.

In Settings : 'Add a new side account' button

Step #2 in Side account creation

(a very light & quick version of onboarding, with only nickname step)
![side account mode copy](https://user-images.githubusercontent.com/37345040/99953009-dd7db900-2d80-11eb-9f6f-e

For classes declared with struct, forward declarations should also use struct. Currently, only struct Message violates this in a few header files (2 or so?).

I come from the OpenBazaar project and I am new to go-libp2p and go-ipfs. Are the examples that use libp2p in a production environment? Where's the best place to learn libp2p by example?

I just recognized in the German translation that the truncation of the new trigger price feature is not configured properly. Also the provided text is not properly translated (I'll take care of this on Transifex myself).

%Yixc7LlyDjFyXyS9NQcSNtT/ItGTAl9UPbrCVuWsx/0=.sha256
This is how it should look:

just switching out H1 already helps but shouldn't be done alone:

Right now, IPFS Desktop installs system-wide protocol handlers (dweb, ipfs, ipns) which converts ipfs://<cid> URI to gateway URL and opens that in default browser.

It is fine, but may be confusing on the first use.

We could improve this behavior and show a dialog window, where user can choose how to open IPFS resource via radio-button-like selector:

• open from public gateway in the d