I know that January 19th 2038 is going to be super interesting and all, but did you know that DVB (the TV stuff) wont blow up? It uses a slightly different timestamp (that is pretty miserable to parse as it turns out), so it can last a whole few more months past the end of the world, DVB will keep ticking along (at least in it's TOT and TDT packets) until May 22nd 2038
benjojo
replied 24 Aug 2025 00:08 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/ZWhvQxPRzdhVzz9p3V
Whoever at ETSI decided that DVB/MPEG-TS would use Modified Julian Date for it's dates is [redacted]
litchralee_v6@ipv6.s..
replied 24 Aug 2025 00:46 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/BL4CJDbDx814RqlgPd
@benjojo Wait, so is this in both the DVB spec and the spec for MPEG-TS? The latter has me concerned, since I think the North American digital TV spec (ATSC) also uses MPEG-TS.
benjojo
replied 24 Aug 2025 08:43 +0000
in reply to: https://ipv6.social/users/litchralee_v6/statuses/115080977790732118
@litchralee_v6 in talking about TOT and TDT packets, that appears in the MPEG-TS streams of DVB, and presumably ATSC as well. But I don't have any of those recordings on hand because I'm not American
benjojo
replied 24 Aug 2025 00:13 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/BL4CJDbDx814RqlgPd
Also we get a whole soft start on the whole "timestamps based explosions" saga on February 7, 2036, when the NTP one will stop working Debian Trixie being year 2038+ ready and all is nice, but I feel like the scope of chaos is so so great that we are still no where near ready and we are still shipping systems that will be running in 2038, only for them to explode..
penguin42@mastodon.o..
replied 24 Aug 2025 00:17 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/3B5ZZ31z6JHwcQQ5XK
benjojo
replied 24 Aug 2025 00:33 +0000
in reply to: https://mastodon.org.uk/users/penguin42/statuses/115080863581595733
dickon@splodge.fluff..
replied 26 Aug 2025 12:03 +0000
in reply to: https://mastodon.org.uk/users/penguin42/statuses/115080863581595733
@penguin42 @benjojo Yes it is, because it isn't the physical layer that's the problem. The AV and metadata streams are basically identical across DVB-{T,T2,S,S2,C}, and it's the MJD in the metadata tables that's the problem. I bitched about this in about 2004, when I discovered it. It's mad.
terinjokes@toots.mee..
replied 24 Aug 2025 00:46 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/3B5ZZ31z6JHwcQQ5XK
@benjojo Everytime the battery runs out on my GPS unit I have to dig out a serial cable and a Windows 98 software to reset the time, as Garmin never thought you'd use it long enough for the GPS epoch to rollover.
mirabilos@toot.mirbs..
replied 24 Aug 2025 00:48 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/3B5ZZ31z6JHwcQQ5XK
@benjojo huh. I just read up a bit on this. The era is never transmitted, Mills just relies on external means (filesystem timestamps, pre-existing RTC setting, build timestamp if must be) to get the expected local time close enough. Urgs. I guess I’ll have to patch that into my Linux ports of rdate and openntpd. (BSD sets the clocktime to the root filesystem time if the latter is larger, at boot; Linux, e.g. on that RPi1 I got as gift, happily boots into January 1970 and then complains.)
q@glauca.space
replied 24 Aug 2025 00:16 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/ZWhvQxPRzdhVzz9p3V