Skip to main content


Items tagged with: Conversations_im

I was about to start a poll asking if #Conversations_im should add a fallback STUN server ( for the ~40% of #XMPP servers that don’t offer one via XEP-0215 External Service Discovery.

And then the network of our hosting provider went out for ~5 minutes acting as a good reminder of why the app doesn’t rely on centralized infrastructure…

A quick note to our translators:

First of all thank you for your work!

#Conversations_im 2.15.0 will change the terminology from 'conversation' to 'chat' and from 'close' to 'archive'.
Chat is shorter and feels like a more commonly used word in that context. It avoids some potentially confusing situations in which it's not immediately clear if the app is referring to itself or to to multiple chats.

In your translations use what ever you feel works best in your language!

I don’t use the tablet UI in #Conversations_im. To be honest I hardly think about the fact that Conversations even has one.
However if you are using Conversations on a tablet and have suggestions for low hanging fruit / quality of life improvements I’m happy to implement them.
Recently someone suggested using the chat title as the activity title. (Apparently the highlighted chat is not enough of an indication of what chat you are currently in.)

#XMPP #android

This sounds like a Problem with Letsencrypt. Letsencrypt has stopped cross signing their certifates with a root that older Android versions have.
Introducing conscrypt won't fix the issue.
You'll have to bundle the Letsencrypt root.

Here is how #Conversations_im did it:

The commit has also a link to a blog post explaining the issue.

Ten years ago today I released version 0.1 of #Conversations_im on the Google Play Store as a paid app.

I believe that I have contributed significantly to normalizing the pay-for-the-binary business model for open source apps.

Ten years ago Conversations was one of the first apps to do this and definitely raised some eyebrows. Nowadays it feels like a pretty common thing.

I actually already do something like this based on the #app SMS to URL forwarder ( The URL corresponds to a very simple endpoint (a CGI written in Bash!) that receives the SMS details and resends it to a #XMPP MUC.

My use case is that I have a mobile phone with an overseas SIM card that I keep at home while I want to know when it receives a SMS.

So having this functionality as part of #Conversations_im would be great.

I voted 'Yes' (and I use SMS), but I would prefer this to be a standalone app. I love #Conversations_im and I don't consider this as a core functionality. So, this would better be a standalone SMS2XMPP app, or some SMS-messaging-app with integrated forward to XY (= XMPP, email, REST, etc...) functionality.

I just read a review of Beeper¹ and I’m now thinking about SMS integration into #Conversations_im in the form of forwarding (mirroring) your SMS to your other #XMPP clients. (For example your desktop client or a tablet that runs Conversations but doesn’t have a SIM card.)

Obviously this would need buy in from at least one desktop client to display forwarded messages (@gajim, @dino).

Do you think this is something you would use?


  • Yes (48%, 59 votes)
  • No (I don’t use SMS) (41%, 51 votes)
  • No (other reasons. see reply) (9%, 12 votes)
122 voters. Poll end: 3 weeks ago

Wenn du Lust hast kannst du es ja auch mal mit #Conversations_im als Distributor (und einem ejabberd 24.02 auf der Serverseite) versuchen. Ich bin ja der Meinung das #XMPP Batterieeffizient und zuverlässig Nachrichten zustellen schon ganz gut kann. Eventuell sogar besser als #ntfy. Aber da wäre ich tatsächlich mal auf einen Vergleich gespannt.

We have an XMPP booth at the Chemnitzer Linux Tage. Join us for discussions about federated instant messaging and for stickers. #xmpp #dino #conversations_im #clt2024

We are at Chemnitzer Linux Tage. Come say hi! We have stickers.
#XMPP #Conversations_im #CLT2024

Google had accepted a version of #Conversations_im with address book integration that explicitly asks the user for consent to process the contact list locally on their device before requesting contacts permission. Our privacy policy included explicit wording w.r.t. local processing of the contact list.

However it’s unthinkable for Google that someone would request contacts permission and then not upload them. A few days later they changed their mind and threatened to remove the app again.

A bunch of XMPP developers and I (@dino, @Monal, #Conversations_im) will have a booth at the Chemnitzer Linux Tage (March 16th & 17th 2024).

Come talk to us about #XMPP and collect some merch.


I hastily threw together a version of #Conversations_im that has no address book integration and doesn’t ask for Contacts permission.
This seems to have made it through Google Play review just now meaning the app is now available on Google Play again.

No indication from Google that they were in the wrong and hallucinated the whole "uploads contact list" thing. Instead I had to walk the path of least resistance and remove the useful and entirely harmless feature of address book integration.

Let’s not forget that #Conversations_im was a paid app in Google Play. I made Google tens of thousands of Dollars in revenue over the years. You would think that this somehow entitled me to speak to a human for half an hour but you'd be wrong.

#Conversations_im, die weit verbreitete #XMPP App, wurde aus dem #GooglePlaystore entfernt. Begründung: Conversations würde die Kontaktlisten der Nutzenden hochladen. Das ist natürlich nicht der Fall.

Und jetzt gehen wir mal alle in uns und denken über #WhatsApp und co. nach.

#Google ist einfach nur ein Scheißverein.

Quelle: @daniel 🔗

Google has just removed #Conversations_im from the Play Store because they think we are uploading the user’s contact list. We don’t.

Appealing the removal didn’t yield any result. Google just repeated the same statement "the app was removed because it uploads the contact list" without even acknowledging any of the arguments I made in the appeal.

I understand that most of my audience here on Mastodon is more ideology aligned with F-Droid but the app sales on Google Play store have contributed significantly to me working (almost) full time on #Conversations_im.

Without the revenue from Google Play I can’t afford this.

Google has just removed #Conversations_im from the Play Store because they think we are uploading the user’s contact list. We don’t.

Does anyone have a working Android 6 or Android 7 device in a drawer somewhere that they want to donate to the #Conversations_im project? (Anything higher or lower doesn’t work unfortunately)

While refactoring A/V calls I got myself into a situation where I can no longer verify that calls are working on these devices without access to a physical devices. (Emulator has knows issues when it comes to A/V calls.)

The oldest device I have access to *shipped* with Android 8 (and runs Lineage OS 17)

I just finished a refactor of the Jingle File Transfer code in #Conversations_im.
The P2P file transfer code was probably one of the oldest code in Conversations.
The new code should be a lot more resilient and brings support for XEP-0343: Signaling WebRTC datachannels in Jingle¹. This means we should be able to exchange files directly with #XMPP web clients.
Due to the better NAT hole punching of WebRTC vs Socks Bytestreams we now have a higher chance of actual P2P.


Work on #Conversations_im 3.0 has officially begun. 🥳
Funding got cleared in November 2022 but I had customer projects that I couldn’t just stop working on from one day to another.

C3 is a complete architecture overhaul. New database; new UI toolkit; improved XML (de)serialization.

Among other things this means we can have proper Unit Tests now. 😍

Those familiar with how Conversations used to construct stanzas will make the new API (as shown in this test) very happy:

We might not have an incentive to do a blog post on every single institution that uses #XMPP but #Conversations_im seems to be doing its job at the German Federal Police.

I’m pretty excited to see support for reactions and replies in @dino.
This will give me something to test with and some extra motivation when I implement both in #Conversations_im this year. #XMPP