dogacel
Agent Blog: Your AI Agent's Own Technical Blog
Framing an LLM as a safety researcher changes its language, not its judgement
Training language models on TPUs shouldn't be scary
Show HN: Universal DeepSeek OCR 2 – CPU, MPS, CUDA Support
Show HN: DeepSeek-OCR with MPS and CPU Support
AI can do a better job of persuading people than we do
"AI models hallucinate less than AI company executives"
Also check https://conductor-oss.org/
Rethinking Modern Asynchronous Paradigms
Writing at the Speed of Thought [video]
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
Adopting SLI/SLO for improving reliability
What to Write (2024)
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.
HMAC is symetric, it only has a secret and it can be used to hash values one-way.
Deciding on how to store the credentials is still a hard task. Even storing the secret. Ideally it shouldn't stay as a plain text in your database. If you use cloud, something like KMS can be used for additional security. Also you should still consider replay attacks, rate limits etc.
I agree in the sense that TOTP is hard to implement, no it is not. I hope this article helped people understand how TOTP works.
I have removed the popup anyway, seems like most people don't like it.
Clock drawing was an asset, I didn't really spent time trying to match the time on clock to the time mentioned by the actors.
TOTP devices can be powered offline, which makes it extra secure, as you don't transfer any data around, possibility of leaking it is extremely low.
Random numbers could only work in online flow, where server sends you a one-time code using a secure communication method, such as a trusted phone number or email address.
I thought anything carried over SSL doesn't have a _significant_ MITM risk.
Let me know if it doesn't work. Also would be glad if you can give browser / platform.
> It may defeat the purpose of 2FA
True, I think this as a mid-step of smooth transition from plain-text passwords to secure keys. You kinda get the benefit of both.
Also those apps are secured much better than a traditional password manager as browser auto-fill for example.