Lists, clobber-prevention #9

New issue

Open

opened 2025-09-04 05:30:51 +12:00 by mikedilger · 1 comment

mikedilger commented

2025-09-04 05:30:51 +12:00

(Migrated from github.com)

Lists (such as contact lists) could use CRDTs like LWW as I suggested for nostr. However, a few thoughts come to mind:

99% of the time it won't be needed as on mosaic everyone will be using the same servers (outbox servers) for handling this list.
Contacts maybe should never be deleted?
Anybody who clobbers is easily identified by the device key, since each device/client has it's own separate key.

Lists (such as contact lists) could use CRDTs like LWW as I suggested for nostr. However, a few thoughts come to mind: * 99% of the time it won't be needed as on mosaic everyone will be using the same servers (outbox servers) for handling this list. * Contacts maybe should never be deleted? * Anybody who clobbers is easily identified by the device key, since each device/client has it's own separate key.

mikedilger commented

2025-09-04 05:34:09 +12:00

(Migrated from github.com)

Servers can't do the merge operation as they cannot generate records on behalf of users.

However servers could verify that the replacing event accounts for all the lines in the event being replaced, and reject the replacement if it didn't. We could add a bit to kind to indicate a list type of event, so servers know when to perform this update verification logic.

Servers can't do the merge operation as they cannot generate records on behalf of users. However servers could verify that the replacing event accounts for all the lines in the event being replaced, and reject the replacement if it didn't. We could add a bit to `kind` to indicate a `list` type of event, so servers know when to perform this update verification logic.