Merging with NextGraph

[joepio]

I had a couple of great conversations with @niko-ng who's working on NextGraph. We've been exploring some ways in which we could work together towards something greater by collaborating. Niko proposed using NextGraph in AtomicServer.

This would be very impactful, but also worth exploring.

This document will be updated / changed as I have more conversations with Niko

Why it would be cool

• Local-first. That's a dream that I've had for a while. It's one of these characteristics that AtomicData doesn't have that would be very powerful, but is very hard to implement. NextGraph already has a lot of answers in this domain.
• Encrypted. NextGraph encrypts everything.
• Real arrays. With insert / splice methods etc. Nice.

NextGraph would replace...

• Atomic Commits as an abstraction layer (NextGraph supports multiple CRDTs). This also includes versioning, history, websockets, subscribing...
• Sled as KV store (with RocksDB)
• Our existing Query index mechanisms (OxiGraph would do the heavy lifting)
• Atomic Agents. NextGraph also has a crypto based user / agent model. Wants to use Opaque, retrieves a wallet (containing your keys) safely from a server. You can open that wallet in a bunch of different ways.
• Webhooks / Subscribing. NextGraph also does synchronization.
• Versioning / history
• Invites.

AtomicServer would still...

• Convert NextGraph resources to HTTP urls
• Similar to how ActivityPods are related to NextGraph right now
• Do schema validation (Atomic Schema)
• Do authorization
• Do pagination

Questions

• How does Atomic Schema relate to what NextGraph is doing?
• Content Addressing?
• P2P?