libp2p

• Version: ipfs-core: 0.14.1
• Subsystem: types, core

Severity: Very Low

Description:

in type definition put: (...) => Promise<CID>, but docs Promise<Block>

Which type is correct?

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

Misc

• add a way to configure the CLI and apps to have two loggers, a full one in JSON in a file + a filtered one formatted for console on stdout
• add i18n support on CLI help messages
• add i18n support on error message

Issues seen while migrating lodestar to latest libp2p:

• configuration page references peer store "persistence", no longer an option, should use PersistentPeerStore instead
• persistent: boolean listed in an unused interface in src/index.ts
• dialer: {...} referenced in configuration page, should instead be under connectionManager
• ...

Describe the feature you are proposing

It would be neat if there's a flag for ipfs-cluster-follow start it up and connect to the cluster, but then send a leave cluster message, remove all locally pins related to the cluster and then delete all files related to the cluster.

As there's already "run --init" I think something like "stop --cleanup" would be appropriate:

$ ipfs-

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

Here is current representation of pin.status

https://github.com/web3-storage/web3.storage/blob/277cc449efe8366a978cce6b573f24a50f5dc65d/packages/db/fauna/schema.graphql#L147-L159

Which is derived from

https://github.com/ipfs/ipfs-cluster/blob/8454cd6383170d17a95180a8d137fcaa2a63bbba/api/types.go#L52-L80

// TrackerStatus values
const (
	// IPFSStatus should never take this va

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

There are a few possibilities to improve the minprotobuf API:
status-im/nim-libp2p#651 (comment)
https://github.com/status-im/nim-libp2p/pull/647/files#r750989474

Besides what was already done in status-im/nim-libp2p#632

I noticed that when Hunter build LLVM as WAVM dependency, it builds all of LLVM.
That significantly increases build time, given that only compiler-rt is needed.
Can be fixed by configuring LLVM_ENABLE_PROJECTS option in WAVM's LLVM custom Hunter config.

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.