dogacel
Joined 2 years ago
Karma
130
Submissions
39
Member since
Jun 1
Recent submissions
Comment · 1 year ago
Comment · 1 year ago
I recently discovered them, it is pretty cool. I really wish we could use it for our business workflows.
Also check https://conductor-oss.org/
Comment · 1 year ago
What is the expected cost of running those tests? I think it would be a good argument to compare this to running cost of unit / integration tests for a function (based on action runners).
If it is so expensive, it can be distributed as a simple GitHub integration / action that runs perodically, what do you think?
Also see, https://dl.acm.org/doi/abs/10.1145/3663529.3664458
Comment · 1 year ago
> A counter that can be synchronized on demand is kinda superfluous --- not really secret and not terribly relevant either. All else being equal, an attacker can sync up just as easily as a legitimate client so why bother with the counter?
A unique counter for each authorization attempt ensures the resulting key is different for each attempt, which makes replay attacks not possible. I agree if you sync the counter two ways, it is better to use a "nonce", a totally random secret each time.
"AI models hallucinate less than AI company executives"