subscribers and rss

Visitors can subscribe to your changelog two ways: email or rss.

rss

Every board with a published changelog exposes a feed at:

https://<your-domain>/b/<board-slug>/changelog/rss.xml

It includes the most recent published entries with title, body, version, and pubDate. Standard rss 2.0; works with every reader.

email subscriptions, the flow

Spirby uses double opt-in so you do not end up in spam folders.

1. Visitor enters their email on the changelog page and submits.
2. Spirby creates a pending subscriber row and emails a confirm link.
3. Subscriber clicks the link → row flips to confirmed. Confirm tokens are valid for 7 days.
4. From now on, every published entry triggers an email to that subscriber.

Subscribe is rate-limited:

• per ip: 5 / hour
• per email hash: 3 / hour

These are tighter than post and vote limits because subscribe is a one-shot from a public page; nothing legitimate fires it more than a couple of times.

unsubscribe

Every email includes a one-click unsubscribe link. Clicking it flips the subscriber to unsubscribed without asking for a sign-in or a confirmation page, that is rfc 8058 (one-click unsubscribe), and it is what mailbox providers expect from every legitimate sender.

Re-subscribing is fine: enter the same email and confirm again.

what subscribers receive

Only published entries trigger emails. Drafts and unpublishes do not. If you publish, unpublish, and re-publish, the broadcast goes out once on the first publish and again on the re-publish, there is no idempotency guard for human-driven publish/unpublish loops.