<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2604.24890/</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/2604.24890/feed.xml" rel="self" type="application/rss+xml" /><item><title>Verifying Provenance of Digital Media: Why the C2PA Specifications Fall Short — mentioned by lern_too_spel</title><link>https://news.ycombinator.com/item?id=49638448</link><guid isPermaLink="false">urn:hackerpapers:mention:2604.24890:49638448</guid><pubDate>Thu, 10 Sep 2026 04:35:51 GMT</pubDate><description>&lt;p&gt;Indeed, on top of Google&amp;#x27;s implementation being a bad joke, it sounds like the C2PA specifications in general are a massive fail so far. https://arxiv.org/html/2604.24890v1 On the other hand, ignoring standards altogether is the wrong way to go because the ecosystem after capture won&amp;#x27;t be there.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2604.24890/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
