-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Peer Friends #2288
Comments
Relevant prior art form go-ipfs: v0.4.20 shipped a concept of "important" connections:
|
I created an issue in js-libp2p that discusses peer tagging to achieve this, libp2p/js-libp2p#369. We could take the list from Another approach I started thinking about was adding support for definable topologies. While more generic, I think they could serve this use case as well. |
I suggest calling this config value something more informative than Friends. Nothing occurs now though 😅 The Conn Manager should be the piece of code that handles this. Note, today you can achieve 90% of this today by adding these peers to the Bootstrap list, as it will try to reconnect if the connection got dropped every 10s https://github.com/libp2p/js-libp2p-bootstrap/blob/master/src/index.js#L40 (the other 10% is because the connections do get dropped, which means you need to pay the cost of dialing again) |
"Bungee Cord Peers" ? |
Related: ipfs/kubo#6097 (comment) |
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. This can be accomplished by tagging friend peers with the |
Can we come up with a solution and track progress on peer "friends" in IPFS?
What is that?
The idea is that friendly peers maintain a persistent connection with each other that is immune from connection manager GC.
Why is it useful?
swarm.connect
)What would need to happen?
Proposal (open to suggestions/changes):
Addresses.Friends
@lidel @Stebalien @daviddias @jacobheun @raulk @olizilla
The text was updated successfully, but these errors were encountered: