The Google Wave team would like to announce a wave data export option intended to support importing wave data from wave.google.com to your own wave server.
We have added an option to the ROBOT_FETCH_WAVE method in the Wave Data API to get the raw deltas from a wavelet. These raw deltas provide the wave's complete history. We expect there will be a little work to turn them into a form suitable for any particular WIAB instance. The raw deltas export and some important caveats about how it works are explained here: http://www.waveprotocol.org/wave-apis/google-wave-data-api/raw-deltas-export The wave Data API (http://www.waveprotocol.org/wave-apis/google-wave-data-api) gives you programmatic access to your data in the Google Wave service. You authenticate using OAuth and can use the Java or Python robot client libraries to access the methods, or access the HTTP protocol directly (http://www.waveprotocol.org/wave-apis/google-wave-data-api/http-protocol). Please try out the raw deltas export. We are looking for help with important work that remains to be done in Wave in a Box. It will be good to implement the raw deltas export option in WIAB's Data API, for testing and for export from one WIAB instance to another. More importantly, import logic is needed to put deltas exported by the Data API into the WIAB wave store. The deltas are exported "as-is", including @googlewave.com addresses and ids. Work required to import includes: - Rewrite wave ids (including in links, etc) and participant addresses to your own domain - Migrate legacy cruft away from Google Wave's internal representation (the Google Wave team will do this bit) - Sign the deltas - (Optional?) Build WIAB UI to serve a web page to users for them to OAuth authorize WIAB to download their waves Soren
