Just make sure you use @collaborynth.com.au On Tue, Sep 14, 2010 at 4:28 AM, Thomas Wrobel <[email protected]> wrote: > Thanks. > I -think- I got my own server working now....had to put it on a wire, > wireless seemed to result in all incoming connections being blocked :) > > None the less, I'll check out and try wave.collaborynth.com.au as a > back up, as I just know any demonstration is 99% certainly going to go > wrong in some way. > Do I have to do anything particularly to connect to > wave.collaborynth.com.au with a client? username/password anything? > > > > On 13 September 2010 15:04, Joseph Gentle <[email protected]> wrote: >> The client-server protocol has changed a touch in the last couple days >> (the max_wavelets parameter has been removed from the ProtocolOpen >> request). Also, there's another change in the works to slightly change >> the snapshotting behaviour: >> http://codereview.waveprotocol.org/117004/show >> ... In particular: >> http://codereview.waveprotocol.org/117004/diff/1/13 >> >> If you're demoing, you might want to make sure the protocol versions >> all match up correctly. >> >> -J >> >> >> On Mon, Sep 13, 2010 at 10:23 PM, James Purser <[email protected]> >> wrote: >>> You could try logging onto mine, but it doesn't seem to be federating >>> very well at the moment. I'm also having issues with regards to the >>> web interface. >>> >>> wave.collaborynth.com.au >>> >>> James >>> >>> On Mon, Sep 13, 2010 at 9:01 PM, ThomasWrobel <[email protected]> wrote: >>>> I'm going to a little open software day on the 18th to demonstrate my >>>> project which makes use of wfp. (arwave.org) >>>> I have a working wave server, but am having trouble getting it >>>> accessible from a remote location - probably just a port issue, but I >>>> couldn't see anything obvious and I have so much to prepare it would >>>> be really usefull if I could just connect to someone else's server on >>>> the 18th if it all goes wrong. >>>> I just need a FedOne server I can log into and read/write >>>> blips..nothing special. >>>> >>>> -- >>>> 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. >> >> > > -- > 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.
