Viewing profile — haadcode

Can you elaborate why you think Rust is a better choice?

No, on both. See above.

> How do you know that? It's not inferrable from the DAG. Is sequencing also provided "a layer up"? I jumped the gun there and made an assumption that the value of a node is the LW…

almost! :) let me elaborate on few points. > you have to reference all of the current concurrent root nodes of the data structure, in effect becoming the new single root node corre…

The log described above is this https://github.com/orbitdb/ipfs-log

Great comments! Indeed, "sign your log appends" gives everything needed for authority. Re. transactions, from OrbitDB's perspective this would be application specific, so you could…

One great piece of writing to think about the use cases and what kind of systems and applications can be built following the concepts applied in OrbitDB is this "Local-first softwa…

Posted this in another reply above, but give this a read: "Merkle CRDTs" ( https://arxiv.org/abs/2004.00107 ).

> Last-Writer-Wins is a conflict resolution strategy that can be used by any kind of data type that needs conflicts resolved, CRDTs included. Unfortunately it's not a very good one…

There's also a Go implementation at https://github.com/berty/go-orbit-db

To clarify here, OrbitDB's core is an append-only, immutable log CRDT. While a mouthful, what is gives, is a distributed (decentralized) database operations log. Almost any type of…

The use case is shared, mutable data structures that don't rely on central coordination or control.

> I guess performance and robustness were not a priority. You'd be surprised how well JS does on both fronts, in addition to being able to run across platforms :)

> * How did this project get started? What problem is it trying to solve? OrbitDB got started because we wanted to build serverless applications, especially for the web (ie. applic…

Absolutely! I don't know the exact history and why it hasn't been applied much, and I'd be very curious to learn, but it's definitely a gem.

tldr version: https://en.m.wikipedia.org/wiki/Ambient_calculus

To summarize the relevant links and Github repos, they are: https://tallylab.com/ https://github.com/orbitdb/orbit-db https://github.com/orbitdb/ipfs-log https://github.com/ipfs/js…

I think it depends on what the use case for IPFS is. Many use it "server-side" to just transfer and store files, so a "native client" makes a lot of sense. The IPFS devs always rec…

The ipfs.io url is a public IPFS gateway, ie. bunch of IPFS nodes running on servers and "caching" content to be served through that domain. From that perspective, you're not acces…

Not quite. The data structures for the "database" part are more complex than a single json structure. Each update to the database is an "individual json" which get linked together …

It's true that availability is not "automatic" as per the software itself (rarely is in P2P networks). To make sure the data stays online (whether IPFS or OrbitDB), one needs to ma…

The blog post is accessible through IPFS here https://ipfs.io/ipfs/QmY2LufsW3v6AfxTTkp6SGqDGa5AeJhSZXH8RSs... in case the original link doesn't work.

This absolutely awesome! I'm very excited for AntidoteDB, for its use cases but also for the underlying, pioneering work you're doing on CRDTs. Thank you for doing it! <3

Unfortunately there's no proper demo page :/ We're working on improving the docs (we know this is big issues atm). There's an old version (from June) of Orbit at http://orbit.libp2…