←back to thread

1480 points sandslash | 4 comments | | HN request time: 0.639s | source
Show context
sneak ◴[] No.44315221[source]
Can we please stop standardizing on putting things in the root?

/.well-known/ exists for this purpose.

example.com/.well-known/llms.txt

https://en.m.wikipedia.org/wiki/Well-known_URI

replies(2): >>44315294 #>>44315797 #
jph00 ◴[] No.44315797[source]
You can't just put things there any time you want - the RFC requires that they go through a registration process.

Having said that, this won't work for llms.txt, since in the next version of the proposal they'll be allowed at any level of the path, not only the root.

replies(3): >>44316300 #>>44316425 #>>44316747 #
1. dncornholio ◴[] No.44316425[source]
> You can't just put things there any time you want - the RFC requires that they go through a registration process.

Excuse me???

replies(1): >>44317022 #
2. jph00 ◴[] No.44317022[source]
From the RFC:

""" A well-known URI is a URI [RFC3986] whose path component begins with the characters "/.well-known/", and whose scheme is "HTTP", "HTTPS", or another scheme that has explicitly been specified to use well- known URIs.

Applications that wish to mint new well-known URIs MUST register them, following the procedures in Section 5.1. """

replies(2): >>44326050 #>>44326522 #
3. zelphirkalt ◴[] No.44326050[source]
Applications, not the websites, web services, or such. I read that as: "If you are making an application and you want it to introduce a new convention, then sign up here." (otherwise do whatever you want)
4. diggan ◴[] No.44326522[source]
Keyword being "mint" there. You can still put whatever you want in there, but in order to "register" it, you need to"mint" it by registering it. But you're in no way obligated to register random stuff you put in /.well-known, that'd be bananas to put in a specification like that.