home.social

#unixtime — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #unixtime, aggregated by home.social.

  1. Time For Everyone

    Decimal Time / Metric Time In 1793, during the French Revolution, the French wanted to decimate decimalise the whole calendar and timekeeping. They somehow kept the 12 months per year, but each month had 30 days - 3 weeks with 10 days each. 360 days total, plus 5-6 buffer days at the end of each year, so the years still align to the seasons. Each day was divided into 10 "hours", 100 "minutes" per hour, and 100 "seconds" per minute. (There's also a nice web-based decimal clock […]

    blog.mbirth.uk/2026/07/19/time

  2. Time For Everyone

    Decimal Time / Metric Time In 1793, during the French Revolution, the French wanted to decimate decimalise the whole calendar and timekeeping. They somehow kept the 12 months per year, but each month had 30 days - 3 weeks with 10 days each. 360 days total, plus 5-6 buffer days at the end of each year, so the years still align to the seasons. Each day was divided into 10 "hours", 100 "minutes" per hour, and 100 "seconds" per minute. (There's also a nice web-based decimal clock […]

    blog.mbirth.uk/2026/07/19/time

  3. Ok, wieso meint #Android (16) oder die #Galaxus Äpp, dass sie mir vor 2032 Jahren (also 1894 — EDIT: 6BC) eine Benachrichtigung über eine neue Rechnung geschickt hat? 🤪

    Mir wäre nicht bewusst, dass irgendein Betriebssystem seine Zeitepoche im Jahr 1894 beginnt. Bei allen Unixen ist's bekanntermaßen der 1.1.1970 (#Unixtime), beim alten MacOS (vor MacOS X) war's der 1.1.1906 🤷 und bei manchen Systemen scheint auch der 1.1.1900 als Beginn der Zeitepoche vorzukommen. Aber 1894? 🤔

    #DigitecGalaxus

  4. Ok, wieso meint #Android (16) oder die #Galaxus Äpp, dass sie mir vor 2032 Jahren (also 1894 — EDIT: 6BC) eine Benachrichtigung über eine neue Rechnung geschickt hat? 🤪

    Mir wäre nicht bewusst, dass irgendein Betriebssystem seine Zeitepoche im Jahr 1894 beginnt. Bei allen Unixen ist's bekanntermaßen der 1.1.1970 (#Unixtime), beim alten MacOS (vor MacOS X) war's der 1.1.1906 🤷 und bei manchen Systemen scheint auch der 1.1.1900 als Beginn der Zeitepoche vorzukommen. Aber 1894? 🤔

    #DigitecGalaxus

  5. 🕒 12 χρόνια απομένουν για το Epochalypse – και τα 32-bit συστήματα είναι η "ωρολογιακή βόμβα" του 2038.

    Στις 19 Ιανουαρίου 2038, στις 03:14:07 UTC, τα συστήματα που χρησιμοποιούν signed 32-bit time_t θα υπερχειλίσουν. Το αποτέλεσμα; Ημερομηνίες του 1901, σφάλματα σε πιστοποιητικά, καταρρεύσεις εφαρμογών – και σε κρίσιμες υποδομές, πιθανή κατάρρευση λειτουργιών.

    Δείτε πλήρη ανάλυση 👉 opensource.uom.gr/index.php/ep

  6. 🕒 12 χρόνια απομένουν για το Epochalypse – και τα 32-bit συστήματα είναι η "ωρολογιακή βόμβα" του 2038.

    Στις 19 Ιανουαρίου 2038, στις 03:14:07 UTC, τα συστήματα που χρησιμοποιούν signed 32-bit time_t θα υπερχειλίσουν. Το αποτέλεσμα; Ημερομηνίες του 1901, σφάλματα σε πιστοποιητικά, καταρρεύσεις εφαρμογών – και σε κρίσιμες υποδομές, πιθανή κατάρρευση λειτουργιών.

    Δείτε πλήρη ανάλυση 👉 opensource.uom.gr/index.php/ep

    #Y2K38 #Epochalypse #Year2038 #Linux #CyberSecurity #IoT #DevOps #UnixTime #Tech

  7. One thing that is always annoying is how the unix datum, 1970-01-01 00:00:00 GMT was in fact 1970-01-01 01:00:00 BST in the UK the very country that invented GMT.

    #utc #unixtime #time #iso8601

  8. One thing that is always annoying is how the unix datum, 1970-01-01 00:00:00 GMT was in fact 1970-01-01 01:00:00 BST in the UK the very country that invented GMT.

    #utc #unixtime #time #iso8601

  9. One thing that is always annoying is how the unix datum, 1970-01-01 00:00:00 GMT was in fact 1970-01-01 01:00:00 BST in the UK the very country that invented GMT.

    #utc #unixtime #time #iso8601

  10. One thing that is always annoying is how the unix datum, 1970-01-01 00:00:00 GMT was in fact 1970-01-01 01:00:00 BST in the UK the very country that invented GMT.

    #utc #unixtime #time #iso8601

  11. One thing that is always annoying is how the unix datum, 1970-01-01 00:00:00 GMT was in fact 1970-01-01 01:00:00 BST in the UK the very country that invented GMT.

    #utc #unixtime #time #iso8601

  12. Sabías que... ❓

    Un día como hoy, pero en 2009, el Epoch, o Unix time, llegó a 1234567890?

    El Unix Time representa el número de segundos transcurridos desde el 1 de enero de 1970 (UTC).

    Es un tiempo estándar muy utilizado en programación y sistemas operativos para registrar intervalos de tiempo y fechas.

    #gnu #linux #unix #epoch #unix #unixtime #date #juncotic

  13. Sabías que... ❓

    Un día como hoy, pero en 2009, el Epoch, o Unix time, llegó a 1234567890?

    El Unix Time representa el número de segundos transcurridos desde el 1 de enero de 1970 (UTC).

    Es un tiempo estándar muy utilizado en programación y sistemas operativos para registrar intervalos de tiempo y fechas.

    #gnu #linux #unix #epoch #unix #unixtime #date #juncotic

  14. #Epoch #UnixTime

    1770000000

    (Bon, en vrai, c’était pré-programmé : à cette heure-ci, je suis dans mon lit et les ordis sont éteints)

  15. #Epoch #UnixTime

    1770000000

    (Bon, en vrai, c’était pré-programmé : à cette heure-ci, je suis dans mon lit et les ordis sont éteints)

  16. 2025 One-Hertz Challenge: It’s Hexadecimal Unix Time - [danjovic] came up with a nifty entry for our 2025 One-Hertz Challenge that lands ... - hackaday.com/2025/07/21/2025-o #2025onehertzcontest #clockhacks #unixtime #clock

  17. 2025 One-Hertz Challenge: It’s Hexadecimal Unix Time - [danjovic] came up with a nifty entry for our 2025 One-Hertz Challenge that lands ... - hackaday.com/2025/07/21/2025-o #2025onehertzcontest #clockhacks #unixtime #clock

  18. Kinda annoyed that there wasn't even a spike in traffic on my website yesterday at 2025-04-16T19:07:44+00:00

    epochalypse.today/

    Was no one watching the bit flip to 01101000 00000000 00000000 00000000?

    Anyway, see you guys at 2029-07-18T05:49:52+00:00 when it flips to 01110000 00000000 00000000 00000000, which is when we'll lose the next bit to the epochalypse.

    #epochalypse #unix #unixtime #year2038 #year2038problem #y2k38 #software

  19. Kinda annoyed that there wasn't even a spike in traffic on my website yesterday at 2025-04-16T19:07:44+00:00

    epochalypse.today/

    Was no one watching the bit flip to 01101000 00000000 00000000 00000000?

    Anyway, see you guys at 2029-07-18T05:49:52+00:00 when it flips to 01110000 00000000 00000000 00000000, which is when we'll lose the next bit to the epochalypse.

    #epochalypse #unix #unixtime #year2038 #year2038problem #y2k38 #software

  20. 🤷 "Hey, what have you been doing recently? "
    🤓 "Ehhhhhhm, I created this #epoch countdown notification script?!"
    🤷 "You're weird!"

    😅

    (disclaimer: I'm aware the timer isn't accurate. Just haven't figured out yet exactly why. I think it's because of leap days or something....I'm tired, to be continued 😁)

    #xfce #xfcepanel #genmon #unixtime #linuxmint

  21. The 2038 Problem: A Ticking Time Bomb for Technology

    As we approach a critical juncture in computing history, the 2038 problem looms large, threatening to disrupt systems worldwide. This issue, rooted in the limitations of 32-bit integers, could have fa...

    news.lavx.hu/article/the-2038-

    #news #tech #TechDisruption #2038Problem #UnixTime

  22. Die #unixzeit hat einen runden Geburtstag 🎉 Es sind jetzt genau 1710000000 (1.71 Mia) Sekunden seit dem Urknall (The #epoch) am 01.01.1970. Wir haben noch gut 437 Mio. Sekunden bis zur #Epochalypse , geniessen wir es!

    #y2k38 #Unix #unixtime

  23. Die #unixzeit hat einen runden Geburtstag 🎉 Es sind jetzt genau 1710000000 (1.71 Mia) Sekunden seit dem Urknall (The #epoch) am 01.01.1970. Wir haben noch gut 437 Mio. Sekunden bis zur #Epochalypse , geniessen wir es!

    #y2k38 #Unix #unixtime

  24. We are now 14 years away from software storing UNIX time as signed 32-bit integers overflowing and taking us back to 1901. Hopefully your software has been upgraded to store UNIX time in 64-bit integers!

    en.wikipedia.org/wiki/Year_203

    #Y2038 #Year2038Problem #Epochalypse #UNIXtime

  25. We are now 14 years away from software storing UNIX time as signed 32-bit integers overflowing and taking us back to 1901. Hopefully your software has been upgraded to store UNIX time in 64-bit integers!

    en.wikipedia.org/wiki/Year_203

    #Y2038 #Year2038Problem #Epochalypse #UNIXtime

  26. @mcc @gsuberland That reminds me of @fuchsiii which knows a thing from the #ArchWiki on how to force Redmondian #Govware to accept #Unixtime as System Clock yet display #LocalTime on the Desktop...

    Maybe she got that link handy...