For those who haven't run into me online or at the DevJams, I'm Max Newbould, the product owner/lead developer for the MySpace OpenSocial container.
We are always hard at work and try to make it into IRC and the forums as much as possible, and want to make sure no useful information is only disseminated on a single medium.
Forthcoming bits (I don't like to give dates but I will post when they are live)
Global AppData Store - you will soon be able to create fetch/update PersonAppDataRequests with an idSpec of MyOpenSpace.Group.GLOBAL_APP_DATA to store key value pairs accessible to all instances of your application.
Client Lib Selection - as you may have already read, we are removing prototype 126.96.36.199 as an implicit include on the container. You can still reference it as detailed here: http://developer.myspace.com/Community/forums/t/1330.aspx. This was done to ween applications off prototype without explicit inclusion, as the new client JS toolkit selection functionality is coming.
PostTo - the ability to post to different MySpace areas from inside an application; messages, comments, profiles, bulletins, etc. This is a huge feature and defined as an extension.
Setting the record straight on AppData
We had been getting bug reports regarding either getting stale versions from cache, or an update not being honored when a fetch was sent in the same request.
Behind the scenes, MySpace has a highly asynchronous nature to meet our scaling requirements. An update will persist to databases after being sent, but we cannot guarantee the timing of when that happens. We're talking 300ms - 3s (3s during peak times/issues), but we need developers to understand this limitation and work with it. It's perfectly fine to send an update and use the local copy of the key value pair until a new fetch is absolutely required.
As always, we love to hear from people using our container and make a huge effort to keep everyone in the loop.