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?

This was cut from the v0.2.0 release for present time constraints however making ipfs-http more accessible as "the" ipfs binary would make the project more accessible to anyone just wanting to try it out. At the moment I see the following obstacles:

• http/README.md has no tutorial on how to try out ipfs-http
• ipfs-http supports only `i

This meta issue contains various ideas that may never be implemented, it's a good place to put things that could create useless noise in the issues section

Doc

• add various demonstration gifs in README.md files (#2080)
• add graphs (flow, DAG) to explain some particular parts

Code Quality

• switch moment.js usage to day.js and remove moment.js (#2174)

Bots

There are many places throughout the codebase where redundant type information is included in the creation of a struct. This causes style errors to be logged in vim-go, and it would be nice to alleviate the extra verbosity of these statements.

A bonus would be to enable a check on this in the linter.

Push identify is missing and needs to be implemented as per the spec - https://github.com/libp2p/specs/blob/master/identify/README.md#identifypush.

Replace gomobile logger (GoLog) by a better binding for ipfs-go-log -> native logger.

Currently, all logs including their metadata are displayed by native logger as a plain text string with GoLog as namespace/tag and error as level. Logs are less readable, filterable, sortable, etc...

We need to forward each metadata (level, namespace, timestamp, etc...) and the log itself from ipfs-go-log t