<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>A study of the effect of JPG compression on adversarial images · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1608.00853/</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/1608.00853/feed.xml" rel="self" type="application/rss+xml" /><item><title>A study of the effect of JPG compression on adversarial images — HN submission</title><link>https://news.ycombinator.com/item?id=14894774</link><guid isPermaLink="false">urn:hackerpapers:submission:1608.00853:14894774</guid><pubDate>Mon, 31 Jul 2017 18:42:18 GMT</pubDate><description>&lt;p&gt;A simple Jpeg defense for the attack from OpenAI authors&lt;/p&gt;&lt;p&gt;One thing I do when a new attack is published is to see if the &amp;#x27;jpeg&amp;#x27; defense works. That is, will the jpeg compressed version of the adversarial image retain its adversarial threat? Turns out the attack from OpenAI authors does not pass this jpeg defense test. Please note: 1: There have been a couple of studies of the effect of JPG compression on adversarial images. See: https://arxiv.org/pdf/1705.02900.pdf https://arxiv.org/pdf/1608.00853.pdf 2: This is NOT a &amp;#x27;Voila - Busted!&amp;#x27; dissemination. The most straightforward idea for a counter-attack is to include jpeg compression part of the…&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/1608.00853/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item></channel></rss>
