Ohhh... so facebook's going to become the entire social backbone to the internet instead of being a standalone website.
I was wondering...
theharmonyguy
· 1 year ago
"There had previously been applications that could leverage the Facebook API prior to the launch of the platform but there are some significant differences now versus before."
Sorry Nick, but I'm still not seeing how this is different... the only difference I see is that the client library lets a developer use just JavaScript to interact with Facebook rather than relying on a server-side language (e.g. PHP, Python, etc.) to interact with Facebook. This would make it easier for outside sites that rely heavily on Ajax to interact with Facebook, as well as help developers who are only familiar with client-side languages. But I don't think it's that big of a change... in fact, I think people have been overlooking the outside API access which has been in place for some time.
What "broader access to Facebook's core features" does this provide? As far as I can tell, the library only makes API calls... which is exactly what outside web sites have been able to do (via server-side languages) since the API launched. Also, I'm not sure what you mean about leveraging cookies... once again, outside web sites have long been able to request a Facebook login and access data - for an example, see moochspot.com.
Peter Koning
· 1 year ago
Hi Nick I'm glad my radar picked up your post.
This will be even bigger than f8 (opening up the facebook app API).
Where can we get more info on the cookie feature?
Zuckerborg
· 1 year ago
Yeah, this really isn't that big of a deal since it requires users to be registered on Facebook. Maybe if they had added support for OpenID too.
Eric P
· 1 year ago
Moochspot is pretty cool example. It even works without having to add Moochspot as an application on FB. Question - doesn't it violate the FB Storable Information rules that you cannot store relations between IDs? That is, I add my FB friends to my piggybank so the piggybank is essentially storing that friend relationship.
113.com
· 1 year ago
Certainly very interesting...
p-air
· 1 year ago
"The second difference is that Facebook has now implemented the ability to leverage cookies to access a user’s data even when they are not at your application."
Hmmm, I wonder if this will open up similar privacy issues as Beacon did.
Luke Noel-Storr
· 1 year ago
Yep, I don't see how this "enables developers to extend their applications to their own websites" any more than the existing API did.
All it is is a method for calling the API from JavaScript without the need to have your secret key embedded in your page.
Rizwan
· 1 year ago
If I understand you Nick than you are telling us that we can now build our own website and allow users to give their facebook id so that we can fetch their information from facebook with new FB library and this can be done with javascript not with server side language like php. Is that what you are trying to say? I m more interested if you give us some sort of live example so we can understand your points in a better way:)
Marc
· 1 year ago
Everyone is saying "what's the advantage here"?. Maybe these people havent experienced the limitations a facebook application developer has within their canvas pages. You have some 400 odd pixels width to work with, and, nested branding.
Ive been elaborating for a week now and specifically just today (before hearing a word about any of this) as to how Facebook is becoming a gaming framework.
All Comments
I was wondering...
Sorry Nick, but I'm still not seeing how this is different... the only difference I see is that the client library lets a developer use just JavaScript to interact with Facebook rather than relying on a server-side language (e.g. PHP, Python, etc.) to interact with Facebook. This would make it easier for outside sites that rely heavily on Ajax to interact with Facebook, as well as help developers who are only familiar with client-side languages. But I don't think it's that big of a change... in fact, I think people have been overlooking the outside API access which has been in place for some time.
What "broader access to Facebook's core features" does this provide? As far as I can tell, the library only makes API calls... which is exactly what outside web sites have been able to do (via server-side languages) since the API launched. Also, I'm not sure what you mean about leveraging cookies... once again, outside web sites have long been able to request a Facebook login and access data - for an example, see moochspot.com.
This will be even bigger than f8 (opening up the facebook app API).
Where can we get more info on the cookie feature?
Hmmm, I wonder if this will open up similar privacy issues as Beacon did.
All it is is a method for calling the API from JavaScript without the need to have your secret key embedded in your page.
Ive been elaborating for a week now and specifically just today (before hearing a word about any of this) as to how Facebook is becoming a gaming framework.
http://www.trumptheniche.com/2008/01/27/online-...