8 ms·
The next version of the llms.txt proposal will allow an llms.txt file to be added at any level of a path, which isn't compatible with /.well-known. (I'm the cr
by jph00 1y ago
The next version of the llms.txt proposal will allow an llms.txt file to be added at any level of a path, which isn't compatible with /.well-known.
(I'm the creator of the llms.txt proposal.)
- nothrabannosir 1y ago[flagged]
- dang 1y ago"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- nothrabannosir 1y agoFair
- nothrabannosir 1y agoPS apologies to jph00. I still believe what I believe but I should have phrased it differently or not at all. Good luck on your endeavors either way.
- achempion 1y agoEven with this future approach, it still can live under the `/.well-known`, think of `/.well-known/llm/<mirrored path>` or `/.well-known/llm.json` with key/value mappings.
- andrethegiant 1y agoDoesn’t this conflict with the original proposal of appending .md to any resource, e.g. /foo/bar.html.md? Or why not tell servers to respond to the Accept header when it’s set to text/markdown?