<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Qwen-Image Technical Report · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2508.02324/</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/2508.02324/feed.xml" rel="self" type="application/rss+xml" /><item><title>Qwen-Image Technical Report — mentioned by schopra909</title><link>https://news.ycombinator.com/item?id=49986981</link><guid isPermaLink="false">urn:hackerpapers:mention:2508.02324:49986981</guid><pubDate>Wed, 07 Oct 2026 01:51:20 GMT</pubDate><description>&lt;p&gt;The approach is cool; but the results feel ~sus~. GenEval and GenEval2 prompts are very terse (~10 tokens) while these models are primarily trained on long-dense captions. So, it&amp;#x27;s pretty common to upsample prompts before running them through benchmarks. That way you&amp;#x27;re testing the model as it was trained, rather than testing it on prompts that are out of distribution. If you look at the Qwen-Image Report before they enhanced it for their 12-25 release, upsampled prompts score 0.87 on GenEval* In this paper they take it from 0.74 to 0.81. To me that reads to me that they&amp;#x27;re basically getting…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2508.02324/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Qwen-Image Technical Report — mentioned by mh-</title><link>https://news.ycombinator.com/item?id=44989645</link><guid isPermaLink="false">urn:hackerpapers:mention:2508.02324:44989645</guid><pubDate>Fri, 22 Aug 2025 20:50:08 GMT</pubDate><description>&lt;p&gt;I see where you&amp;#x27;re coming from, but if you take a look at the system prompts for these models (some are public, some have partially or fully leaked), you&amp;#x27;ll see that is no longer a concern. At least not for the kind of models being discussed here. That older generation of image diffusion models (e.g. Stable Diffusion) used text encoders like CLIP [0], which simply don&amp;#x27;t have the language understanding that even the smaller modern LLMs do. Later image models moved on to using variants of T5 [1], sometimes in addition to CLIP variants (this is how FLUX.1 works). The state of the art for open…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2508.02324/"&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>
