Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: I built a free, simple login service. Would you use this?

login.land

Post reply on HN
Print view View original

81–90 of 110 posts

Re: Show HN: I built a free, simple login service. Would you use this?

#81

Post by chrismorgan »

Jenz wrote: post #64
darau1 wrote: post #41

Earlier quoted context omitted.

I definitely don't think it's /useless/, but I wouldn't use it. Someone out there wants a dead simple login solution that they can get running with a handful of lines of code. That being said, if this was /self hostable/, I'd see myself using it on a few projects.

Off-topic side remark HN ‘markup’ diversity is always a joy for the punctuation mark enthusiast. \Hooray for markup/

(You know, you can get proper italics. Wrap it in asterisks. Some discover this by accident when it mangles asterisks they meant as literal asterisks.)

Re: Show HN: I built a free, simple login service. Would you use this?

#82

Post by varbhat »

No.

Google signin is used because of Chrome/Android(Or browsers in general because of Google account which many people have it atleast because of Gmail).

Apple ID( their login ) is useful because of Apple ecosystem which constitutes IOS,MacOS,etc.

So,there is no appealing reason to use your product. What if it is down in future? Also,it's closed source and not federated.

I am interested in federated login system(Probably OpenID based?)

Think it like a single self hosted login system for all Gitea(which may happen in future)/Gitlab instances or federated open sourced self hosted(or company hosted) alternative to Google signin , speaking common protocol.

Re: Show HN: I built a free, simple login service. Would you use this?

#83

Post by yodon »

koopuluri wrote: post #40

My first thought when I was going through the page: HN will not see much value in this given it's a highly technical crowd. I urge you NOT to get discouraged, and to chat with non-technical online small business builders: you'd find many who market primarily on Instagram, who are just figuring out how to get a nice website for their brand. I see a lot of value if you position your service as a way for them to offer a…

Following up on @kupuluri's note, focus heavily on a very simple very clear tutorial/walkthrough. If you can't make the tutorial simple, keep iterating on the product until you can.

Okta and Auth0 and Cognito are big established competitors but their products are complicated. If you've never done auth before it's not easy to figure out which of the many approaches and examples those services offer is the right one to use, and it's a big job to puzzle through and get them to work.

Handle the 80% case incredibly well with an incredibly simple tutorial. Leave everything that won't fit into the incredibly simple tutorial for later.

Re: Show HN: I built a free, simple login service. Would you use this?

#85

Post by darau1 »

Jenz wrote: post #64
darau1 wrote: post #41

Earlier quoted context omitted.

I definitely don't think it's /useless/, but I wouldn't use it. Someone out there wants a dead simple login solution that they can get running with a handful of lines of code. That being said, if this was /self hostable/, I'd see myself using it on a few projects.

Off-topic side remark HN ‘markup’ diversity is always a joy for the punctuation mark enthusiast. \Hooray for markup/

I used it that way because I've gotten used to the org-mode syntax. It's much easier to /me/.

Re: Show HN: I built a free, simple login service. Would you use this?

#87

Post by benzguo »

colinmorelli wrote: post #75

It's a fun project, and kudos for shipping something at all! My honest feedback: There are already a host of services that do authentication, and a host of services that do payment and subscription management, and the leaders in each of those spaces are actually quite good. Loginland currently sits in the middle - it's not the best authentication system, nor is it the best payment system. It's just a little bit of bo…

Thank you so much for this thoughtful comment! I really appreciate your feedback, and the encouragement :)

I totally agree with you that it feels like this product currently sits in a weird mushy middle – not a great fit for coders on HN, and not differentiated enough in the crowded no-code-storefront space.

I’ll keep iterating!

Re: Show HN: I built a free, simple login service. Would you use this?

#88

Post by pachico »

I would only use it if I needed to create a quick MVP/PoC but then I'd fastly run to implement it once the idea is validated. In addition to the reasons already mentioned here, I'd say login is one of those features every language has a ready-to-use library for. Also, it might be that a certain ACL is required too, which is typically very specific for your domain.

Re: Show HN: I built a free, simple login service. Would you use this?

#89

Post by onli »

kgraves wrote: post #51

will you be there in 10 years?

He does not have to be there in 10 years. If his service where to go away you just change the login system to something else, there are open source alternatives. The id is the email, so there is no lock-in. That's for the login-part at least, adding stripe manually on top would be a bit more complicated, but doable.

Re: Show HN: I built a free, simple login service. Would you use this?

#90

Post by fouc »

wakamoleguy wrote: post #52
IgorPartola wrote: post #37

Earlier quoted context omitted.

Login management should be built into the browsers instead. Imagine a UI where you go to log in and instead of a text/email field for login and a password field you get a drop down with a list of your personas that you’ve created with the option of adding a new one. Under the hood it would use a public/private key pair to authenticate you with the site. Browsers could implement a service that backs up your personas a…

That sounds very much like the goals of Mozilla's Persona service. While it required a separate service and some JavaScript, the idea was that it could be supported natively by browsers in the long run. Unfortunately, it was shut down in 2016 due to lack of interest. (Coincidentally, I just spent this past week hacking on its source code.)

I'd imagine Apple would have more success with this type of service due to the vertical integration. And they are kinda going in this direction..
Post reply on HN