https://
arxiv.org/abs/2404.01413
@jeremyphoward
-
Model Collapse Paper Misses Key Data Retention Finding
By
–
Also the widely-shared model collapse paper ignored the earlier research that showed that models don't actually collapse at all if you keep even a bit of the original data around.
-
Enterprise Tool Adoption Challenges and Knowledge Gaps
By
–
I have no idea what that means. I'm not enterprise-ready enough to know about Slack.
-
Cursor should read llms.txt file by default
By
–
Yeah it would be great if Cursor read /llms.txt by default.
-
Feeding False Information to LLMs via Website Configuration
By
–
If you can modify the website to add a /llms.txt then you can already feed LLMs false information. But I don't see why you'd want to do that about your own website.
-
llms.txt Uses Markdown for Language Models and Agents
By
–
The llms.txt file is unusual in that it uses Markdown to structure the information rather than a classic structured format such as XML. The reason for this is that we expect many of these files to be read by language models and agents.
-
FastHTML Documentation Standards for LLM Integration
By
–
The FastHTML project follows these two proposals for its documentation. For instance, here is the FastHTML docs llms.txt: https://
docs.fastht.ml/llms.txt
And an LLM-ready context file: https://
docs.fastht.ml/llms-ctx.txt
All nbdev projects now create .md versions of all pages by default. -
How Language Models Process Information Differently
By
–
Providing information for language models is different to providing information for humans. Language models generally like to have information in a more concise form, and they can ingest a lot of information quickly.
-
llms.txt standard for LLM-friendly content distribution
By
–
We propose that those interested in providing LLM-friendly content add a /llms.txt file to their site. llms.txt markdown is human and LLM readable, but is also in a precise format allowing fixed processing methods.