wngr
Joined 7 years ago
Karma
42
Submissions
45
Member since
Jan 1
Recent submissions
Comment · 4 months ago
Kudos to the n0 team shipping 1.0! Truly exciting, stellar technical approach and execution; I hope you guys will get sufficient commercial traction to keep going!
Comment · 1 year ago
It’s not nested, that’s the thing.
Comment · 1 year ago
What does that mean in the context of a Merkle tree?!
Comment · 1 year ago
Apart from small software studios with non-SaaS business models, there is just no viable local-first (offline-first with infinitely delayed sync) application category, in the consumer space. Consider military applications with heterogenous and constraint networks, where assets might need to coordinate p2p under adversarial jamming. There might be applications, where AP (choosing Availability and Partion Tolerance, cf CAP theorem) makes sense.
Comment · 1 year ago
That’s a great, nuanced view! Thanks for sharing!
Comment · 1 year ago
One might even say PATHETIC.
Comment · 1 year ago
> I remember Actyx being a rust-libp2p user, but I wasn't aware that they failed. Do you have more info? How and why? It would be great if we could learn from them.
They (we?) unfortunately never found product-market-fit. Actyx targeted the SME factory space with a p2p application platform. Turns out that developers in general don’t want to deal with the additional complexities of anything lesser than strong consistency, especially if they don’t fully drank the distribute-everything kool-aid. And SMEs don’t really bother either.
Philosophically decentralization is the right thing to do, but I’m thinking more and more that federation might actually be the compromise in the long run, at least for consumer apps. The only valid use cases for p2p edge devices with loose connectivity are in military applications.
Comment · 1 year ago
Great idea combining batman with libp2p! You guys have the heart in the right place :-).
Currently, your project seems to be an opinionated wrapper ontop of libp2p. For this to become a proper distributed toolkit you lack an abstraction to for apps to collaborate over shared state (incl. convergence after partition). Come up with a good abstraction for that, and make it work p2p (e.g. delta state based CRDTs, or op-based CRDTs based on a replicated log; event sourcing ..). Tangentially related, a consensus abstraction might also be handy for some applications.
Also check out [iroh](https://github.com/n0-computer/iroh) as a potential awesome replacement for p2p; as well as [Actyx](https://github.com/Actyx/Actyx) as an inspiration of similar (sadly failed) project using rust-libp2p.
Oh, and you might want to give your docs a grammar review.
Kudos for showing!
Comment · 1 year ago
I totally agree with you, but those shows are not what parent means.
Comment · 1 year ago
Also take a look at iroh [0]. It doesn't come with the bloat of ipfs, provides robust core building blocks. They really figured out NAT traversal.
Comment · 2 years ago
I was really impressed when I clicked the reload button -- inspiring attention to detail!
How did you create those?
Comment · 3 years ago
Issues have been deleted in the meantime ..
Comment · 4 years ago
There is quite a bit German community there incl doctors, lawyers etc.
the big hospitals are also okay, although the local youth is fleeing the island.
Comment · 4 years ago
To understand the difference between a manual and a highly industrialised process doesn’t matter here. It’s about the underlying principles that define how things work.