WAwanderingmind·Jan 28, 2022
License link provided here: https://github.com/wireapp/wire
In Wire is now on F-Droidwireapp
wire
OPEN SOURCE2016–2022
wireapp / wire
wire
:wavy_dash: Overview of the open source code for Wire
9Distinct people
9Mentions
0Explicit recommenders
2.6KGitHub stars
What to know before exploring
What it is
:wavy_dash: Overview of the open source code for Wire
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year9 dated mentions
Observed mentions: 2016-06-30 15:41:27 UTC to 2022-01-28 22:36:22 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
9 sourcesI'm amazed that they still don't have any kind of 2FA after nearly four years.
https://github.com/wireapp/wire/issues/85
In Large-Scale Abuse of Contact Discovery in Mobile Messengers [pdf]In addition, their server-side code is open-source and they claimed that federation support is something they are considering to add: https://github.com/wireapp/wire/issues/160
Overall, I'm also not a big fan of Signal's hostility to federated protocols (https://signal.org/blog/the-ecosystem-is-moving/), so I'm more optimistic about Wire in the long run.
In Ask HN: Why does P2P encrypted messaging still suck?Looks great, I was not aware they had open source client.
Given that they were forced to release their Axolotl (aka Signal protocol) under GPLv3+, they try to add some strange restrictions [2]:
"Additionally, if you choose to build an Open Source App, certain restrictions apply, as follows: a. You agree not to change the way the Open Source App connects and interacts with our servers ..."
As I understand I am free to ignore any additions to GPL.
[1] https://medium.com/@wireapp/axolotl-and-proteus-788519b186a7...
[2] https://github.com/wireapp/wire
In Reasons not to use Skype (2012)https://github.com/wireapp/wire#proteuscryptobox for info on Proteus/Cryptobox that Wire uses.
In Facebook Ordered to Stop Collecting Data on WhatsApp Users in GermanyDoes the Wire licence agreement allow you to create a standalone server though?
https://github.com/wireapp/wire/blob/master/README.md
"Additionally, if you choose to build an Open Source App, certain restrictions apply, as follows:
a. You agree not to change the way the Open Source App connects and interacts with our servers"
Even if the company behind Wire seems trustworthy, if I cared about security I wouldn't want any interaction between clients to go through a server I didn't have control over.
In Wire open-sourcedCorrect, there's no server. I will avoid blockquoting large amounts of text but on their open source summary page [1], they give you two options:
1. you point your implementation to their server and you have to abide by their additional terms (which is exactly what I'd expect)
- or -
2. you point your implementation to somewhere else, unspecified, and you're only bound by GPLv3
Right now, #2 is moot because there is no compatible server you can host. Once someone implements a compatible server, this will get a lot more exciting.
[1] https://github.com/wireapp/wire#open-source
In Wire open-sourcedWire – Secure Messenger – Just Went Completely Open Source
9 points · Open discussionIs Semaphor focused on group chat (Slack) or are there plans to support private communications (text, audio, video) like Wire? Unlike Signal, Wire allows registration with only an email address (via http://app.wire.com) and does not force you to upload your contacts to their server.
Article: http://arstechnica.com/business/2016/03/go-ahead-make-some-f...
Security: https://www.documentcloud.org/documents/2756350-Wire-Securit...
Code: https://github.com/wireapp/wire
In Snowden’s Favorite Cloud Service Now Has a Group Chat App