<http://schema.org/articleBody>
"Oosah is a new virtual desktop of sorts, providing you with a web-based way in which to save all of your media.  There are no downloads required, and items can be added from your desktop computer to your account on Oosah's service as easily as attaching a file to an email, or uploading a batch to Flickr.  \nIf you're familiar with Windows desktop or Outlook, then using Oosah will be a walk in the park. Icons are large and easy to discern, and folders can be arranged, re-arranged and named however you want.  Drag'n'drop capabilities allow for easy organization, and media types can be combined to create shareable slide shows as well.  \nOne nice feature on Oosah is its direct upload function that works with your mobile phone and your digital camera.  Most of you are probably accustomed to direct upload services for mobile content, but the digital camera bypassing of the desktop, including a synced, downloadable desktop application, is helpful too. \n\nTags can easily be applied to multiple items at once, and filter options help you find media you've placed on your Oosah account.  Content can be shared directly, via email, RSS, embedding, etc.  There's also options to turn your content into a podcast, or upload your music and share it with other users.  \nIn perusing the Oosah site, I can appreciate the simplicity of the service, but realize the realistic barriers that the company could face in terms of getting users to sign onto yet another media-sharing or virtual desktop service.  I thought about integration options for a Facebook application, importing capabilities from other media-sharing sites, or even syncing features across devices and desktops.  \nFortunately, that's the very direction in which Oosah is headed.  The company already has an API for developers to utilize Oosah's organization and management tools for their own services.  There will be some other upcoming features in the future as well, which we'll be hearing more about at a later date.  For now,  Oosah's simplicity and wealth of native applications makes it a good choice (from a theoretical level) for an API, and its upcoming features will make its API and consumer end approach more useful."^^<http://www.w3.org/2001/XMLSchema#string>
<http://mashable.com/2008/04/03/oosah/>