This is completely wrong. There is no “last writer wins” in CRDTs, you’ve got to give up that CRUD mentality.
Stuffing all your followings into a single “follow list” event is the problem. CRDT fixes that because it persists a history of intents.
Imagine you are dealing with a monotonically increasing counter. You have two options to derive that counter:
A. Emit a state event with the current count every time it increases
B. Emit a increase counter event then derive the counter state by adding all the events
There is not enough context with A to converge into an unambiguous state automatically, that is why clients like Nostur have to ask what you want to do when they detect something “strange” happened.
It is also the reason why keeping an history of follow lists is a pointless exercise.
