[GH-ISSUE #9] Date issues with alert emails - Available for '56 years' #7

Closed
opened 2026-02-27 20:09:03 +03:00 by kerem · 2 comments
Owner

Originally created by @tomballgithub on GitHub (Feb 19, 2026).
Original GitHub issue: https://github.com/misiektoja/xbox_monitor/issues/9

I'll start off with, here's the email for when someone 'stopped playing'. It's very simple.
Could we add the year on here, or better yet just consistent timestamps throughout?
It just seems odd to not have the year given the 'timestamp' is virtually the same and it has the year.
The same thing applies to the "is now offline" emails.
User played game from Wed 18 Feb 20:40 to 21:18

Xbox user XXX stopped playing 'NBA 2K26' after 37 minutes, 58 seconds

User played game from Wed 18 Feb 20:40 to 21:18

Timestamp: Wed 18 Feb 2026, 21:18:30

Why does it matter? Well, I noticed it when trying to eyeball the "is now ONLINE" email I received to determine why it thinks the user was available for 56 years!

And so that is the true 'bug'
And now I see that within this one email the time ranges are treated 2 different ways.
I suggest just using a very thorough timestamp consistently, such as the 2nd version just below but with year added

(Wed 18 Feb 20:25 - 20:40)
(Wed 31 Dec 18:00 - Wed 18 Feb 20:40)
Xbox user XXX changed status from offline to online (XSX)

User was offline for 15 minutes, 9 seconds (Wed 18 Feb 20:25 - 20:40)

User was available for 56 years, 1 month, 2 weeks (Wed 31 Dec 18:00 - Wed 18 Feb 20:40)

User is currently in-game: NBA 2K26 (XSX)

Timestamp: Wed 18 Feb 2026, 20:40:28
Originally created by @tomballgithub on GitHub (Feb 19, 2026). Original GitHub issue: https://github.com/misiektoja/xbox_monitor/issues/9 I'll start off with, here's the email for when someone 'stopped playing'. It's very simple. Could we add the year on here, or better yet just consistent timestamps throughout? It just seems odd to not have the year given the 'timestamp' is virtually the same and it has the year. The same thing applies to the "is now offline" emails. `User played game from Wed 18 Feb 20:40 to 21:18` ``` Xbox user XXX stopped playing 'NBA 2K26' after 37 minutes, 58 seconds User played game from Wed 18 Feb 20:40 to 21:18 Timestamp: Wed 18 Feb 2026, 21:18:30 ``` Why does it matter? Well, I noticed it when trying to eyeball the "is now ONLINE" email I received to determine why it thinks the user was **available for 56 years!** And so that is the true 'bug' And now I see that within this one email the time ranges are treated 2 different ways. I suggest just using a very thorough timestamp consistently, such as the 2nd version just below but with year added ``` (Wed 18 Feb 20:25 - 20:40) (Wed 31 Dec 18:00 - Wed 18 Feb 20:40) ``` ``` Xbox user XXX changed status from offline to online (XSX) User was offline for 15 minutes, 9 seconds (Wed 18 Feb 20:25 - 20:40) User was available for 56 years, 1 month, 2 weeks (Wed 31 Dec 18:00 - Wed 18 Feb 20:40) User is currently in-game: NBA 2K26 (XSX) Timestamp: Wed 18 Feb 2026, 20:40:28 ```
kerem closed this issue 2026-02-27 20:09:03 +03:00
Author
Owner

@misiektoja commented on GitHub (Feb 20, 2026):

Thanks, should be fixed now!

<!-- gh-comment-id:3936534354 --> @misiektoja commented on GitHub (Feb 20, 2026): Thanks, should be fixed now!
Author
Owner

@tomballgithub commented on GitHub (Feb 21, 2026):

Looks fixed. Dates have years. The email line about 'was available for' 56 years has been removed completely

<!-- gh-comment-id:3938230824 --> @tomballgithub commented on GitHub (Feb 21, 2026): Looks fixed. Dates have years. The email line about 'was available for' 56 years has been removed completely
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/xbox_monitor#7
No description provided.