@simon Unfortunately, I'm pretty sure the absence of cues like these is very much by design.
Top-level
@simon Unfortunately, I'm pretty sure the absence of cues like these is very much by design. 4 comments
@allafarce @simon Yes, this is the approach. Unfortunately, this isn't really helpful as an API response as it requires consumers (people or software) to parse out inconsistent warnings. @allafarce @dbreunig that's the approach that u don't think works well enough I want those things to be visually distinct and shown outside of the main conversation @simon @allafarce Same. I don't think it's in their current priority set. They want to both drive massive adoption while stoking fears to drive protective regulation. There are a steady stream of examples of Altman talking out of both sides of his mouth. |
@dbreunig @simon My experience with ChatGPT so far is that they seem to be focusing on the cues being in the model response, not out of band, no? (Not saying I don't like the idea in general, just saying it seems to me they are more interested in directly caveating by model tweak than interface, which is especially important given this affordance doesn't really work in an API by default)