Valkertown Blog

Speeqe is a tremendous idea to bring multi user chat(MUC) into the simplest possible web service you can think, if you want to invite your friends they all just have to follow an url you send and start chatting, things can be more complicated but it’s not required to start participating. Well now I have installed speeqe on my own server quite successfully, it wasn’t an easy task, yet it wasn’t that difficult.

If you want to try it check it here: Valkertown’s rooms you will need a Valkertown’s jabber account to test it, but I will solve this problem asap.

Here’s a list of some of the stuff I had to work around:

• There’s still a lot of hardcoded strings in the js,css,templates with the speeqe url
• The templates, js,css doesn’t prepend the djangos settings for MEDIA_ROOT, I wish I solved this nicely but all I did is set them
  manually.
• Everything on my test server is server using an https connection that includes the http-bind. I figured how to solve this and it was not a big deal.
• I had to do some minor modifications to the django/python client so it connects using https and to the ejabberd’s bosh module.

Here’s some of the stuff I disabled.

• The demo stuff
• The register stuff(I simply didn’t understand it) I tought it created a new xmpp account but it looks like it doesn’t, just an speeqe account, correct me if I’m wrong.
• Virtual host, I’m not planning to do subdomain rooms.
• Message search, I don’t like much this feature, I would like more a room search.
• The static urls serve in the urls, I would activate it using some kind of flag, it’s just not good to see it there, I think it may lead to problems.

Here’s some of the stuff I modified:

• I replaced virtual host to normal chat rooms urls, I would like and plan to setup shorter urls for local rooms without using dns
• Templates to match my own domain where it made sense.

At last:

• I’m missing the autologin feature, I’m guessing on how to deal with this but I want to keep the modifications I do to the code at a minimum.