<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cookies on Kliku Kliku</title><link>https://klikukliku.dev/tags/cookies/</link><description>Recent content in Cookies on Kliku Kliku</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://klikukliku.dev/tags/cookies/index.xml" rel="self" type="application/rss+xml"/><item><title>remark42 in Hugo: a cross-domain session without third-party cookies</title><link>https://klikukliku.dev/posts/hugo-comments-remark42/</link><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><guid>https://klikukliku.dev/posts/hugo-comments-remark42/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;This is another post in the series about comment systems for Hugo. In the previous one I set up the remark42 app itself on a VPS alongside the existing &lt;code&gt;caddy-docker-proxy&lt;/code&gt;: &lt;strong&gt;&lt;a href="https://klikukliku.dev/posts/remark42-self-hosted-vps/"&gt;Self-hosting remark42 alongside an existing Caddy on a VPS&lt;/a&gt;
&lt;/strong&gt;. The backend replies &amp;ldquo;pong&amp;rdquo;, the BoltDB database accepts writes. But those aren&amp;rsquo;t yet comments under posts. For them to appear on the page you need to wire in the widget: a piece of JavaScript that causes an iframe with a thread list and a form to be created.&lt;/p&gt;</description></item></channel></rss>