Lennard wrote an echoey robot but the extra events and operations code that it needs in the Wave in a Box robot proxy is still unfinished. That is, he almost has a robot replacement for the echoey agent but not quite yet. (As you know, the existing echoey agent quickly disconnects because of http://code.google.com/p/wave-protocol/issues/detail?id=110. Does anyone have an idea how to fix that?)
On Wed, Oct 20, 2010 at 1:45 PM, Joseph Gentle <[email protected]> wrote: > Did Lennard re-enable echoey? > > -J > > On Wed, Oct 20, 2010 at 1:08 PM, Soren Lassen <[email protected]> wrote: >> FYI, I'm running acmewave.com and it's federating with wavesandbox.com >> fine, so I'm confident that wavesandbox.com federates. >> >> The acmewave.com cert was renewed last week and the wavesandbox.com >> cert was renewed last month. >> >> acmewave's run-config.sh has: >> WAVESERVER_DISABLE_VERIFICATION=false >> WAVESERVER_DISABLE_SIGNER_VERIFICATION=false >> >> I'm running prosody with tls disabled. >> >> -- >> 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. >> >> > > -- > 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. > > -- 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.
