home.social

#timestamps — Public Fediverse posts

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

  1. Ah, yes, because the world desperately needed a deep dive into crafting the Usain Bolt of #Linux #timestamps 🏃‍♂️⏰ for the three people who plan to rewrite their system clocks 🤓. Congrats on discovering how to reinvent the wheel with extra steps, all while no one cares 🤦‍♂️.
    hmpcabral.com/2026/04/26/the-f #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated

  2. Are your dev teams struggling with slow feedback loops and constant friction?

    💡 Building #PsychologicalSafety fosters better collaboration, open communication, and stronger outcomes - making it safe to ask questions and admit mistakes.

    🎧 Learn more! Watch the #InfoQ #podcast video for more insights: bit.ly/3GHGNkz

    ⏱️ #timestamps included in the description!

    #DeveloperExperience #TeamWork #TeamCollaboration

  3. Are you a senior software developer, architect, or engineering leader looking to #StayAhead in 2025?

    Dive deep into the critical trends shaping #SoftwareArchitecture, featuring expert insights from Thomas Betts, Eran Stiller, Daniel Bryant & Sarah Wells.

    🎧 Don’t miss out – watch the #InfoQ #podcast now: bit.ly/3S9Heql

    ⏱️ #timestamps included for easy navigation!

    💪 Knowledge is power! #TrendsReport

  4. ⏰✨ Welcome to the #future of #note-taking, where every thought is chained to the tyranny of time! Notetime: because apparently, #simplicity means plastering #timestamps all over your fleeting genius. 📝⏳
    notetimeapp.com #fleeting-genius #productivity #HackerNews #ngated

  5. One of my students from a #FOR508 class I taught took some of my initial research on #macOS #timestamps and extended it further to find macOS updates timestamps differently for different file types as well 🤯

    Here’s there research that Crystal Tan recently did. If you do macOS #DFIR work, this is definitely worth a read.

    🔗 forensicatorjourney.gitbook.io

    #digitalforensics

  6. I deeply respect @briankrebs, but in this case I think the data he's presenting is fundamentally invalid. A little-known fact about #Git history is that #timestamps are both definable and mutable. While you might be able to make statements about when a Git commit was pushed to a server using the server-side SSH or HTTP logs, the fact that you can set GIT_AUTHOR_DATE and GIT_COMMITTER_DATE as environment variables means you can't rely on commit timestamps alone for this type of analysis.

    This is a feature of Git since the ability to squash or rewrite its mutable history is a key differentiator compared to #FossilSCM or other #SCMs that treat history as immutable(ish). For example, allowing one to do things like report a commit as the time a patch or source document was originally written rather than just noting when it was committed or merged can be very useful in accurately representing the real-world evolution of data created outside the repository.

    This is not a flaw in Git. Anyone savvy enough to craft the #xz attack could just as easily have adjusted their system clocks instead, leading to fraudulent timestamps in the commit history anyway.

    Forensically, you'd need to look at the timestamps from NTP-backed server or router logs, not just the Git history. All Git clients are technically "offline" until they push one or more commits to a remote, so there's really no way to validate client-side SCM timestamps. This is also true of email headers, filesystem attributes, and any other data that relies on real system clocks or user-defined timestamps, so you'd need more points of correlation than are provided here.

    linkedin.com/posts/bkrebs_one-

  7. One of the issues on Ingenuity early flights was the navigation camera dropping frames, which in turns caused timestamp issues in subsequent frames. Having spent a non-trivial amount of time fighting dropped frames and inaccurate timestamps I'm comforted by NASA having similar issues...

    youtube.com/watch?v=cIrX6gpUxy

    #mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler

  8. One of the issues on Ingenuity early flights was the navigation camera dropping frames, which in turns caused timestamp issues in subsequent frames. Having spent a non-trivial amount of time fighting dropped frames and inaccurate timestamps I'm comforted by NASA having similar issues...

    youtube.com/watch?v=cIrX6gpUxy

    #mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler

  9. One of the issues on Ingenuity early flights was the navigation camera dropping frames, which in turns caused timestamp issues in subsequent frames. Having spent a non-trivial amount of time fighting dropped frames and inaccurate timestamps I'm comforted by NASA having similar issues...

    youtube.com/watch?v=cIrX6gpUxy

    #mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler

  10. One of the issues on Ingenuity early flights was the navigation camera dropping frames, which in turns caused timestamp issues in subsequent frames. Having spent a non-trivial amount of time fighting dropped frames and inaccurate timestamps I'm comforted by NASA having similar issues...

    youtube.com/watch?v=cIrX6gpUxy

    #mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler

  11. One of the issues on Ingenuity early flights was the navigation camera dropping frames, which in turns caused timestamp issues in subsequent frames. Having spent a non-trivial amount of time fighting dropped frames and inaccurate timestamps I'm comforted by NASA having similar issues...

    youtube.com/watch?v=cIrX6gpUxy

    #mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler

  12. today's distributed system fun is different log systems that record their timestamps with different rounding (ms vs μs) so some events move back in time by an average of half a millisecond

    #timestamps
    #rounding
    #logging