-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Comments
Why only libp2p ? Why not IPFS (containing IPLD, etc.) ? |
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 |
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. |
We need radical change, and because it's easier to use IPFS directly.
14/15, not 16
Yeah, IPZN seems not feasible this moment, because pubsub is WIP |
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. 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. |
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 |
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.
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. |
I'm waiting .... |
Waiting for what? Many people here told you to go away until you have something to show, whom are you waiting for? |
He's talking about you coding it. Not him. |
...for a ipfs feature
…________________________________
From: Maciej Krüger <[email protected]>
Sent: Tuesday, September 17, 2019 1:36:32 AM
To: HelloZeroNet/ZeroNet <[email protected]>
Cc: blurHY <[email protected]>; Mention <[email protected]>
Subject: Re: [HelloZeroNet/ZeroNet] Proposal: Using libp2p for network-related communication (#2198)
I'm waiting ....
He's talking about you coding it. Not him.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#2198?email_source=notifications&email_token=AH5CPRGQLUJDUOOSVZIBCHDQJ672BA5CNFSM4IW4BHBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6Z5MCY#issuecomment-531879435>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AH5CPRCQD6O53XR4BGMK2NTQJ672BANCNFSM4IW4BHBA>.
|
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:
// cc @filips123 @imachug @blurHY
The text was updated successfully, but these errors were encountered: