Skip to main content

Search

Items tagged with: Conversations_im


Ich überlege gerade einen Vortrag auf den #Datenspuren in Dresden einzureichen.
Der grobe Aufhänger wäre was ich aus 10 Jahre #Conversations_im gelernt habe. Wie sich #XMPP weiter entwickelt hat aber auch wie das finanziell funktioniert Vollzeit an Open Source zu arbeiten.
Gibt es weitere Themenbereiche die euch in diesem Zusammenhang interessieren und die in den Vortrag passen würden?


@Jami I have a little question. Is it possible to use conversations as a distributor app for Unified Push? Or does this only work with ntfy, NextPush and UP-FCM?
#jami #conversations_im
Best regards
Carsten


#Conversations_im has just surpassed 250,000 installs on Google Play. 🥳

The official, publicly visible, install badges are handed out for 100k and 500k. Growth has been very linear over the last ten years so stay tuned for the next big milestone in 2034! 😜


Continuing a tradition #Conversations_im is available for free on the Google Play Store for the next 7 days.

play.google.com/store/apps/det…


@daniel

Thank you for sharing your insights, and for your excellent XMPP app #conversations_IM!

Does anyone know about implementation plans for @dino?

/cc @larma


We (The XSF / People who write and implement XEPs) have a tendency to wait with advancing a XEP to stable until we have sufficient implementation experience.
Your question (which matters more for end users) should be: Why hasn't this been implemented?
Implementing reactions is not as straight as it might seem. Both #Conversations_im and #Gajim wanted to rewrite the database layer to accommodate this feature. On the Conversations side we also wanted to rework the UI before this.


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


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 (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.


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?

¹: 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: 4 months 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.
#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…


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