As part of our continous efforts towards giving orkut users more ways to share interesting content with their friends, we are happy to announce the launch of the orkut Share API. The API allows website owners to enable their visitors to share the content on their website, with visitors' friends on orkut.

Users can share the content and optionally promote it to make recommendations to their friends, which then appears in their activity updates. Every such shared item has the potential to spread virally and get wider attention from orkut users, increasing the traffic to the website.

Web publishers can post orkut share buttons like the one above on their page using a simple JavaScript library. We also support the JavaScript and HTTP APIs for a more direct interaction of sharing-related UI actions with the server. These options combine to give web publishers, flexibility in the way sharing features are implemented. The user experience remains consistent and secure in each case.

Some of our early access developers like addthis.com, have already started supporting orkut in their list of services. If your website has implemented sharing functionality using the 'addthis' button, you can simply configure orkut in the destination network list.

Details of orkut share API and sample code can be found here.

So spread the word, have fun sharing!

As part of our continous efforts towards giving orkut users more ways to share interesting content with their friends, we are happy to announce the launch of the orkut Share API. The API allows website owners to enable their visitors to share the content on their website, with visitors' friends on orkut.

Users can share the content and optionally promote it to make recommendations to their friends, which then appears in their activity updates. Every such shared item has the potential to spread virally and get wider attention from orkut users, increasing the traffic to the website.

Web publishers can post orkut share buttons like the one above on their page using a simple JavaScript library. We also support the JavaScript and HTTP APIs for a more direct interaction of sharing-related UI actions with the server. These options combine to give web publishers, flexibility in the way sharing features are implemented. The user experience remains consistent and secure in each case.

Some of our early access developers like addthis.com, have already started supporting orkut in their list of services. If your website has implemented sharing functionality using the 'addthis' button, you can simply configure orkut in the destination network list.

Details of orkut share API and sample code can be found here.

So spread the word, have fun sharing!

We just launched a faster, richer and more intuitive experience on the new orkut. You need an invite to see the new orkut - we will send out invites to developers this week.

OpenSocial applications take center stage as part of this redesign. You can now customize your 'About me' section with OpenSocial apps and even make your favorite app the default view for 'About me'. When your friends visit your profile, your app will showcase your personality (whether your daredevil race car avatar or your smiley face today). Apps on profile view also move above the fold and have a larger area for display.

Few tips to leverage the redesign -

1. Currently we support a small profile view size of 540 x 280. With the redesign you have a wider profile view size of 660 x 225. As we roll out the new orkut, both these views will be supported. To take advantage of this, you can add another profile view using the view name profile660.

</ModulePrefs>
<Content type="html" view="profile660">
<![CDATA[
<h1>Profile view for the new orkut!</h1>
]]>
</Content>

For users with the new orkut, the new profile view will be used, while old users continue to see the old view. Currently the new orkut supports both views, but as the redesign rolls out fully, the new view (profile660) will be standard and the old view (profile) will be phased out.

2. Build a profile view that allows users to showcase their personality. If your app is a game, let the users showcase their high scores in profile view. If your app promotes self expression, then let users pick the expression they want to showcase on profile view.

The new orkut is a work in progress - we will continue to act on user feedback to improve it even more. OpenSocial apps are a key part of our strategy and you will see this reflecting in many parts of the new orkut going forward.

We just launched a faster, richer and more intuitive experience on the new orkut. You need an invite to see the new orkut - we will send out invites to developers this week.

OpenSocial applications take center stage as part of this redesign. You can now customize your 'About me' section with OpenSocial apps and even make your favorite app the default view for 'About me'. When your friends visit your profile, your app will showcase your personality (whether your daredevil race car avatar or your smiley face today). Apps on profile view also move above the fold and have a larger area for display.

Few tips to leverage the redesign -

1. Currently we support a small profile view size of 540 x 280. With the redesign you have a wider profile view size of 660 x 225. As we roll out the new orkut, both these views will be supported. To take advantage of this, you can add another profile view using the view name profile660.

</ModulePrefs>
<Content type="html" view="profile660">
<![CDATA[
<h1>Profile view for the new orkut!</h1>
]]>
</Content>

