Comments on: The battle for the future of the social web http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/ This can all be made better. Ready? Begin. Mon, 16 Apr 2012 18:32:33 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Facebook unmasked http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-103274 Facebook unmasked Fri, 26 Dec 2008 11:17:17 +0000 http://factoryjoe.com/blog/?p=953#comment-103274 "If you want your information removed from our servers, we can do this for you. However, you need to first log in and delete all profile content. Once you have cleared your account, let us know, and we'll take care of the rest. We apologize for any inconvenience this may cause." The email address for privacy issues is privacy@facebook.com. http://www.facebookunmasked.com “If you want your information removed from our servers, we can do this for you. However, you need to first log in and delete all profile content. Once you have cleared your account, let us know, and we’ll take care of the rest. We apologize for any inconvenience this may cause.”

The email address for privacy issues is privacy@facebook.com.

http://www.facebookunmasked.com

]]> By: Data Portability | Blogs @ Northern Light http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99871 Data Portability | Blogs @ Northern Light Mon, 21 Jul 2008 15:06:26 +0000 http://factoryjoe.com/blog/?p=953#comment-99871 [...] The Battle for the Future of the Social Web Factory City, May 23, 2008 [...] [...] The Battle for the Future of the Social Web Factory City, May 23, 2008 [...]

]]> By: Marc’s Voice » Blog Archive » A reference design for building the Open Mesh http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99400 Marc’s Voice » Blog Archive » A reference design for building the Open Mesh Wed, 18 Jun 2008 17:16:23 +0000 http://factoryjoe.com/blog/?p=953#comment-99400 [...] that others will do it their own way, so any platform for the open mesh must deal with - head on - the anarchy and chaos which we live in today.  Google will continue to one-up Facebook and Microsoft, Yahoo is playing catch-up and MySpace [...] [...] that others will do it their own way, so any platform for the open mesh must deal with – head on – the anarchy and chaos which we live in today.  Google will continue to one-up Facebook and Microsoft, Yahoo is playing catch-up and MySpace [...]

]]> By: Marc’s Voice » Blog Archive » Live Mesh could be Twitter’s Plan B or we might have to do it ourselves http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99258 Marc’s Voice » Blog Archive » Live Mesh could be Twitter’s Plan B or we might have to do it ourselves Tue, 03 Jun 2008 17:56:53 +0000 http://factoryjoe.com/blog/?p=953#comment-99258 [...] In the chaos that we’re building that becomes the open mesh, there are no single winners - ’cause I don’t think Evan Williams is hanging out in Dubai, Moscow or Singapore enough to do that. [...] [...] In the chaos that we’re building that becomes the open mesh, there are no single winners – ’cause I don’t think Evan Williams is hanging out in Dubai, Moscow or Singapore enough to do that. [...]

]]> By: Marc’s Voice » Blog Archive » June 2nd blogging '08 http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99252 Marc’s Voice » Blog Archive » June 2nd blogging '08 Mon, 02 Jun 2008 20:38:52 +0000 http://factoryjoe.com/blog/?p=953#comment-99252 [...] likes what Chris Messina has to say.  Me too.  Favorite quotes from this post: I’m coming over to Eran and others‘ point that 1) [...] [...] likes what Chris Messina has to say.  Me too.  Favorite quotes from this post: I’m coming over to Eran and others‘ point that 1) [...]

]]> By: Patrick Chanezon http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99206 Patrick Chanezon Tue, 27 May 2008 21:51:58 +0000 http://factoryjoe.com/blog/?p=953#comment-99206 About the REST API, there is one that is being defined in OpenSocial. The spec has been proposed in february in the public spec discussion group, and is finalized these days. http://code.google.com/apis/opensocial/docs/dataapis.html http://groups.google.com/group/opensocial-and-gadgets-spec/msg/87df6973a9f94fe1 proposed february http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/d4eecee18d84eea1/259d9ff6c5e06f38?lnk=gst&q=rest#259d9ff6c5e06f38 About the REST API, there is one that is being defined in OpenSocial. The spec has been proposed in february in the public spec discussion group, and is finalized these days.
http://code.google.com/apis/opensocial/docs/dataapis.html
http://groups.google.com/group/opensocial-and-gadgets-spec/msg/87df6973a9f94fe1
proposed february
http://groups.google.com/group/opensocial-and-gadgets-spec/browse_thread/thread/d4eecee18d84eea1/259d9ff6c5e06f38?lnk=gst&q=rest#259d9ff6c5e06f38

]]> By: Scott Rafer http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99203 Scott Rafer Tue, 27 May 2008 20:35:26 +0000 http://factoryjoe.com/blog/?p=953#comment-99203 Create their own RESTful API? yes, they do, though there's no reason not to clone others' syntax. And there's no reason to re-build the metering/security/reporting/metrics infrastructure. Mashery does all that as a service bureau. Create their own RESTful API? yes, they do, though there’s no reason not to clone others’ syntax. And there’s no reason to re-build the metering/security/reporting/metrics infrastructure. Mashery does all that as a service bureau.

]]> By: George Koiliaris http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99199 George Koiliaris Tue, 27 May 2008 08:51:43 +0000 http://factoryjoe.com/blog/?p=953#comment-99199 A really good article. Especially the first part with the Game consoles ;) A really good article. Especially the first part with the Game consoles ;)

]]> By: Julian Bond http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99198 Julian Bond Tue, 27 May 2008 06:52:03 +0000 http://factoryjoe.com/blog/?p=953#comment-99198 The big activity here at the moment is all about gadgets and gadget containers. But what of RESTful APIs? Does *every* site have to follow the Twitter model and create their own? The big activity here at the moment is all about gadgets and gadget containers. But what of RESTful APIs? Does *every* site have to follow the Twitter model and create their own?

]]> By: theharmonyguy http://factoryjoe.com/blog/2008/05/23/the-battle-for-the-future-of-the-social-web/comment-page-1/#comment-99197 theharmonyguy Tue, 27 May 2008 05:43:27 +0000 http://factoryjoe.com/blog/?p=953#comment-99197 Great perspective, Chris - I really hadn't viewed the whole scenario in this light yet. Much to think about. One thing that I've hardly seen discussed anywhere, though, is a technical comparison of the platforms. Regardless of what you think about Google, Facebook, the OpenSocial Foundation, etc., both platforms have different architectures that raise big concerns. For instance, all of the sites I've seen using Google's new Friend Connect lose all social features when JavaScript is disabled. OpenSocial is heavily reliant on iframe's and client-side code, raising questions of accessibility, security, and performance. Even if you think Facebook is an evil proprietary walled garden, you have to give them credit for building a platform that tightly integrates into the site via a template structure that's processed server-side. Usable Facebook applications can be built with their entire frontends free of iframe's and scripts (or not - iframe's and scripts aren't inherently evil, I'm just making a point). For all the "proprietary" talk regarding FBML, the end result is still HTML. I see OpenSocial and F8 following two very different paths regarding implementation, and while I respect OpenSocial's steps to be more "open," the iframe/script approach gives me great concern. Regardless of whether Facebook and Google work together or a DiSo approach takes over or what, I hope the eventual "winner" is one that takes into account these kind of technical issues - for the good of both developers and users. Great perspective, Chris – I really hadn’t viewed the whole scenario in this light yet. Much to think about.

One thing that I’ve hardly seen discussed anywhere, though, is a technical comparison of the platforms. Regardless of what you think about Google, Facebook, the OpenSocial Foundation, etc., both platforms have different architectures that raise big concerns.

For instance, all of the sites I’ve seen using Google’s new Friend Connect lose all social features when JavaScript is disabled. OpenSocial is heavily reliant on iframe’s and client-side code, raising questions of accessibility, security, and performance. Even if you think Facebook is an evil proprietary walled garden, you have to give them credit for building a platform that tightly integrates into the site via a template structure that’s processed server-side. Usable Facebook applications can be built with their entire frontends free of iframe’s and scripts (or not – iframe’s and scripts aren’t inherently evil, I’m just making a point). For all the “proprietary” talk regarding FBML, the end result is still HTML.

I see OpenSocial and F8 following two very different paths regarding implementation, and while I respect OpenSocial’s steps to be more “open,” the iframe/script approach gives me great concern. Regardless of whether Facebook and Google work together or a DiSo approach takes over or what, I hope the eventual “winner” is one that takes into account these kind of technical issues – for the good of both developers and users.

]]>