21–30 of 73 posts
I see it as oblivious executives trying to monopolize whatever they think they can monopolize.
The future is in yubikey-style authentication.
I’m not a dev but a consumer in this question and I’d just say a service or site that has Sign In with Apple and Apple Pay available on the web is and instant use on my end. I will continue to vote with my paltry wallet for these technologies to take off even more, especially Sign In with Apple. I don’t want to give my actual email out. I like the relay aspect. And it should make logging in and user management and si…
What apps are using Apple Sign In, anyway? I haven't run into any and kind of just assumed it died or hasn't launched yet.
I’m not a dev but a consumer in this question and I’d just say a service or site that has Sign In with Apple and Apple Pay available on the web is and instant use on my end. I will continue to vote with my paltry wallet for these technologies to take off even more, especially Sign In with Apple. I don’t want to give my actual email out. I like the relay aspect. And it should make logging in and user management and si…
I’m not a dev but a consumer in this question and I’d just say a service or site that has Sign In with Apple and Apple Pay available on the web is and instant use on my end. I will continue to vote with my paltry wallet for these technologies to take off even more, especially Sign In with Apple. I don’t want to give my actual email out. I like the relay aspect. And it should make logging in and user management and si…
Failing that, have you heard of spamgourmet? Along with a password manager, I have unique logins and passwords to most websites I use.
A workaround is to use a domain you own and either point it at one of those services or set up a catch-all address with your e-mail provider. I do the latter. I have @subdomain.adomainiown.example configured at FastMail with * delivered to a folder in my main e-mail account. As a nice bonus, I can also send messages with alias@subdomain.adomainiown.example as the From address when needed.
Since it is a domain I own and no one else uses it, no services will likely stop me from using it. And since it's a subdomain, it's not easy to discover so spammers can't indiscriminately blast away at everypossibleaddress@adomainiown.example.
I’m not a dev but a consumer in this question and I’d just say a service or site that has Sign In with Apple and Apple Pay available on the web is and instant use on my end. I will continue to vote with my paltry wallet for these technologies to take off even more, especially Sign In with Apple. I don’t want to give my actual email out. I like the relay aspect. And it should make logging in and user management and si…
I’ve spent at least $2000 using Apple Pay on the Web that I wouldn’t have otherwise.
(Also, everyone who uses Stripe for payment flow--not just processing, but with the Stripe widget--should take 10 minutes and enable Apple Pay. On the other hand, maybe please don't because then I'll be very broke and in debt with the ease of purchasing...)
I’m not a dev but a consumer in this question and I’d just say a service or site that has Sign In with Apple and Apple Pay available on the web is and instant use on my end. I will continue to vote with my paltry wallet for these technologies to take off even more, especially Sign In with Apple. I don’t want to give my actual email out. I like the relay aspect. And it should make logging in and user management and si…
I don’t want to sound dismissive but the fact that a very tech-savvy HN user likes Sign In with Apple isn’t all that indicative of anything broader. I think that’s why the OP wanted to know what things look like on the backend.
It reminds me of when I used to participate in a lot of gaming related forums and etc. The enthusiast crowd would pan a game as just terrible and unplayable ... and it would go on to sell lot hot cakes and just rake in the money.
Earlier quoted context omitted.
Failing that, have you heard of spamgourmet? Along with a password manager, I have unique logins and passwords to most websites I use.
The issue I ran into in the past with sites like spamgourmet is once they get moderately known, other sites start blocking the use of their addresses (that is, Zorflab.whatever will refuse to let users put in a @spamgourmet.com address). A workaround is to use a domain you own and either point it at one of those services or set up a catch-all address with your e-mail provider. I do the latter. I have @subdomain.adoma…
What's nice with SG is that the emails are sent to /dev/null once the count is over whereas with a catchall, you keep receiving everything sent to any address for ever.
Haven’t done anything with Apple sign in, but I worked with a lot of other providers before. If you have multiple options, users might forget what service they used. This becomes an even bigger problem if the paid for a service with a different provider and can’t find their purchase. If you do use something like this, only having one provider (only Apple) makes things less confusing.
Yes, that is a problem. If your app/site supports multiple login options you may have users who "lose" their account (I'm one of them). However your solution... doesn't work. Apple requires apps that support social app to have sign in with apple. Google has similar requirements (because your app better be multi-platform in this day in age). Facebook is way popular. So that's three right there.
Earlier quoted context omitted.
The issue I ran into in the past with sites like spamgourmet is once they get moderately known, other sites start blocking the use of their addresses (that is, Zorflab.whatever will refuse to let users put in a @spamgourmet.com address). A workaround is to use a domain you own and either point it at one of those services or set up a catch-all address with your e-mail provider. I do the latter. I have @subdomain.adoma…
Yes, this happens. Although I've been using SG for something like 10 years now and it's rare when a website blocks @SG (and the dozen other synonym domains) addresses. What's nice with SG is that the emails are sent to /dev/null once the count is over whereas with a catchall, you keep receiving everything sent to any address for ever.
That's true, and I wish Fastmail had a better way of managing rules remotely (with something like remote sieve or an API) so I could script a click-button-turf-address-forever. On the other hand, I don't mind still getting the follow-ups for some stuff. For example, Target has target@thatdomain.italkedabout.example for years to use for order confirmations.
Haven’t done anything with Apple sign in, but I worked with a lot of other providers before. If you have multiple options, users might forget what service they used. This becomes an even bigger problem if the paid for a service with a different provider and can’t find their purchase. If you do use something like this, only having one provider (only Apple) makes things less confusing.