4 ms·
This is exactly what happened. Although I am involved in product on 100% of the time, I don't deal with specific implementation details, the engineers working o
by danielpal 14y ago
This is exactly what happened. Although I am involved in product on 100% of the time, I don't deal with specific implementation details, the engineers working on the solution deal with that. So I tried to be a truthful as possible and answer all the questions I could, I simply got some details wrong. One of the engineers noticed and I rectified my answer.
- blake8086 14y agoI'm not trying to be rude, but they weren't "details", they were the difference between "secure" (which is the service you sell) and "insecure".
- danielpal 14y agoDetails are really important. That doesn't mean I could possibly handle every single detail myself, I can't. We have a whole team that handles different parts of the system and they are fully qualified. In fact the engineers doing this feature did write the correct implementation. I simply made a mistake answering the question. I think people are confusing the Authy Google Authenticator Support with the Authy product. We do not sell Google Authenticator or aim to be a replacement for it. We simply added the possibility to add Google Authenticator tokens into the Authy App - mostly since our existing clients wanted this -. Our Service, it's usage etc are completely separate.. If you are not using Authy you can simply use Google Authenticator App. The only thing in common is we both use RFC 6238 which is an open standard for Time based OTP's.