61–70 of 77 posts
Nice start, but perhaps Magic can also suggest the user's password by searching for their email address in a database of known password leaks.
Best feature suggestion ever. But what would be cool is to do that, but instead of pre-fill in their password, notify them that they are using a password that is known to have been a previously leaked password of theirs.
Tried about eight of my email addresses. School and work ones did nothing, and neither did my Outlook.com account, or Yahoo.com.
For Gmail addresses it just pulled the name from my Google+ account for the one that had it, and failed on all the rest.
Not super impressive IMO. Especially considering all my email addresses are some variation on firstname.lastname or flastname.
Why would you use this instead of login with Facebook/Google/Twitter/etc., which only requires two clicks from most users and actually has better privacy implication since the user knows which data you can access? Or maybe the goal of the service is for web sites to surreptitiously get more data from users who are otherwise unwilling to provide it, but are somehow willing to provide an e-mail address tied to their re…
Why would you use this instead of login with Facebook/Google/Twitter/etc., which only requires two clicks from most users and actually has better privacy implication since the user knows which data you can access? Or maybe the goal of the service is for web sites to surreptitiously get more data from users who are otherwise unwilling to provide it, but are somehow willing to provide an e-mail address tied to their re…
We saw much higher FB auth rates on desktop web than mobile—bad enough that we may forego Facebook login on mobile web entirely.
On the plus side - The convenience factor is compelling, like auto-complete. - As a v1 you can see the true magic in a seamless signup. On the downside: - It does something unusual / unexpected / creepy. - It's too slow - noticeable lag vs. say the auto-suggest in search. - If accuracy is good why bother exposing that to the user? Intercom.io does this all in the backend off of email only registrations and seems to h…
> If accuracy is good why bother exposing that to the user? That's a great point. A prior startup I worked at used a nice social referral tool, whose name slips my mind right now, but their backend would asynchronously pull Facebook, Twitter, etc. links for each of your customers. It was really convenient and worked for 80-90% from what I recall.
Earlier quoted context omitted.
Probably a caching layer on their side.
Sounds like a TOS violation
> How long can I retain the data?
> Forever! We have a very liberal data licensing policy.
So now I can find out the first and last name of the owner of whatever email I punch in there?
I don't understand what's the value of exposing this autofilled data to the user. Why not just do it on the server-side?
I wonder if a new way to do signups would be just an emailto: link that you click and send. From there it automatically logs you in and sends you a password.