<oembed><type>rich</type><version>1.0</version><title>Technical Debt wrote</title><author_name>Technical Debt (npub14w…u3rwx)</author_name><author_url>https://yabu.me/npub14w4qnk43lsllls2qnldj3vfcxtx5qvtsf3xlvxv9yha8afrxhmfqju3rwx</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>This is completely wrong. There is no “last writer wins” in CRDTs, you’ve got to give up that CRUD mentality.&#xA;&#xA;Stuffing all your followings into a single “follow list” event is the problem. CRDT fixes that because it persists a history of intents.&#xA;&#xA;Imagine you are dealing with a monotonically increasing counter. You have two options to derive that counter:&#xA;A. Emit a state event with the current count every time it increases&#xA;B. Emit a increase counter event then derive the counter state by adding all the events&#xA;&#xA;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.&#xA;&#xA;It is also the reason why keeping an history of follow lists is a pointless exercise.</html></oembed>