Having federation up&running (see previous email), I'm currently running tests federating with the other 2 wave servers.... with varying results. Specifically:
* Federating with waveinabox.net: upon first delta, I received a failure to validate cert info; this seems to be either due to lack of SSL, or lack of cert caching. Full stackdump at http://pastebin.com/S71UXg4V . * Hacking WaveSignatureVerifier.java & removing all signature verifying operation resulted in successful(!) federation IF, and only IF the wave resides on waveinabox.net, but not vica versa. Deltas go both way, though, and I can access waves to which I was added to on WIAB from local server. Relevant questions: * What's the security policy on accessing "public" waves (ie those shared with @waveinabox.net) remotely? Is there a way to query for that? * Federating with wave-dev.alown.co.uk was met with zero success; specifically, it fails to discover the relevant wave service: Aug 31, 2014 8:13:02 PM org.waveprotocol.wave.federation.xmpp.RemoteDisco finish INFO: Could not discover remote JID: error_code: UNDEFINED_CONDITION for wave-dev.alown.co.uk Aug 31, 2014 8:13:02 PM org.waveprotocol.box.server.waveserver.WaveletNotificationDispatcher$2 onFailure WARNING: delta update failure: error_code: RESOURCE_CONSTRAINT error_message: "error_code: UNDEFINED_CONDITION\n" Relevant question: What's the policy on servers federating, in general? To give an analogy, what good is an SMTP service, if you can only send emails to host-local users with it? -SDr
