<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Disqus on CSP Guide</title>
    <link>https://csp-guide.com/tags/disqus/</link>
    <description>Recent content in Disqus on CSP Guide</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 16 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://csp-guide.com/tags/disqus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CSP for Disqus Comments: Pros, Cons, and Policy Patterns</title>
      <link>https://csp-guide.com/posts/csp-for-disqus-comments/</link>
      <pubDate>Sun, 16 Aug 2026 00:00:00 +0000</pubDate>
      
      <guid>https://csp-guide.com/posts/csp-for-disqus-comments/</guid>
      
      <description>&lt;p&gt;Disqus is one of those integrations that looks trivial right up until you try to keep a strict Content Security Policy.&lt;/p&gt;
&lt;p&gt;Drop in the default embed snippet and your clean CSP usually turns into a pile of allowances for third-party scripts, frames, images, XHR, and inline behavior you didn’t ask for. I’ve had this exact fight before: comments are useful, but they come with a bigger trust boundary than most teams expect.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
