4 ms·

It seems like the reason websites are starting to do this is that facebook authentication gives the developer more information than just an email/credentials.

It seems like the reason websites are starting to do this is that facebook authentication gives the developer more information than just an email/credentials. The developer can access all of the basic data in the user's profile and also grab their friend list. This means that later down the line they can automatically connect friends together inside the developer's own service without having to ask their users for that data, which as you know means 90% won't bother. It's essentially a value add to the developer (and much more debatably to the user) over other authentication options. I can see the interest in requiring or at least encouraging users to use this feature.

gregable 16y ago
Not that this means I agree that you as a developer should do this, just that I understand. There are lots of hidden issues too - your service now has added another third-party dependency that could kill you if they decided to break in some way that you couldn't reverse from. Facebook now has all of your user/traffic numbers which they can use against you if they ever decide to compete with you on any front. In the future, advertisers can potentially reach users you've pre-targeted without paying you and instead paying facebook. The list goes on. It's putting a lot of trust in your relationship with facebook.
xiongchiamiov 16y ago
The reasons you point out as benefits I see as downsides. Facebook tends to leak personal information like crazy as it is; they don't need any help from random 3rd parties.
ajleary 16y ago
Well said. Seems like most people replying are speaking as users who guard their privacy everywhere. Most consumer products are aimed at people that are looking for the bacon immediately. Facebook gives developers a lot of useful information fast so they can get on to deliver the content or service the user thinks they are getting. When the plumbing works, it's a lot easier to enjoy the architecture where developers and designers deliver real services.

gregable 16y ago

Not that this means I agree that you as a developer should do this, just that I understand. There are lots of hidden issues too - your service now has added another third-party dependency that could kill you if they decided to break in some way that you couldn't reverse from. Facebook now has all of your user/traffic numbers which they can use against you if they ever decide to compete with you on any front. In the future, advertisers can potentially reach users you've pre-targeted without paying you and instead paying facebook. The list goes on. It's putting a lot of trust in your relationship with facebook.

xiongchiamiov 16y ago

The reasons you point out as benefits I see as downsides. Facebook tends to leak personal information like crazy as it is; they don't need any help from random 3rd parties.

ajleary 16y ago

Well said. Seems like most people replying are speaking as users who guard their privacy everywhere. Most consumer products are aimed at people that are looking for the bacon immediately. Facebook gives developers a lot of useful information fast so they can get on to deliver the content or service the user thinks they are getting. When the plumbing works, it's a lot easier to enjoy the architecture where developers and designers deliver real services.