• Full support of all the features of OpenSocial v0.9
• A more friendly payment interface
• Support for the RESTful API of OpenSocial
• More useful info on the wiki

• Google and the Social Web
• Building a Business with Social Apps
• Designing OpenSocial Apps for Speed and Scale
• The Social Web: An Implementor's Guide
• Powering Mobile Apps with Social Data
• Google Friend Connect In The Real World
• OpenSocial in the Enterprise
• Beyond Cut & Paste: Deep integrations with Google Friend Connect
• Google Friend Connect Gadgets: Best Practices in Code and Interaction Design

• The biggest real-name based network in the world
• Payment API with proven virtual currency, Dotori
• Viral distribution system integrated with NateOn, the leading instant messenger in Korea with 27 million registered members

• 23 million registered members
• Among them, 13.6 million members log in on the site more than once per month
• Average number of 1-chon (friends) per member, 47.8
• All Cyworld members are connected to each other by 4.5 degrees of separation
• 6.6 billion photographs uploaded
• 19.6 billion postings
• 12 million postings posted everyday
• 8 million replies posted everyday
• 2,320 stars with Cyworld Minihompies
• 1.7 million members visiting their Minihompies everyday

• Wonder how Playfish, RockYou!, Zynga and others have attracted millions of users to their apps? Ask questions for the Fireside Chat with App Developers here!
• Thinking of starting your own OpenSocial container, but not sure where to start? Ask questions for the Fireside Chat with Containers here!
• Wondering how you can take this technology into the enterpise? Ask questions for the "OpenSocial in the Enterprise" session here!
  

1. Client requests profile and friend info from the container (via DataRequests)
   
2. Container responds with the social data
   
3. Client requests application data from a remote server (via makeRequest)
4. Container proxies request to remote server
   
5. Remote server responds to container with application data
   
6. Client combines the social and application data and presents it to the user (via JavaScript)

1. Client requests an application view
2. The container sends social data to the remote server
3. The remote server combines social and application data, returning HTML and JavaScript
4. The container sends the content to the client

• New ideas are proposed and discussed on the spec list (which anyone can contribute to).
• Proposals that are selected by the community are prototyped to flesh out the details.
• After a vote, the new version of the spec is published.
• Containers implement support for the new spec.
• App developers start using the new features.

<script xmlns:os="http://ns.opensocial.org/2008/markup" type="text/os-data">
 <os:PeopleRequest key="friends" userId="@viewer" groupId="@friends">
</script>

<Require feature="opensocial-templates">
 <Param name="process-on-server">true</param>
</Require>

<script type="text/os-template">
  <ul>
   <li repeat="${friends}">
     <span class="name" id="id${Context.Index}">${Cur.name.givenName}</span>
   </li>
  </ul>
</script>

• repeat - iterate over the 'friends' object by adding the repeat attribute to the element.
• Context.Index - an index for the object being repeated.
• Cur - a reference to the current object. In this case that object is a JSON representation of a person so you can access fields directly.

1. Go to the 'Labs' tab under Gmail Settings.
2. Enable the 'Add any gadget by URL' experiment and click 'Save Changes.'
3. Now you'll have a 'Gadgets' tab under Settings.
4. Enter the URL of an OpenSocial gadget spec and click 'Add'.

1. Your app can only access information about users that have been whitelisted for the sandbox.
2. You can install any app (not just those approved for the directory) by entering the URL in the Edit applications page.

Slapster began as an idea scribbled on a piece of paper, and now orkut users all over the site are totally slapping each other silly. At Games2win, we said to ourselves, “Hey! A whole lotta people enjoy Slapster. Let’s get them together and have a party!” Thus, the Official Slapster Community was born.

We didn’t have many Slapster users jumping on in the couple of weeks, but once we decided to included a link in our application to join the community we started to see thousands of users join. Now with more than 70,000 users in the Official Slapster community, all I have to say is "The more the merrier!"

The community has proven to be helpful in more than one way. What started out as an exercise in simply bringing people who like Slapster together, soon turned into a means for connecting to our users. They started telling us what they liked about Slapster, what they didn’t like, what could be improved. The community also gave us a channel for sharing news about our next project: Crapster! When Crapster was ready to launch users in the Slapster community were excited to see our latest offering! Crapster gained popularity quickly, proving that communities make great marketing tools as well.

So here’s a step by step guide to building and using communities as ways to promote your own apps and having fun while you’re at it:

1. Get yourself a killer app ;)
2. Create a community on orkut and invite everyone you know. In simple words, you have your horn, now blow it. Be sure to let everyone know that your community is the authentic, official one.
3. Place a link to the community on the app info page and also inside the app. This will make it easier for people to find your community and establish it as the official one.
4. Once you have people in your community you have to keep them busy. Start fun topics, polls, conversations, anything under the sun and have fun while you’re at it. In the midst of all the fun, you can also ask users what new features the app could use or what changes they would like to see.

So there you have it. The magic, not-so-secret, formula to a successful community for your app. Hope it helps :)

-Sugumaran

• Don't automatically post an update when the user installs or views an app.
• Remove all ads from the profile view.
• Be sure to use gadgets.util.escapeString to properly escape user input.

function sendEmail() {
  var params = [];
  params[opensocial.Message.Field.TITLE]="Hola!";
  var body="Como estas?";   
  var message = opensocial.newMessage(body, params);
  var recipient = opensocial.DataRequest.PersonId.OWNER;
  opensocial.requestSendMessage(recipient, message);
};

• 51 Access to the application's ID
• 79 adjustHeight only works for first app on profile page
• 98 requestNavigateTo("canvas") from profile goes to a different app's canvas view
• 100 gmodules proxy doesn't support gzip data
• 103 POST data in signed makeRequest calls is not used in generating the signature base string
• 104 Prototype library interferes with OpenSocial API
• 107 gadgets.json.parse throwing exceptions

• 23 - Signed makRequest IDs do not correspond with Person.getId() values
  
• 64 - Activity updates not showing in "My Updates"
  
• 70 - opensocial_viewerid not passed on signed makeRequest calls
  
• 75 - Links now showing up in the activity stream
  
• 80 - adjustHeight creates a scrollbar on Firefox
  
• 82 - Firebug throws "os_a.rpc has no properties" error
  
• 91 - makeRequest throughput is slow in IE
• 92 - OwnerFriends + OwnerData is unauthorized
• 98 - requestNavigateTo('canvas') links to the wrong application
  

We are making updates to the app data store and will be doing some
maintenance work today. You may notice some inconsistencies when
reading and writing app data during the afternoon today.

• Apps aren't rendering in IE - This is priority numero uno and will likely make it into the sandbox before Friday.
  
• Unable to fetch a Person by ID
  
• URL parameters sent to requestNavigateTo() are parsed incorrectly
• Signed requests are passing the wrong owner ID
• If a user hasn't set their profile photo, the API returns a bad URL.