←back to thread

1480 points sandslash | 1 comments | | HN request time: 0.252s | source
Show context
nodesocket ◴[] No.44315062[source]
llms.txt makes a lot of sense, especially for LLMs to interact with http APIs autonomously.

Seems like you could set a LLM loose and like the Google Bot have it start converting all html pages into llms.txt. Man, the future is crazy.

replies(3): >>44315157 #>>44315298 #>>44315385 #
practal ◴[] No.44315385[source]
If you have different representations of the same thing (llms.txt / HTML), how do you know it is actually equivalent to each other? I am wondering if there are scenarios where webpage publishers would be interested in gaming this.
replies(2): >>44315617 #>>44315789 #
andrethegiant ◴[] No.44315617[source]
<link rel="alternate" /> is a standards-friendly way to semantically represent the same content in a different format
replies(1): >>44326650 #
1. diggan ◴[] No.44326650[source]
Also HTTP headers Accept/Content-Type which in theory could let you serve HTML, XML and JSON all under the same URL/URI but depending on Accept values.