home.social

#unixtime — Public Fediverse posts

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

fetched live
  1. Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC

    #UnixTime #1785000000

  2. Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC

    #UnixTime #1785000000

  3. Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC

    #UnixTime #1785000000

  4. Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC

    #UnixTime #1785000000

  5. Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC

    #UnixTime #1785000000

  6. 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

  7. 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

  8. The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂

    time.is/Unix_time

    #Y2K38 #UnixTime

  9. The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂

    time.is/Unix_time

    #Y2K38 #UnixTime

  10. The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂

    time.is/Unix_time

    #Y2K38 #UnixTime

  11. The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂

    time.is/Unix_time

    #Y2K38 #UnixTime

  12. The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂

    time.is/Unix_time

    #Y2K38 #UnixTime

  13. Unix Time 1783333333 will occur on Monday, July 6, 2026 at 10:22:13 UTC

    Then Unix Time 1783456789 will be on Tuesday, July 7, 2026 at 20:39:49 UTC

    #UnixTime

  14. Unix Time 1783333333 will occur on Monday, July 6, 2026 at 10:22:13 UTC

    Then Unix Time 1783456789 will be on Tuesday, July 7, 2026 at 20:39:49 UTC

    #UnixTime

  15. Unix Time 1783333333 will occur on Monday, July 6, 2026 at 10:22:13 UTC

    Then Unix Time 1783456789 will be on Tuesday, July 7, 2026 at 20:39:49 UTC

    #UnixTime

  16. Unix Time 1783333333 will occur on Monday, July 6, 2026 at 10:22:13 UTC

    Then Unix Time 1783456789 will be on Tuesday, July 7, 2026 at 20:39:49 UTC

    #UnixTime

  17. Unix Time 1783333333 will occur on Monday, July 6, 2026 at 10:22:13 UTC

    Then Unix Time 1783456789 will be on Tuesday, July 7, 2026 at 20:39:49 UTC

    #UnixTime

  18. Unix Time 1783000000 was about 6000 seconds ago at Thursday Jul 2nd 2026 at 13:46:40 UTC+0000 (Greenwich Mean Time).

    Apologies I was distracted by sometime interesting on the Interwebs.

    #UnixTime #1783000000

  19. Unix Time 1783000000 was about 6000 seconds ago at Thursday Jul 2nd 2026 at 13:46:40 UTC+0000 (Greenwich Mean Time).

    Apologies I was distracted by sometime interesting on the Interwebs.

    #UnixTime #1783000000

  20. Unix Time 1783000000 was about 6000 seconds ago at Thursday Jul 2nd 2026 at 13:46:40 UTC+0000 (Greenwich Mean Time).

    Apologies I was distracted by sometime interesting on the Interwebs.

    #UnixTime #1783000000

  21. Unix Time 1783000000 was about 6000 seconds ago at Thursday Jul 2nd 2026 at 13:46:40 UTC+0000 (Greenwich Mean Time).

    Apologies I was distracted by sometime interesting on the Interwebs.

    #UnixTime #1783000000

  22. Unix Time 1783000000 was about 6000 seconds ago at Thursday Jul 2nd 2026 at 13:46:40 UTC+0000 (Greenwich Mean Time).

    Apologies I was distracted by sometime interesting on the Interwebs.

    #UnixTime #1783000000

  23. Some upcoming Unix Time Milestones

    Unix Time 1782000000 - Sunday, June 21, 2026 00:00:00 UTC+0000

    Unix Time 1783000000 - Thursday, July 02, 2026 13:46:40 UTC+0000

    Unix Time 1787654321 - Tuesday, August 25, 2026 10:38:41 UTC+0000

    Unix Time 1788000000 - Saturday, August 29, 2026 10:40:00 UTC+0000

    Unix Time 1788888888 - Tuesday, September 8, 2026 17:34:48 UTC+0000

    Unix Time 1789000000 - Thursday, September 10, 2026 00:26:40 UTC+0000

    #UnixTIme

  24. Some upcoming Unix Time Milestones

    Unix Time 1782000000 - Sunday, June 21, 2026 00:00:00 UTC+0000

    Unix Time 1783000000 - Thursday, July 02, 2026 13:46:40 UTC+0000

    Unix Time 1787654321 - Tuesday, August 25, 2026 10:38:41 UTC+0000

    Unix Time 1788000000 - Saturday, August 29, 2026 10:40:00 UTC+0000

    Unix Time 1788888888 - Tuesday, September 8, 2026 17:34:48 UTC+0000

    Unix Time 1789000000 - Thursday, September 10, 2026 00:26:40 UTC+0000

    #UnixTIme

  25. Some upcoming Unix Time Milestones

    Unix Time 1782000000 - Sunday, June 21, 2026 00:00:00 UTC+0000

    Unix Time 1783000000 - Thursday, July 02, 2026 13:46:40 UTC+0000

    Unix Time 1787654321 - Tuesday, August 25, 2026 10:38:41 UTC+0000

    Unix Time 1788000000 - Saturday, August 29, 2026 10:40:00 UTC+0000

    Unix Time 1788888888 - Tuesday, September 8, 2026 17:34:48 UTC+0000

    Unix Time 1789000000 - Thursday, September 10, 2026 00:26:40 UTC+0000

    #UnixTIme

  26. Some upcoming Unix Time Milestones

    Unix Time 1782000000 - Sunday, June 21, 2026 00:00:00 UTC+0000

    Unix Time 1783000000 - Thursday, July 02, 2026 13:46:40 UTC+0000

    Unix Time 1787654321 - Tuesday, August 25, 2026 10:38:41 UTC+0000

    Unix Time 1788000000 - Saturday, August 29, 2026 10:40:00 UTC+0000

    Unix Time 1788888888 - Tuesday, September 8, 2026 17:34:48 UTC+0000

    Unix Time 1789000000 - Thursday, September 10, 2026 00:26:40 UTC+0000

    #UnixTIme

  27. Some upcoming Unix Time Milestones

    Unix Time 1782000000 - Sunday, June 21, 2026 00:00:00 UTC+0000

    Unix Time 1783000000 - Thursday, July 02, 2026 13:46:40 UTC+0000

    Unix Time 1787654321 - Tuesday, August 25, 2026 10:38:41 UTC+0000

    Unix Time 1788000000 - Saturday, August 29, 2026 10:40:00 UTC+0000

    Unix Time 1788888888 - Tuesday, September 8, 2026 17:34:48 UTC+0000

    Unix Time 1789000000 - Thursday, September 10, 2026 00:26:40 UTC+0000

    #UnixTIme

  28. 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

  29. 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

  30. 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

  31. 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

  32. 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

  33. Unix zählt Sekunden.
    GPS zählt Wochen.
    DVB zählt Tage.

    Drei unterschiedliche Zeitmodelle.
    Drei unterschiedliche Standards.
    Und wieder taucht 2038 auf.

    Neuer kurzer Blog über den DVB-Zeit-Rollover und Modified Julian Date.

    y2k38.ch/dvb-modified-julian-d

    #Y2K38 #DVB #GPS #UnixTime #MJD

  34. Unix zählt Sekunden.
    GPS zählt Wochen.
    DVB zählt Tage.

    Drei unterschiedliche Zeitmodelle.
    Drei unterschiedliche Standards.
    Und wieder taucht 2038 auf.

    Neuer kurzer Blog über den DVB-Zeit-Rollover und Modified Julian Date.

    y2k38.ch/dvb-modified-julian-d

    #Y2K38 #DVB #GPS #UnixTime #MJD

  35. Unix zählt Sekunden.
    GPS zählt Wochen.
    DVB zählt Tage.

    Drei unterschiedliche Zeitmodelle.
    Drei unterschiedliche Standards.
    Und wieder taucht 2038 auf.

    Neuer kurzer Blog über den DVB-Zeit-Rollover und Modified Julian Date.

    y2k38.ch/dvb-modified-julian-d

    #Y2K38 #DVB #GPS #UnixTime #MJD

  36. Unix zählt Sekunden.
    GPS zählt Wochen.
    DVB zählt Tage.

    Drei unterschiedliche Zeitmodelle.
    Drei unterschiedliche Standards.
    Und wieder taucht 2038 auf.

    Neuer kurzer Blog über den DVB-Zeit-Rollover und Modified Julian Date.

    y2k38.ch/dvb-modified-julian-d

    #Y2K38 #DVB #GPS #UnixTime #MJD

  37. Unix zählt Sekunden.
    GPS zählt Wochen.
    DVB zählt Tage.

    Drei unterschiedliche Zeitmodelle.
    Drei unterschiedliche Standards.
    Und wieder taucht 2038 auf.

    Neuer kurzer Blog über den DVB-Zeit-Rollover und Modified Julian Date.

    y2k38.ch/dvb-modified-julian-d

    #Y2K38 #DVB #GPS #UnixTime #MJD

  38. Unix Time 1781000000 will occur on Tuesday 9th June at 10:13:20 UTC

    🙂🖖

    #UnixTime #1781000000

  39. Unix Time 1781000000 will occur on Tuesday 9th June at 10:13:20 UTC

    🙂🖖

    #UnixTime #1781000000

  40. Unix Time 1781000000 will occur on Tuesday 9th June at 10:13:20 UTC

    🙂🖖

    #UnixTime #1781000000

  41. Unix Time 1781000000 will occur on Tuesday 9th June at 10:13:20 UTC

    🙂🖖

    #UnixTime #1781000000

  42. Unix Time 1781000000 will occur on Tuesday 9th June at 10:13:20 UTC

    🙂🖖

    #UnixTime #1781000000

  43. UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂

    #UnixTime #1780000000

  44. UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂

    #UnixTime #1780000000

  45. UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂

    #UnixTime #1780000000

  46. UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂

    #UnixTime #1780000000

  47. UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂

    #UnixTime #1780000000

  48. Unix Time 1777700000 will occur shortly on Sat May 02 2026 05:33:20 UTC

    Unix Time 1777777777 will occur on Sun May 03 2026 03:09:37 UTC

    #UnixTime #1777777777

  49. Unix Time 1777700000 will occur shortly on Sat May 02 2026 05:33:20 UTC

    Unix Time 1777777777 will occur on Sun May 03 2026 03:09:37 UTC

    #UnixTime #1777777777

  50. Unix Time 1777700000 will occur shortly on Sat May 02 2026 05:33:20 UTC

    Unix Time 1777777777 will occur on Sun May 03 2026 03:09:37 UTC

    #UnixTime #1777777777

  51. Unix Time 1777700000 will occur shortly on Sat May 02 2026 05:33:20 UTC

    Unix Time 1777777777 will occur on Sun May 03 2026 03:09:37 UTC

    #UnixTime #1777777777

  52. Unix Time 1777700000 will occur shortly on Sat May 02 2026 05:33:20 UTC

    Unix Time 1777777777 will occur on Sun May 03 2026 03:09:37 UTC

    #UnixTime #1777777777

  53. 🕒 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