It is that time of year when my @blog expires, so I'm taking the opportunity to give the site's style/CSS a quick makeover.

Do you like my new subscribe form, would you change something?

#fediverse #css #blog #staticsites #mastodon

There have been many experiments with adding simple ActivityPub support to static blogs, enabling authors to publish their blog into the fediverse to be followed and get commented on. Some of these experimenters have documented what they did, and I've started a list of examples here;

https://codeberg.org/fediverse/fediparty/wiki/Fediverse-comments-on-static-blogs

I chucked this together in a hurry, so please prod me about any mistakes, or any additions that could be made to the list.

#FediDevs #ActivityPub #blogs #StaticSites #FediverseParty

Fediverse comments on static blogs

:milky_way: A quick look into Fediverse networks -

Codeberg.org

A Guide to Implementing ActivityPub in a Static Site (or Any Website) - Part 9: Quote Posts

Summary:

Find the index and earlier parts of this series here.

Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation

Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.

In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse

Find the index and earlier parts of this series here.

Quote Posts for Static Sites: A Practical Guide to FEP-044f Implementation

Transform your static blog into a consent-respecting quote-enabled node in the fediverse. This guide shows you how to implement quote post support that works with Mastodon, GoToSocial, and other ActivityPub servers while respecting author preferences.

In this guide: You’ll learn to build quote-enabled blog posts that can be responsibly shared across the fediverse

Why Quote Posts Matter (And Why They’re Controversial)

The User Experience Problem

