News for hackers. Stuff that matters.
Re:Wire messenger server code open-sourced by y0ghur7_xxx on Saturday April 08, 2017 @03:13PM (#14068477)
there is something i never understood, maybe someone can help me: what makes wire better than xmpp? why do we need yet another protocol for chat?
Re:Wire messenger server code open-sourced by Arathorn on Saturday April 08, 2017 @05:23PM (#14069112)
I can't respond for XMPP, but the same question probably goes for Matrix (or any other open comms standard). Reasons you might use Wire over Matrix are probably if you prefer the app's UI/UX to any of the Matrix clients out there, or if you like some of Wire's more unusual features like sketch-sharing, or if you want compulsory E2E crypto, decent group VoIP calling, or a system which does not consider itself beta.

Conversely, the reasons you might use Matrix over Wire is if you want an open standard for the protocol (simple HTTP+JSON), or an ecosystem of different clients, servers, bots & bridges, or Apache licensed impls rather than AGPL, or implementations which were built from the outset as FOSS, or to decentralise history across an open federation of multiple servers rather than be forced to federate via a centralised service, and bridges through to things like IRC, Slack, Gitter etc.

Re:Wire messenger server code open-sourced by voidz on Saturday April 08, 2017 @09:38PM (#14070014)
Video calling works splendidly, which is why my wife and I chose Wire.

Back when our boy was just a few months old and my wife's maternity leave came to an end, keeping in touch with video made going back to work a less difficult. She'd call every time she needed some assurance that we were OK, and I could show her we were, in high resolution.

Signal didn't have video calling back then, and Skype is out of the question because I really distrust Microsoft.

Re:Wire messenger server code open-sourced by 0x6c6f6c on Saturday April 08, 2017 @04:28PM (#14068832)
As a service, what it's provided is consistency for the group of friends I use it with. We've tried XMPP and Matrix on multiple accounts and had trouble on the server and client side. Wire is out of the box a great option with open source ideologies and some feature we liked that weren't available with XMPP or Riot.

They could have done the same thing with existing protocols, but I do like the way it was done and how well it works for us, and as a consumer of the service it's satisfied areas where XMPP/Matrix felt.. fragile.

Not that XMPP or Matrix are vastly inferior, there's certainly an issue or two we've had with Wire, but just how well it worked for us immediately was largely why we've stuck to it.

Re:Wire messenger server code open-sourced by Arathorn on Saturday April 08, 2017 @04:40PM (#14068900)
It would be great if you could detail what issues you encountered with Matrix (and/or file some bugs to help things improve). Unlike XMPP, Matrix is still considered in beta which gives us a lot of flexibility in addressing shortcomings :)
Re:Wire messenger server code open-sourced by 0x6c6f6c on Monday April 10, 2017 @08:59AM (#14078090)
Issues I encountered were already reported on their GitHub pages if I recall correctly. I normally make a point to document and report these issues, if I can't submit a PR myself ;)
Re:Wire messenger server code open-sourced by feld on Saturday April 08, 2017 @04:37PM (#14068880)
XMPP is terribly fragmented and the clients all suck.
Re:Wire messenger server code open-sourced by unicornporn on Saturday April 08, 2017 @08:13PM (#14069783)
I just tried https://conversations.im/ and I must I'm very impressed.
Re:Wire messenger server code open-sourced by jhasse on Sunday April 09, 2017 @05:33AM (#14071336)
The clients on everything except Android all suck.
Re:Wire messenger server code open-sourced by Xylakant on Sunday April 09, 2017 @05:47AM (#14071392)
To add to that, try enabling omemo across 4 different OS (Andoid, iOS, MacOS and Linux) and you'll want to burn all of your devices. Messages showing up on some devices randomly or not, etc. nice thing in general and I really like the idea of xmpp, but not exactly user-friendly for non-technical folks.
Re:Wire messenger server code open-sourced by rodrigo67 on Monday April 10, 2017 @11:36AM (#14079395)
Fragmented is not the right word, it is federated. Many clients suck, not all.

Be sure to choose a good server: https://gultsch.de/compliance_ranked.html

And a good client: https://omemo.top

Dino is a new Linux client. It's nice and simple.

Re:Wire messenger server code open-sourced by jtrevner on Saturday April 08, 2017 @06:14PM (#14069357)
I was able to get my grandmother and non-techie friends to use it. What Signal and Wire have over other encrypted chat is user experience. I'm no longer a tin-foil hat crypto nerd only talking to other tinfoil hat crypto-nerds.
Re:Wire messenger server code open-sourced by isilauzelis on Saturday April 08, 2017 @11:24PM (#14070257)
I assume it's the same thing as signal is for me: it's the thing with UX good enough to convince some of my friends to use it. They wouldn't use buggy xmpp, tox clients or things without many of the features like ricochet.

I like testing these tools with cryptonerd friends though.