• quatrocentix (unregistered)

    2026 + 261 = 2287 2287 - 1970 = 317 317×365×24×3600 ≈ 10¹⁰

  • quatrocentix (unregistered)

    Dangit, my newlines:

    2026 + 261 = 2287

    2287 - 1970 = 317

    317×365×24×3600 ≈ 10¹⁰

    (sorry, feel free to delete my previous comment)

  • Tevildo (unregistered) in reply to quatrocentix

    The assumption that 1 year = 365 24-hour days is going to bite them very quickly.

  • Conradus (unregistered)

    "Important according to Google magic" caught my eye. Apparently this is a thing in Gmail.

  • quatrocentix (unregistered) in reply to Tevildo

    To be fair, that was just my back-of-the-envelope calculation ("quick maths" as the saying goes) to see if the UNIX timestamp is near some recognizable value. Now that I'm back at the desktop, python's datetime library says UNIX timestamp 10 billion is 2286 Nov 20 18:46:40.

    Amusing sidechannel attack: as of today (2026 Aug 7), UNIX 10¹⁰ is just under 260.5 years, so it would be rounded down to 260 years. For it to be over 260.5 years in the future and thus rounded up to 261 years, the screenshot had to have been taken no later than 2026 July 23.

  • (nodebb)

    Given how 𝛶𝛺 describes the community, I'd say that the new member likely started the registration process, including uploading a profile picture, and then had an hour-long think about whether they really wanted to join.

  • Hmmmm (unregistered)

    A friend was able to flash his Acura TL so that it worked correctly again. I think there was a patch someone figure out that added the correct offset back in.

  • YΩ (unregistered)

    Out of curiosity, I scrolled down the profile history to the beginning, checked and compared the timestamps (which are actually shown on mouseover). It says the picture was uploaded 3:39 PM and the user joined 4:48 PM.

  • (nodebb)

    Yeah, my car's GPS time is screwed up because of the rollover. If I turn on GPS time sync it'll go to some oddball time. But at least it lets me set the clock and calendar manually. Not ideal, but oddly works.

  • (nodebb) in reply to YΩ

    That could be explained if the "user joined" event happens after completing an account verification process that a lot of systems have, where you can still access your profile before that, but not post anything, a la web forums and such.

  • YΩ (unregistered) in reply to gordonfish

    Indeed, that seems to be the case. I looked at some other recent profiles with pictures and found that usually the first picture was uploaded before the account was created. Usually it was just a few minutes difference, and so I never noticed it. In this particular case I was just lucky that the difference was more than 1 hour and I ran across the profile a couple of hours later, when it would still display "1 hour" and "2 hours", instead of "x days" on both events a few days later.

  • mihi (unregistered) in reply to quatrocentix

    The screenshot has been taken before June 2nd 2025, since at that time Netvibes shut down their services :)

  • (nodebb)

    TRWTF is who thought it was necessary, let alone a good idea, for a car to use space and time to display the current year? Not enough UI space for Doc Brown, waste of UI space for everyone else.

  • 516052 (unregistered) in reply to Paddles

    Ah, to be young. Trust me, when you get to a certain age you start having days when you can't remember the year you are in. :(

  • (nodebb) in reply to Worf

    at least it lets me set the clock and calendar manually. Not ideal, but oddly works.

    Oh dear. Back in the day, that was the only way to set the correct date and time. How on earth did we manage?

    Now get off my lawn.

Leave a comment on “Time Wounds All Heels”

Log In or post as a guest

Replying to comment #703139:

Log Out

« Return to Article