https://xn--gckvb8fzb.com/superhighway84/

On Tue, 28 Dec 2021 06:53:48 -0000 (UTC), meff wrote:

> https://xn--gckvb8fzb.com/superhighway84/

According to the github readme:

>
- The OrbitDB that Superhighway84 uses is a public database, meaning
everyone can alter its data. Since its using a standard _docstore_, PUT
and DELETE events can alter existing data. This issue will be solved in
the future by customizing the store to ignore these types of events.

Does this mean that the local DB connects to *any* remote DB or is there
actually a centralized DB that is connects to?

On Mon, 3 Jan 2022 21:13:14 -0000 (UTC), Jason Evans wrote:

> On Tue, 28 Dec 2021 06:53:48 -0000 (UTC), meff wrote:
> Does this mean that the local DB connects to *any* remote DB or is there
> actually a centralized DB that is connects to?

Huh this is a good question. I did some digging into this. OrbitDB is
backed by a CRDT. Most CRDTs are append-only (due to the way consensus
works with most CRDTs), so I was curious about how a PUT or DELETE would
work. The field manual (https://github.com/orbitdb/field-manual) doesn't
seem ready yet, so it's not documented there and I didn't have a chance to
dive into the code. Having implemented CRDTs before, I imagine they append
some sort of edit or tombstone record onto the shared stream and use that
to note edits and deletes.

In sum, a client can connect to any DB node, and these DB nodes should
have consensus on the state of the database. In theory, each client can
run its own node that connects to the CRDT swarm, but it's unclear how
easy that would be given the state of IPv4 NAT these days.