2020y ago

[NWA6]

What is this anomaly‘2020y ago’ that I see on many replies to posts?

[SeasideSusie Remembering]

I can't see that on my tablet or PC. Layout is different on a phone so maybe it's something to do with that, a glitch perhaps.

[Peanut31 in reply to SeasideSusie]

It appears there is a fault, this happened to someone that replied to me, I couldn’t reply back and when I looked it said 2020y ago.

Best wishes

Peanut31

[helvella Administrator Thyroid UK]

Some time ago someone reported that. I took it up with HU support - they could not explain it and had not had other reports at that time.

Your browser looks at the date/time of a post and works out how long ago it was posted, then displays in what they think is an approrpiate format e.g. "10 hours ago" or "4 months ago". If you hover your mouse over that display, it will tell you the exact date and time of the post. In order for it to be displaying 2020y, it is probably seeing a big difference between what it thinks is the date/time and the date/time of the post itself.

Is there any possibility that your computer/tablet/phone has the wrong time set? I know that under some circumstances the clock can be wrong when a device is restarted. It then connects to the internet, finds a time server, and sets the time correctly (phones might do this differently). But if something goes wrong...

So, first thing, check the date and time settings on your device.

[NWA6 in reply to helvella]

I’m using my phone, definitely got my date and time correct as I need alarms to go off for calendar reminders.

I’ll check updates.

[NWA6 in reply to NWA6]

Nope not my phone or the HU app.

[JumpJiving in reply to helvella]

With my techie hat on (I develop and test software), it sounds like a bug in HealthUnlocked code. My assumption would be that datetime values are initialised to -1 until such time as the correct value has been retrieved from the system clock. For whatever reason, that -1 is not getting overwritten with the correct value. As a result, calculating how long ago a post was created results in 2019-(-1), hence 2020 years ago.

[JumpJiving in reply to helvella]

There are various reasons why the datetime value used in the "how long ago" calculation might not be updated correctly. However, to track down the reason, it might be worth collating information about the posts on which the problem appears, namely for the device used by the person making the post, what type of device they were using, what operating system, what operating system version, were they using the HealthUnlocked app (if so, what version), or were they using a browser (if so, which browser and version), and the timezone that the poster was in. If a pattern emerges, it might be possible to identify how to fix/workaround the problem.

[NWA6 in reply to helvella]

Yeah hubby (coder) just said the same as you, the posters date/time is out of whack on their device/computer. But he also asked if anyone else is seeing the same in their screen or are the seeing the actual reply? Is the reply a ghost for everyone else too?

[Angel_of_the_North]

It's almost certainly problem with the way the browser on your phone interprets unicode characters (or fails to run a script). Use a PC.