<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hyvor-Talk on CSP Guide</title>
    <link>https://csp-guide.com/tags/hyvor-talk/</link>
    <description>Recent content in Hyvor-Talk on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/hyvor-talk/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Hyvor Talk Comments: A Real Before/After Fix</title>
      <link>https://csp-guide.com/posts/csp-for-hyvor-talk-comments/</link>
      <pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-hyvor-talk-comments/</guid>
      
      <description>&lt;p&gt;I’ve seen this pattern a lot: a site has a reasonably tight Content Security Policy, then someone adds a third-party comments widget, and suddenly the console turns into a wall of CSP violations.&lt;/p&gt;
&lt;p&gt;That’s exactly what happens with Hyvor Talk if you drop in the embed code and hope your existing policy will “just work”.&lt;/p&gt;
&lt;p&gt;For a developer site like &lt;code&gt;csp-guide&lt;/code&gt;, this is extra awkward. You want comments, but you also can’t publish a sloppy &lt;code&gt;script-src *&lt;/code&gt; policy and call it a day.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
