amTimeAgo with different timezones

[nicolassharp]

I have an issue at the moment where my server returns a timestamp in UTC, and the user's computer is UTC + 1 (BST). This means that an action they just performed says '1 hour ago'.

I'm using {{activity.timestamp | amTimeAgo}}, would {{activity.timestamp | amUtc | amTimeAgo}} fix this?

I would just test myself but I don't have access to the endpoint right now.

---

Update: I've now tested using {{activity.timestamp | amUtc | amTimeAgo}} and unfortunately it doesn't fix the error.

[nicolassharp]

Has no one faced this issue? Any help would be really appreciated!

[connormlewis]

Does the time returned from the server have timezone information in it? Could you provide sample data? I believe the amUtc pipe just puts the moment object in UTC mode, which just changes how the information is displayed/manipulated.

[connormlewis]

@nicolassharp give {{ activity.timestamp | amFromUtc | amLocal | amTimeAgo }} a try. The amLocal may not be necessary, but you could try it just to be safe. Make sure you’re on version 1.7.0 of this package.

[Roshan2892]

@connormlewis Thanks your solution worked for me. But can you explain what's exactly happening in your snippet?