@strypey Wire is open source and planning federation?I thought it was proprietary.Maybe I'll give it a try when federation is ready.
@nipos Not only is Wire #FreeCode, but under #copyleft licenses (a mix of GPL and AGPL depending on the component). Federation could be a ways down the track, but it's already an improvement on popular encrypted chat apps like #WhatsApp (non-free and owned by FB), #Skype (non-free and owned by MS), #Telegram (proprietary server), or #Signal, which has no desktop or web clients, and its developers are totally against #FDroid, and against federation on principle:
@strypey Thanks,but I already know that the four other messengers totally suck.Currently I'm only using Matrix and Jabber,both decentralized and open source.But as I already said I may give Wire a try now.I thought it was closed source.I read that multiple times in the past.
... and then the server in 2017.
@erAck my apologies, that's true. But my understanding is that like the #WeChat desktop clients, Signal's don't work unless the user first registers an account using one of the mobile apps, which requires giving #OWS your cell phone number. No thanks. There's an extensive discussion here about Signal's failings as a privacy protection tool:
#Wire is an #Electron app too. I still find it better than using the web app. When I care a lot more about resource usage than #UX (eg when recording a podcast with a remote co-host or guest) I use #Mumble. It would be cool if someone forked the Mumble clients and replaced the #IRC-a-like UI with an IM one.
the #Signal blog post about federation, like Signal apologetics in general, is misleading in a whole bunch of ways that have been discussed exhaustively on the fediverse and elsewhere on the web. See:
@chebra it's one of the downsides of #FreeCode software being developed by a business, with business goals. Getting a #Wire app into #FDroid users is unlikely to bring in many paying users, so it's never going to a priority for the core team. They would merge patches to make it happen, eventually, but only if the community generates them and convinces the Wire team they don't compromise security or #UX for paying users.
@stevenroose ironically, I'm only indirectly responsible for this. My post from when you originally pointed me at that issue keeps getting discovered and boosted every few weeks, like a gift that keeps on giving ;)
@strypey Which one is that?
@stevenroose scroll up ...