there can be situations where another client is updating an older version of one you have locally that is newer. this would technically be the "newest" even though its updating an older list. A delta would notice something is off

Reply to this note

Please Login to reply.

Discussion

I'm going to end up reinventing CRDTs aren't i

chatgpt things so:

CRDT-Based Approach

Model the contact list as a Set CRDT:

• Add-Wins Set (AWSet): Always prefer additions to the set unless explicitly removed.

• Ensure removals are deliberate by tracking deletion markers (tombstones) for each p tag.

hrm

Now that i think about it, the safest thing to do is ask the user which follows and unfollows were intentional whenever it notices that it is updating multiple p tags at once. You don’t even need historical deltas for this

nm im dumb

safest isn't best

That's very elegant, yes.

The alternative would probably be moving to individual relationship status events.