GitLab

This way, users can disable transports (especially QUIC), and set muxer/security
transport priorities.

see https://github.com/ipfs/go-ipfs/issues/6402

Hopefully, we can get the community to start pooling knowledge of how to run
go-ipfs in production.

* Explain _why_ it exists.
* Explain how it can be used.

MVP for #6097

This feature will repeatedly reconnect (with a randomized exponential backoff)
to peers in a set of "peered" peers.

In the future, this should be extended to:

1. Include a CLI for modifying this list at runtime.
2. Include additional options for peers we want to _protect_ but not connect to.
3. Allow configuring timeouts, backoff, etc.
4. Allow groups? Possibly through textile threads.
5. Allow for runtime-only peering rules.
6. Different reconnect policies.

But this MVP should be a significant step forward.

Co-authored-by: Steven Allen <steven@stebalien.com>

Additional documentation for running subdomain gateway behind reverse proxy with TLS.

Mostly:

1. Remove old experiments.
2. Update reasons for features being experimental.
3. Comment on experiments that will be enabled in the near future.

1. Update go-ipfs-config to fix default datastore.
2. Update TOC.
3. Update profiles list and indicate that badger isn't experimental.

People may assume that HAMT gets enabled only for directories over some arbitrary threshold.
This is not the case. Right now it is a global setting 
which will impact the final CID of all directories produced by ipfs.add.