<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Indexing AI Risks with Incidents, Issues, and Variants · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2211.10384/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2211.10384/feed.xml" rel="self" type="application/rss+xml" /><item><title>Indexing AI Risks with Incidents, Issues, and Variants — mentioned by smcgregor</title><link>https://news.ycombinator.com/item?id=35632258</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.10384:35632258</guid><pubDate>Wed, 19 Apr 2023 19:28:18 GMT</pubDate><description>&lt;p&gt;Incident 73 dates back several years -- it is part of the initial Google spreadsheet from 2018. At the time, we had no formal definitions [0] or criteria [1] and only a vague idea of what we would find. My cursory re-read of 73 agrees with your assessment. We are likely to define it as not being an AI incident, but the incident profiles are also meant to be permalinks that the research/blogging/etc communities can analyze and build community around. I&amp;#x27;ll bring 73 to our weekly editors meeting and we may add it to the list of incidents that didn&amp;#x27;t pass additional scrutiny [2]. Like Wikipedia…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.10384/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CY</category></item><item><title>Indexing AI Risks with Incidents, Issues, and Variants — mentioned by smcgregor</title><link>https://news.ycombinator.com/item?id=35630633</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.10384:35630633</guid><pubDate>Wed, 19 Apr 2023 17:07:12 GMT</pubDate><description>&lt;p&gt;(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…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.10384/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CY</category></item></channel></rss>
