Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Di 18.06.2024 00:00:00 12.176 +1 6.560.642 538,8 chaos.social 4.2.9 500 Mo 17.06.2024 00:00:03 12.175 +2 6.553.782 538,3 chaos.social 4.2.9 500 So 16.06.2024 00:00:04 12.173 +3 6.548.511 538,0 chaos.social 4.2.9 500 Sa 15.06.2024 00:00:04 12.170 0 6.543.090 537,6 chaos.social 4.2.9 500 Fr 14.06.2024 00:00:01 12.170 +5 6.536.920 537,1 chaos.social 4.2.9 500 Do 13.06.2024 00:00:04 12.165 +3 6.542.845 537,8 chaos.social 4.2.9 500 Mi 12.06.2024 00:00:03 12.162 +2 6.535.802 537,4 chaos.social 4.2.9 500 Di 11.06.2024 00:00:05 12.160 +3 6.528.923 536,9 chaos.social 4.2.9 500 Mo 10.06.2024 00:00:06 12.157 +2 6.521.513 536,4 chaos.social 4.2.9 500 So 09.06.2024 00:00:00 12.155 0 6.513.072 535,8 chaos.social 4.2.9 500
Mathias Panzenböck (@bloody_albatross) · 08/2018 · Tröts: 1.603 · Folger: 66
Di 18.06.2024 20:37
Always nice when a "timestamp" field is just "number" without any further explanation. The API client is #JavaScript, but the API of course exists for many languages. Is it seconds since the #Unix epoch or milliseconds (later is what JavaScript uses)? Is it even relative the Unix epoch? I know Microsoft uses a different epoch, but this API isn't by Microsoft. Somewhere with Google I found out its seconds since the Unix epoch. 5 words in the docs would have been enough!
[Öffentlich] Antw.: 0 Wtrl.: 0 Fav.: 0 · via Web