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

Why we won’t be supporting Sign in with Apple

blog.anylist.com

Post reply on HN
Print view View original

271–280 of 485 posts

Re: Why we won’t be supporting Sign in with Apple

#271

Post by TheArcane »

renewiltord wrote: post #88
TheArcane wrote: post #76

> 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. Ironically, this is also why I use Sign Up with Apple at every opportunity I can

How is this ironic? It is by design and obviously they know why people do it because the very next sentence says that. Why on Earth would you'd want to use a list-sharing app that uses email as the addressing system and then not share your email.

It's ironic because anylist cites that as a reason to stop supporting that very feature. That would only reduce my desire to Sign Up for that app.

Re: Why we won’t be supporting Sign in with Apple

#272

Post by bpicolo »

rtpg wrote: post #254
fladrif wrote: post #202

Earlier quoted context omitted.

With a password manager though, I avoid having tradeoffs in the first place. I get some amount of anonymity by separating my accounts, and it's trivial to login to sites with the same amount of clicks as with third party sso.

Password manager doesn't stop you from having to fill in a bunch of stuff. Like yeah, it's only a couple minutes, but if it's for an app you'll use a handful of times in your life, just hitting that G will be much nicer.

Most of them have a hotkey for fill out + submit form.

Re: Why we won’t be supporting Sign in with Apple

#273

Post by godelski »

muro wrote: post #18
djrogers wrote: post #4

This makes perfect sense from their standpoint - especially since they've had similar problems to what they outline with Facebook sign-in and are now dropping that as well. This is also a win for Apple & end-user privacy, as there's one less app using FB's login feature now. I think Sign in with Apple is a great step forward even if all it does is eliminate apps that require Facebook and/or Google accounts to log in.…

I've never seen an app that required a FB or Google login. It was always possible to use email+password.

DnDBeyond only has these types of logins and does not allow email+password

Re: Why we won’t be supporting Sign in with Apple

#274

Post by ryanianian »

crazygringo wrote: post #157

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…

I create dummy logins in my password manager for sites that use external auth. Username of just “LOGIN WITH GOOGLE”. Hacky but it makes me smile every time it gets filled in.

Re: Why we won’t be supporting Sign in with Apple

#275

Post by nuker »

intellirogue wrote: post #3

Worth noting that AnyList automatically subscribed me to a marketing list without double opt-in or any kind of consent, which is exactly the kind of behaviour that makes me not want apps to have my real email address.

> automatically subscribed me to a marketing list

Side note, disabling 'load remote content' in email client stops all spam in a while, they think emails are not read.

Re: Why we won’t be supporting Sign in with Apple

#276

Post by threeseed »

dahfizz wrote: post #221
pwinnski wrote: post #193

Earlier quoted context omitted.

The nature of "other" platforms means that example code could be in any language at all. The fact that their iOS documentation is so much better than average doesn't mean their "other platforms" documentation is inadequate. It just means there's plenty of room for third parties like indie bloggers to documentation their own approaches in JavaScript, Python, Ruby, Rust, or whatever.

I think you're missing the point. Part of the problem is that android is an "other platform" in the first place. Sign in with apple is supposed to be a cross platform feature, but Apple can't be bothered to even write out some decent documentation for a platform with over 2 billion devices. Compare, for example, the Google sign in for iOS[1]. They provide a working example project and full documentation. If you are a…

> This is not something that you just copy paste from some half baked blog post. It is amazing to me you think that's acceptable.

Have you ever actually implemented a proper sign-in process e.g. with OIDC, JWT, SSO etc ?

Because half baked blog posts is the industry standard.

Re: Why we won’t be supporting Sign in with Apple

#277

Post by sudoit »

AnonC wrote: post #228
rahimnathwani wrote: post #194

Earlier quoted context omitted.

"all their arguments apply to all third-party sign-ons" No they don't. Other sign-on options don't obfuscate the email address. They are likely removing FB login as otherwise their next app update will be rejected by Apple for supporting third party login but not Apple login.

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.

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.

Re: Why we won’t be supporting Sign in with Apple

#278

Post by bradleybuda »

rattray wrote: post #237
AnonC wrote: post #228

Earlier 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.

There's two kinds of "obfuscation" at play with Sign In With Apple. One is true obfuscation - "hide my email". That would be a poor choice for use with any app you hope to have an ongoing relationship with, I'd think. The other is just the use of iCloud email addresses, detailed in the post, which seemed like a very good and concerning point. It's also much less likely to be a problem with FB or Google login.

I can have an ongoing relationship with an app without that app’s developer having an ongoing relationship with my inbox.

Re: Why we won’t be supporting Sign in with Apple

#279

Post by mssio »

Developer should just ask for user's email after new sign up using third party provider. Even Facebook does not require email for user to sign up. They should separate the email used for the account & the email used for third party sign in. Because 1 user can have multiple third party sign in, all with different email.

I think they did not need to care about customer who did not check the reply email from support, because customer can also have multiple email and did not use their primary email to sign up to your service.

Re: Why we won’t be supporting Sign in with Apple

#280

Post by kripy »

crazygringo wrote: post #157

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…

Perform an audit on yourself. Both Facebook [1] and Google [2] have pages where you can check third-party apps that you have connected with. You might be surprised what you find.

[1] https://www.facebook.com/settings?tab=applications&ref=setti...

[2] https://myaccount.google.com/security

Post reply on HN