Why does header interest show "8 minutes ago" activity at times?

@Amagnimo (637)
India
September 12, 2008 9:49am CST
I noticed that sometimes, 8 minutes is the display of the most active interest. I mean, when it should so "0 seconds ago" or "few seconds ago", it updates showing "8 minutes ago" It would just update within less than a minute, and it shows "8 minutes ago". This happens with me almost daily? Does it happen with you too? Do you know why? I do know of a site where - newest post show "2 hours ago". Is it the same way here - sometimes?
1 person likes this
2 responses
@klaudine (3652)
• Indonesia
12 Sep 08
Hi Nemo, I can't believe you made this funny discussion here LOL.. it's not always like that. I saw something like 0second ago here in the no response discussions. I mean, it is put randomly in the list, right? Well.. if today you saw too many '8 minutes ago' I usually take it as a sign LOL. Maybe it is the winning number for the horse race tomorrow :p you would never know. LOL. Good luck finding out this mystery, Nemo!
@Amagnimo (637)
• India
12 Sep 08
Well, I didn't get the most of the part of the thing that you wrote. I mean, what's that about LOL and thing, I really don't know why is that happening. I just noticed it out randomly... Well, waiting for a response that answers it... do mylot people reply? Happy Mylotting... Nemo.
1 person likes this
@klaudine (3652)
• Indonesia
12 Sep 08
Sorry... I was a little bit lost of concentration back then. LOL. I mean, I were you, seeing the same numbers here and there, I would take it as a sign and maybe put the number on the horse race bet, in case it was the number of the winning horse LOL.
1 person likes this
@Amagnimo (637)
• India
13 Sep 08
Well, now I get it...but that happens most frequently. Its not something that absurd so as to try for the next-day horse! lol. anyways, take care... Nemo
@underdogtoo (9599)
• Philippines
14 Sep 08
I have not noticed something like 8 minutes although I know there is some kind of clock being used to monitor when things were done. There might be some error in the algorithm used or it might just be some kind of discepancy relating to the times when updated and the times the page arrived at the browser.