#timestamps — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #timestamps, aggregated by home.social.
-
ChatGPT conversations still lack timestamps after years of requests
https://community.openai.com/t/timestamps-for-chats-in-chatgpt/440107?page=3
#HackerNews #ChatGPT #Timestamps #ChatGPT #Conversations #UserFeedback #OpenAI #Community
-
ChatGPT conversations still lack timestamps after years of requests
https://community.openai.com/t/timestamps-for-chats-in-chatgpt/440107?page=3
#HackerNews #ChatGPT #Timestamps #ChatGPT #Conversations #UserFeedback #OpenAI #Community
-
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: https://bit.ly/3S9Heql
⏱️ #timestamps included for easy navigation!
💪 Knowledge is power! #TrendsReport
-
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: https://bit.ly/3S9Heql
⏱️ #timestamps included for easy navigation!
💪 Knowledge is power! #TrendsReport
-
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.
-
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.
-
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...
https://www.youtube.com/watch?v=cIrX6gpUxyw
#mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler
-
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...
https://www.youtube.com/watch?v=cIrX6gpUxyw
#mars #computerVision #cameras #droppedFrames #timestamps #ingenuity #basler