4 ms·

It sounds like if I offer Facebook google as an option I also have to allow Apple sign in right? We're not talking about requiring a social login, just offering

It sounds like if I offer Facebook google as an option I also have to allow Apple sign in right? We're not talking about requiring a social login, just offering one.

thaumasiotes 7y ago
Right, we're talking about protecting people from "Facebook-only" logins. This is a terrible practice on the part of developers, in which the only authentication the application supports is Facebook authentication. I've seen online courses require this on the theory that "we don't want to waste time learning how to do authentication". Having the rule "if you can log in with Facebook, you can also log in with Apple" is in fact a protection against Facebook-only login.
- cageface 7y ago
  If I offer email signup, with Facebook as an option, that is not Facebook only. If this new rule applied only to apps/sites where social logins are the only option it would be a bit less fishy.
- sturgill 7y ago
  This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I do not buy their company line at all. This is simply Apple flexing its power in the App Space to require developers to implement an ecosystem very few would do of their own volition. You can argue it’s a good thing. I disagree. But it is hopefully clear that Apple being able to wield this kind of power is indicative of monopolistic power in that marketplace.
  - scarface74 7y ago
    Exactly. Because developers are lazy. Apple shouldn’t put developer’s interests over user’s interests - and yes I am a developer.
  - Marsymars 7y ago
    > This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I don't think that's correct. Anyone who currently gives FB login as an option is required to support Sign On with Apple. If FB Login was previously an option, but was removed at some point, Sign On with Apple is not required.
    - sturgill 7y ago
      They clearly aren’t saying FB login is bad (or they’d just disallow it). They are saying “we want in on the game and we can force it on you.” I happen to have an app out there which we maintain security updates but aren’t adding new features. It was built with a FB login option. So now we either never update or have to implement features we don’t care about.

It sounds like if I offer Facebook google as an option I also have to allow Apple sign in right? We're not talking about requiring a social login, just offering one.

thaumasiotes 7y ago

Right, we're talking about protecting people from "Facebook-only" logins. This is a terrible practice on the part of developers, in which the only authentication the application supports is Facebook authentication. I've seen online courses require this on the theory that "we don't want to waste time learning how to do authentication". Having the rule "if you can log in with Facebook, you can also log in with Apple" is in fact a protection against Facebook-only login.

cageface 7y ago
If I offer email signup, with Facebook as an option, that is not Facebook only. If this new rule applied only to apps/sites where social logins are the only option it would be a bit less fishy.
sturgill 7y ago
This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I do not buy their company line at all. This is simply Apple flexing its power in the App Space to require developers to implement an ecosystem very few would do of their own volition. You can argue it’s a good thing. I disagree. But it is hopefully clear that Apple being able to wield this kind of power is indicative of monopolistic power in that marketplace.
- scarface74 7y ago
  Exactly. Because developers are lazy. Apple shouldn’t put developer’s interests over user’s interests - and yes I am a developer.
- Marsymars 7y ago
  > This isn’t a protection, it applied retroactively as well. Anyone who ever gave FB login AS AN OPTION is now required to create Sign In with Apple. I don't think that's correct. Anyone who currently gives FB login as an option is required to support Sign On with Apple. If FB Login was previously an option, but was removed at some point, Sign On with Apple is not required.
  - sturgill 7y ago
    They clearly aren’t saying FB login is bad (or they’d just disallow it). They are saying “we want in on the game and we can force it on you.” I happen to have an app out there which we maintain security updates but aren’t adding new features. It was built with a FB login option. So now we either never update or have to implement features we don’t care about.