HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
signalapp
Signal-Desktop
TypeScript2014–2025
signalapp / Signal-Desktop

Signal-Desktop

A private messenger for Windows, macOS, and Linux.

91Distinct people
110Mentions
0Explicit recommenders
16.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A private messenger for Windows, macOS, and Linux.

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, 5:04:15 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 year110 dated mentions

Observed mentions: 2014-07-21 20:03:41 UTC to 2025-11-29 07:17:05 UTC.

051015202014-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): 12 mentions; 1 submissions, 11 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 21 mentions; 8 submissions, 13 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 12 mentions; 2 submissions, 10 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 8 mentions; 0 submissions, 8 comments2025

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 UTC12111
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC505
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC13112
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC14014
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC202
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC1019
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC21813
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC12210
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC505
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC523
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC808

What Hacker News says

21 sources
Not the person you replied to, but a GitHub issue thread [1] seems quite close. I find it somewhat confusing and potentially troubling that (from a few minutes of searching so correct me if I’m wrong) a full-featured ARM-native fork seems to have been created in the community, but the team apparently doesn’t want to go the extra mile of designing the build/CI system to incorporate this as an official release. [1] https://github.com/signalapp/Signal-Desktop/issues/5612
In Become a Signal Sustainer
Sorry, yes. There's multiple sources, but a lot of it collected here: https://github.com/signalapp/Signal-Desktop/issues/4461 They keep shutting down tickets about it, refuse to review a PR that implemented it for them, and won't even tick the box on the Signal iPad app that would make it available on M1 Macs (where side-loaders have already confirmed for them that it works perfectly. 90% of my Signal usage was on desktop, so this has left such a bad taste that I'd rather use almost anything else now.
In Become a Signal Sustainer
Yes, contempt is an accurate assessment. Shipping nonconsensual spyware is unethical, and there are too many devs in our industry who are happy to behave unethically so long as their boss tells them to. Creating more social and reputational consequences for individual worker bees who make such commits on the job is also on my to-do list. Ultimately the opt out vars are token efforts by developers anyway. These projects only do the bare minimum of opt-out-ability because they have to be able to point to the opt-out setting as justification for their shipping of spyware-by-default. Making it easier to opt out isn't something they want, regardless of how much I do or don't mask my contempt for such unethical, user-hostile practices. The way the Audacity thing is playing out is instructive. Many devs simply feel entitled to take over your
Read the rest
machine as if it is theirs and your double-click is a blank check. My PRs against autoupdates have run in to similar developer resistance. https://github.com/signalapp/Signal-Desktop/issues/4578 https://github.com/bitwarden/desktop/issues/552
In Console Do Not Track – Proposal for a standard environment variable
OT and tinfoil hat on; there was a strange event last week with users of Signal on the Telia ISP.[1] For about 24 hours no messages could be sent, resulting in a 401 unauthorized error from the server side. Telia is the former state-owned Swedish ISP that is now only half state-owned I believe. They have a bad rep already for sending out extortion letters to torrent users and are almost assumed to be monitoring all user traffic for the police. No explanation of the event has been provided by anyone. Users have done some basic troubleshooting but couldn't really establish much. I personally would love to see what those 401 errors looked like on the Signal server side. What exactly were these clients sending that was unauthorized on the server side? I guess we'll never know, hopefully it wasn't even stored. 1. https://github.com/signalapp/S
Read the rest
In Grand jury subpoena for Signal user data, Central District of California
How or why would they ban you for publishing software? If they ban end-user accounts that use your client software to connect to their API, that's obviously a bug in your software as it diverges from the behavior of the official client. This is why anyone making an alternative client should be doing so with a fork of upstream that is regularly updated. You'd need to keep it in sync pretty closely. Most official Signal clients autoupdate (a huge security vulnerability in and of itself[1], as SolarWinds demonstrated very nicely for everyone), but not all of them (you can't override the user's systemwide app autoupdate setting on iOS), so they have to maintain BC with out of date versions for at least a few weeks/months. [1]: https://github.com/signalapp/Signal-Desktop/issues/4578
In Signald: Unofficial daemon for interacting with Signal

Showing the 15 most recent of 21 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.