#unixtime — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #unixtime, aggregated by home.social.
-
Unix Time 1788888888 will occur today, Tuesday September 8th 2026 at 17:34:48 UTC 🙂
#UnixTime #1788888888
-
Unix Time 1788888888 will occur today, Tuesday September 8th 2026 at 17:34:48 UTC 🙂
#UnixTime #1788888888
-
Unix Time 1788888888 will occur today, Tuesday September 8th 2026 at 17:34:48 UTC 🙂
#UnixTime #1788888888
-
Unix Time 1788888888 will occur today, Tuesday September 8th 2026 at 17:34:48 UTC 🙂
#UnixTime #1788888888
-
Unix Time 1788888888 will occur today, Tuesday September 8th 2026 at 17:34:48 UTC 🙂
#UnixTime #1788888888
-
Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC
#UnixTime #1785000000
-
Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC
#UnixTime #1785000000
-
Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC
#UnixTime #1785000000
-
Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC
#UnixTime #1785000000
-
Unix Time1785000000 will happen on Saturday 25th July 2026 at 17:20:00 UTC
#UnixTime #1785000000
-
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 […] -
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 […] -
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 🙂
-
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 🙂
-
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 🙂
-
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 🙂
-
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 🙂
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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
-
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? 🤔
-
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? 🤔
-
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? 🤔
-
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? 🤔
-
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? 🤔
-
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.
https://y2k38.ch/dvb-modified-julian-date-2038-problem-end-of-days
-
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.
https://y2k38.ch/dvb-modified-julian-date-2038-problem-end-of-days
-
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.
https://y2k38.ch/dvb-modified-julian-date-2038-problem-end-of-days
-
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.
https://y2k38.ch/dvb-modified-julian-date-2038-problem-end-of-days
-
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.
https://y2k38.ch/dvb-modified-julian-date-2038-problem-end-of-days
-
-
-
-
-
-
UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂
#UnixTime #1780000000
-
UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂
#UnixTime #1780000000
-
UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂
#UnixTime #1780000000
-
UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂
#UnixTime #1780000000
-
UNIX Time 1780000000 will occur on Thursday May 28 2026 at 20:26:40 UTC 🙂
#UnixTime #1780000000
-
-
-
in a few seconds it will be 1777777771 seconds since jan 1 1970 #epoch #time #EpochTime #UnixTime #UnixTimeStamp
-
in a few seconds it will be 1777777771 seconds since jan 1 1970 #epoch #time #EpochTime #UnixTime #UnixTimeStamp
-
in a few seconds it will be 1777777771 seconds since jan 1 1970 #epoch #time #EpochTime #UnixTime #UnixTimeStamp
-
in a few seconds it will be 1777777771 seconds since jan 1 1970 #epoch #time #EpochTime #UnixTime #UnixTimeStamp
-
in a few seconds it will be 1777777771 seconds since jan 1 1970 #epoch #time #EpochTime #UnixTime #UnixTimeStamp
-
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