Heartbeat updating activities but not timestamp.

[Tafmakura]

It seems that the auto feed update feature works but when a new activity is loaded in the activity stream via heartbeat and Ajax the activity timestamps remain static. For example when you add an update it will say added 10sec ago, and when you add a new update 15mins later without refreshing the activity stream page but clicking the "Load Newest" it will record the new activity as 15sec ago for example but it will not update the rest of the earlier posted activities in the stream which means that the first update will still say 10sec ago and the new one will say 15sec ago which seems as if the new update is older than the first. Also if someone leaves their activity stream open and they return an hr later, the last activity will still be 15sec ago.

Looking at twitter they update the timestamp for all visible activities at each heartbeat and when a new activity is added, this is more intuitive

[Tafmakura]

Theses activities seem seconds apart but in reality they are minutes apart , also the latest activity seems older than the second

[DJPaul]

Yep.

[Tafmakura]

An alternative solution could be something more intuitive where when the activity stream is updated via Ajax the new activity item will have a "just now" timestamp and when an even newer activity update is added and loaded via Ajax it will get the "just now" timestamp and change all other activity elements that have a "just now" timestamp to "a while ago". If an activity is posted and gets a "just now" timestamp and remains inactive for maybe 3 minutes it's time stamp value will change to "a while ago" I'm sure all this can be done via Javascript.

The great thing is that it will all work without heartbeat. If Heartbeat auto refresh is enabled then the actual timestamps for all visible activities will be updated

[boonebgorges]

Maybe this would be a good time for us to consider using a JS library to make all of our timestamps dynamic, using something like ​http://momentjs.com/. See #5757. (ping @r-a-y)

[r-a-y]

Going to mark this ticket as a duplicate of #5757.

Work will continue in that ticket.