libp2p | Libraries and utilities

I am trying to make this example work. It is supposed to create two nodes with mdns support. Mdns is supposed to announce the peer every second, each peer is setup to print a statement once a peer is found.

When running it, the console output is merely empty. It prints out some garbage error in my concern: (node:51841) ExperimentalWarning: Readable[Symbol.asyncIterator] is an experimental feature. This feature could change at any time

How do i enable debugging log so that i can try to understand what is going on under the hood ? I would like to verify the mdns announce packets are issued, and possibly received, or not.

Alternatively, i am trying to use the bootstrap module to begin over wan peers, though expect it to be much slower, thus i would prefer to use mdns.

I tried to add various configuration and modules without much success, it is not clear to me if i am required to use the gossip module if i only want to announce some data on the dht. stuff like that.

any help is appreciated.

I'm trying to implement libp2p inside an electron application, which (obviously) has node support turned on.

I tried catching errors with the following code:

I'm using this code to play around with IPFS in the browser. I'm wondering how I can access the ip addresses of the webRTC peers? or even know if the peers are actually webRTC, or http peers?

I'm using this code in the browser. It seems to be connecting to ipfs.io via http?. I'm looking to only connect to DHT webRTC peers. I'm guessing I need to pass some option to Ipfs.create? I see an example of custom libp2p here but the amount of options are overwhelming. https://github.com/ipfs/js-ipfs/blob/master/examples/custom-libp2p/index.js

I'm trying to decode the buffer stored in the addr key found in the output returned by the IPFS swarm peers function back to the original string. I tried to use the toString() method with all supported encodings, but the output I'm getting is not correctly decoded.

I think the underlying connection of a stream should have a direction, so how do I know the host is at a server side or client side when the host gets a stream in go-libp2p?

for example, I want to know how I can get the information that the host is at the server side or client side according to the underlying transport connection of a stream in the stream handler function.

I am using IPFS and trying to understand its structure.

ISSUE: 1 The issue I am facing is that when I am trying to shrink the storage size of IPFS (for testing it is taking so long time, hence I just want to shrink File System for a while) but is unable to shrink.

I tried to configure the config file by changing the StorageMax limit using this command

ipfs config Datastore.StorageMax 1GB

but still it does not work, it accepting (ipfs add ) the files after the 1GB also, why he is not limiting the file-storage?

anyone, please suggest me How to reduce file-system size?

ISSUE: 2 Even in case of IPFS's default storage limit (Which is 10 GB), I saw when I am adding the files on IPFS it is not stopping to store files after crosses 10GB (which was limit). It should not be cross after the limit ends, for this what to do?

below is the config file

I need to pull this commit into my go project.

I've tried multiple versions of go.mod:

my question refers to the libp2p library in golang: https://github.com/libp2p/go-libp2p

This video explains the background: https://www.youtube.com/watch?v=hP0hSZ7E7_Y

The peers in the network communicate via buffered streams rw. For each new connecting peer there is a new stream created that connects him to an existing peer using addresses. This means there are multiple streams but not all peers are directly connected with each other. Using those streams, the peers can read and write data from it via

rw := bufio.NewReadWriter(bufio.NewReader(stream),bufio.NewWriter(stream))

by writing messages `rw.WriteString("message"),rw.Flush()``

and reading this messages via message := rw.ReadString(rw).

As the peers are not all connected, they only receive messages from directly connected peers and not even all of them if there are multiple connections.

Exactly this problem is mentioned in the video, around time 09:45. The author of the video says that this could be easily modified to send messages not only to directly connected peers but also to multiple hosts. But how can this be done?

My goal is to send message from one peer and that all other peers in the network, also the not directly connected ones, can receive (and answer) it.