Notices by Daniel Gultsch (daniel@gultsch.social)

At this point, the Google Play app review process has become a security liability. I have had an app update for #Conversations_im in the review queue since April 28th. Previously, app updates have been rejected for stupid, hallucinated reasons; this time, we are just being ignored entirely. The release is not shipping any security fixes, but imagine if it did.

#XMPP

@aerion There is no such thing as port. Basically the entire codebase is very Android specific so it would be a full rewrite. On the other hand Dino already exists and has mobile Linux support. So if anything I would probably collaborate more closely with the Dino developers.

I’m delighted to announce that the OpenPGP implementation in #Conversations_im will see some love over the next ~6 months. Simultaneously, we will be laying the groundwork for OMEMO2 by implementing Stanza Content Encryption.

Thanks to funding from @nlnet and the European Commission.

https://nlnet.nl/project/Conversations-OpenPGP-refresh/

#XMPP #Jabber #OMEMO #OpenPGP

I recently added a display to #Conversations_im showing the number of stanzas (XMPP packets) sent/received in the current session. What are your counts and how long has your session been active? (Account Details -> 'Server info' in the overflow menu.)

#XMPP #Jabber

Historically, events like Meta announcing ads in WhatsApp haven’t significantly impacted #Conversations_im download numbers. This time feels different. February saw double the installs of a typical month. It seems the sentiment against Big Tech is finally translating into action.

#DiDay #XMPP

RE: https://furry.engineer/@soatok/116088639302283341

I’m not qualified to comment on the alleged security vulnerability in #Matrix, but 'the entire Matrix community sucks because one user once disagreed with me on the Internet' is such a wild take.

I consider myself a 0.5x developer because I think twice as long about the potential consequences of my actions.

RE: https://social.coop/@django/116019244368171843

Dear #Fediverse developers, please do more cool things with #ActivityPub C2S.

Just note that "Direct Messaging apps" are way more complex than you might realize and that #XMPP has solved most of the problems you might encounter.

There are IM apps mostly pushed by a few loud enthusiasts on Mastodon, and then there is #XMPP, which is used in the real world.

For example:

• Evacuating people from battlefields in Afghanistan: That’s XMPP.
• Shipping metric fuck tons of cocaine across the globe: That’s XMPP.

#ThatsXMPP #Jabber

The only relevant feature for any instant messaging app (or social app, for that matter) is: Are my friends using it? People will gladly overlook minor inconsistencies or missing features as long as they can communicate with their friends. We shouldn’t recommend #Signal as a stepping stone before Jabber/XMPP becomes "good enough," if goodness is defined by the number of people using it.

#Jabber #XMPP #Conversations_im

Happy Jabber Day 🎂 🥳

On January 4, 1999, Jabber was first announced to the public¹.

Twenty-seven years later, Jabber—or XMPP, as it became known after standardization through the #IETF—remains the only truly vendor-independent, federated instant messaging platform.

In almost three decades, XMPP has never stopped evolving and remains our best tool for digital independence.

¹: http://tech.slashdot.org/article.pl?sid=99/01/04/1621211

#DigitalIndependenceDay #Jabber #XMPP #DiDit #DigitalSovereignty #DiDay #JabberDay

@morph @S1m NextPush is just an alternative. Both are distributors. Both use different protocols to talk to their respective push server implementations. If you have Conversations you don't need NextPush. If you don't use Conversations you can use NextPush.

@S1m I always wanted to add push support to #Conversations_im. I think a federated instant messenger is a natural fit because you get the decentralization and the connection for free. And adding it to the messenger is also what Google did with gtalk.

So I was very happy that I found #UnifiedPush as a quasi standard when I finally got around to implement it.
Thank you for your for work!

I’m happy to announce the 12th annual Holiday season Conversations giveaway. 🎄☃️

The federated instant messaging client is now available for free on Google Play until New Year’s Eve. 🧨🎆

Merry Christmas, Happy Holidays. Enjoy #39C3.

https://play.google.com/store/apps/details?id=eu.siacs.conversations

#XMPP #Jabber #Conversations_im #DigitalSovereignty #Fediverse

@tris two things: I already said in my follow up post that if someone wants to build their own clients on top of XMPP and prefers MLS over OMEMO, the XMPP community is very open to that. A protocol is much more than just the encryption. They would still benefit from all the other things XMPP has solved.

A lot of what's in that blog post is ill-informed and bordering on disinformation and fear mongering.

@tris there are three actively developed protocols for federated instant messaging (XMPP, Matrix, Deltachat). At least one of them is very open to new developers and new ideas and has a structure in place to collaboratively work on those ideas and bring various stake holders together. With no disrespect to that individual I don't see why there needs to be a forth protocol loosely based on ActivityPub.

@pixelschubsi @tris Yes, agreed. Tremendous value in reusing identities and login credentials. Big skepticism with regards to using AP as a protocol. One can probably kinda make it work… But why? What’s the benefit?

@silverpill @pixelschubsi @tris you can have a single account (or as I phrased it 'identity and login credentials') across different protocols.
For example your Google account works across multiple protocols. And even in the federated world we have several cases where email address == xmpp address.
So to repeat myself: using the same identity is good. Doesn't mean you are locked into ActivityPub if you want to build instant messaging.

As a community, we often ask ourselves how to attract more users to #XMPP. Yet the real tragedy is that people would rather build something entirely new (loosely based on email or #ActivityPub) than consider XMPP. Need end-to-end encryption by default? If compatibility with existing XMPP clients is a secondary concern, you can implement it in your own solution while still benefiting from our two decades of experience in instant messaging.

I consider this a failure on our part but I don’t really know what to do about it. Most arguments against #XMPP don’t hold if you’re building from scratch anyway:

• #Conversations_im looks very outdated: OK, but you are developing your own clients anyway.

• XMPP doesn’t have an SDK: Neither does your #ActivityPub or email stack

• OMEMO is insecure and I would prefer #MLS: Yes, let’s work on that together and you’ll still benefit from XMPP’s 100+ solved IM problems.