Found a really odd #indiekit bug, the indiekit-endpoint-posts, which manages posts in the backend via micropub can only edit posts up to 40 posts back in time, so i forked it and fixed it: now it queries the database directly by MongoDB _id, which is efficient and works regardless of how many posts exist.
I made customization to many #indiekit parts, they are all available here : https://www.npmjs.com/~rmdes
Added a Search feature to my #indiekit / #Eleventy powered blog/site https://rmendes.net/search/ itself powered by pagefind, works really well !
I think I never subscribed to as many RSS feeds from small blogs as I did recently since I got myself my own #microsub reader integrated into my blog engine powered by #indiekit
it’s just very comfortable to use, you read the blog post and you can reply, like or repost right from the integrated Reader view (inspired by Monocle)
it makes me read more and subscribe to more people’s blogs, which from my weekend exploration is a huge world to explore… there are so many interesting people writin...
There's some discourse about whether RSS(*) readers should be designed like email inboxes or not. There's a number of good points being made, and one of them is that it is a choice to make "unread" a state within the user interface, and this choice ought to be questioned.
On the other hand, I have a few contrary thoughts.
1. The layout of desktop mail clients used to be far better, when there was a full-width table of messages on top and a full-width message view below. No current RSS readers that I know of are laid out in the old fashioned way, so I think the question should be rephrased as "Do we want our newsreaders to be designed like crappy modern mail clients?" For me the answer is "No", but this doesn't have anything to do with the differences between email and news. NetNewsWire Lite from ~2006 was, in my opinion, a more usable app than the current one.
2. One of the reasons suggested for why newsreaders should not behave like email inboxes is that news reading is consumptive, and replies are not part of the model. That's currently true, but I actually believe we should move toward RSS Reader+Writer apps, where you *do* reply (directly onto your own blog) from the news reader. In that case, the email client model is actually a good place to start, and what is needed is to think carefully about the aspects of email that are stressful and the aspects that are empowering.
I'm all in favour of getting rid of "unread", or coming up with a new kind of state model that prevents one's news from feeling like a todo list. But I believe the future is bidirectional RSS, and email is a good start.
(*) By "RSS" I mean both RSS and Atom and JSON Feed, etc. Any kind of standards-based syndication.
@jonmsterling Feels like all of this already exist and is being put in practice, this is my #microsub endpoint reader which basically is able to consume any type of feeds (rss, atom, jsonfeed) and then I can directly read or like/repost/comment on it from my blog backend, powered by #indiekit
2 media
Yes I have used Claude to orchestrate the development of #indiekit from @paulrobertlloyd
I have made a few plugins and then the entire development of a #microsub endpoint for indiekit (6K line of code) based on the excellent #ekster wiki and inspired by https://github.com/pstuifzand/ekster
Deploy Your Own #IndieWeb Site on #Cloudron with #Indiekit
https://rmendes.net/articles/2026/01/24/deploy-your-own-indieweb-site
Très content de mon nouveau site / CV / blog
https://rmendes.net/
j’ai créé un plugin pour #indiekit qui rapatrie mes données GitHub sur mon blog et dans la foulée un plugin #funkwhale pour afficher mes “listening” sur mon blog !
Bhe je suis content, j’ai récupéré tous mes posts sur mon blog depuis le début des années 2000 et j’ai complètement changé de système, j’utilise désormais #indiekit pour le backend #Eleventy pour le frontend
ma “base de données” c’est des fichiers de textes, c’est plus sécurisé et j’ai contrôle total sur le code et l’aspect et expérience utilisateur, sans être coincé par les limites ou la manière de faire de WordPress ou Microblog ou Ghost (la liste est longue)