**Commit sur main** · c1fb5cf · @paulrobertlloyd * * * docs: update IndieAuth specification support * * * Ouvrir sur GitHub →

Publish to your own website with Micropub and IndieAuth. No accounts, no server, no analytics.

Publish to your own website with Micropub and IndieAuth. No accounts, no server, no analytics.

I’m happy to share that the official public beta of OutPost for Mac is available. You can download the latest from: https://jimmitchell.dev/outpost ## What does OutPost do? OutPost is an Indieauth compliant Micropub editor for Mac (iOS/iPad coming soon) that will let you publish new and edit existing posts on your Micropub enabled blog. ## What platforms does OutPost work with? These platforms have been confirmed to work with OutPost to some degree. The mission, adventurous user, is for you to help me know what other platforms it works with and to what extent. If you know your website is Micropub enabled, give OutPost a try. **Platforms:** * Clodd CMS - the proprietary blog platform this site runs on, compatible with both Indieauth & Micropub. * Micro.blog - full compatibility with Indieauth & Micropub. * Pika.page - verified compatibility with Micropub. Some Pika editor features may not be completely compatible. Heavy testing from friends is needed here. * **Other editors?** You tell me if it works with your platform by emailing me at outpost@jimmitchell.dev. I’ll add it to the list. ## What version of macOS will OutPost work with? OutPost should work with macOS 15 (Sequoia) or later on both Intel and Apple Silicon. Let me know if it doesn’t. ## How do I report bugs? Send an email to outpost@jimmitchell.dev explaining the issue you encountered with as much detail as possible. Attach screenshots too. Lots of screenshots. A picture is literally worth a 1,000 when debugging software. ## Where’s the documentation? LOL. Silly user… There is no documentation; not yet anyway. I’d like to see if users find using the app intuitive to start with. If you get stuck, questions will be answered through outpost@jimmitchell.dev of course. ## Is OutPost free? It sure is, but I will gladly accept donations if you find it useful or simply want to support my Indieweb passion project. You can buy me a coffee to show some love. Remember; coffee fuels development. ## What else? **Big scary warning:** This is a public beta. There are inherent risks that come with trying software like this and bugs might exist. I’ve done my best to be sure they don’t, and the app works great on my devices. By downloading and using OutPost, you guarantee not to hold me accountable for any data loss whatsoever. Sorry, I have to say that. If this scares you, wait a while. Finally, keep in mind I’m a guy who has a _really_ demanding day job. Replies to email might take a day or two – maybe even three or more. Simple questions can be directed to me on Mastodon: @jimmitchell@indieweb.social. I usually reply pretty quickly there. Thanks for giving OutPost a go! Let me know what you think. _**Note:** This post was written with OutPost…_ 😎

In reply to: Re: MIndie-Agent: An IndieAuth Bot This is an interesting approach (and unattended IndieAuth has been desirable for quite some time, particularly for things like private posting appearing in feeds and authenticated Webmention and so on) but it will be really annoying if this is what ends up catching on instead of Ticket Auth, which was meant to solve this very problem much more simply but never got any real adoption.

**Discussion · Ideas** · Discussion #968 Micropub Spec Testing · @aciccarello * * * The Indieauth testing (#967) has gotten me thinking about other specs. It would be good to do some testing against the micropub spec. https://micropub.rocks/implementation-reports/servers/ Note, this suite is a bit older and has a list of almost 40 open issues so there may be a few inaccurate tests. * * * Ouvrir sur GitHub →

**Reponse de discussion** · Discussion #967 IndieAuth Spec Testing · @aciccarello * * * I ran the tests against my IndieKit instance. * 45 passed * 9 failed * 12 warnings * 15 skipped (1 manually skipped) https://dev.indieauth.rocks/implementations/1 * * * Ouvrir sur GitHub →

**Discussion · Ideas** · Discussion #967 IndieAuth Spec Testing · @aciccarello * * * @aaronpk has put up a dev version of the indieauth.rocks website that includes a tool for testing spec compliance. I know some work has been done recently (e.g. #938, #883, #890) and some is still to do (e.g. #535, #911) It’d be great to check indiekit’s compliace level, give Aaron some feedback on the testing tool, and eventually get indiekit listed on the indieauth.rocks website (when live). https://dev.indieauth.rocks/server-tests * * * Ouvrir sur GitHub →

**Commentaire de pull request** · PR #966 docs: add profile support to IndieAuth · @paulrobertlloyd * * * Ah yes, I should break this out into `profile` and `email`, and leave `email` unchecked for now. * * * Ouvrir sur GitHub →

