Wire Messaging Application – The Downfalls | Hacker News Reader

Wire Messaging Application – The Downfalls

crysp.uwaterloo.ca

42 pointsmaxt12 comments

Since I'm a Wire-messenger fanboy, I'm really happy to see an analysis of the messenger. So thanks for that!

Regarding the last point:

"So, I sent a message to the CTO of Wire, Alan Duric, asking why the server was closed. He immediately got back to me to let me know that releasing the source code for the server was underway. When I pushed for specifics, I got the following response:

“License will be the same GPLv3 and timeline is next year.”" [0]

[0] http://www.networkworld.com/article/3140014/open-source-tool...

Wire (client) was open sourced after (because?) they failed to gain popularity. They also failed with monetization - even today they are burning investor's money.

Open sourcing the client was always the plan after moving everything to E2EE. Just took a number of months to get the code into a shape that we wanted.

Monetization - we've invested 0 dev time into this so far. So a bit early to claim "they also failed".

Have you had much problems with bugs using Wire? I've been using it intensely for over a year or so and I can say that I've never used a buggier app to this day.

Calls connect 75% of the time (at best) and the app is still filled to the brim with UI bugs. Example: often, when I open a notification I'm transported to the right conversation, but at the beginning of the conversation history. This is a year back, and when I begin scrolling down the app hangs. I need to force stop the app and open it again to see the actual message.

It seems they're obsessed with adding new features (like robot voice fx for audio messages), but don't know to fix the important things.

Still, strangely enough, I continue to use it. It works, but has a ton of quirks. I use stock unrooted Android on a 5X and the other 7 or so people that I know uses Wire have all experienced the same problems.

Have you created these issues on github? They have fixed all bugs I reported, even new features (except grouping contacts)

The audio/video call doesn't work as expected. Thats true.. But for me, the reason for that could be my old Iphone.

However, I extensively use the chat functionality on iphone/android/linux/osx and that works perfect. And I really appreciate that I can logged-in, with multiple devices at the same time.

Hi mate, fair criticism. After working on making everything E2EE we had to play catch up in terms of features for a while. Turns out people want security and privacy AND useful and fun features.

We're now focused on clearing up some of the technical debt and the issue you describe is being worked on.

Another thing we're rewriting is the calling part to speed up connection time, improve robustness, reduce meta data footprint. This is now in internal testing.

Are you still a Wire fanboy after reading the report?! I much prefer Threema, not only for security reasons but also because of the interface. Wire looks like a design student's first project.

Glad to see this under scrutiny. A lot of websites are eager to recommend any application that claims to be secure, and it is often the case that neither the author nor the audience is equipped to make that judgment. Hopefully we'll see full fledged security audits for less popular secure messaging apps in the future.