I'd love to read more about this!

Comments URL: https://news.ycombinator.com/item?id=47348652

Points: 291

# Comments: 142

Comments URL: https://news.ycombinator.com/item?id=35321898

Points: 19

# Comments: 15

Comments URL: https://news.ycombinator.com/item?id=35019142

Points: 1

# Comments: 1

Comments URL: https://news.ycombinator.com/item?id=33766477

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=31510476

Points: 126

# Comments: 38

Comments URL: https://news.ycombinator.com/item?id=30598565

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=30592477

Points: 7

# Comments: 3

I'm 21 :-)

We built a product in ~5 months with real-time collaboration, extensive interactivity, Oauth, Stripe and Gmail integrations with a standard Ruby on Rails stack.

It's rock-solid, performant, dead-simple and extremely productive to work with.

Why're we throwing away years of learning to build unstable, complex and inaccessible applications?

https://support.twilio.com/hc/en-us/articles/223181668-Can-T...

Looks like you need to get the feature enabled, so you can receive SMS from shortcodes. You also need a number in the same country as the shortcode, so users of the service would need to indicate which country the number is for. This would most likely be fine, as I think most people only use 1 number in 1 country anyway.

Hopefully this would solve (1)

Twilio allows you to register mobile numbers, so I think (2) would be ok.

3. I'm not intending to use any hardware, so I think I could disregard this limitation, although it's useful to know anyway!

I'm thinking about building a service which is capable of receiving your 2FA SMS texts from third parties, and forwarding them to you via email.

We'd do this by registering numbers on your behalf, which you'd then use when signing up for the third-party (or setting up 2FA later).

This has a number of advantages:

    SMS can be unreliable and/or slow
    your phone might not be nearby, charged, or have signal
    you could share the codes with other trusted contacts (via email, or have their own accounts to view online)
    can use auto-generated numbers to reduce risk (multiple numbers, multiple services)
    "new phone who dis?" no probs, your number isn't bound to any of those services any more

I can see this being especially useful for SMEs where a lot of 'personal' SaaS plans are being used—where there's often only a single root user which multiple people access—or individuals who dislike being bound to a phone number.

I will never have enough information to access their account for the 3rd party service, and I'll only be processing the codes. Privacy & security is my primary concern with this, I am not interested in holding the keys to anyone's castles, so I will be operating on a minimum trust basis.

Really keen to get some thoughts on this project. If I go ahead with it, I'm intending to build it as an Open Startup and share progress in public.

I've got a landing page here for those who wish to register their interest: https://onetime.codes/

I've also got a bare-bones post on ProductHunt if that's more your jam: https://www.producthunt.com/posts/onetime-codes

Comments URL: https://news.ycombinator.com/item?id=30424437

Points: 6

# Comments: 8

Comments URL: https://news.ycombinator.com/item?id=29612398

Points: 7

# Comments: 2

`bin/rails g component Button --sidecar`