Google Wave FedOne component with Prosody XMPP server
Wanting to be ready for the day when Google Wave opens the federation spigot, I decided to revisit the FedOne component reference code and get it setup with my test XMPP Server.
After following the normal Prosody install methods and this time making sure my SSL environment is clean, I then switched over to the wiki pages to get the component configured and installed. Except for the small bit about Java SSL code (FedOne is written in Java) not liking good old normal PEM formats, everything went according to the documentation – go figure! ;)
Anthony Baxter clearly documented installing the component into the Prosody environment on the FedOne wiki so I don’t need to go into messy details here – thanks Anthony!
After restarting Prosody, running the FedOne component, it’s time for a test and thankfully the Google gang included with FedOne a basic command line client to test with:
./run-client-console.sh username
Following this wiki guide on how to use the test client, I was able to test my local server and now I’m set for testing later – I think. :)
Total time to do the install with the following, about an hour:
2. November 2009 at 09:52
Hi Bear!
Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn't think so..
Questions, questions..
2. November 2009 at 11:40
It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth. The only thing you don't get is the fancy UI client.
Yep, it is completely federated – it's already making attempts to reach out and contact other servers when you add remote JID's – Google just has it turned off on the public facing servers so it fails.
2. November 2009 at 14:52
Hi Bear!
Does this give you your own Wave server that you can log into and write waves in? Using the same web interface that Google has? And further, if *I* set one up, can you and I federate? Or is there some magical switch that Google needs to throw? I wouldn't think so..
Questions, questions..
2. November 2009 at 16:40
It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth. The only thing you don't get is the fancy UI client.
Yep, it is completely federated – it's already making attempts to reach out and contact other servers when you add remote JID's – Google just has it turned off on the public facing servers so it fails.
16. March 2010 at 04:10
I was able to test successfully the wave exchanges by two clients..(made active by ” ./run-client-console.sh username”)..
I have a question..Is it possible to have a XMPP client registered with the server share waves with the FedOne user (made active by ” ./run-client-console.sh username”).
I am not sure if I framed my question correctly. Please suggest
16. March 2010 at 04:18
That will be possible when FedOne allows for a federation server (that isn't a Google server) to connect.
16. March 2010 at 04:25
Can you please elaborate!
16. March 2010 at 04:29
any xmpp client can connect to a FedOne server as a client but not as a Wave Client – so you can get an xmpp connection but not “see” the wave data.
A federated server would allow you to run a bot or other Wave software item that then connects to the FedOne server.
25. June 2010 at 09:24
Speaking of Google Wave, does anyone know when they'll be done with it and present their product to the whole wide world?
Sandra @ VPS Servers