Picture this: Someone finds your blog post fascinating and wants to share it with their followers, but they also want to add their own perspective or why is important. Without quote posts, they have two unsatisfying options:

  • Simple share: Just boost with no commentary (or reply)
  • Link sharing: Add a link to the blog post in their note
  • Neither option creates the rich, attributed conversations that make social media engaging.

    The Solution: Consent-First Quote Implementation

    We’re implementing FEP-044f: Consent-respecting quote posts in our federated blog.

    What this means for your readers:

    • They can quote your posts with confidence that you’ve opted in
    • Their quotes include proper attribution and linking

    What this means for you:

    • Automatic handling of quote requests
    • Future-ready for advanced moderation features (like in the fuuutuuure)

    Implementation Overview

    We are going to:

  • Modify the Notes JSON to assert that the notes are quotable.
  • Modify our Index function (the only dynamic POST endpoint) to handle quote requests and send the appropriate approval back (blanket approval).
  • 1. Modifying the Notes: Enhanced ActivityPub Context

    What We Changed: Extended the @context from a simple string to a rich object array supporting the GoToSocial namespace.

    Before:

    "@context": "https://www.w3.org/ns/activitystreams"

    After:

    "@context": [ "https://www.w3.org/ns/activitystreams", { "gts": "https://gotosocial.org/ns#", "interactionPolicy": {"@id": "gts:interactionPolicy", "@type": "@id"}, "canQuote": {"@id": "gts:canQuote", "@type": "@id"}, "automaticApproval": {"@id": "gts:automaticApproval", "@type": "@id"} } ]

    We are also adding this section at the end of the Note:

    "interactionPolicy": { "canQuote": { "automaticApproval": "https://www.w3.org/ns/activitystreams#Public" } }

    If you want to be specific about who can quote your post, this is where you do it, read more in here.

    You can see an example of the implementation in RssUtils.cs - in the GetNote method.

    2: Quote Request Processing

    Now we need to add the quote request handling system that processes incoming quote requests and automatically approves them based on our interaction policy.

    New Components:

    • QuoteRequestService: Processes incoming quote requests from the fediverse
    • Auto-Approval Logic: Automatically approves public quote requests as defined in our interaction policy
    • Quote Authorization: Issues authorization tokens (stamps) for approved quotes

    The Quote Request Flow:

    sequenceDiagram participant Requester as Fediverse User participant Inbox as Our Inbox participant QRS as QuoteRequestService participant Target as Target Instance Requester->>Inbox: QuoteRequest for our post Inbox->>QRS: Process quote request QRS->>QRS: Check interaction policy QRS->>QRS: Generate authorization stamp QRS->>Target: Send Accept + Authorization Target->>Requester: Quote approved

    Checkout the implementation in the QuoteRequestService.cs.

    Key Takeaways

    By implementing FEP-044f, we’re not just adding quote functionality - we’re building consent-respecting social interactions into the protocol level.

    Why This Matters:

    This implementation shows how static sites can participate in modern social web standards while keeping their simplicity and performance benefits. Right now, we’re automatically allowing all public quotes, but this foundation sets us up for more granular consent controls in the future - like requiring approval for specific users or implementing follower-only quoting.

    The consent-respecting approach means our content can be shared thoughtfully across the fediverse, with the infrastructure already in place to handle more sophisticated permission systems as they evolve.

    Next Steps: The Quote Visualization Challenge

    Now that we’ve successfully implemented the backend infrastructure for consent-respecting quote posts, we face an equally important question: How should we display these quotes on our website?

    Treat quoted posts as special reply types? Quotes have different semantic meaning than replies - they’re more like “shared with commentary” So maybe create a separate “Quoted By” section similar to how we handle likes and shares?

    Any ideas?

    Also readable in: https://maho.dev/2026/02/a-guide-to-implementing-activitypub-in-a-static-site-or-any-website-part-9-quote-posts/ by @mapache:

    #fediverse #activitypub #static-sites #hugo #azure #mastodon #web-development #social-web #webfinger #http #quote-posts #fep-044f

    A guide to implement ActivityPub in a static site (or any website)

    Hi! I have created this index for easy navigation. In Part 1, we will discuss why it is important to bring your site to the Fediverse. In Part 2, we will delve into an overview of the design of my implementation. In Part 3, we will make your blog discovereable in the fediverse. In Part 4, we will generate our notes and outbox, which contains posts ready to be shared in the Fediverse. Part 5, is an interlude to implement a subscribing to your site feature with fediverse accounts.

    Spent last week debugging Hugo issues in our R-Ladies website - I wanted to add one page per Chapter. However, we have chapter data as Hugo site data, which doesn't render into pages, I needed to setup a content adapter, which I had never done before. Here's how I used Claude to solve it 🧵

    #Hugo #WebDev #Debugging #AI #StaticSites #RLadies

    #Development #Trends
    2025 JavaScript Rising Stars · Top starred GitHub projects in the past year https://ilo.im/169lph

    _____
    #JavaScript #Frameworks #Libraries #StaticSites #CssInJS #Tooling #AI #WebDev #Frontend #Backend

    2025 JavaScript Rising Stars

    A complete overview of the JavaScript landscape in 2025: trends about frontend, fullstack and Node.js frameworks, React and Vue.js ecosystems, build tools, state management...

    No new posts on my blog since 2026 began... because I've been adding new features on my Hugo site instead!

    I have 5 new pages:
    - All (aka Firehose feed)
    - Sitemap
    - Stats
    and 2 IndieWeb pages:
    - Notes (aka microblogs)
    - Photos

    A page I really enjoyed making was the Statistics page. I added a new line graph from #ECharts and used Hugo inbuilt calculations.

    ➡️ https://burgeonlab.com/stats

    #BurgeonLab #blogs #blogger #hugo #staticsites #indieweb #microformat #apache #ApacheECharts #webdev

    If all goes according to plan, you can now #comment on my blog posts via the #fediverse!

    https://blog.k3can.us/posts/2025/dec/commenting/

    #hugo #staticsites #staticblog #blog

    Like, Comment and Subscribe - k3can blog

    I'm finally getting around to trying out statichost.eu. Probably shouldn't be beginning with a custom Docker image, because all I'm discovering so far is my failure to configure said image correctly.

    #staticSites

    New blog post: Blog Updates and Dirty Tricks

    In this post you’ll find some recent blog updates (boring), dirty tricks to achieve them (interesting), and unreasonable amounts of praise to Zola (deserved). It might be useful if you’re hosting a blog too.

    https://urmaul.com/blog/blog-updates-and-dirty-tricks/

    #Blogging #StaticSites #Zola

    Blog Updates and Dirty Tricks — urmaul.com

    🚀 Bovine Pages Server v0.1.1 is here!

    New features for self-hosted static sites:

    🔒 DNS TXT Verification - Prevent domain hijacking with cryptographic proof of ownership

    🔀 Custom Domain Redirects - URL redirect system with .redirects file support, automatic Traefik middleware creation

    Self-host your static sites with Forgejo/Gitea - no vendor lock-in, full control, automatic HTTPS via Traefik.

    🔗 https://code.squarecows.com/SquareCows/pages-server

    #OpenSource #SelfHosted #StaticSites #Forgejo #Gitea #Traefik #WebDev

    pages-server

    A Pages server for forgejo (and possibly gitea) that integrates with Traefik for custom domains and SSL.

    code.squarecows.com: Powering business with open source!