14 karma · joined August 11, 2011
[0] https://arxiv.org/abs/2211.10384
[1] https://incidentdatabase.ai/editors-guide/
[2] Listed in the report here: https://incidentdatabase.ai/cite/298/#r2471
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
We index everything that people believe is AI. Including GOFAI, for example: https://en.wikipedia.org/wiki/GOFAI
We also index incidents related to people transferring decision authority to simple programs like the Stanford vaccine distribution: https://incidentdatabase.ai/cite/91/
In general, we err towards indexing useful information to the state of AI safety and introduced indexing "AI Issues" to develop the boundary and collect information on systems likely to produce incidents in the future: https://incidentdatabase.ai/apps/discover/?display=details&i...
Our editing guide is here: https://incidentdatabase.ai/editors-guide/
[0] F. Beato, I. Ion, S. Capkun, M. Langheinrich, and B. P. (2013). For Some Eyes Only: Protecting Online Information Sharing. In ACM Conference on Data and Application Security and Privacy.
edit for sub-comment: A traditional web app updates every time you hit the URL. In a browser extension your code is not necessarily tied to any remote origin, including the Chrome/Firefox stores. It is a user's choice to automatically receive updates from the vendor and this is the same choice that you make if you use apt-get vs manual download/checksum/sig check/audit.