Low-Maintenance, No-Login Comments for Whisk(e)y Advent

A deep dive into replacing Hypothesis for the 2026 calendar. Your constraints: no account/login for commenters, low maintenance, and self-hostable on your existing DigitalOcean droplet next to the Quarto static site.

Why Hypothesis underperformed

Hypothesis is an annotation tool, not a comment box. To leave anything, a reader has to create a Hypothesis account, learn the margin-sidebar interface, and highlight text. That is a lot of friction for a once-a-day devotional audience. The systems below instead put a familiar comment box at the bottom of each page where a reader can type a name (optional) and post — no signup, no email required.

The shortlist

The three best fits for your requirements are Remark42, Isso, and Comentario. All are open-source, self-hosted, actively maintained, and support fully anonymous comments. A fourth option, Staticman, is included because it needs no running comment server at all.

System Stack / storage Anonymous posting Maintenance Best for
Remark42 (recommended) Single Go binary / Docker image; embedded file DB (no external database) Yes — set AUTH_ANON=true Very low: one container, one volume, reverse-proxied by nginx A privacy-first box that “just runs” beside your site
Isso Python + SQLite Yes — name optional, by default Low: tiny footprint, one process The simplest classic Disqus-style box
Comentario Go + PostgreSQL Yes (configurable per domain) Medium: needs a Postgres database A moderation dashboard with roles/blocking
Staticman Comments become Git commits/PRs in your repo; no comment server runtime Yes — readers fill a form, never log in Low-to-medium setup, then near-zero Keeping comments in version control with the site

Avoid for your case: Giscus and Utterances (both require a GitHub login, which fails your no-account rule), Cusdis (lightweight and pleasant but effectively unmaintained/broken as of 2025), and Disqus (third-party, ad-supported, tracks readers).

Recommendation: Remark42

It matches every constraint with the least ongoing work. It ships as a single Docker image written in Go, stores everything in one embedded data file (no separate database to babysit), is explicitly privacy-focused, and has a first-class anonymous mode. You run one small container on the droplet, point nginx at it, and add a few lines to Quarto.

Trade-off to plan for: anonymous commenting means no built-in identity wall against spam, so turn on moderation. Remark42 gives you an admin view, email notification of new comments, and the ability to pre-moderate or remove posts. For a low-traffic seasonal site this is a minute or two a day at most. (If spam ever becomes a problem, Remark42 also supports an “email-only” mode — readers enter just an email, still no account — which cuts drive-by spam dramatically while staying near-frictionless.)

How it runs on your droplet

A minimal docker-compose.yml needs: REMARK_URL (the public URL of the comment service, e.g. https://comments.yoursite.com), a SITE id, a long random SECRET, AUTH_ANON=true, and a persistent volume for /srv/var. Put it behind nginx as a reverse proxy with SSL (Let’s Encrypt), forwarding to the container’s port 8080 with the usual X-Real-IP / X-Forwarded-For headers. The Remark42 docs include a ready nginx manual and a sample compose file.

How it plugs into Quarto

Quarto only natively supports Hypothesis, Utterances, and Giscus, so for Remark42 you inject a small HTML partial with include-after-body. Create comments.html:

<div id="remark42"></div>
<script>
  var remark_config = {
    host: "https://comments.yoursite.com",  // your REMARK_URL
    site_id: "advent",
    components: ["embed"]
  };
  (function(c){for(var i=0;i<c.length;i++){var d=document,s=d.createElement('script');
    s.src=remark_config.host+'/web/'+c[i]+'.js';s.defer=true;
    (d.head||d.body).appendChild(s);}})(remark_config.components);
</script>

Then enable it for the calendar pages in _quarto.yml (or per-page in the front matter):

format:
  html:
    include-after-body: comments.html

Because each day file already has a unique URL, Remark42 automatically scopes the thread to that page — no per-post configuration needed. You can drop the comments: hypothesis: true block from the 2026 files entirely (already removed in the new templates).

If you’d rather keep it even simpler: Isso

Isso is the lightest classic option — Python with a SQLite file, anonymous by default (a reader can type a name or stay blank), and basic per-IP rate limiting baked in. It’s an excellent fit if you want the absolute minimum to maintain and don’t need Remark42’s richer admin tooling. Integration is the same pattern: run the Isso server on the droplet and add its <script data-isso=...> embed via include-after-body.

If you want comments in version control: Staticman

Staticman is the interesting outlier: there is no comment database or running comment app to keep alive. A reader submits a normal HTML form, and Staticman turns each comment into a commit (or pull request for moderation) in your site’s Git repo, which then rebuilds the static site. Readers never log in. The catch is that the old public Staticman instance is gone, so you’d self-host the small Staticman bot and wire up the form and rebuild — more upfront setup, but afterward it’s about as low-maintenance as it gets, and your comments live alongside your .qmd files.

Suggested decision

Start with Remark42 in anonymous + moderation mode on the droplet, behind nginx, wired into Quarto via include-after-body. It’s the best balance of zero-login friction, low maintenance, privacy, and active upstream support. Keep Isso as the fallback if you want something even smaller, and consider Staticman only if keeping comments in Git appeals to you.

Sources