Your rating: None Average: 4.6 (11 votes)

Shmoose - Xmpp Client for Sailfish OS


ATTENTION!!! Database format will change until v1.0.0. All your existing conversations from a previous installation will not show up anymore after this update!!!


What you get is:

- One to one messaging

- Initial group messaging (Automatic room join on inventation or join open room by address)

- Sent, received and read status of messages

- Notifications on new messages

- Send pictures


Keep in mind that this is an alpha release. Many things work. Some things may have bugs. Lot of features are missing. For current status see the project page on github:

Are you good at qml, C++ or encryption? Any help is appreciated.

Application versions: 
File harbour-shmoose-0.1.0-1.armv7hl.rpm16.23 MB25/01/2017 - 22:49
File harbour-shmoose-0.1.1-1.armv7hl.rpm16.24 MB28/01/2017 - 22:22
File harbour-shmoose-0.2.0-1.armv7hl.rpm16.23 MB15/02/2017 - 21:54
File harbour-shmoose-0.3.0-1.armv7hl.rpm16.35 MB03/08/2017 - 21:31
File harbour-shmoose-0.4.0-1.armv7hl.rpm16.35 MB12/12/2017 - 21:38
File harbour-shmoose-0.5.0-1.armv7hl.rpm2.41 MB20/02/2019 - 22:27
File harbour-shmoose-0.6.0-1.armv7hl.rpm2.43 MB03/10/2019 - 22:05


  • Additionally to 1on1 messaging, the status of messages in MUC rooms will also be shown
  • Improved the simple MAM for MUC's
  • Fixed bug in http upload where put and get urls where swaped
  • i18n updates


  • Stripped binary for smaller footprint
  • Fixed room rejoin on connection handover
  • New settings dialog (by slohse)
  • i18n updates


  • message read status through xep 0333
  • http upload fixed (by slohse)
  • i18n (by Caballero)
  • sort pictures by creation date in picker
  • some gui improvements

First draft of group chats

  • Display contact avatars
  • Some gui improvements



Updated Contacts Page

  • Show names of JID's
  • Show subscription and availability status
  • Implemented contact add and remove functionality


Fixed a bug which prevents the app to close properly


schorsch's picture

Hello. I sent you an xmpp authorisation request via shmoose yesterday, but did not get an response until now. Can you check your xmpp client?

will99's picture

Maybe this is something for filing in github but I report it here first:

Http file upload might be not compatible with all servers. I use prosody with an external webserver (mod_http_upload_external). For uploading an image to the sever the put-URL has to have an extra argument (v2):


This extra argument is to prevent others from uploading unwanted content to the webserver and is presented by the server in the put-tag but is skipped by shmoose, resulting in the server not accepting the upload.

Could that be fixed? Many thanks.

A loyal shmoose user.


schorsch's picture


That's interessting. I just had a quick look at the code and it should use the complete url for the put address - independed what it looks like. Is it possible to get an test account on your server? That would make resolving of the problem a lot easier.

will99's picture

Hallo Schorsch,

of course, a test account is possible. Can you send me a message via shmoose to:

I will prepare the account and send the credetials back than.

Regards Wilhelm


4carlos's picture

Oh, i'm sorry. Didn't see that and it sounds great. Will give a try.

barbaar's picture

Hi there,

xmpp with omemo is one of the few things that keep me from switching to sailfish -still using lineage with conversations- 

Installed shmoose 4.1 omemo from github. As far as I can see sending encrypted messages to conversations seems to work, receiving messages doesn't.

I'm not good at programming more of type poweruser, is there anything I could do to support?

Thank You so far 

schorsch's picture

Hi. I also tested mainly against Conversations. It worked for me in bot ways. Please have a look at the github page. There is a description where the logs are located. Take them, remove your private stuff and open a github issue with that log files. Hopefully I am able to track down the cause.

schorsch's picture

You have to also watch the branches ;-). There is an omemo beta release.

4carlos's picture

Any progress here last times? GitHub does not show any changes since Feb 2019.

norayr's picture

thank you for the application. i don't use android compatibility layer so it solves the muc problem.

the most important features to me today are:

XEP-0313 message archive

XEP-0280 message carbons

