Sure, OpenSocial has mostly focused on consumery stuff — Ning, MySpace, Orkut — and that's cool, but it has great potential behind the firewall. Atlassian is leading the charge here, using OpenSocial to help our products exchange data and components, and opening the door to new types of interoperability between enterprise and consumer systems.
OpenSocial is commonly described as a more open cross-platform alternative to the Facebook Platform, it's a set of common application programming interfaces (APIs) for web-based social network applications, developed by Google along with MySpace and a number of other social networks.
On Netlog, you can create your own web page with a blog, pictures, videos, events and much more to share with your friend
Google Friend Connect provides simple user authentication using any OpenID account, including Google, Yahoo and AIM. Instead of filling in yet another profile form, your users can connect to their existing identities, showing current profile pictures. By making login easier and connected to existing identity, you'll see increased engagement and comment activity. The Google Friend Connect plugins are proof-of-concept code to integrate users with external accounts into your site. A user can visit your site and leave a comment with a Google Account, Yahoo Account, any OpenID, or in future other sites that participate in OpenSocial. See separate instructions for the WordPressPlugin, DrupalPlugin and PhpbbPlugin
In the year and half since OpenSocial's public launch, there are now over 700 million end users of OpenSocial applications across numerous social sites (containers) around the world. With OpenSocial's proven global success in traditional social applications, the enterprise software community has now begun to realize its potential and build innovative solutions that cater to the enterprise. Join us for a session centered on how the enterprise software development community is successfully bringing social concepts and technology into the enterprise. Key enterprise players will present and demonstrate how they've successfully used OpenSocial software to build new social solutions.
What is Shindig? Shindig is a container for hosting social application consisting of four parts: * Gadget Container JavaScript: core JavaScript foundation for general gadget functionality (read more about gadget functionality). This JavaScript manages security, communication, UI layout, and feature extensions, such as the OpenSocial API. * Gadget Rendering Server: used to render the gadget XML into JavaScript and HTML for the container to expose via the container JavaScript. * OpenSocial Container JavaScript: JavaScript environment that sits on top of the Gadget Container JavaScript and provides OpenSocial specific functionality (profiles, friends, activities, datastore). * OpenSocial Data Server: an implementation of the server interface to container-specific information, including the OpenSocial REST APIs, with clear extension points so others can connect it to their own backends. Shindig is the reference implementation of OpenSocial API specifications, a standard set of Social Network APIs which includes: * Profiles * Relationships * Activities * Shared applications * Authentication * Authorization
]]>
]]>
]]>
Imagine if Google Accounts added support for the (upcoming) OpenSocial REST APIs. All of a sudden, each of these App Engine sites could start injecting activity and querying for activity across each other. Maybe you'll argue that this just means that Google Accounts could become the next big social network, but isn't it a bit different when this functionality is just a part of your hosting infrastructure? What if Google Accounts ignored the notion of friends and instead left that to actual social networks? If done right, this really could be the first shipping glimpse of the distributed social web that there is to come.
]]>
]]>
]]>
]]>
]]>
]]>
"As part of this continuing innovation, you acknowledge and agree that Google may stop (permanently or temporarily) providing the API (or any features of the API) to you or to users generally at Google.s sole discretion, without prior notice to you."
]]>
]]>
]]>
]]>
]]>
Le lancement d'OpenSocial a beaucoup fait parler de lui ces derniers jours. En tant que partenaires de lancement, nous reconnaissons qu'il s'agit là d'une excellente initiative, bien que cela ne réponde pas à la question principale : quid du conteneur d'applications ? Les développeurs devront-il coder plusieurs versions de leur applications en utilisant différents conteneurs en fonction de la plateforme ? C'est pourquoi nous avons décidé que dès l'instant où la technologie sera mature, toutes les API sociales existantes seront intégrés en tant que plugins à l'UWA, notre Universal Widget API.