Latest

A few years ago, around the same that I create ek, I also created ekstereye. It is hosted at reader.p83.nl. It is a browser only Microsub client, that connects directly with a Microsub server. Everything happens in the browser and there is no server, except for the static files.

This has a big problem. The first problem is that you depend on that your servers supports CORS headers. Your indieauth server, microsub server and micropub server need to support the CORS headers, otherwise the browser will not be able to call the endpoint that is required to login, read microsub or post a like or bookmark.

What is ek reader?

The reader subcommand of ek serves ekstereye as a local web server on your localhost. You first login with ek connect <website> to your website and then run ek reader and it hosts a microsub proxy with the web reader locally on your own computer.

It is a web interface for your microsub server, where you can read and update your channels, feeds and so on. And this is all available in a small 15MB single static binary. The allows you to download 1 files from Github and then read blogs and other feeds right in your browser.

Where can I find it?

On github.

• Four levels of time handling in a database (post)
• What I run on my $10 USD OpenStick homelab | Bosscher (post)
• brennan.day/the-indieweb-now-has-genai-and-claude-built-in-w… (post)
• magequery (post)
• Pray for Chaos (post)

Likes

• Liked aaronparecki.com/2026/10/17/5/rebuilding-my-indieweb-project…
• Liked indiebookclub.biz/updates#post-2026-11-06

Read

• Reading Iron John by Robert Bly (post)

Today I let Hermes write the whole thing in Go and imported the old posts. I added micropub, Indieauth and webmentions. Then I asked Hermes to also write an Android app. In an afternoon I have a state of the art Indieweb website and publishing workflow.

My content already were just files, I could just import the old posts and webmentions. The links are still the same, even though new permalinks will use year/month/slug instead of just the id's.

I'm very happy to see that I can just replace my website in an afternoon with a more secure and fast version. This will also allow me to shrink my hosting bill a little.

• microformats from websites
• Feeds (implemented) RSS, JSON feed, XML
• Micropub posting (implemented) so other services can post messages Example: Pipedream receives email and posts as item
• API's for specific websites
• Saved search

Processing and filtering:

• Exclude posts with regex (implemented)
• Exclude posts based on post-type-discovery (implemented)
• Improve post content
• Advanced processing with user-defined flows (like Huginn?)

Specific outputs:

• Global and channel search (implemented)
• Standard feed reader (implemented)
• Share to your own website (micropub likes, bookmarks, and replies)
• Share to other services (Instapaper)
• Notifications

What else?