Logical clock
Would it be helpful to add an (optional) logical clock mechanism to ActivityPub?
https://en.wikipedia.org/wiki/Logical_clock
For example, to handle Delete before Create or Undo before the activity being undone?
Syndicated from the fediverse. Read and engage on the original instance.
View original on activitypub.spaceView original on activitypub.space
5 replies
Good idea (esp. the optional). Do we know other protocols in the W3C space, that use this already?
@lobingera As far as I can tell, no other W3C protocols use logical clocks.
@evan I read this similar and after browsing this https://www.chriswirz.com/distributed-systems/03-understanding-logical-clocks-in-distributed-systems
i'm not sure anymore, that a simple clock (lamport) would address (all?, i have not read your FEP ... was away from a real computer); "Limitations: Cannot determine causality between events based solely on timestamps"
@evan I suppose it would be a helpful data point if one were implemented.
For example, if every activity pertaining to a specific object were given an increasing counter recorded separately :shrug:
So long as it's standardized in some way, I don't see any reason why this would interfere with regular federation.
I added a FEP today: https://codeberg.org/fediverse/fep/pulls/945