Facebook is going everywhere. It had Facebook Connect, which allows you to login to other websites with your Facebook credentials, and then now it had features for personalization, allowing 3rd party sites to use your Facebook interest and information. And then there's the Like button. And sooner or later there will be sites build using mostly Facebook API, using your Facebook credentials, social graph, photo, and any other Facebook information you have.
In building application architecture, if there is one thing we must always guard against, it would be single point of failure.
Imagine those sites that uses Facebook Connect for login exclusively. And imagine the day when Facebook goes down. And now we can no longer login to those sites.
How about a sudden serious exploit/bug that was detected, and Facebook temporary disable the API calls for many sites. If the sites failed to cache the data, or the data expired before Facebook re-offer those data, you will not be able to use those sites.
Think of a future where Facebook managed to assimilate most of the Internet, and Facebook goes down. Pretty scary thought, actually.
I'm not really a fan of centralized single sign-on. Or putting all your eggs into a single basket. The internet was not designed in that way. It was designed to be decentralized, such that if a single node fail, the internet still works. There are multiple paths to reach the same destination. We need to learn from that design. Decentralize your social graph and social profile. Federate the login credentials. We need to guard against the single point of failure that may descend upon us anytime.