#y2k38 — Public Fediverse posts

#y2k38 Challenge: in your next team or architecture meeting - ask for plans about the y2k38 issue. Come back and tell me, how many people in the group had the issue in their radar:

#y2k38 Challenge: in your next team or architecture meeting - ask for plans about the y2k38 issue. Come back and tell me, how many people in the group had the issue in their radar:

#y2k38 Challenge: in your next team or architecture meeting - ask for plans about the y2k38 issue. Come back and tell me, how many people in the group had the issue in their radar:

#y2k38 Challenge: in your next team or architecture meeting - ask for plans about the y2k38 issue. Come back and tell me, how many people in the group had the issue in their radar:

#y2k38 Challenge: in your next team or architecture meeting - ask for plans about the y2k38 issue. Come back and tell me, how many people in the group had the issue in their radar:

I had a ludicrous idea: an OS network stack that assigns a new outbound #IPv6 address within the subnet and with the 32-bit UNIX timestamp encoded in the IP, once per second. At least until #Y2K38, this would allow Wireshark traces to be located in time with 1 sec precision. Think of the debuggability improvements!

The downside is effectively DoSing the NDP neighbor tables for the entire LAN.

I had a ludicrous idea: an OS network stack that assigns a new outbound #IPv6 address within the subnet and with the 32-bit UNIX timestamp encoded in the IP, once per second. At least until #Y2K38, this would allow Wireshark traces to be located in time with 1 sec precision. Think of the debuggability improvements!

The downside is effectively DoSing the NDP neighbor tables for the entire LAN.

I had a ludicrous idea: an OS network stack that assigns a new outbound #IPv6 address within the subnet and with the 32-bit UNIX timestamp encoded in the IP, once per second. At least until #Y2K38, this would allow Wireshark traces to be located in time with 1 sec precision. Think of the debuggability improvements!

The downside is effectively DoSing the NDP neighbor tables for the entire LAN.

I had a ludicrous idea: an OS network stack that assigns a new outbound #IPv6 address within the subnet and with the 32-bit UNIX timestamp encoded in the IP, once per second. At least until #Y2K38, this would allow Wireshark traces to be located in time with 1 sec precision. Think of the debuggability improvements!

The downside is effectively DoSing the NDP neighbor tables for the entire LAN.

I had a ludicrous idea: an OS network stack that assigns a new outbound #IPv6 address within the subnet and with the 32-bit UNIX timestamp encoded in the IP, once per second. At least until #Y2K38, this would allow Wireshark traces to be located in time with 1 sec precision. Think of the debuggability improvements!

The downside is effectively DoSing the NDP neighbor tables for the entire LAN.

@gtronix This article clearly misses what Y2K actually was. We were very prepared as first Y2K issues popped up in 60s and 70s with life insurance policies in banking systems. The cash register issues were just comical side effects that were good for TV news cycles. So no, response to Y2K was not sudden, all the work was done in the background during the 1970s and 1980s. Your 104 year old getting an invitation was a local recent code issue with a comical but very small impact. See also our podcast episode 7 "Y2k vs Y2k38". Https://ithorrorstories.eu/#ep07 #y2k #technology #y2k38

@gtronix This article clearly misses what Y2K actually was. We were very prepared as first Y2K issues popped up in 60s and 70s with life insurance policies in banking systems. The cash register issues were just comical side effects that were good for TV news cycles. So no, response to Y2K was not sudden, all the work was done in the background during the 1970s and 1980s. Your 104 year old getting an invitation was a local recent code issue with a comical but very small impact. See also our podcast episode 7 "Y2k vs Y2k38". Https://ithorrorstories.eu/#ep07 #y2k #technology #y2k38

@gtronix This article clearly misses what Y2K actually was. We were very prepared as first Y2K issues popped up in 60s and 70s with life insurance policies in banking systems. The cash register issues were just comical side effects that were good for TV news cycles. So no, response to Y2K was not sudden, all the work was done in the background during the 1970s and 1980s. Your 104 year old getting an invitation was a local recent code issue with a comical but very small impact. See also our podcast episode 7 "Y2k vs Y2k38". Https://ithorrorstories.eu/#ep07 #y2k #technology #y2k38

