That’s how you’d do it with strfry or similar.
Using a globally replicated db like Turso it should be transparent. Strfry has made sync much more efficient with ngentropy.
That’s how you’d do it with strfry or similar.
Using a globally replicated db like Turso it should be transparent. Strfry has made sync much more efficient with ngentropy.
Oh okay so that works basically how I thought it would.
I would imagine a bunch of instances of nostr-rs trying to talk to the replicated backend would probably result in a race condition. But I've never heard of Turso before.