Re:Introducing .app, a more secure home for apps on the web
by tokyodude on Tuesday May 01, 2018 @12:53PM
(#16968818)
Is everything on the backlog? Still not supporting long DKIM keys. Still using deprecated and discouraged SMS as 2factor. Are your margins really that thin? It's been years :(
[ Parent
| on HN ]
Re:Introducing .app, a more secure home for apps on the web
by et-al on Tuesday May 01, 2018 @06:09PM
(#16972194)
> It's been years :(
Check out this older thread from 2014: https://news.ycombinator.com/item?id=8254757
"We're rolling out Google Authenticator support sometime in the fall." What happened? :(
Re:Introducing .app, a more secure home for apps on the web
by ted0 on Tuesday May 01, 2018 @03:15PM
(#16970430)
We introduced an alternative to 2FA SMS - Authy OneTouch. We're working on adding TOTP as well.
Re:Introducing .app, a more secure home for apps on the web
by et-al on Tuesday May 01, 2018 @05:01PM
(#16971580)
Hey Ted, since you're here, may I please suggest that the future implementation of 2FA not require a separate app? Even though Namecheap is using Authy OneTouch, it still requires a dedicate app, which is unnecessary. Thanks.
Re:Introducing .app, a more secure home for apps on the web
by ted0 on Wednesday May 02, 2018 @01:37AM
(#16974348)
We partnered with Authy/Twilio on this integration to try something new. Totally get that we need additional options.
Re:Introducing .app, a more secure home for apps on the web
by et-al on Wednesday May 02, 2018 @11:47AM
(#16978075)
Thanks for the reply Ted. Looking forward to something more standardised!
Re:Introducing .app, a more secure home for apps on the web
by TheAceOfHearts on Wednesday May 02, 2018 @12:48PM
(#16978821)
Just wanna give a quick +1 to this request. The lack of proper 2FA is one of my complaints as well.
Authy OneTouch pushes you towards some fairly strong platform and vendor lock-in, which I always try to avoid.