@gtronix This article clearly misses what Y2K actually was. We were very prepared as first Y2K issues popped up in 60s and 70s with life insurance policies in banking systems. The cash register issues were just comical side effects that were good for TV news cycles. So no, response to Y2K was not sudden, all the work was done in the background during the 1970s and 1980s. Your 104 year old getting an invitation was a local recent code issue with a comical but very small impact. See also our podcast episode 7 "Y2k vs Y2k38". Https://ithorrorstories.eu/#ep07 #y2k #technology #y2k38

@gtronix This article clearly misses what Y2K actually was. We were very prepared as first Y2K issues popped up in 60s and 70s with life insurance policies in banking systems. The cash register issues were just comical side effects that were good for TV news cycles. So no, response to Y2K was not sudden, all the work was done in the background during the 1970s and 1980s. Your 104 year old getting an invitation was a local recent code issue with a comical but very small impact. See also our podcast episode 7 "Y2k vs Y2k38". Https://ithorrorstories.eu/#ep07 #y2k #technology #y2k38

Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
https://www.laliberte.ch/articles/monde/le-bug-de-2038-pourrait-tout-faire-planter-1411046
Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
#Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
https://www.laliberte.ch/articles/monde/le-bug-de-2038-pourrait-tout-faire-planter-1411046
Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
#Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
https://www.laliberte.ch/articles/monde/le-bug-de-2038-pourrait-tout-faire-planter-1411046
Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
#Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
https://www.laliberte.ch/articles/monde/le-bug-de-2038-pourrait-tout-faire-planter-1411046
Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
#Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

Ein bemerkenswerter Artikel in der Schweizer Zeitung La Liberté über das Jahr-2038-Problem:
https://www.laliberte.ch/articles/monde/le-bug-de-2038-pourrait-tout-faire-planter-1411046
Besonders erfreulich: Er erwähnt XSTP.epoch, das im Juni von ITU-T SG17 in Genf verabschiedet wurde.
Und im Acknowledgement wird auch unsere Arbeit aus der FIRST Time SIG und der Epochalypse-Community gewürdigt. Ein kleiner, aber schöner Meilenstein.
#Y2K38 #XSTPepoch #y2038 #DasJahr2038Problem

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 🙂

https://time.is/Unix_time

#Y2K38 #UnixTime

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 🙂

https://time.is/Unix_time

#Y2K38 #UnixTime

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 🙂

https://time.is/Unix_time

#Y2K38 #UnixTime

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 🙂

https://time.is/Unix_time

#Y2K38 #UnixTime

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 🙂

https://time.is/Unix_time

#Y2K38 #UnixTime

@nixCraft @beoz

https://det.social/@beoz

#Y2k38

@nixCraft @beoz

https://det.social/@beoz

#Y2k38

@nixCraft @beoz

https://det.social/@beoz

#Y2k38

@nixCraft @beoz

https://det.social/@beoz

#Y2k38

@nixCraft @beoz

https://det.social/@beoz

#Y2k38

@HoffmanLabs my first job out of uni in 1995 was doing Y2K fixes in PL/1 code in an all IBM house. I discovered coding wasn't my thing and pivoted to sysadmin work, and spent NYE 1999 in an eerily quiet datacentre with everything turned off.

I'm One Of Those People who gets quite upset when people say the Millenium Bug was all a lot of hot air and nothing happened. Nothing happened because we all made damn sure nothing happened 😏

So I'm keen for #Y2K38 to Not Be My Problem 😀

@HoffmanLabs my first job out of uni in 1995 was doing Y2K fixes in PL/1 code in an all IBM house. I discovered coding wasn't my thing and pivoted to sysadmin work, and spent NYE 1999 in an eerily quiet datacentre with everything turned off.

I'm One Of Those People who gets quite upset when people say the Millenium Bug was all a lot of hot air and nothing happened. Nothing happened because we all made damn sure nothing happened 😏

So I'm keen for #Y2K38 to Not Be My Problem 😀

@HoffmanLabs my first job out of uni in 1995 was doing Y2K fixes in PL/1 code in an all IBM house. I discovered coding wasn't my thing and pivoted to sysadmin work, and spent NYE 1999 in an eerily quiet datacentre with everything turned off.

