Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: Using libp2p for network-related communication #2198

Open
mkg20001 opened this issue Sep 15, 2019 · 13 comments
Open

Proposal: Using libp2p for network-related communication #2198

mkg20001 opened this issue Sep 15, 2019 · 13 comments

Comments

@mkg20001
Copy link
Contributor

libp2p aims to be a catch-all solution for all things p2p-network.

That means that adding components such as mDNS doesn't require any careful development for each solution on it's own, but rather enables application creators to pick from a gigantic library of existing modules that implement capabilities such as mDNS, kademila DHT, TCP and UDP networking support

I'm making this proposal, to see whether and how it can be implemented

The plan to enable it would be to:

  • First integrate py-libp2p networking and run a seperate swarm besides the current swarm, but on the same port (this should be possible by first checking if the incoming data is multistream or TLS)
  • Integrate all custom networking components into the libp2p swarm using modules
  • Switch the other swarm off for good, once the functionality of the libp2p swarm is confirmed and a majority of users has upgraded

// cc @filips123 @imachug @blurHY

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019

Why only libp2p ? Why not IPFS (containing IPLD, etc.) ?

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019

Do you guys know IPFS can replace all of lower-layer protocols ZeroNet use ?

@mkg20001
Copy link
Contributor Author

Do you guys know IPFS can replace all of lower-layer protocols ZeroNet use ?

Do you know that a migration is performed step-by-step rather than full-force at an instant?

You can go ahead and make a separate network on top of IPFS, but if you want to link them, do it step-by-step

@mkg20001
Copy link
Contributor Author

You're 16

By that age I was already smart enough to know, that most of the time I might not be the most right in any given circumstance. Honor that. Otherwise we'd just be 2 teenagers yelling at each other.

I'm not saying the "just libp2p" idea is the best. I'm just saying: It's what seems feasible at the moment.

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019

Do you guys know IPFS can replace all of lower-layer protocols ZeroNet use ?

Do you know that a migration is performed step-by-step rather than full-force at an instant?

You can go ahead and make a separate network on top of IPFS, but if you want to link them, do it step-by-step

We need radical change, and because it's easier to use IPFS directly.

You're 16

14/15, not 16

It's what seems feasible at the moment.

Yeah, IPZN seems not feasible this moment, because pubsub is WIP

@mkg20001
Copy link
Contributor Author

We need radical change, and because it's easier to use IPFS directly.

If you need radical change, you first need to establish it in between a select group of supporting individuals and not try to force it large.
This allows you to prove your methods work, since everyone will be skeptical at first.
Changing upstream has consequences, so everyone has got a legitimate reason to be skeptical and it's not just nilly-willy.

Come back once you have something working or try it step-by-step

Just fyi, I'm trying the same thing with a friend in a completely non-code project. So I know what I'm talking about.

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019

a select group of supporting individuals and not try to force it large.

Will you be one of the group

@mkg20001
Copy link
Contributor Author

Will you be one of the group

Right now I have my head stuck in other things.

Like, paperwork (taxes), projects (animus), more projects (see my gh profile), work, more work

@purplesyringa
Copy link
Contributor

We need radical change, and because it's easier to use IPFS directly.

It might be easier to make a new IPFS-based project (like what IPZN seems to be about), but we're looking for a way to persist compatibility with classic ZeroNet sites.

14/15, not 16

Age doesn't matter.


Seriously, you're shouting "I know, I know!" but don't even try to code it yourself... We can't just believe everyone when they say "this will work, I promise... maybe", we don't have enough time and contributors for that. We should instead start with simple and obvious stuff and switch to something complex later.

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019

don't even try to code it yourself.

I'm waiting ....

@purplesyringa
Copy link
Contributor

Waiting for what? Many people here told you to go away until you have something to show, whom are you waiting for?

@mkg20001
Copy link
Contributor Author

I'm waiting ....

He's talking about you coding it. Not him.

@blurHY
Copy link
Contributor

blurHY commented Sep 16, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants