Facebook Login
, now has a tighter approval process. Apps that wish to use Facebook’s social login feature must adhere to "strict requirements." The company also says: “We will reduce the data that an app can request without app review to include only name, profile photo and email address. Requesting any other data will require our approval.” Tinder, a dating platform, is the most notable app borked by Facebook’s changes. Users reported being suddenly unable to use the app, which was quickly identified as a Facebook login issue. Gizmodo reporter Melanie Ehrenkranz then tried to create a unique profile via Tinder and was unable to do so, which could be indicative of users creating profiles en masse; an innocent DDoS, so to speak. Tinder’s issues suggest Facebook made changes without alerting partners. At the time I write this, it’s unclear what Tinder’s best path forward is; using it on desktop seems to work for some, but that’s not how most people use (or want to use) Tinder. [caption id="attachment_136636" align="aligncenter" width="750"] Facebook HQ[/caption]
Can Developers Really Avoid Social Login APIs Like Facebook's?
In the wake of Facebook’s huge scandal surrounding how it handles personal data, a change to its app login API is leaving some apps nearly broken. It’s a reminder that building your own stack is probably best... but is it the best thing to do when it comes to logins and authentication? The API in question,