<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Divide, Denoise, and Defend against Adversarial Attacks · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1802.06806/</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/1802.06806/feed.xml" rel="self" type="application/rss+xml" /><item><title>Divide, Denoise, and Defend against Adversarial Attacks — mentioned by igorkraw</title><link>https://news.ycombinator.com/item?id=29385304</link><guid isPermaLink="false">urn:hackerpapers:mention:1802.06806:29385304</guid><pubDate>Mon, 29 Nov 2021 21:08:36 GMT</pubDate><description>&lt;p&gt;I work in this field, I have a project specifically on adversarial examples and I have a strong opinion on this. I personally think worrying about adversarial examples in real life production systems is like worrying about getting the vanilla linux kernel to perform RT critical tasks. It is fundamentally not a burden you should put on that one component alone and is a problem you can only solve with a system approach. And if you do that, it is for all practical purposes already solved: apply multiple, random perturbations to the input, project your perturbed version onto a known,safe image…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1802.06806/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item></channel></rss>
