HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
handshake-org
hs-names
C2019–2023
handshake-org / hs-names

hs-names

Pre-reserved Handshake Names

4Distinct people
5Mentions
0Explicit recommenders
31GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Pre-reserved Handshake Names

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, 3:56:07 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 year5 dated mentions

Observed mentions: 2019-09-18 08:20:14 UTC to 2023-01-29 12:35:49 UTC.

0122019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

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
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 UTC000
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

5 sources
> Because in some cases, that is the rule. See Rule #5 https://github.com/handshake-org/hs-names How does the rule in any shape or form contradict what I have stated? It says: "The domain must not collide with a higher-ranked domain. For example, google.co.uk would lose to google.com. Only the owner of the higher-ranked domain is able to redeem it" Point is that many developers invested a lot of time and effort into establishing rules for reservation to maximize fairness, so when a domain is not reserved my statement above applies: why would some company co in country x be more entitled to the one in country y? After all the reservation rules have been applied and determined some specific reservation outcome. There are some proposed solutions in that case too, some of which I have outlined before. >Why should any brand be entitled to such
Read the rest
things? Exactly, but you are the one making a fuss about in the first place. >Can you quote where I did this? I could for you I already did, it's your rant directly to my long elaboration to your question. I'm not going to further entertain your flame baits, everybody can see how much effort each of us put into thoughtful responses and can judge accordingly.
In Domain Registry Takes Sci-Hub’s .SE Domain Name Offline
> why should be some company "co" from country x be more entitled to their own tld than the company co with the same name from country y? Because in some cases, that is the rule. See Rule #5 https://github.com/handshake-org/hs-names > if a brand was not significant enough to reach internet search significance why should they be entitled to their own tld? Why should any brand be entitled to such things? > but resorting to hand-wavy rants won't be constructive or helpful for any serious dialogue. Can you quote where I did this? I could for you
In Domain Registry Takes Sci-Hub’s .SE Domain Name Offline
> When ICANN does issue new TLDs, they’ll only allow at most 500 new TLDs per year. The likelihood of conflict is low even though conflicts can technically happen. Oh, "only" 500? Out of which a substantial fraction will be common words and therefore likely to be squatted on if Handshake is even remotely popular? I wondered if Handshake was at least trying to reserve English words, but apparently not, judging by this: Names which were added _after_ the final snapshot: - `charity` - A new gTLD added on ICANN's system. - `inc` - A new gTLD added on ICANN's system. - https://github.com/handshake-org/hs-names/blob/master/README... Please tell me there's something I'm missing...
In Handshake: Decentralizing DNS to Improve the Security of the Internet

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.