I'm making some progress on my micropub endpoint based on the https://go.hacdias.com/indielib library.

I can now use my endpoint for IndieAuth, and store posts on the filesystem, in the custom TOML page format I use. I'm having some trouble with the `micropub?q=config` route, and haven't started working on git sync or the media endpoint yet. One step at a time.

The main issue that's holding me back now, is that it's really hard to test if everything works as intended. I've been testing using Quill and Sparkles via my server now, but it's less than ideal to not be able to test it locally. Any advice would be appreciated 😅

Also, https://micropub.rocks doesn't work for me at all, because it doesn't use PCKE apparently.

But the clients are way easier than how I was updating my site until now, so I have enough motivation to keep at it!

#micropub #IndieAuth #indieweb

This also made me realise I want to give implementing #micropub and #indieauth for my website another go. It isn't the easiest of protocols, last time I gave up. But I'd love to remove some friction of posting to my site (esp. images). Too bad there isn't a ready made Go project of these protocols, that builds a static site and syncs with Git. I'll try rolling my own again using https://pkg.go.dev/go.hacdias.com/indielib by @hacdias and see if I have better luck this time.
indielib module - go.hacdias.com/indielib - Go Packages

@aaronpk
When will Mastodon be a supported authentication provider for the #IndieAuth / #IndieWeb ?
and so does #indieauth
done
my comment-api service (oh crap its a very basic axum server proxied as a #tailscale warp service seems alive and healthy to serve for #indieauth comments for hakyll static pages
hastodon lib hackage just won't work I needed to write a new #haskell lib just for this
/ bookmarked for when I am back to my regular day

Fixed: IndieAuth login broken for third-party apps

After adding security headers (Content-Security-Policy) to harden the site, logging in with IndiePass and other IndieAuth clients silently failed — tapping “authorize” did nothing.

The culprit was form-action ‘self’ in the CSP, which blocked Browsers from following the consent form’s redirect to the client’s callback URL (e.g., indiepass.app/android-callback).

Changed to form-action ‘self’ https: to allow IndieAuth redirects to any HTTPS callback. Affects all third-party IndieAuth clients (Micropub editors, Microsub readers, etc.), not just IndiePass.

🔗 https://rmendes.net/notes/2026/02/22/a202f

Stumbled over #IndieAuth again and am once again reminded that I (badly?) chose all my domain names that I like them, but not have them as my "handle" on any platform. I don't want to be @f5n.org - so this is something of a problem for adopting that pattern.
Building an IndieAuth Comment System for Your Static Site

A journey through authentication, CORS issues, and the joy of owning your comments! Learn how to build a comment system for your static site using IndieAuth and Netlify Functions, storing the comments in your git repository.

brennan.day

Finished my December Adventure with an unfinished project, as is tradition. I'm in the process of extracting a standalone IndieAuth client atop the OAuth2 crate. Full adventure log:

https://rossabaker.com/series/december-adventure-2025/

#DecemberAdventure #IndieAuth #Rust

Ross A. Baker: December Adventure, 2025

My December Adventure detoured into an implementation of IndieAuth. I need an authenticated section to process the pending Webmentions before they're made visible to the public. Instead of maintaining my own credentials, I wanted to stay in the IndieWeb spirit and authenticate against my own website and its rel=me links. Success!

- more on IndieAuth: https://indieauth.net/
- ongoing adventure log: https://rossabaker.com/series/december-adventure-2025/

#IndieAuth #Webmentions #IndieWeb #DecemberAdventure

IndieAuth