[Bug]: utc_offset field on /v1/api/people/@me/profile does not handle DST

[dwyazzo90]

Checked Existing

• I have checked the repository for duplicate issues.

What happened?

Requesting the /v1/api/people/@me/profile endpoint includes on the response a timezone name and UTC offset that the Wii U uses to calculate time in most apps instead of using the actual consoles clock.

The value of the "utc_offset" field on the response is used on the loading screens for apps like Miiverse and Nintendo TVii, and others to calculate the time (ex: new Date() on these apps are based from the utc_offset)

What did you expect to happen?

The "utc_offset" field would handle DST depending of the zone and add the extra hour so this new value would be included on the response, so the apps could show the accurate time instead of it being an hour behind.

Steps to reproduce?

No response

Other relevant information. (OPTIONAL)

No response

[jonbarrow]

UTC offsets themselves are static. They do not take DST into account because that is a local thing, and not everywhere recognizes it. Even in countries like the United States, DST recognition varies by state even for states within the same time zone. The observed time is managed by the system, by adjusting the time locally, but the offset itself remains the same. The offsets we use for those profile values were obtained via scraping Nintendo's servers if I remember correctly, they are the correct values

Regardless, the Wii U's system time is handled in multiple ways and gets the value from multiple sources. You can set the local time of the system to whatever you want, but certain applications like the Miiverse loading screen obtain the value from the server. They use the /v1/api/admin/time NNAS endpoint for this, taking the X-Nintendo-Date response header as the current time. The UTC offset in the account data doesn't have anything to do with it

That being said, we are implementing the /v1/api/admin/time endpoint correctly. The endpoint doesn't take DST into account, and would show the "wrong" time for users in a DST region even on Nintendo's servers. This was gone over in this issue a while ago Nightkingale/Wii-U-Time-Sync#21

So while the time may be off, our emulation of the endpoint is accurate. So I'm not inclined to think we should change it. The "correct" implementation in this case is to just have the "wrong" time. Our endgoal is always accurate emulation, even at the cost of funky stuff like this

[oxixes]

I live in Spain and DST IS taken into account by Nintendo's servers, both in the timezones and in the profile endpoint.

[dwyazzo90]

I just checked into Nintendo Network and yeah, i set my region to Wisconsin and to Central Time which should be seeing DST as were talking, and indeed, /v1/api/profile/@me/profile actually took DST in account, it is infact 8:58pm in Wisconsin, compared to the Pretendo account server who does not take DST into account and does return the wrong time (7:58pm) so i hope you can take this in mind and actually fix this issue, because Nintendo DID fix this issue at some point, i literally have the proof here since i mitm NN rq and i remembered this issue and decided to check in case and lo and behold the time was the correct one, not to say the Reddit post you linked is 11 yr ago. it was an issue , yeah, but on the early days of the Wii U, becuase its fixed, i hope Pretendo fixes this, and the Miiverse loading screen and other apps that use the UTC offset value from NN can display the correct time!

[minihoot]

I use Australian Eastern Standard Time and whenever I open Juxt (Wii U) the clock is always 2 hours ahead even though my Wii U's clock is correct