libp2p

Here is what I've noticed:

• ipfs.block.get
  • docs say it returns a Block, but it returns a Uint8Array
  • docs are missing the preload option
• ipfs.block.put
  • docs say it can also take a Block as a parameter, but it can only be a Uint8Array
  • docs say it can take a cid as an option, but the implementation ignores such a parameter
  • docs say it returns a Block, b

When a contact is already added, open the contact profile or the existing conversation

The error check is done here: https://github.com/berty/berty/blob/097eb0229f22e2abce3addd750c8dce98e92845f/js/packages/components/modals/InvalidScan.tsx#L126

We shouldn't show the invalid scan modal but navigate instead

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?

@D4nte commented on Thu Apr 22 2021

When not passing any filter in the browser, I understand that filter dnsWsOrWss is being used.
When trying to connect to an ip4 ws address, it fails due to the filter, however the error returned by libp2p is very obscure (see below).

Would there be a way to make this error point to the filte

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.

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

In pubsub, allow msgIdProvider to fail (either through a exception, or a ValidationResult), and if it fails, completely skip the message (don't store it in the seen cache, etc)

More info: status-im/nimbus-eth2#3043

Libp2p allows to configure a user agent via libp2p.UserAgent(...).

I'm thinking of using nebula-crawler/{version} while {version} should come from a central source.