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.

SMS to URL Forwarder | F-Droid - Free and Open Source Android App Repository

simple incoming SMS to URL forwarder

^f-droid.org

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…

Beeper couldn’t bring iMessage to Android — but it can still make a great chat app

After taking on Apple, Beeper has returned to its original goal of building a chat app for Android that encompasses messages from social platforms and your RCS / SMS service.

^{Emma Roth (The Verge)}

• Yes (48%, 59 votes)
• No (I don’t use SMS) (41%, 51 votes)
• No (other reasons. see reply) (9%, 12 votes)

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.
#XMPP

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.

chemnitzer.linux-tage.de/2024/…

@clt_news

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.

¹: xmpp.org/extensions/xep-0343.h…

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: codeberg.org/iNPUTmice/Convers…

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.

bundespolizei.de/Web/DE/Servic…