headermask image

header image

Perfect example of un-informed , irresponsible journalism

from here

Having been on holiday, I missed the excitement over Google’s OpenSocial, but at least I’m in time to observe the inevitable backlash. Having read the news reports, three things are moderately suprising.

First, as far as I can see, it’s just a widget format, ie Google Gadgets. I’m sure there is value to having a common Google-sponsored widget format for mini-applications, because it reduces the amount of work needed to put Vampires or whatever on different social networking sites. But really, who cares?

Second, I can’t see what’s open about it. Sure anybody can write apps for it, but anybody can write apps for Facebook, or, indeed, Windows. There’s more to come, but at the moment, it looks just as proprietary as the Facebook system it more-or-less copies. The main difference being that Google appears to own and control the OpenSocial container/API in which the widgets run. But should it feel the need, Facebook can make its system just as “open” as Google’s, simply by allowing other sites to host Facebook apps.

Russell Beattie has had a whinge about openness in Where the hell is the Container API?

Would people be jumping on this bandwagon so readily if it was Microsoft unilaterally coming up with an API, holding secret meetings geared towards undercutting the market leader, and then making sure that only those anointed partners get a head start on launch day by making sure a key part of the API isn’t released — even in alpha. (It obviously exists already, all the partners have that spec and even sample code, I’m sure. The rest of us don’t get access yet, until the GOOG says otherwise).Christ, if this was a Microsoft move, there’d be torches and pitchforks out. I honestly don’t see why Google gets a free pass here.

Third, if there’s a need to transfer personal data between social networking sites, there’s a much simpler and easier way to do than OpenSocial. A microformat like a suitably-expanded hCard would do the job perfectly well in an industry standard way, similar to the vCard standard, RFC 2426. (Marshall Kirkpatrick at Read/Write Web makes the same point in OpenSocial: Three Big Concerns.) But I’ve tried talking to Google about microformats before, and it appears to be one of their blind spots (to their cost: Gdata has been a huge flop). You don’t actually need OpenSocial to transfer or share your personal data, and from reading Dare Obasanjo, OpenSocial looks worse. As for transferring relationship data, who gave you the right?

Dare Obasanjo aka Carnage4Life has posted OpenSocial: Technical Overview and Critique exploring some of the technical problems, though he concludes: “Despite these misgivings, I think this is a step in the right direction. Web widget and social graph APIs need to be standardized across the Web.” Fair enough.

I can also understand the enthusiasm of people like Marc Andreesson (of Ning), because it puts all the non-Facebook social networks on a level playing field, from the widget hosting point of view:

With the Facebook platform, only Facebook itself can be a “container” — “apps” can only run within Facebook itself. In contrast, with Open Social, any social network can be an Open Social container and allow Open Social apps to run within it.

from here
Yes, that’s good for developers, but it still doesn’t mean anything until people start to decide on their social network according to which widgets it will run. At the moment, they don’t care. When they do care, there’s nothing to stop Facebook from adding OpenSocial/Gogle Gadgets as well. Which will take seconds.

Over the long term, there are good reasons for thinking — and for hoping — that a good open system will beat a good closed system, like Facebook. So far, however, OpenSocial has yet to show that it’s either good or open. The idea that it signals the death of Facebook in the foreseeable future is just stupid.

WHY DO I CALL IT UN INFORMED ?

because to write for Windows or for Facebook one needs to learn a proprietary language and API, Open Social runs on ” open source ” / standardised languages - read up here - now there is, obviously, a lot in common with FCBK in the way the data is treaetd in between page refreshes etc. but one is OPEN the other is CLOSED.

Schofields ` article is perfect example of how many people still have not understood what open standards are or what it means. ergo - un informed and ultimately irreposnsible.

infact his article smacks of MSFT gravy - “Would people be jumping on this bandwagon so readily if it was Microsoft unilaterally coming up with an API, holding secret meetings geared towards undercutting the market leader, and then making sure that only those anointed partners get a head start on launch day by making sure a key part of the API isn’t released — even in alpha. (It obviously exists already, all the partners have that spec and even sample code, I’m sure. The rest of us don’t get access yet, until the GOOG says otherwise).

Christ, if this was a Microsoft move, there’d be torches and pitchforks out. I honestly don’t see why Google gets a free pass here.

a ) there is nothing unilateral about the API, the world is still free Schofield, Google never held a gun to anyones head, they just cmae up with a great idea and MySpace and Linked In decided to join

b ) Why ? bcos unlike MSFT and FCBK , the GOOG never asked for them to give up any rights, in fact they are releasing the Open Social platform as ” open ” so any one can do as they like with it, LinkedIn and the like joined to benefit and to benefit future users

c )  holding secret meetings geared towards undercutting the market leader - my response :  refuse to be a Microserf for life,

d ) I see the spec here but Russel Beattie  did not and Schofield merely copied his errenous assertion

e ) ” Yes, that’s good for developers, but it still doesn’t mean anything until people start to decide on their social network according to which widgets it will run. “  Schofield I suggest you actually research the topics you are talking about before you publish such nonsense bcos this para makes it clear that even you can publish your apps to your own page using Open Social, ie. people dont need to choose their network based on whether or not it support OS cos ALL sites are potential targets for OS,

Get more on Open Social here

If you liked my post, feel free to subscribe to my rss feeds

Post a Comment

You must be logged in to post a comment.