02-20-2017, 05:24 AM
Hi!
I've been working on a website for a while now and researching the various options for drop-in authentication, and I'm impressed with UserSpice as it almost (almost) meets all of the requirements that I have.
I am sure I have a laundry list of things I'd like to see, and as I become familiar with the product, I'll learn to write them in a UserSpice friendly way. Off the top of my head, a few things are keeping me from transitioning over.
1. Now that you have social logins, the only two I need to finish this are Twitter and LinkedIn. I wrote code to do this on my 'old site' and it's not all that different from Oauth2 for Facebook. The more social logins that are supported, the more useful this will be, and perhaps there is some tutorial that makes it easy to set these up.
2. A contact form that sends an email. If the user is logged in, fill in their contact info, if not, allow them to still send it.
3. AJAX forms. I really like using jQuery and Ajax to reduce amount of data required for forms processing, it would be cool to do this.
4. Birthdate. It's somewhat important, at least from my perspective, that new users indicate they are over the age of 13. There are legal reasons for this. My site is not an adult site, but collecting data from users under the age of 13 is somewhat of a quagmire. I imagine that I could just put this into the TOS but I also like to have birthdates for profiles and things.
I am sure there are plenty of nuances and features I would like to see here, but these are the items keeping me from just hopping on the bandwagon, and leaving the authentication problem to UserSpice, and focusing on the internals of the website.
Thanks for your efforts, hopefully it will meet the need.
I've been working on a website for a while now and researching the various options for drop-in authentication, and I'm impressed with UserSpice as it almost (almost) meets all of the requirements that I have.
I am sure I have a laundry list of things I'd like to see, and as I become familiar with the product, I'll learn to write them in a UserSpice friendly way. Off the top of my head, a few things are keeping me from transitioning over.
1. Now that you have social logins, the only two I need to finish this are Twitter and LinkedIn. I wrote code to do this on my 'old site' and it's not all that different from Oauth2 for Facebook. The more social logins that are supported, the more useful this will be, and perhaps there is some tutorial that makes it easy to set these up.
2. A contact form that sends an email. If the user is logged in, fill in their contact info, if not, allow them to still send it.
3. AJAX forms. I really like using jQuery and Ajax to reduce amount of data required for forms processing, it would be cool to do this.
4. Birthdate. It's somewhat important, at least from my perspective, that new users indicate they are over the age of 13. There are legal reasons for this. My site is not an adult site, but collecting data from users under the age of 13 is somewhat of a quagmire. I imagine that I could just put this into the TOS but I also like to have birthdates for profiles and things.
I am sure there are plenty of nuances and features I would like to see here, but these are the items keeping me from just hopping on the bandwagon, and leaving the authentication problem to UserSpice, and focusing on the internals of the website.
Thanks for your efforts, hopefully it will meet the need.