FAQ

OpenSocial is a JavaScript API (Application Programming Interface) that makes it possible to build a gadget (or 'application') that works on multiple social networking sites.

The OpenSocial standard is a collaboration of Google and other social networking sites (a list of launch partners can be found here: Google OpenSocial Partners).

The gadgets are written using plain old HTML and JavaScript and any other web technology a developer may require, like Flash. More information about the OpenSocial API can be found at Google OpenSocial.

A gadget (or 'application') is a piece of code which a user can install on their own profile. A gadget can enhance a users profile and adds to the functionality on the Hyves platform.

We support two main types of gadgets:

OpenSocial

This is the current standard for gadgets on Hyves. These gadget are relatively 'smart'. You can retrieve user information and see the difference between the Owner and the Viewer of the gadget. There are multiple social interactions possible, which is preferable for a social network like Hyves.

Embed/iFrame

We do support the YouTube-type gadgets. Simple pieces of code which can not interact with the user itself. These gadgets are therefor considered relatively 'dumb'. When a gadget concept is achievable in OpenSocial we do not allow the gadget as an embed/iframe.

To sum it up, some of the advantages (for us and you, the developer) of using OpenSocial on Hyves:

• OpenSocial uses open web standards that are widely used like XML, JavaScript and HTML.
• Applications that already run on other OpenSocial containers can (in practice) easily be ported to run on Hyves, instantly adding extra functionality to Hyves and expanding the user base for gadget developers.
• Through the caching system that OpenSocial offers, developers are able to host gadgets with minimum hardware and network requirements.
• With one click on an install button a user can install a gadget on his profile page and gadget canvas page. No need to copy/paste html codes.
• Easy localization (translation) through the use of language files.
• Gadgets can be A LOT smarter than before, like knowing who is viewing the gadget, who installed it and who the friends are of the viewer or owner of the gadget.
• Also place gadgets on the gadget profile page of the Hyver and get a large viewport to navigate to, the so called Canvas view.

Hyves at the moment supports OpenSocial version 0.7.
Google OpenSocial 0.7

In the future we'll be supporting new versions, while remaining backwards compatible with older versions.

See the Getting started section

We are building Examples, we have Code snippets that can be a great example. You can also go to Google's OpenSocial tutorial 0.7 for examples from Google.

There are 4 ways to add a gadget.

1. By direct linking to the item page (your gadget does not have to be in the gallery for this). Here is an item page example: Buddypoke. You can edit this page when the gadget is added to your live apps www.hyves.nl/api/opensocial This is the only option where you can add parameters to you installation (http://developers-hyves.nl/documentation/opensocial/general-information-limitations).
2. By making an API call gadgets.createByXML and adding the original XML-url to this call (note: this is not a different xml for each user, only one gadget url).
3. By pressing a "add" or "voeg toe" button at the bottom of the gadget on the profile page or on the canvas page.
4. By getting an invite from a friend for the application (aka application invite message).

• OpenSocial gadgets can't be placed in groups or hubs (spots, companies, interests, brands, etc). At the moment an OpenSocial gadget is connected to a single Hyver.
• You can't place more than one instance of an !OpenSocial gadget on a profile.
• OpenSocial gadgets can't be placed in scraps, messages, blogs, etc. other then the title and thumbnail in a special format.

You will have to check what spec your gadget needs and what functionality your gadget needs. Not every network supports all the features.

No, but we do provide heavy caching for the OpenSocial XML and other resources, so ''in theory'' you could host your gadget from your home ADSL line.

Of course the hosting requirements and data traffic also depends on the complexity and usage of your gadget.