645
edits
Changes
Jump to navigation
Jump to search
Line 15:
Line 15: + +
no edit summary
The actual storage is always in offset linux epochs to save resources. Right? And envelopped wrapped output is in more human readable format including local time if they ask. But API machine to machine i always not local time.[[User:DG|DG]] ([[User talk:DG|talk]]) 01:49, 5 January 2022 (UTC)
The actual storage is always in offset linux epochs to save resources. Right? And envelopped wrapped output is in more human readable format including local time if they ask. But API machine to machine i always not local time.[[User:DG|DG]] ([[User talk:DG|talk]]) 01:49, 5 January 2022 (UTC)
: For most devices and apps it's really unclear how they internally save the timestamp information as one can only see how they expose the data APIs or data export formats. In those cases it can be any of the options I listed on the page (e.g. Fitbit does local time, no TZ info while Apple Health stores local time + TZ information). - [[User:Gedankenstuecke|Gedankenstuecke]] ([[User talk:Gedankenstuecke|talk]]) 14:14, 27 January 2022 (UTC)