#timestamps — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #timestamps, aggregated by home.social.
-
Software architect and consultant Oskar Dudycz shares a tale of negative experiences with PostgreSQL's timestamp functions inside transactions, that led to a fiendishly difficult to diagnose bug.
TL;DR? There is subtle, yet important difference between now() and clock_timestamp(), specially if you're measuring time lapse inside a transaction.
"How soon is now in PostgreSQL?"
https://www.architecture-weekly.com/p/how-soon-is-now-in-postgresql
#postgresql #timestamps #programming #transactions #databases
-
Software architect and consultant Oskar Dudycz shares a tale of negative experiences with PostgreSQL's timestamp functions inside transactions, that led to a fiendishly difficult to diagnose bug.
TL;DR? There is subtle, yet important difference between now() and clock_timestamp(), specially if you're measuring time lapse inside a transaction.
"How soon is now in PostgreSQL?"
https://www.architecture-weekly.com/p/how-soon-is-now-in-postgresql
#postgresql #timestamps #programming #transactions #databases
-
Software architect and consultant Oskar Dudycz shares a tale of negative experiences with PostgreSQL's timestamp functions inside transactions, that led to a fiendishly difficult to diagnose bug.
TL;DR? There is subtle, yet important difference between now() and clock_timestamp(), specially if you're measuring time lapse inside a transaction.
"How soon is now in PostgreSQL?"
https://www.architecture-weekly.com/p/how-soon-is-now-in-postgresql
#postgresql #timestamps #programming #transactions #databases
-
Software architect and consultant Oskar Dudycz shares a tale of negative experiences with PostgreSQL's timestamp functions inside transactions, that led to a fiendishly difficult to diagnose bug.
TL;DR? There is subtle, yet important difference between now() and clock_timestamp(), specially if you're measuring time lapse inside a transaction.
"How soon is now in PostgreSQL?"
https://www.architecture-weekly.com/p/how-soon-is-now-in-postgresql
#postgresql #timestamps #programming #transactions #databases
-
Software architect and consultant Oskar Dudycz shares a tale of negative experiences with PostgreSQL's timestamp functions inside transactions, that led to a fiendishly difficult to diagnose bug.
TL;DR? There is subtle, yet important difference between now() and clock_timestamp(), specially if you're measuring time lapse inside a transaction.
"How soon is now in PostgreSQL?"
https://www.architecture-weekly.com/p/how-soon-is-now-in-postgresql
#postgresql #timestamps #programming #transactions #databases
-
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 🤦♂️.
https://www.hmpcabral.com/2026/04/26/the-fastest-linux-timestamps/ #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated -
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 🤦♂️.
https://www.hmpcabral.com/2026/04/26/the-fastest-linux-timestamps/ #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated -
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 🤦♂️.
https://www.hmpcabral.com/2026/04/26/the-fastest-linux-timestamps/ #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated -
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 🤦♂️.
https://www.hmpcabral.com/2026/04/26/the-fastest-linux-timestamps/ #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated -
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 🤦♂️.
https://www.hmpcabral.com/2026/04/26/the-fastest-linux-timestamps/ #UsainBolt #SystemClocks #TechHumor #ReinventingTheWheel #HackerNews #ngated -
Events und #Zeitstempel: Wann ist etwas wirklich passiert? | Developer https://www.heise.de/blog/Events-und-Zeitstempel-Wann-ist-etwas-wirklich-passiert-11136630.html #TimeStamp #TimeStamps
-
Events und #Zeitstempel: Wann ist etwas wirklich passiert? | Developer https://www.heise.de/blog/Events-und-Zeitstempel-Wann-ist-etwas-wirklich-passiert-11136630.html #TimeStamp #TimeStamps
-
Events und #Zeitstempel: Wann ist etwas wirklich passiert? | Developer https://www.heise.de/blog/Events-und-Zeitstempel-Wann-ist-etwas-wirklich-passiert-11136630.html #TimeStamp #TimeStamps
-
Events und #Zeitstempel: Wann ist etwas wirklich passiert? | Developer https://www.heise.de/blog/Events-und-Zeitstempel-Wann-ist-etwas-wirklich-passiert-11136630.html #TimeStamp #TimeStamps
-
Time to slow down and take my time when traveling in digital worlds during #livestreams that become videos in 2026.
To help set #timestamps for making #YouTube #video chapters, I made this stream marker tool:
-
🚀 Oh, the eternal quest for #timestamps in #ChatGPT chats continues like a never-ending sequel nobody asked for. Apparently, expecting a basic feature in 2025 is like asking for a unicorn to type your code for you. 🌈 Keep holding your breath, folks, because time is a flat circle... and ChatGPT doesn't know what it is! ⏳
https://community.openai.com/t/timestamps-for-chats-in-chatgpt/440107?page=3 #features #technews #frustration #humor #HackerNews #ngated -
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
-
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
-
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
-
Der touch-Befehl in Linux: Dateien erstellen, Timestamps setzen & praktische Beispiele
Der touch-Befehl in Linux ist ein grundlegendes Coreutils-Tool, das leere Dateien erstellt oder die Zugriffs- (atime) und Änderungszeiten (mtime) von bestehenden Dateien auf die aktuelle Systemzeit setzt – essenziell für schnelle Dateioperationen ohne zusätzliche Inhalte. Grundlegende Verwendung: Dateierstellung Die einfachste Anwendung ist das Erstellen einer leeren Datei ohne Optionen – ideal für schnelle Vorlagen oder Tests. Erneutes nutzen des selben Befehls aktualisiert den […] -
Der touch-Befehl in Linux: Dateien erstellen, Timestamps setzen & praktische Beispiele
Der touch-Befehl in Linux ist ein grundlegendes Coreutils-Tool, das leere Dateien erstellt oder die Zugriffs- (atime) und Änderungszeiten (mtime) von bestehenden Dateien auf die aktuelle Systemzeit setzt – essenziell für schnelle Dateioperationen ohne zusätzliche Inhalte. Grundlegende Verwendung: Dateierstellung Die einfachste Anwendung ist das Erstellen einer leeren Datei ohne Optionen – ideal für schnelle Vorlagen oder Tests. Erneutes nutzen des selben Befehls aktualisiert den […] -
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: https://bit.ly/3GHGNkz
⏱️ #timestamps included in the description!
-
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: https://bit.ly/3GHGNkz
⏱️ #timestamps included in the description!
-
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: https://bit.ly/3GHGNkz
⏱️ #timestamps included in the description!
-
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: https://bit.ly/3GHGNkz
⏱️ #timestamps included in the description!
-
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: https://bit.ly/3GHGNkz
⏱️ #timestamps included in the description!
-
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
-
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
-
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 #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
-
Are #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
-
Are #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
-
Are #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
-
Are #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
-
⏰✨ 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. 📝⏳
https://www.notetimeapp.com #fleeting-genius #productivity #HackerNews #ngated -
⏰✨ 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. 📝⏳
https://www.notetimeapp.com #fleeting-genius #productivity #HackerNews #ngated -
⏰✨ 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. 📝⏳
https://www.notetimeapp.com #fleeting-genius #productivity #HackerNews #ngated -
⏰✨ 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. 📝⏳
https://www.notetimeapp.com #fleeting-genius #productivity #HackerNews #ngated -
First blog post of year: #Ruby #Rails #API #timestamps shenanigans!
https://blog.richarddegenne.fr/2025/01/03/rails-api-and-timestamps-shenanigans/
Follow the blog on Mastodon: @richard.degenne
-
@treyka the #y2038 problem will potentially affect #timestamps USED (#software), STORED (#filesystems), and COMMUNICATED (#protocols) ❗❗❗
-
@treyka the #y2038 problem will potentially affect #timestamps USED (#software), STORED (#filesystems), and COMMUNICATED (#protocols) ❗❗❗
-
@treyka the #y2038 problem will potentially affect #timestamps USED (#software), STORED (#filesystems), and COMMUNICATED (#protocols) ❗❗❗
-
@treyka the #y2038 problem will potentially affect #timestamps USED (#software), STORED (#filesystems), and COMMUNICATED (#protocols) ❗❗❗
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.