June 19, 2026
URL soap opera in /.well-known
So You Want to Define a Well-Known URI
Internet rulebook sparks eye-rolls as commenters ask: who is this even helping?
TLDR: The article says special website shortcut pages should only be used when an app already knows the site and needs one central place to find something important. Commenters split between cheering the anti-clutter message and mocking the advice as vague, overcomplicated, and weirdly specific.
A web standards veteran tried to lay down some gentle advice on when websites should use special site-wide shortcut pages—the kind hidden in a reserved spot so apps, browsers, or bots can quickly find things like password changes or access rules. In plain English, the message was: use these only when they solve a real problem, not because they make your project look official. Sounds sensible, right? The comments immediately turned it into a mini revolt.
The loudest reaction was basically: this is too vague, too fussy, and maybe too precious. One commenter wanted to know why these reserved links are so oddly specific instead of using one generic “link tree” for everything, calling the whole process a waste of time. Another flat-out shrugged, saying the post felt like “nothing” dressed up as expertise. Ouch. And then came the snark: “How well-known are those URIs though?”—a perfect little jab that practically wrote itself.
But there was also a real camp of cleanup enthusiasts cheering the broader point. They’re fed up with every new project dumping files in the top level of a website, with llms.txt becoming the villain of the moment. Their rallying cry: stop polluting the root of the domain. Even that sparked aesthetic drama, though, because one person looked at a sample address ending in /.well-known/robots.txt and basically said, “Honestly? That’s not prettier either.” So yes: a niche standards post somehow became a food fight over internet tidiness, usefulness, and whether naming things online is secretly impossible.
Key Points
- •The article says well-known URIs work best when a client already knows a site and needs site-wide information or interaction.
- •robots.txt is presented as a key example because it centralizes access policy for crawlers and avoids checking every response.
- •The author says registering a well-known URI does not itself provide legitimacy or guarantee adoption for a protocol.
- •Using well-known URIs as a substitute for conveying full URLs can create rigid one-service-per-site deployment constraints.
- •The article highlights discovery ambiguities, such as whether clients should query a subdomain or parent domain and how redirects should be handled.