3 ms·
This is the same approach that Supabase Clippy took: https://supabase.com/blog/chatgpt-supabase-docs https://supabase.com/blog/chatgpt-supabase-docs They calle
by kaycebasques 4y ago
This is the same approach that Supabase Clippy took: https://supabase.com/blog/chatgpt-supabase-docs 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).
- kiwicopple 4y agoThe lawyers haven’t reached out yet! Too distracted with all the LLM-generated emails they are getting sent no doubt
- triyambakam 4y agoWhy call it Clippy at all if you anticipate a conflict? It feels immature.
- kiwicopple 4y agoyes, 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