From d5a4cb0d4f331f36c75d869309dad3a3c57eee10 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 26 Sep 2026 17:09:01 +0200 Subject: [PATCH] =?UTF-8?q?Issue=20122:=20count=20it=20properly=20?= =?UTF-8?q?=E2=80=94=2030=20of=2071=20definitions=20name=20this=20installa?= =?UTF-8?q?tion?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The five modules this report first named were what a first look found. A sweep of all 71: 49 public domains across 26, the node's own name 58 times across 19, a routable IP 12 times in one, 798 absolute paths across 70 (issue 119's number, grown), and no email addresses at all. The sharpest case is not a domain: a mail module states the node's public IPv4 as the address it trusts a real-IP header from, so a node that moves or gains a second address stops attributing mail correctly, silently. Two upstream resolvers are excluded deliberately — naming a public DNS service is a policy default, true of any mesh, not a fact about this one. --- .../00-report.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/04-ISSUES/122-a-module-cannot-ask-for-its-own-public-name/00-report.md b/04-ISSUES/122-a-module-cannot-ask-for-its-own-public-name/00-report.md index 0045a88..98c114e 100644 --- a/04-ISSUES/122-a-module-cannot-ask-for-its-own-public-name/00-report.md +++ b/04-ISSUES/122-a-module-cannot-ask-for-its-own-public-name/00-report.md @@ -30,6 +30,28 @@ automation module, whose environment file states its host, its protocol and a fu URL as literals; two more — the proxy and the builder — carry a complete clone URL for a repository on this mesh's own forge, scheme, host and port included. +**Counted properly, 2026-09-26.** The five were what a first look found. A sweep of all 71 +definitions, for values that could only be true of one installation: + +| What is named | Occurrences | Modules | +|---|---|---| +| A public domain, or a name under one | 49 | 26 | +| The node's own name | 58 | 19 | +| A routable IP address | 12 | 1 | +| An absolute path on the machine | 798 | 70 | +| An email address | 0 | 0 | + +The path row is [issue 119](../119-a-module-definition-decides-where-its-files-live/00-report.md), +counted again and grown. The rest is this issue. **Thirty of the seventy-one definitions name this +installation** in one of the first three ways, and the worst single case is not a domain at all: a +mail module states the node's own public IPv4 as the address it trusts a real-IP header from, so a +node that moves, or gains a second address, silently stops attributing mail to the right sender. A +private subnet, the mail domain, the site name and the administrator's domain sit in the same block +of values. + +Two upstream resolvers are excluded from the count deliberately: naming a public DNS service is a +policy default, true of any mesh that wants it, not a fact about this one. + So the three under review are the visible edge of a pattern the catalogue already follows, which changes what this issue is for. It is not a matter of refusing three changes; there is no version of this catalogue today that does not name the mesh it was written in, and a mechanism is the only -- 2.54.0