3 ms·
Why load it unless it’s being actively used for authentication?
by RL_Quine 6y ago
Why load it unless it’s being actively used for authentication?
- cassianoleal 6y agoWell, how do you get consistent tracking then? Obs: I'm being sarcastic but since it's either this or developer laziness, I'm betting on tracking since I always start from the principle that the developers analysed the situation and made an explicit choice.
- Sephiroth87 6y agoExcept, you know, when does a developer ever have a choice? You are asked to put the SDK in and you do it...
- zuppy 6y agothis, combined with a wrong past technical decision that we can not change it instantly. unfortunately it's not as easy to fix mobile bugs as it is on the web, as you have to both pass the approval process and wait for the full rollout to clients. in our case, it's just a wrong decision, we don't use it for tracking. also, if you use facebook login, the terms and conditions force you to use their SDK (which automatically initialises when included and does this crap). https://developers.facebook.com/policy/ https://developers.facebook.com/policy/ - 8.2 "Native iOS and Android apps that implement Facebook Login must use our official SDKs for login. "
- zentiggr 6y ago> we don't use it for tracking True, you're just facilitating, not profiting. Such a clear and obvious good reason to drop support and walk away.
- Sephiroth87 6y agoSome people like to keep their job...
- cassianoleal 6y agoJust to clarify, when I say "the developer" I don't necessarily mean the person writing the code: I mean the organisation developing the software, so they definitely have the choice. In terms of the person writing the code, they can certainly push back. Being asked to add the Facebook SDK is either a red flag enough for him/her to do so, or they don't mind. In either case, they've made that choice.