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?

Since we can now run interop tests against go-ipfs and js-ipfs quite easily, we could adjust some of our existing tests so that they automatically become interop tests with the right feature turned on.

Consider the recent changes to [tests::connect_two::connect_two_nodes_by_addr](https://github.com/rs-ipfs/rust-ipfs/blob/master/tests/connec

This package generates banners, used by our CLIs and also in some external repos :)

You can open new PRs against this file: https://github.com/berty/berty/blob/master/go/pkg/banner/quote.go

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