Post

Getting close to being able to demonstrate the complementarity of #DialogDB and #ATProto. Bi-directional sync between a general purpose, local-first (private by default) database and any PDS.

Let's not get ahead of ourselves 😅 there is work yet to be done. But: the sketch starts with OAuth via control panel UI on the Dialog Remote (think Git Remote); looks a lot like "log in w/ your PDS."

The core of Dialog authz is a capability delegation scheme via UCANs. PDS doesn't know about Dialog. And, Dialog embedders transact with PDS data like any other data in their database. The interop happens on the Remote, which tracks changes and syncs w/ the PDS.

If you are interested to glean more about how the bi-directional / interop part works, I recommend our Sync conf talk from last year. bsky.app/profile/cdat...

cdata@cdata.earth

I've been trying to come up with a spin on "there's an app for that," but for Dialog Rules (which, among other things, enable opportunistic / uncoordinated interop between app domains without the risk of one party clobbering other apps' data www.youtube.com/watch?v=4n-2...).

0 reposts0 likes

No replies yet.