HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
futo-org
Grayjay.Desktop
C#2024–2024
futo-org / Grayjay.Desktop

Grayjay.Desktop

Read-only mirror of Grayjay.Desktop repo for issue tracking

3Distinct people
3Mentions
1Explicit recommenders
900GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Read-only mirror of Grayjay.Desktop repo for issue tracking

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I love the right to repair work Louis Rossmann does, and this project goal as a whole, but this license is a major step backwards for software distribution with high assurances…

lrvick used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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, 1:49:46 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 hour3 dated mentions

Observed mentions: 2024-12-20 19:11:22 UTC to 2024-12-21 07:35:27 UTC.

012024-12-20 19:00:00 UTC to 2024-12-20 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 20, 19:002024-12-20 20:00:00 UTC to 2024-12-20 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-12-20 21:00:00 UTC to 2024-12-20 22:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-20 22:00:00 UTC to 2024-12-20 23:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-20 23:00:00 UTC to 2024-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 00:00:00 UTC to 2024-12-21 01:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 01:00:00 UTC to 2024-12-21 02:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 21, 01:002024-12-21 02:00:00 UTC to 2024-12-21 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 03:00:00 UTC to 2024-12-21 04:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 04:00:00 UTC to 2024-12-21 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 05:00:00 UTC to 2024-12-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 06:00:00 UTC to 2024-12-21 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-21 07:00:00 UTC to 2024-12-21 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsDec 21, 07:00

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
Dec 20, 19:002024-12-20 19:00:00 UTC2024-12-20 20:00:00 UTC101
Dec 20, 20:002024-12-20 20:00:00 UTC2024-12-20 21:00:00 UTC101
Dec 20, 21:002024-12-20 21:00:00 UTC2024-12-20 22:00:00 UTC000
Dec 20, 22:002024-12-20 22:00:00 UTC2024-12-20 23:00:00 UTC000
Dec 20, 23:002024-12-20 23:00:00 UTC2024-12-21 00:00:00 UTC000
Dec 21, 00:002024-12-21 00:00:00 UTC2024-12-21 01:00:00 UTC000
Dec 21, 01:002024-12-21 01:00:00 UTC2024-12-21 02:00:00 UTC000
Dec 21, 02:002024-12-21 02:00:00 UTC2024-12-21 03:00:00 UTC000
Dec 21, 03:002024-12-21 03:00:00 UTC2024-12-21 04:00:00 UTC000
Dec 21, 04:002024-12-21 04:00:00 UTC2024-12-21 05:00:00 UTC000
Dec 21, 05:002024-12-21 05:00:00 UTC2024-12-21 06:00:00 UTC000
Dec 21, 06:002024-12-21 06:00:00 UTC2024-12-21 07:00:00 UTC000
Dec 21, 07:002024-12-21 07:00:00 UTC2024-12-21 08:00:00 UTC101

What Hacker News says

3 sources
lrvick·Dec 21, 2024Recommendation phrase
I love the right to repair work Louis Rossmann does, and this project goal as a whole, but this license is a major step backwards for software distribution with high assurances of security, freedom and privacy. Debian, Arch, Guix, F-droid or any other independent signed reproducible build channels require a true Open Source license to function legally. The license thus forces users to download unsigned non-reproducible binaries off grayjay servers and trust blindly that their build server is creating binaries from exactly the published code and not compromised to inject tracking or malware not in the public repo (an increasingly common attack they may not even know about for years!). Or say the grayjay domain is hijacked or even a BGP attack or a LAN MITM. All sorts of ways they could be helping distribute malware and not know it with no
Read the rest
signatures or reproducible build proofs. Thing is, your team would not have to solve these problems if you licensed it so the community could solve them for you, as we do for thousands of open source software projects. I really want to see a project like this take off and would gladly donate, but only if it can be opened up for accountability via third party compilation and distribution channels so it can never be backdoored or co-opted for surveillance if your leadership or release engineers are ever compromised. Said license: https://github.com/futo-org/Grayjay.Desktop?tab=License-1-ov... There are other licenses like AGPL that would kill any attempt for someone to rip your code off to make their own proprietary offering, without locking yourself out of established freedom, security, and privacy preserving software distribution channels. If anyone from the team is reading this, I would be happy to detail and discuss my concerns further as a software supply chain security specialist. Hit me up.
In Grayjay Desktop App

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.