Conversation

Notices

1. Embed this notice
   Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Friday, 10-Jan-2025 04:21:47 JST Haelwenn /элвэн/ :triskell:

   in reply to

   • Hugh
   • Erin 💽✨
   @erincandescent @linus @eloy @hugh
   https://pubs.opengroup.org/onlinepubs/9799919799/basedefs/V1_chap04.html#tag_04_19
   > The relationship between the actual date and time in Coordinated Universal Time, as determined by the International Earth Rotation Service, and the system's current value for seconds since the Epoch is unspecified.
   
   How POSIX of it, even expanding the acronyms to be precise about… lack of precision.
   
   Also even did graphs for how it behaves in another section: https://pubs.opengroup.org/onlinepubs/9799919799/xrat/V4_xsh_chap01.html#tag_22_02_08_18
   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Friday, 10-Jan-2025 04:21:48 JST Erin 💽✨

     in reply to

     • Hugh

     @hugh @eloy @linus if POSIX stated that CLOCK_REALTIME was seconds UT1 since the epoch, all would be forgiven

     Alas.

   • Embed this notice
     Hugh (hugh@social.crablab.uk)'s status on Friday, 10-Jan-2025 04:21:50 JST Hugh

     @eloy @linus I've been convinced by a friend that Unix timestamps are the worst, because of the way they (don't) handle leap seconds.