HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
signalapp
Signal-Server
Java2014–2026
signalapp / Signal-Server

Signal-Server

Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS

108Distinct people
125Mentions
0Explicit recommenders
10.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS

GitHub

Where it is used

No documented product use was verified in the last source check.

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

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 7:27:27 AM 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 year125 dated mentions

Observed mentions: 2014-05-06 00:52:45 UTC to 2026-10-31 15:44:48 UTC.

02040602014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 9 mentions; 0 submissions, 9 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 64 mentions; 6 submissions, 58 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC303
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC303
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC909
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC725
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC808
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC11011
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC64658
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC606
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC404
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC303

What Hacker News says

64 sources
Signal has access to more data than they would like you to believe. Each account at Signal is identified by a phone number or an UUID. This account also contains a [list of devices](https://github.com/signalapp/Signal-Server/blob/c21eb6aa5098...). Each of the devices has some uinteresting metadata assigned to it, but more importantly it links to a specific Android or iOS device through the [push token](https://github.com/signalapp/Signal-Server/blob/c21eb6aa5098...). This gives the authorities a link to an account at Google or Apple which then of course contains much more data.
In MLAT order from Luxembourg for Signal user data
Related: does anyone know why the Signal-Server code allows for toggling request logging? [0] If this allows for logging raw HTTP(S) requests server-side, presumably this could be grabbing the passwords generated and held on each device used for authentication [1]? There's also no mention of TLS termination in the Signal-Server repository on GitHub, or TLS between the Redis cluster in use. If FBI or NSA has compromised the AWS VPC, then all of this network traffic would be in the clear to be picked up behind the load balancer(s). The Account DynamoDB table [2] also seems to indicate more information is tied to the phone number in cleartext than what is indicated by the response? [0]: https://github.com/signalapp/Signal-Server/blob/14f5271c2012... [1]: https://github.com/signalapp/Signal-Server/blob/14f5271c2012... [2]: https://github.com/
Read the rest
In Grand jury subpoena for Signal user data, Central District of California
Signal choosing not to federate isn't in the scope of this thread. IMO not federating is a guarantee of client quality. The last time I had a look at Matrix E2EE implementations, only Riot was barely usable. There was a ton of clients that didn't support it, didn't intend to, didn't have the confidence to go about implementing etc. >Also, what about the server source code? https://github.com/signalapp/Signal-Server There you go, last commit two days ago.
In Cryptographers unearth vulnerabilities in Telegram's encryption protocol
> I am 99% sure they did. Why? > I can't say affirmatively that anyone is running anything exactly Signal provides a means for reproducing Android builds so you can affirmatively determine what you're running. https://signal.org/blog/reproducible-android/ > but they now claim they did. Signal claims they shipped server updates without releasing code? Do you have a link to that? When others were complaining about the lack of an update to server, they're complaining about the client and server APIs being out of sync. Reading through these comments, I don't get the impression that the server code published is what's actually running. In fact the following comment even refers to it as a reference implementation: https://github.com/signalapp/Signal-Server/commit/3432529f9c... At the end of the day, it doesn't really matter much what server
Read the rest
code is running since the Clients manage encryption and the Server has no insight into the messages being exchanged.
In Update on beta testing payments in Signal
My theory is that the reason Signal was so reluctant to add slightly-less-secure-but-usable backups is that it is going to have some unified infrastructure for crypto and messaging storage/backup. The backup usability weirdness makes way more sense in that context. I don't understand security/crypto stuff so much, but the new version of the server seems to use the same secret token for crypto transactions as it does for backup https://github.com/signalapp/Signal-Server/search?q=userAuth... , which offers some evidence that this be the case.
In Et Tu, Signal?

Showing the 15 most recent of 64 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.