Simple, honest tools for the small web.

This is where I share short updates and notes as I build Pure Commons. Every post is syndicated to Mastodon, and there's an RSS feed if that's more your thing.

For the past 6 weeks or so, I've been doing a major re-factor of Pure Blog to clean some stuff up. I'm ready to release it, but it will be a breaking update, as it includes changes to the update process.

So people won't be able to update from within #PureBlog, but I'm not sure how to manage this? Should I just communicate this everywhere and hope people see it? Or should I mark the next release as pre-release in GitHub so the in-app updater doesn't work?

I'm open to any other ideas to..

There's been some back and forth on creating a #PureBlog Blogroll recently after a couple of very cool people from the community decided to make unofficial ones.

Anyway, there's now an official Pure Blog Roll, so if you're running Pure Blog, get your site added!

https://roll.pureblog.org

Translations for #PureComments are done, but I've only included English and (AI generated) German. Please feel free to submit PRs with other languages.

⚠️ Make sure you read the changelog on this one too, as there's a breaking change in the update process.

https://purecomments.org/changelog