Skip to main content


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?

¹: theverge.com/2024/3/20/2410621…

  • 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: 8 months ago

in reply to Daniel Gultsch

I don't write SMSes long enough that having a proper keyboard would make a difference
in reply to Daniel Gultsch

No. I prefer my SMS stay where they are – inside their own ugly domain, untouched by programs unrelated to it.
in reply to Daniel Gultsch

💯 I would definitely use it and I can try to implement it in @gajim but my MR would have to be approved by lovetox.
in reply to Daniel Gultsch

sms weniger. beantrag doch lieber den Interoperabilitätszugang bei meta. die hoffen ja imo das den keiner will/kennt.
in reply to Daniel Gultsch

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.
in reply to Daniel Gultsch

I loved Notify2Jabber from fdroid that did this and more. Sadly it stopped working on Pixel 8. So YES, as it solves half of my problems 🤗
@gajim @dino
Unknown parent

If not, have another separate version of the client:
There is
"Conversations",
and
"Quicksy",
why not
"Conversations Exchange"
as a suite to collect ALL communications. 😉
in reply to Daniel Gultsch

I actually already do something like this based on the #app SMS to URL forwarder (f-droid.org/packages/tech.bogo…). 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.

This entry was edited (8 months ago)
in reply to Daniel Gultsch

before I used jmp.chat full time I would have loved this as a standalone feature, and even now I get the occasional SMS from my sim card provider even though I can't get SMS from others at that number, so having it in Conversations along with my actual SMS's would be great! If I receive a mix of bridged SMS's with Cheogram and direct sim-card SMS's and I'm replying from the desktop I wonder if it would be confusing which number is going to be used to reply?
in reply to Daniel Gultsch

I voted no because I don't use desktop XMPP clients anymore. Apart from that, I also use SMS only rarely.
Unknown parent

Peter Vágner
@Debacle @J👀 @Nicoco @xıʃǝɟ @Daniel Gultsch I have used android-sms bridge from beeper however now it appears this is built into their app and this sms-bridge that can use my phone sms is no longer in development. Thus this would be a super #conversations feature I must say.
gitlab.com/beeper/android-sms/
in reply to Daniel Gultsch

Voted yes, but wouldn't that kind of access open another can of worms from google reviewers?
in reply to Daniel Gultsch

3) No. I don't use SMS much, but when I do I want to keep it as far away from my daily computing as possible. No love for cell providers...

@gajim @dino

in reply to Daniel Gultsch

absolutly not. No use of sms at all. How an encrypted platform think of plan text. For God sake, donot commit this sin.
This entry was edited (8 months ago)