<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Guidelines for Artificial Intelligence Containment · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1707.08476/</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/1707.08476/feed.xml" rel="self" type="application/rss+xml" /><item><title>Guidelines for Artificial Intelligence Containment — mentioned by xpe</title><link>https://news.ycombinator.com/item?id=41853387</link><guid isPermaLink="false">urn:hackerpapers:mention:1707.08476:41853387</guid><pubDate>Tue, 15 Oct 2024 21:38:50 GMT</pubDate><description>&lt;p&gt;Of course I grant the above point that software systems are not &amp;quot;ethereal&amp;quot;. They have a physical form: often as electromagnetic states in matter. I hope my contribution to the conversation was clear: the nature of the physical embodiment matters. Things that are easy and cheap to copy are harder to contain. Containment of intelligent systems is very difficult, based on what we know about human flaws and security systems. &amp;gt;&amp;gt; When software can relocate its source code and data in seconds or less, containment strategies begin to look increasingly bleak. &amp;gt; Hard? sure. Impossible? No I don&amp;#x27;t need…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1707.08476/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.AI</category></item></channel></rss>
