so the app at dayjob has an internal scheduler, one of the formats for which handles, like, "on the 12th at 8am" tests for it were failing intermittently, in daily CI job only i'm curious if there are any devs out there whose trauma runs deep enough they already know the story
-
-
No see, what you have to do is make a timestamp server, in case your clock has drift in it. And the only way to know that the timestamp is correct is to build a hash tree, and the only way to protect against bad actors populating the tree is to prove you did the work.
-
For real though, not storing the originating timestamp is the "just guess the encoding" of time programming.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.