I'm One Of Those People who gets quite upset when people say the Millenium Bug was all a lot of hot air and nothing happened. Nothing happened because we all made damn sure nothing happened 😏

So I'm keen for #Y2K38 to Not Be My Problem 😀

@HoffmanLabs my first job out of uni in 1995 was doing Y2K fixes in PL/1 code in an all IBM house. I discovered coding wasn't my thing and pivoted to sysadmin work, and spent NYE 1999 in an eerily quiet datacentre with everything turned off.

I'm One Of Those People who gets quite upset when people say the Millenium Bug was all a lot of hot air and nothing happened. Nothing happened because we all made damn sure nothing happened 😏

So I'm keen for #Y2K38 to Not Be My Problem 😀

@HoffmanLabs my first job out of uni in 1995 was doing Y2K fixes in PL/1 code in an all IBM house. I discovered coding wasn't my thing and pivoted to sysadmin work, and spent NYE 1999 in an eerily quiet datacentre with everything turned off.

I'm One Of Those People who gets quite upset when people say the Millenium Bug was all a lot of hot air and nothing happened. Nothing happened because we all made damn sure nothing happened 😏

So I'm keen for #Y2K38 to Not Be My Problem 😀

Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss.
Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ

Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse

#GPS #Y2K38 #Zeitsynchronisation

Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss.
Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ

Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse

#GPS #Y2K38 #Zeitsynchronisation

Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss.
Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ

Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse

#GPS #Y2K38 #Zeitsynchronisation

Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss.
Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ

Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse

#GPS #Y2K38 #Zeitsynchronisation

Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss.
Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ

Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse

#GPS #Y2K38 #Zeitsynchronisation

Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was.

#Y2K38

Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was.

#Y2K38

Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was.

#Y2K38

Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was.

#Y2K38

Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was.

#Y2K38

Ja, die aktuelle reaktionäre Politik möchte die Zeit zurückdrehen. Ich halte das für keinen zielführenden Ansatz im Umgang mit dem 2038-Problem.

#y2k38 #y2k38problem #pol

Ja, die aktuelle reaktionäre Politik möchte die Zeit zurückdrehen. Ich halte das für keinen zielführenden Ansatz im Umgang mit dem 2038-Problem.

#y2k38 #y2k38problem #pol

Ja, die aktuelle reaktionäre Politik möchte die Zeit zurückdrehen. Ich halte das für keinen zielführenden Ansatz im Umgang mit dem 2038-Problem.

#y2k38 #y2k38problem #pol

Ja, die aktuelle reaktionäre Politik möchte die Zeit zurückdrehen. Ich halte das für keinen zielführenden Ansatz im Umgang mit dem 2038-Problem.

#y2k38 #y2k38problem #pol

Ja, die aktuelle reaktionäre Politik möchte die Zeit zurückdrehen. Ich halte das für keinen zielführenden Ansatz im Umgang mit dem 2038-Problem.

#y2k38 #y2k38problem #pol

RE: https://mastodon.social/@countdownY2K38/116798041708067353

Soon we'll be yet another percentage point closer to the #Epochalypse aka #Y2k38.

RE: https://mastodon.social/@countdownY2K38/116798041708067353

Soon we'll be yet another percentage point closer to the #Epochalypse aka #Y2k38.

RE: https://mastodon.social/@countdownY2K38/116798041708067353

Soon we'll be yet another percentage point closer to the #Epochalypse aka #Y2k38.

RE: https://mastodon.social/@countdownY2K38/116798041708067353

Soon we'll be yet another percentage point closer to the #Epochalypse aka #Y2k38.

RE: https://mastodon.social/@countdownY2K38/116798041708067353

Soon we'll be yet another percentage point closer to the #Epochalypse aka #Y2k38.

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

#Y2K38 #DVB #GPS #UnixTime #MJD

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

#Y2K38 #DVB #GPS #UnixTime #MJD

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

#Y2K38 #DVB #GPS #UnixTime #MJD

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

#Y2K38 #DVB #GPS #UnixTime #MJD

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

#Y2K38 #DVB #GPS #UnixTime #MJD