XEP-0363 http file upload

4carlos's picture

Thanks for replay

4carlos's picture

Will the project be further developed? The last version is from December 2017 and there are some gaps in functionality.

Desirable would be background notification when Shmoose is closed and Omemo encryption.

schorsch's picture

Yes, the development ist really slowed down. There are fixes and improvements on github. I will release a new version the next weeks. After that I will start to integrate the alpha omemo implementation as an option. But this is far from being usable on a regular basis.

Currently there are only two developers on this project who are bringing in new code. So, any contributions are welcome!


dirksche's picture

Suddenly sending pictures work.

schorsch's picture

Please start the app from terminal. Try the sending and post the error as a ticket on github.

dirksche's picture

Sending pictures does not work on my Xperia X. After selecting a picture and accepting nothing happens. Just get back to the conversation

dirksche's picture


schorsch's picture

I have a draft omemo implementation in one of the branches. It uses lurch, the libpurple plugin for pidgin. The main problem is workload at my real job. Sorry, donations won't help here. I try to get a working beta omemo implementation in the app before spring 2019...

dirksche's picture

I also would be glad about OMEMO integration. Would a donation be helpfull?

ladoga's picture

OMEMO encryption would be nice.

objectifnul's picture

Indeed, thx. (Note for other users: 'strip' is part of binutils: do 'pkcon install binutils')

schorsch's picture

Actually, I noticed that I missed a 'strip' in the build file after compilation. I will fix this in the next release. Meanwhile you can try a 'devel-su strip /usr/bin/harbour-shmoose'. That should result in about 14M...

schorsch's picture

Shmoose uses the swiften library, which is not available on the device. So I had to do a statically linked binary which includes all the stuff. Hence the big file size. It's stripped, but besides that I have no idea how to additionally reduce the file size.

objectifnul's picture

Nice again, with a "but": /usr/bin/harbour-shnoose is quite big (85.6 Mb). As you probably know, available space in root partition is critical with current partition scheme of Xperia X. No way to reduce the size of your binary?

kfiatan's picture

Hi, is it possible to set Shmoose to receive notifocations about incoming messages when the app is closed? I mean for example if the default SMS app in sailfish is closed this means that it works in the background and when new SMS is received the sound and pop-up notification appears. When I use Shmoose and close it by slide a finger from top to bottom of the screen it gets completely closed and when I get a message from any contact I do not receive a notification until I log-in again. I could keep the app open (just minimize it sliding a finger from the right to the left) but it drains a battery almost twice quicker than when app is closed. Thanks in advance.

schorsch's picture

Hi. Daemon mode for the app is planed for one of the next releases. But I am not sure if this has an impact on the battery life time. As far as I know, Daemon mode just hides the cover and starts the app automatically on boot up. On my device (Jolla 1) I didn't notice battery drain. I have it running all the time and got a uptime of two days on regular use. Which device are you using?

kfiatan's picture

I use Nexus 4. I just noticed that when the app is running the battery is discharged within less than one day. When I don't use apps like Shmoose, Whisperfish etc. it takes about 2 day before the battery is empty. But if it gives nothing (running in background) regarding a battery life it is not worth to implement it isn't it? I was sure that if the app works "in a background" uses less energy than when is up all the time... that why I asked here if it's possible. Anyway thank You for this reply schorsch. Good luck and take care!

broncheoli's picture

Dear Schorsch,great app on the way to a native XMPP-client but  I have a question: I have an account. Am I right that Shmoose is not able to read the archive from If not, would it be possible to integrate that kind of functionality because that way it would be possible to use both apps (C. and Shm) parallel before switching to Shmoose completely.

Keep a stiff programmers upper lip, greetings, broncheoli.

schorsch's picture


Do you mean Xep-0136 Message Archiving? You are right, shmoose does not have this feature. Personally I don't like to have my messages on a foreign server. I just checked the swiften xmpp library for that feature. But unfortunatelly the library doesn't have support for that. So it isn't 'just to turn it on'. I had to implement it by myself from scratch. So this is currently out of scope for the 1.0 release. Sorry.

will99's picture

Good work. Since all my contacts use "conversations", I am looking forward to having a decent xmpp-client for sailfish. Keep on going...