News for hackers. Stuff that matters.
Re:Knowledge retrieval architectures for LLMs (2023) by kaycebasques on Thursday April 27, 2023 @08:35PM (#35736227)
This is the same approach that Supabase Clippy took: https://supabase.com/blog/chatgpt-supabase-docs

They called it "context injection" but the OpenAI community appears to call it "retrieval-augmented generation".

Edit: I see now that Matt's post is talking all about these ideas. I'm happy that the terminology around this space is solidifying.

(Tangent) I will go to the grave continuing to call it Supabase Clippy even though presumably this prediction from the Supabase blog post became true:

> Today, we're doing our part to support the momentum by releasing “Supabase Clippy” for our docs (and we don't expect this name to last long before the lawyers catch on).

Re:Knowledge retrieval architectures for LLMs (2023) by kiwicopple on Thursday April 27, 2023 @09:10PM (#35736435)
The lawyers haven’t reached out yet! Too distracted with all the LLM-generated emails they are getting sent no doubt
Re:Knowledge retrieval architectures for LLMs (2023) by triyambakam on Thursday April 27, 2023 @11:29PM (#35737171)
Why call it Clippy at all if you anticipate a conflict? It feels immature.
Re:Knowledge retrieval architectures for LLMs (2023) by kiwicopple on Friday April 28, 2023 @12:26AM (#35737468)
yes, it's immature, however in January not many companies had created something like this and it was the most analogous way of explaining the functionality. it's also memorable