Feeds come with what seems a Lamport clock, which mean items in a feed are ordered relatively (first element has a 0 timestamp, second 1 etc).
When implementing a Twitter-like app, different feeds from other users have to be replicated and presented to the user. This poses a problem when trying to visualize them as they were temporally ordered, because we have no way to know the exact order of the union of two feeds.
A way to solve this would be letting users specify the UTC timestamp of their posts, but that would be easily abusable (users setting the timestamp in the future or in the past, for example). While a cool functionality, it would disrupt the concept of timeline.
This issue is to discuss a way of time-ordering different feeds in a reliable way.
Feeds come with what seems a Lamport clock, which mean items in a feed are ordered relatively (first element has a 0 timestamp, second 1 etc).
When implementing a Twitter-like app, different feeds from other users have to be replicated and presented to the user. This poses a problem when trying to visualize them as they were temporally ordered, because we have no way to know the exact order of the union of two feeds.
A way to solve this would be letting users specify the UTC timestamp of their posts, but that would be easily abusable (users setting the timestamp in the future or in the past, for example). While a cool functionality, it would disrupt the concept of timeline.
This issue is to discuss a way of time-ordering different feeds in a reliable way.