Shmong

Rating: 
5
Your rating: None Average: 5 (3 votes)

Shmong is a XMPP client for SailfishOS.

XMPP is the open standard for messaging and presence.

What you get in this very first alpha release:

- One to one messaging

- Omemo 0.3 encryption compatible with Android Client Conversations

- Sent, received and read status of messages

- Notifications on new messages

- Send pictures and files

Shmong is a new edition of Shmoose application using QXmpp library. 

Source code: https://github.com/ron282/shmong

Known issues:

- Reconnection not always working

 

 

Application versions: 
AttachmentSizeDate
File harbour-shmong-0.1.1-1.aarch64.rpm217.41 KB20/07/2023 - 23:45
File harbour-shmong-0.1.1-1.armv7hl.rpm202.66 KB20/07/2023 - 23:45
Changelog: 

(none)

Comments

norayr's picture

can you make sure unicode domains work? i cannot use my ծոց.հայ domain with shmong.

Ron282's picture

Hi  guyz n girlz, sorry for being lazzy not checking comments. i will post an update of qxmpp, shmong. i currently working on kaidan for sailfish. i have a version that displays the roster, the uncrypted messages but there is a lot to do on the qml part. not really usable. i will update sources on github for thoses who want to have a look.

 

 

 

 

citronalco's picture

I'm using Shmong for the first time after some months. The last 10 minutes it continously displays notifciations for all the messages I received during that time, still ongoing.

Would be good if it would only notify on new (means: since starting Shmong) messages by default.

Ron282's picture

I'm sorry for that. Check with latest release. I'm using it every day. I know that it needs debugging. This is really alpha. 

poetaster's picture

Ok, qxmpp builds too, which means I can work on getting you into chum. One thing would help. Tag your last working state so that I can pull from obs. Thanks! Or, I can fork and tag on mine. But having you upstream is less foo.

poetaster's picture

I realized that I'd have to do some work to get it to build. https://build.sailfishos.org/package/show/home:poetaster:qt5.15/shmong

Builds fine, but it's with my mods to your repo which might be too much of a pita for you:

https://github.com/ron282/shmong/compare/main...poetaster:shmong:main

Basically, I moved things around to be able to use qt's make install. I'm pushing it to chum testing to see if I've got all the bits right.

 

poetaster's picture

Just a note/question I'm working on packaging all the deps on chum. perhaps we could get shmong building on chum when libomemo-c and qxmpp , etc, are finished? I'm working on kaidan https://forum.sailfishos.org/t/xmpp-in-sailfish-how-to-start/12960/42?u=...

Ron282's picture

@poetaster. yes it's a good idea. I saw your post and congrats to get Kaidan on Sailfish. If you  try it with the QXmpp version I published, I'm interested to know if it works fine with the Android client Conversions.

poetaster's picture

I just got stuck trying to create 'schmong' compatible libs in chum. Using submodules with your repos, QCA compiled fine, but QXmpp is choking. Maybe you can see a reason: https://build.sailfishos.org/package/live_build_log/home:poetaster:qt5.1...

The repo it's building from: https://github.com/poetaster/qxmpp/tree/sfos

Thanks for all your efforts!

 

poetaster's picture

Hej! Are you building qxmpp without omemo? If I use your repo at 1.5 to build, with   -DBUILD_OMEMO=ON \ I do not succeed?

Ron282's picture

The qxmpp that works with sailfish is the qxmpp-sfos branch in my repository. The master branch is a copy of the current qxmpp. I'm always compiling with -DBUILD_OMEMO=ON and with -DBUILD_OMEMO_V03

poetaster's picture

One more question, when you build qxmpp, you're getting libQXmppQt5.so* ? The version I've built for opt-kf5 is libqxmpp.so and co.?

poetaster's picture

Thanks! I'll try that now. libomemo-c (debian repo upstream) and qca (using your repo upstream) now build fine on chum testing. If -DBUILD_OMEMO_V03 works, I'll try building shmong in chum! Kaidan builds, but I couldn't get anything newer than 0.8.0 to compile because, I believe, our g++ ist too old.

poetaster's picture

I'm just packaging the last bits where kaidan is concerned.  As it stands, the qxmpp I've built is 'opt' only, but i'm thinking I'll build a generic version in chum to accompany the omemo library which is generic. Then I'd do a generic qca and off we go. I could use your github repos as submodules since you're the primary consumer :) But let me know if that makes sense.