in #newsletter #indieweb (also on IndieNews)
This is the first post I've seen on the IndieWeb that has multiple in-reply-to links. I guess that makes sense. Nice!
Yesterday I watched Peter Van Hardenberg - Local First: the secret master plan. I've come across Peter and Ink & Switch before. It caught my interest then, and it caught my interest now again.
This time I saw similarities between the local first concept and IndieWeb.
One of the requirements for local first (particularly in the context of collaboration) is the ability to diff different versions of a document and sync changes between different people. In the programming world, we have had this luxury for a long time with version control systems. But they want to enable that for all types of documents. This sounds so cool.
I found the URL design page particularly interesting.
I have given URL design some thought. I should maybe write up the thinking behind the current design.
However, I've sometimes gotten frustrated because I felt that I couldn't reach a perfect design. And perhaps there is no right and wrong. Only trade-offs as in other types of design.
I want to implement URL rewriting so that I can fix bad URL design with HTTP redirects so that old links can keep working while still promoting the newer better design.
I'm curious about how private posts could look like on the open web.
I see a need to share certain posts only with certain people and not have everything on my blog public. Today I have to share that in another way. And I'm not sure they can all co-exist on my blog and what that would look like.
This was such a nice read. I especially resonated with "posting versus publishing" and that a blog can be an "archive and long memory".
I've now implemented a way to download mentions from Webmention.io and display them on my blog posts.
My blog is a static site. So the way it works is that I download mentions via the Webmention.io API. Then I extract only the information that I need to display the mentions on my blog. I save that information in json files that I can read when the website is generated. Right now, they look like this:
$ cat posts/2023/04/06/what-should-a-ci-server-do/mentions.json | jq
{
"https://blog.rickardlindberg.me/2026/01/24/how-does-ci-work-in-projects2.html": {
"wm-property": "mention-of",
"wm-received": "2026-02-04T19:41:15Z"
}
}
Here is how I test microformats markup on my website.
First I install mf2py:
sudo dnf install python3-mf2py
Then I define this one-liner Bash function:
mf2test() { python -c 'import sys; import mf2py; import json; print(json.dumps(mf2py.parse(url=sys.argv[1])))' $1 | jq; }
And then I can test a website like this:
$ mf2test https://blog.rickardlindberg.me/2026/02/05/075110.html
{
"items": [
{
"type": [
"h-entry"
...
What is Rickard working on and thinking about right now?
Every month I write a newsletter about just that. You will get updates about my current projects and thoughts about programming, and also get a chance to hit reply and interact with me. Subscribe to it below.