For users with the new orkut, the new profile view will be used, while old users continue to see the old view. Currently the new orkut supports both views, but as the redesign rolls out fully, the new view (profile660) will be standard and the old view (profile) will be phased out.

2. Build a profile view that allows users to showcase their personality. If your app is a game, let the users showcase their high scores in profile view. If your app promotes self expression, then let users pick the expression they want to showcase on profile view.

The new orkut is a work in progress - we will continue to act on user feedback to improve it even more. OpenSocial apps are a key part of our strategy and you will see this reflecting in many parts of the new orkut going forward.

In order to use the tool, here are some requirements -

1. You must have claimed ownership of the existing app.

To claim ownership of an app, visit http://www.google.com/gadgets/directory/verify

2. You be logged in with the account with which you claimed ownership.

3. The existing app must be a featured app on Orkut.

4. The new application URL must NOT have been used as an app on ANY google container -- including orkut, iGoogle, etc.

Note: This is very important, otherwise the migrate request will fail. It is recommended that you create an absolutely new and unique URL when migrating. Unfortunately, this also means that you cannot test the new app URL on sandbox before issuing a migrate request.

Steps to use the tool -

1. Visit http://sandbox.orkut.com/AppUrlMigrate.aspx

2. Type in your existing app url and the new URL to migrate to.

3. Check the exisiting and new app URLs. (see attached screen shot)

4. Double check - (you really don't want a typo in the new URL).

5. Hit the submit button.

6. A migration confirmation message will appear.

7. The migration changes will propagate through caches and will be live in 24 hours.

In order to use the tool, here are some requirements -

1. You must have claimed ownership of the existing app.

To claim ownership of an app, visit http://www.google.com/gadgets/directory/verify

2. You be logged in with the account with which you claimed ownership.

3. The existing app must be a featured app on Orkut.

4. The new application URL must NOT have been used as an app on ANY google container -- including orkut, iGoogle, etc.

Note: This is very important, otherwise the migrate request will fail. It is recommended that you create an absolutely new and unique URL when migrating. Unfortunately, this also means that you cannot test the new app URL on sandbox before issuing a migrate request.

Steps to use the tool -

1. Visit http://sandbox.orkut.com/AppUrlMigrate.aspx

2. Type in your existing app url and the new URL to migrate to.

3. Check the exisiting and new app URLs. (see attached screen shot)

4. Double check - (you really don't want a typo in the new URL).

5. Hit the submit button.

6. A migration confirmation message will appear.

7. The migration changes will propagate through caches and will be live in 24 hours.

We're happy to announce that applications that use server-side templates and data pipelining now show up in the profile view on orkut. Data pipelining allows you to specify the data that you want to use in your application, while templates let you describe how to render the app. If you haven't already, you can get started creating your profile views with templates and data pipelining using this tutorial.

As you may remember, we had temporarily disabled profile views for OpenSocial applications on orkut to help prevent the phishing attacks occurring in a small subset of applications. The addition of template values, which are HTML-escaped by design, will help reduce applications' vulnerability to issues like XSS moving forward. Enabling data pipelining and templates also reduces the number of round trips between orkut and your server, making your application render faster.

For all of you with applications that currently show up in profile view without templates, you'll have until May 31st to make the switch. After that date, all apps not using templates will be removed from profile view.

We know that it's not easy to make changes to your applications and would like to thank you for the patience and support that you've shown. We're confident that these changes will improve the apps experience for orkut users.

We're happy to announce that applications that use server-side templates and data pipelining now show up in the profile view on orkut. Data pipelining allows you to specify the data that you want to use in your application, while templates let you describe how to render the app. If you haven't already, you can get started creating your profile views with templates and data pipelining using this tutorial.

As you may remember, we had temporarily disabled profile views for OpenSocial applications on orkut to help prevent the phishing attacks occurring in a small subset of applications. The addition of template values, which are HTML-escaped by design, will help reduce applications' vulnerability to issues like XSS moving forward. Enabling data pipelining and templates also reduces the number of round trips between orkut and your server, making your application render faster.

For all of you with applications that currently show up in profile view without templates, you'll have until May 31st to make the switch. After that date, all apps not using templates will be removed from profile view.

We know that it's not easy to make changes to your applications and would like to thank you for the patience and support that you've shown. We're confident that these changes will improve the apps experience for orkut users.