3 ms·
awesome velocity - i could have sworn this was another of your famous Launch Weeks but its just a regular week for you now lol there's been a lot of these bots
by swyx 4y ago
awesome velocity - i could have sworn this was another of your famous Launch Weeks but its just a regular week for you now lol
there's been a lot of these bots coming out, and some of the poorly implemented ones are probably going to make this endeavor look bad, and i'm wondering for your thoughts - what Quality Control/testing approach do you think makes sense for an unbounded chat bot like this?
- kiwicopple 4y agoin our MVP checklist we had "XSS testing" and "Prompt injection", the latter somewhat cursory because there's no feasible way to prevent it right now. We found a lot of ways to "break out" of the prompt (which is also very visible since we're open source). Luckily, prompt break-outs are relatively benign (as long as we have spend-caps on OpenAI). The biggest win for companies like us is that something like this becomes ubiquitous, so that people get bored of prompt-hacking and then just use the tool like they are supposed to. Over time we'll add rate-limiting, caching, and other hardening.
- redeux 4y agoI’m actually working on an open source project to mitigate against prompt injections, handle cache, etc. and I’m collecting instances of prompt misuse. I’d love to see your findings. Did you document them anywhere that I can review?
- kiwicopple 4y agowe're not saving the prompts in this version. It's really an MVP, we couldn't have stripped it back much more We'd be happy to share some prompts in the future (as long as we can determine that it respect out users' privacy/safety)