**Revue de pull request (APPROVED)** · PR #966 docs: add profile support to IndieAuth · @rmdes * * * _(aucun texte)_ * * * Ouvrir sur GitHub →

**Revue de pull request (APPROVED)** · PR #966 docs: add profile support to IndieAuth · @rmdes * * * Both are right. Profile information comes back on the token and profile-URL responses when the profile scope is granted, and /userinfo is mounted and advertised in the metadata. Still unsupported and correctly unticked: email, refresh tokens, token revocation. * * * Ouvrir sur GitHub →

**Pull request (OPEN)** · PR #966 docs: add profile support to IndieAuth · @paulrobertlloyd * * * I believe #938 means we can tick off a few more supported features for IndieAuth, right @rmdes? * * * Ouvrir sur GitHub →

Every time I check in somewhere on Swarm, a post appears on my blog automatically. Micropub helps make this happen. Micropub is an open standard for posting to your own site from third-party clients. Instead of logging into WordPress, you authenticate once via IndieAuth and then use any Micropub-capable app to publish notes, articles, checkins, and more — directly to your site. OwnYourSwarm is a service that takes your Swarm (Foursquare) checkins and posts them to your site via Micropub. Your checkins live on your own site, with a static map image, and optionally syndicate out to Mastodon or Bluesky. ## Micropub on WordPress The **Micropub** plugin by the IndieWeb community adds a Micropub endpoint to WordPress. Install it and your site immediately advertises the endpoint via `rel="micropub"` in the page head. Authentication goes through **IndieAuth** , which is handled by a separate plugin. IndieAuth lets you use your own domain as your identity — apps redirect to your site’s authorization endpoint, you log in with your WordPress credentials, and the app receives a token it uses for future requests. ## OwnYourSwarm setup 1. Visit ownyourswarm.p3k.io 2. Connect your Foursquare/Swarm account 3. Sign in with your site URL via IndieAuth 4. OwnYourSwarm is now authorised to post to your site From this point, every Swarm checkin triggers a Micropub POST to your WordPress site. The post includes the venue name, location coordinates, and a Swarm checkin URL. ## Shaping the checkin post The raw Micropub payload from OwnYourSwarm needs some processing before it makes a readable WordPress post. I handle this with a WordPress mu-plugin using the `pre_insert_micropub_post` filter. The filter sets the post format to `status`, generates post content from the checkin data (venue name, any note you added in Swarm), and sets a short excerpt for card previews. Checkin cards on the archive: map thumbnail, venue name, location, and a Read More link. ## The static map Simple Location is a plugin that handles geo data on WordPress posts. When OwnYourSwarm sends coordinates, Simple Location picks them up and can display a map on the post. I use a static map image in the card excerpt area on archive pages — a small 16:9 thumbnail showing the location. This comes from Simple Location’s map provider integration. Mapbox works well and has a free tier sufficient for a personal site. On single post pages, Simple Location renders a full map and the location text (“Manchester, Greater Manchester”). The map loads at priority 11 in `the_content` filter — something to know if you’re wrapping content in `e-content` for microformats (that wrapper needs to go at a lower priority, after the map). ## Per-checkin syndication When posting via Micropub, syndication targets are available as checkboxes in supporting clients. Quill queries `q=syndicate-to` from your Micropub endpoint and shows your configured Mastodon and Bluesky targets. You tick which ones you want per post. OwnYourSwarm doesn’t expose a syndication target picker — it just posts. If you want checkins to syndicate automatically, configure that in Syndication Links’ global settings. If you want per-checkin control, post manually via Quill instead. Check in somewhere on Swarm. A post appears on your site within minutes, with venue name, your note, a location tag, and a static map thumbnail. From there it can syndicate to Mastodon or Bluesky if you want. Likes and replies from those platforms come back as webmentions. My checkin history lives on my own site. If Facebook shuts down Swarm, I still have my own copy.

Juhis tells us that there is no membership card for the Indieweb blogging community. I like his thesis as I sort of feel like I'm at least on the periphery of the Indieweb movement. But I also feel like I'm on the outside, being judged for not being "indie" enough. But to understand my thinking on the matter you first have to have an understanding of what the Indieweb is.

IndieAuth is an identity layer on top of OAuth 2.0 [RFC6749], primarily used to obtain an OAuth 2.0 Bearer Token [RFC6750] for use by [Micropub] clients. End-Users and Clients are all represented by URLs. IndieAuth enables Clients to verify the identity of an End-User, as well as to obtain an access token that can be used to access resources under the control of the End-User.

✎ Note 15 August 2026 Testing Plume from Firefox, now you can see the steps indieauth take against your site for the initial connection, there is also a welcome tab for onboarding (Inspired by O...