At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga.
Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus.
Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
Not the answer you are looking for? Search for more explanations.
@rajathsbhat It sometimes happens.
The issue is that 5:34 AM is the time in the OpenStudy Headquarters when it is 6:14 PM in India.
Refreshing or waiting for two seconds may help well.
You can assume at any given moment that our server time is more accurate than your computer's time. It's synced to atomic time via NTP (the Network Time Protocol), though granted only nightly. Times are saved on the server in server time, then sent to your browser in UTC and converted to your local timezone by your browser. Just about every time we've seen issues with timestamps and relative times, it's been because someone's system clock was off on their computer ;)
@shadowfiend does that include those "a few moments ago", "x minutes ago", etc?