As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. So there's nothing specifically against Apple, despite the title seeming to imply it -- just that they're taking the move right now because of Apple's new policy coming into effect. I've got to say, I really wish there were a way to know whether I already used Facebook, Google, or Apple t…
This is as close as we got trying to do it from the app itself: https://www.lukew.com/ff/entry.asp?1906 I absolutely agree that password managers could remember this stuff. Single-signon is pretty easy to identify and you could setup the relationship.
Why we won’t be supporting Sign in with Apple
401–410 of 485 posts
Re: Why we won’t be supporting Sign in with Apple
#402Earlier quoted context omitted.
Not necessarily. I have an app with 1,000 users, and about 99% of them choose to obfuscate. My app isn’t untrustworthy at all either. It’s an experimental app which attempts to let users create an iOS app on iOS. My suspicion is that people choose to obfuscate because it’s what’s selected by default.
It's also likely that 99% of users have no reason to share their email with you. Also, your app is extremely untrustworthy. It sounds like a random app you find by searching for key words. You're not Microsoft or Google, you have no reputation or credibility. They have no relationship with you, they don't know you, they likely have never interacted with your company before this. If I need an email to verify I'm not a…
This was addressed in the article. If the service provider does not have your email address, they are severely hampered with regards to customer support.
Re: Why we won’t be supporting Sign in with Apple
#403> Apple reserves the right to disable Sign in with Apple on a website or app for any reason at any time. Holy cow, how is this acceptable to any app developer or software company? This is reason enough for me to never use Apple/Facebook/Google sign-on as a developer -- huh, or even as a user. Apple/Facebook/Google could lock out all your users and literally destroy your business in a split second for an arbitrary pol…
You know the reason. It's on the front page of HN today even. Apple will support Sign in with Apple until it is co-opted by "white nationalists" or other scary characters, at which point they will disassociate with that website or app and prevent their services from working with them. Which is their right of course, but at the end of the day it means we get changes like these in the fine print. Gatekeepers like Apple…
Re: Why we won’t be supporting Sign in with Apple
#404> Apple reserves the right to disable Sign in with Apple on a website or app for any reason at any time. Holy cow, how is this acceptable to any app developer or software company? This is reason enough for me to never use Apple/Facebook/Google sign-on as a developer -- huh, or even as a user. Apple/Facebook/Google could lock out all your users and literally destroy your business in a split second for an arbitrary pol…
Re: Why we won’t be supporting Sign in with Apple
#405Just give me sign in without involvement of a third party.
Re: Why we won’t be supporting Sign in with Apple
#406Earlier quoted context omitted.
Not necessarily. I have an app with 1,000 users, and about 99% of them choose to obfuscate. My app isn’t untrustworthy at all either. It’s an experimental app which attempts to let users create an iOS app on iOS. My suspicion is that people choose to obfuscate because it’s what’s selected by default.
> My app isn’t untrustworthy at all either. That's up to the user to decide. For me trustworthy = something like Basecamp, Amazon, etc, not some random small app.
> trustworthy = [...] Amazon
Good point, because your example includes one of the few companies I don't trust at all.
Re: Why we won’t be supporting Sign in with Apple
#407Earlier quoted context omitted.
Obfuscation of the email address is an explicit choice by the user when using Sign in with Apple. It’s not something forced by the service. If users are choosing to do that, it says something about the lack of trust the users have with whatever they’re signing up for.
The biggest problem is that Apple insists on tying the fake email with your iCloud email, which the vast majority of people don’t use. If they tied it instead to what people’s normal mail was, a lot of issues would be averted.
Re: Why we won’t be supporting Sign in with Apple
#408Re: Why we won’t be supporting Sign in with Apple
#409Re: Why we won’t be supporting Sign in with Apple
#410As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. So there's nothing specifically against Apple, despite the title seeming to imply it -- just that they're taking the move right now because of Apple's new policy coming into effect. I've got to say, I really wish there were a way to know whether I already used Facebook, Google, or Apple t…
"Another issue is Sign in with Apple’s “Hide My Email” feature. With this feature, if you create an account with us, Apple will generate a special email address just for that account. So rather than your email address being john.doe@icloud.com, we will see your email address as something like dpdcnf87nu@privaterelay.appleid.com. While this is an intriguing idea that provides a measure of privacy, in practice it creates numerous support and user experience headaches..."