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

5 sources
They announced the feature coming to desktop "shortly" seven (7) years ago [1]. It has been implemented on mobile for ages, and is generally one of the most-popular features of any modern messaging service. In the years since, things like in-app cryptocurrency were implemented. Issues on GitHub dating back to 2017 were unceremoniously locked [2]. A community feature request has been open since 2018 [3]. When more issues on GitHub were created, they were told to discuss it in the one that was already locked, and didn't respond further once that was noted to be impossible [4]. When the PR was thoughtfully created long after it was clear that they wouldn't be honoring their own announcement, they said (approximately a year ago) that they would review and implement it with credit. After 6 months of darkness and petitioning, it was dismissed a
Read the rest
s being harder to review than to implement while disingenuously counting things like SVGs and license text as LOC. When some specific concerns were finally provided, the author responded point-by-point in how they were already researched and addressed, with a polite request for evidence so that they could correct any misunderstandings. The subsequent response ignored everything in that but the suggestion to update the contribution guide to align with their previously-unstated intent. Serially mishandled. I'm not moving off of that position. 1: https://signal.org/blog/giphy-experiment/ 2: https://github.com/signalapp/Signal-Desktop/issues/1862 3: https://community.signalusers.org/t/add-gif-search-giphy-to-... 4: https://github.com/signalapp/Signal-Desktop/issues/4841
In Privacy is priceless, but Signal is expensive
If you only have the phone app then yes they are instantly downloaded and removed from their servers. But if you have Desktop client(s) registered, then they need to hold onto those messages until you open your client(s). That is why they have a 30 day login limit on Desktop clients. If they didn't they'd potentially have to hold onto messages forever. https://github.com/signalapp/Signal-Desktop/issues/4730 https://community.signalusers.org/t/dont-unlink-devices-afte...
In Privacy is priceless, but Signal is expensive
The main idea of my experiment was to run IPv6 only setup without any IPv4 connectivity: sudo ip route get 8.8.8.8 RTNETLINK answers: Network is unreachable So I intentionally decided not to have IPv4 connectivity system wide to catch apps with issues in IPv6 only environment and then carefully evaluate issues and report them to authors: https://github.com/mozilla-mobile/mozilla-vpn-client/issues/... https://github.com/signalapp/Signal-Desktop/issues/4121 Dual stack setups tend to hide IPv6 implementation issues and may create illusion that app is IPv6 compatible but in reality it's not. Clearly my setup is too hostile for home users but as developer I enjoy it a lot.
In Enabling IPv6 support for IPv4 only apps on Linux

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.