Just had a voice call on #Wire, using their GNU-Linux desktop app (still in beta), on an ancient netbook (Acer Aspire One) over a VPN. Really impressed with the performance! We could hear each other clearly, and it didn't jitter if we started talking at the same time. We were able to send images and links to each other while talking with no loss of voice quality. Top Marks Wire!
@thibaultamartin@rysiek@sir@Purism have you tried #Wire? Much simple to understand than #Matrix, and with a smoother UI. Plus not tied to BDFL who is antithetical to software freedom (eg Wire actually want their app in F-Droid). I'm @strypey on Wire too if you want to test it.
@js I mean, they could use #Wire, but unless they are going to set up their own Wire server for the purpose, what practical difference would it make? I guess they would be contributing to the network effect of a 100% #FreeCode encrypted messaging app, instead of a 50% free one (client but not server). Hmm, guess I just answered my own question. But Wire only released their server code recently, some people may not realize that now makes it more libre than Telegram?
@lightweight I've had a few plays with Jit.si, turns out my poor old PC can't handle anything that relies on #WebRTC (can't play #PeerTube videos either so I presume it's that). Would love to try chatting on #Wire though. I've tried text chat on the web app, but I'm planning to install the beta desktop app, and hoping my PC can cope with at least a voice chat ;)
@officialcjunior from everything I've read, #Wire seems like a better option than #Signal. Marlinspike's attitude to #SoftwareFreedom is at best ignorant, and worst suspicious, and forcing everyone to squeeze their "secure" chat through his central server screams #HoneyPot.
@ignitionigel interesting hey? I notice #Wire is in the green in that first line, while #Telegram is not. #Riot is not only because it's encryption is not turned on by default, which is because the #E2EE features are still in beta. From what I've read, that will change when they are our of beta (and hopefully had an external code audit)
@ignitionigel that was meant to be *shameless* self-promotion, oops! Anyway, I've been looking into this for a while, as I'd love to have Skype / Hangouts replacement for talking to my family back home, and #WebRTC stuff (eg Jitsi Meet) is too CPU heavy for my poor old netbook. At present I'm leaning towards #Wire so I can install desktop client but family can use web app.
#wire is using #mixpanel (tracking company from the US) to analyse users behaviour. This is activated by default as @kuketzblog reported.
Wire about themself: ''Wire client applications can collect usage data with the aim of improving future versions of Wire. Usage data helps Wire engineers to assess how Wire is used and to identify areas of improvement. Usage data doesn’t contain personally identifiable information.''
@silkevicious I use !XMPP, #Wire, and #Matrix ( via the #Riot client ). I formerly tried #Ring (but after an update, I needed to reconnect to all my contacts) and #Tox ( a new ID on each device, so contacts never know how to reach you quickly ).
@bob #Wire has promised to implement federation (which is why I was willing to try it). For most of my uses (1:1 or small group chats), it blows #Matrix (via Riot Web, Riot Android, Riot iOS) out of the water.
IMO, at its current stage of development, Matrix/Riot is not suitable for nontechnical users, but I actually have family members communicating with me on Wire.