MNmnot·May 10, 2023
You can open an issue:
https://github.com/protocol-registries/well-known-uris
In Tell HN: We should start to add “ai.txt” as we do for “robots.txt”protocol-registries
well-known-uris
OPEN SOURCE2021–2023
protocol-registries / well-known-uris
well-known-uris
Registry for Well Known URIs
3Distinct people
3Mentions
0Explicit recommenders
63GitHub stars
What to know before exploring
What it is
Registry for Well Known URIs
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, 5:04:57 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 month3 dated mentions
Observed mentions: 2021-08-30 03:28:56 UTC to 2023-05-10 14:11:21 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Aug 2021 | 2021-08-01 00:00:00 UTC | 2021-09-01 00:00:00 UTC | 1 | 0 | 1 |
| Sep 2021 | 2021-09-01 00:00:00 UTC | 2021-10-01 00:00:00 UTC | 1 | 0 | 1 |
| Oct 2021 | 2021-10-01 00:00:00 UTC | 2021-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2021 | 2021-11-01 00:00:00 UTC | 2021-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2021 | 2021-12-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2022 | 2022-01-01 00:00:00 UTC | 2022-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2022 | 2022-02-01 00:00:00 UTC | 2022-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2022 | 2022-03-01 00:00:00 UTC | 2022-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2022 | 2022-04-01 00:00:00 UTC | 2022-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2022 | 2022-05-01 00:00:00 UTC | 2022-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2022 | 2022-06-01 00:00:00 UTC | 2022-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2022 | 2022-07-01 00:00:00 UTC | 2022-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2022 | 2022-08-01 00:00:00 UTC | 2022-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2022 | 2022-09-01 00:00:00 UTC | 2022-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2022 | 2022-10-01 00:00:00 UTC | 2022-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2022 | 2022-11-01 00:00:00 UTC | 2022-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2022 | 2022-12-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2023 | 2023-01-01 00:00:00 UTC | 2023-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2023 | 2023-02-01 00:00:00 UTC | 2023-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2023 | 2023-03-01 00:00:00 UTC | 2023-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2023 | 2023-04-01 00:00:00 UTC | 2023-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2023 | 2023-05-01 00:00:00 UTC | 2023-06-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sourcesIf a given server doesn’t have a SRV record instructing where to look, I take it it just queries that domain directly. If so, putting the API at /plan/ is problematic, because in situations where user content is hosted from a domain it can allow any user to control the appearance of the domain by hosting certain stuff under /plan/, and also various domains will already be using /plan/ for something else.
The solution for this is well-known URIs <https://www.rfc-editor.org/rfc/rfc8615.html>: put it under /.well-known/, where all such hosting providers should know not to allow users to place files.
So perhaps /.well-known/plan/ or /.well-known/dotplan/. And if you’re serious about this project, once you’ve got the basics ironed out and specified in detail, and probably some degree of interest from others, request registration in the registe