@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
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.
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
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.
If a friend bought the #39C3 ticket for you and sent the .pkpass file via #XMPP, those files are now properly identified in #Conversations_im and display with a nice icon instead of a generic unknown file icon.
@foss_warn Seems like this release broke compatibility with #Conversations_im again?
Previously this was due to the relatively long URLs that Conversations uses but I was under the impression that this had been fixed.
„The features matter a lot less than the people who are using the platform. […]
It can sometimes be a bit misleading when you get a lot of ideas and feature requests in a community, and the conversations become, ‘We definitely need feature X to grow because that’s what’s stopping people from using the platform.‘ While that’s true in some cases, the sad reality is that any flaw can be overlooked as long as the people you want to reach are there.“
This feels true for #Conversations_im as well.
Fortunately, getting killed by the CIA by means of predator drone strike is not everybody's threat model. For others - certain French judges for example - a real threat can be getting sanctioned by the US government and completely locked out of US services.
So yes, know your threat model when picking between #Signal and #Conversations_im.
@metaphil @unifiedpush @nextcloud @mozilla Even #Conversations_im can be a distributor 😉
@zeank
When I'm on the invite page, I have to select #conversations_im or Yaxim but when I select Conversations (which is already installed on my phone) I'm redirected to my app store and after opening C, it doesn't propose me to create an account on your server
Day 2 of the Hackathon went great. Marvin ( @larma) helped me implement an opt-in feature in #Conversations_im which routes all P2P sessions (calls and files transfers) via the users home server (similar to the feature found in Signal).
I went on a nice walk to a viewpoint on Mount Royal afterwards.
Now looking forward to Day 1 of #IETF124.
Day 2 of the Hackathon went great. Marvin ( @larma) helped me implement an opt-in feature in #Conversations_im which routes all P2P sessions (calls and files transfers) via the users home server (similar to the feature found in Signal).
I went on a nice walk to a viewpoint on Mount Royal afterwards.
Now looking forward to Day 1 of #IETF124.
The first day of the Hackathon at #IETF124 in Montreal is coming to an end.
We implemented the relatively niche feature of XEP-0444: Message Reactions that allows channels or group chats to restrict the type and number of emoji reactions users can do.¹
This brings us a step closer to advancing and stabilizing the XEP. We didn’t want to do that before, since we aim to have complete implementations before requesting a Last Call.
¹: https://xmpp.org/extensions/xep-0444.html#disco-restricted
@dcatoffm Please do not use c0nnect. This is an outdated fork of #Conversations_im with several severe security issues (simply due the fact the developers haven't kept up with fixes I made to Conversations over the years.)
These days Conversations and aTalk are the only actively maintained Android clients that aren't just bad copies of something else.
In terms of calls not working this does depend on your server (and network situation)
Try conversations.im (the server) for example.
Testing GNU Taler at #Datenspuren was fun. And by fun I mean mostly unspectacular. It just worked. I scanned a QR code. I got some Kolle Mate.
I think some sort of GNU Taler integration into #Conversations_im would be pretty cool.
If you would like to integrate Taler into Conversations there are currently funding opportunities available¹ from @nlnet and both the Taler developer as well as myself are happy to help with scoping.
Testing GNU Taler at #Datenspuren was fun. And by fun I mean mostly unspectacular. It just worked. I scanned a QR code. I got some Kolle Mate.
I think some sort of GNU Taler integration into #Conversations_im would be pretty cool.
If you would like to integrate Taler into Conversations there are currently funding opportunities available¹ from @nlnet and both the Taler developer as well as myself are happy to help with scoping.
Two minor nitpicks on my GNU Taler experience. (And the fact that I’m complaining about those should be taken as an indication on how well the experiment went otherwise.)
• From checkout (by the merchant) to creation of the QR Code it sometimes took a little bit too long (seconds instead of instant). I think it round trips to the server and maybe the network was slow.
• The wallet app on Android looks very plain and boring. If we integrate this into #Conversations_im it needs to look cooler.
