As some of you already noticed, switching to the 0.8 openSocial version allows you to send and receive events for your application.This beta release of the MySpace Activities has some limitations and known issues. But we think it is in a state that we can release it to the developers for early feedback, and you can start implementing a critical feature for your viral spreading inside the MySpace social network.
Limitations of the beta release(**)
-
Templates cannot be published yet. Every template will stay in developers only mode.
-
A template in developer's mode only accepts events from the developers of the application and will only show the events to the developers of the application.
-
We are NOT prompting the user yet before sending the event. But this will be in effect when we go live.
-
We do NOT support the OpenSocial message bundles. While we're using the OpenSocial variables and template constructs, we're not supporting message bundles. Thus, we've developed our own template editor to help you build, test and integrate your app activities. Note that our live release for activities will also not support the message bundles. We hope to jump direct to OSML.
Restrictions
-
Every template must have a title section and within the title the variable '${subject}' must be defined at least once.
-
A template title can contain up to 160 visible characters.
-
The optional template body can contain up to 260 visible characters.
Once a template definition has been ‘published’ it is not allowed to introduce new variables. However it is allowed to change the template text.
-
A template definition is allowed to make use of limited HTML tags:
-
Up to 4 template variables can be defined. A variable is defined by ${ yourVarName }.
-
The maximum visible text length of a variable value is 60 characters. And up to 200 characters including the HTML tags.
-
The following system variables can be used:
-
${subject} : expands to the name, linked to the profile, of the user.
-
${subject.DisplayName} : expands to the display name of the user
-
${subject.Id} : expands to the id of the user
-
${subject.ProfileUrl} : expands to the profile url of the user
-
${canvasUrl} : expands to the url for the applications canvas
-
${XXX.Count} : displays the number of aggregated items, where XXX is the aggregated variable.
The XXX variable must be defined in your template.
-
Values for the templates are restricted to the same HTML limitations as defined for the template definition
-
When raising an activity, you can associate 2 images. The images must be stored on the MySpace network. We accept the following references:
-
"http://api.myspace.com/v1/users/" + userid + "/albums/" + albumid + "/photos/" + photoid
[2008-12-1:CONFIRMED NOT WORKING]
This follows the syntax as defined for the REST resources of photos.
-
Events can only be raised from the CanvasPage (Not Home or Profile). This works currently with the Beta release, but this will be restricted once we go live.
Bugs
-
Once a body has been defined for the aggregated format, the body definition cannot be completely removed. Workaround; create a new template.
-
The template editor could show a duplicate image for testing the media item association. One image refers to the user profile image; the other image is a public image in your developers album. Note this is only for demonstration purpose. The media item and the test values will not be saved in the template editor.
-
When you do not define any variables, the generated javascript misses a '{' It should be params[opensocial.Activity.Field.TEMPLATE_PARAMS] = { }
but it generates
params[opensocial.Activity.Field.TEMPLATE_PARAMS] = }
-
The javascript priority opensocial.CreateActivityPriority.HIGH has no effect yet.
-
The only MediaItem that currently works is the profile picture of a user, regular images are not showing up yet.
UPDATE
**Since the 17th of December the feature is currently live for all users. No more Limitations of the beta release