#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! 😜
@christian@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.
Are you running #Conversations_im on an Realme or OnePlus devices with stock ROM? Are calls still working for you on version 2.14.2 and above?
Not working would likely manifest itself as a dialog that says "Call not sent" or the operating system opening the default calling app instead of the Conversations UI. Incoming calls would likely be rejected as busy immediately. (There may or may not be other symptoms.)
Please let me know either way and tell me your Android version.
I was about to start a poll asking if #Conversations_im should add a fallback STUN server (stun.conversations.im) 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…
It seems that #Fedilab started to fail for some instances. That happens on older devices (Android 5 and 6).
We will reintroduce conscrypt to patch the security provider for older devices. https://github.com/google/conscrypt
@apps 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.
«Il ricorso contro la rimozione non ha prodotto alcun risultato. Google ha semplicemente ripetuto la stessa affermazione "l'app è stata rimossa perché carica l'elenco dei contatti" senza nemmeno riconoscere nessuno degli argomenti da me avanzati nel ricorso»
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 no 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.
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.
The reason I’m thinking about #XMPP<->Telephone Network is that I’m currently reworking how Conversations A/V calls integrate into the operating system and I’m one small step away from being able to tell Android "hey I can route normal phone calls for you"; However if one proprietary provider is virtually the only sensible way to do this I’m not interested. Given users the ability to easily self host is very important to the design philosophy of #Conversations_im.
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.
New NGI pilot awarded!
1/2 MOBIFREE is a new NGI project starting 1st December with the ambition to foster a fair mobile software ecosystem that prioritizes privacy and openness, applying open-source principles and using open data and standards, contributing to #EUdigitalsovereignty of citizens and organizations. The project is led by the E foundation (@gael) and brings together 12 of Europe’s leading organizations in this area
@waag @murena @Qwant for search services
Rapid.space for cloud services
Merlinux for #deltachat @microg for #microg @larma #Conversations_im
The Foundation for Art and Technology for supporting #fdroid
NLnet for supporting third parties
University of Amsterdam for Ethical & Legal issues
Code For Romania
Biosense representing sector use case
For Conversations 2.12.12 I refactored how DNS resolution works including adding support for "Private DNS" (That’s what Android calls DNS over TLS). Obviously DNS is vital to Conversations functioning correctly.
Please help us test this - especially, but not just - if you connect through a VPN and/or are using Private DNS! 🙏
Conversations 2.12.12-beta.2 is now available on F-Droid (if you allow Beta updates) and on the Google Play Store Beta Channel.
If you have a minute can you help me do one final round of testing? #Conversations_im 2.12.12-beta.3 is out on F-Droid and the Google Play beta channel.
To test DNS properly you have to set up a second account (It doesn’t have to have valid credentials; running into 'Unauthorized' is enough to validate DNS).
I forgot to mention this last time but Conversations does cache the last successful address it was able to connect to as a last resort endpoint. (Caching is per account)
Those who were scandalised by @element selling encrypted @matrix communications services to cops, and suggesting XMPP as a replacement, you might be interested to know that...
"Conversations_im seems to be doing its job at the German Federal Police."
Yes, this seems like a different situation entirely, Matrix devs were actively seeking patronage from the police ( all while making weird rants against their own userbase) whereas in this case it appears the Duetzch Pigs selected #Conversations_im / XMPP based on their own assessment that it's a secure app/protocol to use.