If you care about user privacy, don’t use Facebook JavaScript SDK
1–10 of 105 posts
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#2That brings up the question : does Facebook get any less information because you used a 3rd party OAuth library to authenticate from FB, instead of using FB's own SDK which injects an iframe?
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#3The last two words of the title seem rather superfluous.
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#4Original article from Dev.to: https://dev.to/simplelogin/if-you-care-about-user-privacy-do...
I've recently implemented authentication for my project and I would just like to say to all the relatively amateur programmers out there: for web based authentication just stick with HTTPOnly SECURE cookies with DB backed sessions that you can revoke.
The reason I'm saying this is that there's way too many posts talking about JWT (which isn't suitable for newbies), Oauth (which is more useful if you have separate authentication and resource servers) and other token based mechanisms which are what cookies are except more suitable for non web based clients.
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#5That brings up the question : does Facebook get any less information because you used a 3rd party OAuth library to authenticate from FB, instead of using FB's own SDK which injects an iframe?
The point of the article was that Facebook gets information on not only those who are using Facebook to login, but those who aren't, because the "Login with Facebook" button is an iframe when using the SDK.
OAuth does not have this issue.
If you choose to login with Facebook, it is implicit that Facebook receives information.
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#6[deleted]
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#7Why would any developer or engineer who has even an iota of consideration for privacy, web standards, and, indeed, humanity want to work for such a repugnant company as Facebook?
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#8Alternatively, only use SDK in login page, and keep the login page separate, or use a click even to load it. And after login is done, you no longer need to load the SDK ever again.
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#9Why would any developer or engineer who has even an iota of consideration for privacy, web standards, and, indeed, humanity want to work for such a repugnant company as Facebook?
[deleted]
Re: If you care about user privacy, don’t use Facebook JavaScript SDK
#10Why would any developer or engineer who has even an iota of consideration for privacy, web standards, and, indeed, humanity want to work for such a repugnant company as Facebook?
Not a FBer myself, but I do know that people do worse things for less pay.