<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Deepfake on JVQ.net: Just Very Quick</title>
    <link>https://jvq.net/tags/deepfake/</link>
    <description>Recent content in Deepfake on JVQ.net: Just Very Quick</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 09 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jvq.net/tags/deepfake/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI-generated fake X-rays fool radiologists</title>
      <link>https://jvq.net/ai-generated-fake-x-rays-fool-radiologists/</link>
      <pubDate>Thu, 09 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://jvq.net/ai-generated-fake-x-rays-fool-radiologists/</guid>
      <description>&lt;p&gt;Deepfake X-rays are now convincing enough that radiologists in tests couldn&amp;rsquo;t reliably tell them apart from real ones — especially when they didn&amp;rsquo;t know fakes were in the mix.&lt;/p&gt;&#xA;&lt;p&gt;The obvious nightmare scenarios write themselves: insurance fraud, evidence fabrication, diagnostic errors from compromised image databases.&lt;/p&gt;&#xA;&lt;p&gt;The less obvious one: this probably forces a rethink of how medical images are authenticated and stored. Digital signatures for scans, chain-of-custody verification. It&amp;rsquo;s all possible, just not standard yet.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
