@s_wilson @luca @twisterrm @kaidan
Todays best options on Linux are probably #Dino by @dino and #Gajim by @gajim. Or #Conversations_im by @daniel on Android and #Monal by @Monal on iOS.
#Encryption is done using #OMEMO nowadays, which is better than OTR, because it handles offline usage and supports multiple devices.
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.
@greatsword @phocque @opensourceopenmind @kolev Be careful recommending #monocles. They’ve stopped back porting critical security updates from #Conversations_im some time ago. Just go with the original. Monocles is just the Blabber disaster waiting to happen again.
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 😉
1) Yes, everyday!
2) @prosodyim or @ejabberd are free, selfhostable, rock solid, and will offer you everything you need and more!
3) @profanity for the linux terminal, @monocles , #Conversations_im or #Cheogram for Android. @Monal for iOS
@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.
#XMPP: Kennt jemand das Problem, dass Nachrichten bei manchen Gruppenmitgliedern nicht ankommen? Alle Mitglieder sind auf demselben Server (Debian 13 mit #Prosody) und verwenden #conversations_im (F-Droid-Version). Das Problem tritt seit einigen Wochen auf. Ein Update von Debian 12 auf Debian 13 hat keine Besserung gebracht.
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
@eternaltyro @signalapp @hetzner Last time I looked, #XMPP #MUC had rather evolved group ownership and sort-of moderation features. I'm not sure about the evolution of multi device suppport together with #OMEMO. I think that one was a bit lacking last time. With #conversations_im there is a really polished UX available that likely rivals what #Threema and #Signal offer.
I haven't tracked the state of the XMPP desktop clients, but I guess your mom isn't using any of Signal desktop client and rather just her phone. In general, I've seen all sorts of people get used to all sorts of technical shenanigans, especially if supported by the friendly #familyadmin, if a need is perceived.
But sure, as you say, XMPP ain't Whatsapp (anymore).
Basic point: No real need to sell the alternatives short in times when the primary services aren't available.
#Conversations_im is doing pretty extensive DNS caching. If you set the TTL of your DNS records relatively high (86400 seconds for example) Conversations can avoid some round trips during connect. Another round trip can be avoided if you prioritize the _xmpps-client SRV entry. This can significantly improve the performance in rough networking environments.
In good networks we can establish a full connection in under 500ms.
I finally gave in and got my #XMPP account with #conversations_im. As usual, you'll find my handle on my homepage. I have also removed the link to my X profile as I'd rather direct ppl to Mastodon and federated social media :mastodon:
@LinuxDayTorino
Buongiorno tutti!
Ci sarò dalle 14.00 per una presentazione di
#lineageos
#fdroid
#xmpp / #gajim / #conversations_im / #dino / #monal /#quicksy
Tengo a subito ringraziare @monocles per suo sostegno marketing (venite numerosi, stickers, chiavette USB e QR code per #monocles chat gratis!)
@delta Daniel doesn't need solidarity, he's tight with cops (or so he thinks): https://gultsch.social/@daniel/115314564451493773
But Daniel, you might ask, won't the criminals just use Conversations then? Yes, they already do. And thank you for realizing why chat control is stupid.
We are not going to write open letters on how we are heroically going to withdraw from Europe. We will stay here continuing to operate as usual. We are infrastructure.
