Thanks - I spotted that too and filed as http://code.google.com/p/wave-protocol/issues/detail?id=135
On 1 November 2010 21:13, James Purser <[email protected]> wrote: > Shiny. > > OKay quick notes: > > Leaving a wave and then coming back to it changes the names to anon and the > time to 1st January 1970. > > Federated conversations result in external participants display 1st January > 1970 > > While I can open a new blip on externally hosted waves, the response I type > doesn't appear on the external wave host. > > James > > > On Mon, Nov 1, 2010 at 8:47 PM, James Purser <[email protected]>wrote: > >> Excellent am building now >> >> James >> >> >> On Mon, Nov 1, 2010 at 6:32 PM, Alex North <[email protected]> wrote: >> >>> Big news: the new wave panel (named "undercurrent") is hooked up! If you >>> haven't pulled the latest code now is a great time to check out what's new. >>> We're working towards getting WIAB in a reasonable state to play with at the >>> summit (persistence, somewhat stable, etc). >>> >>> *Docs, etc* >>> >>> - Design doc for the new wave panel: >>> >>> http://www.waveprotocol.org/protocol/design-proposals/new-wave-panel-undercurrent >>> - Draft for file-based wave store: >>> >>> http://www.waveprotocol.org/protocol/design-proposals/wave-store-design-for-wave-in-a-box >>> >>> >>> *Code >>> * >>> >>> - Finished hooking up the new "undercurrent" wave panel - it's >>> pretty! >>> - Lots of refactors to our use of deltas and ops in preparation for >>> new c/s protocol >>> - Security is now enforced on all remote connections. The console >>> client has been updated accordingly. >>> - Expanded robot event handling >>> - Echoey the robot >>> >>> >>> Progress report wave: >>> https://wave.google.com/wave/waveref/googlewave.com/w+tYBKatJxA >>> >>> P.S. As we're gathering more contributions from you all it's getting more >>> difficult to track everything that happens. If you do something you think is >>> worthy of mention in a progress report please drop me an email to remind me. >>> >>> Alex >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Wave Protocol" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<wave-protocol%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/wave-protocol?hl=en. >>> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
