Notices tagged with wire, page 3

The #Wire team are open to the idea of using #XMPP for federation between instances of the Wire server:
"Please feel free to use this issue to post links / papers / reading material of any kind that might help us make a more informed decision"
https://github.com/wireapp/wire-server/issues/631

@kfwyre I've been using #Wire on and off for a while. I had to stop using the Wire desktop client when #Electron (which it depends on) stopped supporting 32-bit. When I log on using the web app, on the same device, logged in as the same user, I get all my chat history just fine.

@wire perhaps I'm getting confused between #Signal, #Telegram, and #Wire. From what I remember, Moxie liberated the Signal client source before setting up #OWS, but resisted releasing the server source for some time, claiming there was no point. Just as he still claims there's no point replacing Google Play Services in mainstream Signal, or distributing the Android client in #FDroid, or supporting #federation between servers. Some people discussing this in 2016:
https://whispersystems.riseup.narkive.com/LvP523Tg/signal-server-source-code
@alexl

#Wire also confirmed that while the company is focused on supporting their existing web client and the desktop clients using the #Electron wrapper, they welcome the #SoftwareFreedom community to help develop alternative clients to be used with their service, like #Coax (currently in alpha):
https://github.com/wireapp/wire/issues/266#issuecomment-473873942

... and in #GoodNews, #Wire not only confirms they're working on secure, federated chat, but #federation will be part of the #MLS protocol being standardized at the #IETF :
"During this interim the proposal was made to include federation more strongly in the design considerations and the proposal was adopted as a future goal for MLS. Wire's goal has always been to achieve federation between different compatible backends and this brings us one step closer to that goal!"
https://wire.com/en/blog/mls-meeting-summary/

I've reported #Wire's lack of server>server federation as an issue, and explained how it could benefit them as a company. I mentioned that there might be hackers out there willing to help them make it happen. Let's see what they say:
https://github.com/wireapp/wire/issues/266

@alexl BTW all chats and calls on #Wire are #E2E by default, and they do not use roll-your-own crypto

@tao

Because of #Electron abandoning support for 32-bit PCs, this bug in #Wire is unlikely to be fixed, and I may have to give up on trying to use the Wire desktop client on my 32-bit laptop:
https://github.com/wireapp/wire-desktop/issues/2038

It just occurred to me that #GitHub ran out of money and had to sell themselves to MS. While companies like #Loomio, whose code is 100% free under #AGPL, and #Wire (A/GPL), are still in business. Doesn't that prove that the infamous "#OpenSource almost everything" creed of the GH founders is a failure, and you might as well free all your code? (looking at you #GitLab)
http://tom.preston-werner.com/2011/11/22/open-source-everything.html

@wiktor fair point. I guess the argument I'm making is that if we want to make it possible for Jo User to encrypt their email (for example), or use encrypted chat without trusting a third party like #OWS/ #Signal or #Wire, we need to create authentication / key management systems for that which are as easy to use as house keys or cars keys (or as close to that as possible).
@bob @nolan

@gentoorebel I managed to get my family (all hooked on FB Messenger) to talk to me on #Wire. Mainly by absolutely refusing to chat with them via accounts on FB or other #DataFarms. Wire has all the benefits of Signal (#FreeCode, #E2EE, user-friendly etc), but is developed but a team employed by a private company (Swiss), not controlled by one cypherpunk celebrity. Plus, server>server federation is in Wire's roadmap (Moxie has said Signal will *never* do this)
@noorul

@greenjon if you want a similar service to Signal that isn't US-based, is planning to implement server>server federation, and is more friendly to the software freedom movement, I suggest trying #Wire. #GNU #Jami (formerly #Ring) is also worth a try, but much less user-friendly (at least last time I tried it).

@grainloom nope:
> Basic security precautions for non-profits and journalists in the United States, mid-2017.

For activists and journalists, the #5Eyes are a much more dangerous adversary to protect against than random crackers (ask #EdwardSnowden). Besides, there are other apps providing the same kind of #E2EE service as Signal that are not US-based (eg #Wire). Why recommend Signal specifically? It bothers me that this list provides no rationale or evidence to back up its recommendations.

@xj9 #Wire is ready for use by non-geeks *now*, on all major platforms (desktop, mobile, and web). Name a single federated chat system that has clients with the #UX polish of Wire across the same range of platforms, clients that can reliably support voice/video chat and file transfer. Clients you could realistically recommend to your Grandpa who lives in a cabin in the woods as a #Skype replacement. The hard truth is neither #XMPP nor #Matrix clients are ready for primetime.

@switchingsocial I know you've addressed this in your FAQ but I really want to challenge not listing #Wire on your list of messenger apps. It's much easier for non-technical people to understand and use than #Jami / #Ring (I've got my family using Wire with me). Also, unlike Signal, Wire can be used without supplying a phone number, and they have plans to implement server>server federation:
https://github.com/wireapp/wire/issues/160#issuecomment-446551908

@z428 gratis doesn't automatically mean unethical. It can mean a service is provided by volunteers (eg #RiseUp.net or #Disroot.org), which removes the single largest cost most internet service providers have (paying staff). It can also mean costs are being covered by users paying for premium features most users don't need, as with #Loomio, #Wire, or the new #FlickR (post acquisition by #SmugMug).
@jomo @switchingsocial

@sheogorath also #Wire have plans to implement server>server federation, at least between Wire servers (hopefully more broadly too):
https://github.com/wireapp/wire/issues/160#issuecomment-446551908
@Privacy

I love #Wire, and would use it every day, except for that fact that I can't get it working on my ancient Android/Linux device (4.2.2) either (despite heaps of help from their helpdesk), and I can't use it on on my GNU/Linux laptop (#Trisquel 8) because it's blocked by the Great Firewall, and our #VPN service won't work on my laptop ATM
@sheogorath @Privacy