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.

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?

Arrange the app's common assets neatly in the js/assets folder with sub-folders named by type:

• fonts
• audio (e.g notification sounds)
• images (e.g default avatar)
• etc...

And properly wire the different layers of the app (js/RN, iOS and Android) so that they can access them. For example: add a "Build Phase" in XCode that copies the sound files of the notifications to the IPA.

Note: An

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

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.

At the very least, there are this use cases:

• Announced addresses are merged with bound addresses
• Announced addresses replace bound addresses

Probably, the most flexible way of doing this is providing a hook that the application can use to return the set of addresses it deems appropriate to announce.

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