New Features At Speeqe

29Jul08

We just released some new features for Speeqe, a simple group chat application for the Web.  This release includes private room messages, external MUC support, early access for interested people to host their own rooms, external Jabber authentication, and image inlining.

Please check it out.  We’re looking for people interested in starting their own Speeqe rooms.  If you’d like your own space, just email us, and we’ll make it happen.

Jabber Bugs

We use negative presence priority to keep the Speeqe client from stealing your normal private messages.  Unfortunately, if you set a negative priority on your resource, both Jabberd 2.x and the Google Talk server stop sending you presence of any kind.  This means that you never get the presence status of people in a chat room, not even intiially.  This is a pretty big bug for us, and if anyone has any suggestions on workarounds while we try and work with Google and smoku to get it resolved we’d love to hear them.

External MUCs

As we demoed in Portland at the 5th XMPP Summit, you can now use Speeqe with external MUC rooms.  Just substitute the address of the room in this URL: http://www.speeqe.com/room/ADDRESS/ .

After you enter a room for the first time, you can log in using any federated Jabber account (including Gmail).  Once you do this once, any room you join will reuse the same information.

UI Love

The UI is a work in progress.  We know some things are currently a bit ugly, and we’re working hard to address them.  In particular this release was more about technical features than UI design.  The next release should have more UI design elements.

Everything in the room is themeable.  In a release or two, we will open up the theme creation tools to everyone.  Themes are just HTML pages, and Speeqe uses CSS selectors to decide where to fill in content.  It can already do quite a lot – see the demo themes for an example.

Advertisements


3 Responses to “New Features At Speeqe”

  1. 1 dpc

    AFAIK not sending messages to resources with priority < 0 is not a bug. If you don’t want to “steal” messages just send a 0 priority – the lowest priority that still gets messages.

  2. 2 metajack

    @dpc: I didn’t say that was a bug, but we send directed presence (not with priority = -1) to a muc room, and we are not getting the presence of the participants back. It is being blocked. even though we sent directed available presence and should be received presence directed to our resource. What is the point of priority -1 if you can receive nothing?

  3. 3 mm

    If you send a directed presence from client to the groupchat with nonzero priority, that should work right ?
    You should be getting messages from that jid … while presence/message all others in roster would be not sent …



%d bloggers like this: