Hacker News new | past | comments | ask | show | jobs | submit login

(I am from the org behind the Incident Database)

I agree about it being a stretch, but we err towards indexing boundary cases. This one turns on whether you would consider the web application as being part of ChatGPT or not. In aviation, there are many systems that are part of safely flying from point to point that are not part of the plane itself. The control tower, the runway markings, and the processes built around these things. While the ChatGPT web application is not the model underlying the ChatGPT front end, it is part of the whole intelligent system.

More information: https://incidentdatabase.ai/editors-guide/

Edit: On Slack we considering downgrading this one to the second tier status, which is an "issue," but our "issue" definition typically differentiates between events (a harm happened) and non-events (a harm may happen). This doesn't quite fit here. We have robust editor discussions around these ontological problems and are developing the ruleset in response to challenges. We aim for inter-rater reliability via the editor's guide. More details are here https://arxiv.org/abs/2211.10384




It's fine to consider the web app code as part of "ChatGPT".

But you shouldn't say that and also say "ChatGPT is an AI" at the same time. Those are two slightly but importantly different definitions of "ChatGPT".

Looking at your glossary here, the definition of "AI incident" should probably be adjusted, and in its current form it should not be taken too literally. Because if a server fell over on someone, and that server was hosting an AI, that would technically fit your definition.


Great point! We are constantly discussing the criteria. For example, if a robot lost power and fell on someone, do you think that is an incident? What if the robot was never turned on and fell on someone in shipping? When these challenges come up, we try to expand the editing guide to meet the challenge of all the ways intelligence of the artificial variety can go wrong.


Just make it easy to filter out. Possibly make it the default to filter out.


Collaborators are already working to provide data labels to all incidents that would support this particular filter. Many filters are available here: https://incidentdatabase.ai/apps/discover/?display=details&i...




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: