Blog
All posts including articles and notes. (2576 total)
-
I now display AI usage (or not) on every post I create on my blog.
I forked
indiekit-endpoint-postsand added metadata properties that I can fill when creating a post. These properties generate their own Frontmatter and display:- An AI badge visible even before clicking into the full post view
- An AI Usage box below the post specifying whether the text or the code was produced with AI assistance or not
This is aligned with my AI transparency page.
Current AI Usage Breakdown
Level Label Posts % 0 None (human-written) 1,992 99.3% 1 Editorial assistance 11 0.5% 2 Co-drafted 2 0.1% 3 AI-generated 0 0.0% — Unset 0 0.0%
99.3% human-written. 13 posts used AI at some level (editorial assistance or co-drafted), and zero were fully AI-generated.
-
https://status.claude.com/incidents/s0pmy4yywshvPermalink
API Error 500, its Friday for half the planet already !
-
Released v2.4.0 of my ActivityPub plugin — unified the reader and explore processing pipelines into a single shared path. Posts now go through the same enrichment (avatars, media, quotes, hashtags) regardless of whether they come from your home timeline or the explore feed. Also fixed a race condition on the muted users index that could cause startup errors.
-
Just shipped two new features for my GitHub page: a searchable starred repos browser that syncs all 5k+ stars via GraphQL and caches them in MongoDB, with filtering by language, topic, and full-text search — and GitHub Lists support with tabs, sorting, and filtering. Finally easy to find that one repo you starred months ago.
-
AI: T1/C1
So I created this code to reorganize my 5,000 GitHub starred repositories.
It took Claude Code a little over two hours to sort everything into structured categories and lists, all while respecting GitHub API rate limits.
Before that, I had a “To Sort” list with more than 600 unsorted repositories, plus dozens of manually created lists. Every time I starred a repository, I tried to place it in the most relevant list. But over time, the diversity and depth of my starred repositories outgrew the structure I had manually built. My 32 lists simply weren’t granular enough anymore.
So I decided to scrap all manually created lists and start fresh.
With Claude, I analyzed the actual data behind my starred repositories and defined a new set of list categories based on real distribution patterns instead of intuition. Once the taxonomy was defined, the automated classification process began. A bit more than two hours later, everything was sorted.
Now, when I star a new repository, I finally have a list structure that reflects the real diversity of what I collect. I can sort new stars manually from GitHub (mobile or desktop), and if needed, I can always rerun the stargazer Python script to reclassify and effectively “fact-check” existing classifications.
Since this workflow proved so effective, I decided to build a dedicated search page on my site to explore all 5,000 repositories more easily.
Here is the result:
-
This challenge was initiated by Alexandra from wrywriter.ca — thanks for putting this together! Why did you make a blog in the first place? My first blog goes back to the early 2000s — it was called “Make Love Not War” and it was a space where I was...
Read more → AI: T1 -
Testing my new Micropub MCP client — posting from the terminal via Claude Code, with automatic syndication and OG image generation.
-
Heh! this is fun !
-
Yay! my cloudron package for #funkwhale was adopted by Cloudron team, its now officially in the cloudron app store ! Unstable for now but ready for testing ! I’m going to think about how to migrate buzzworkers.com to the official funkwhale package !
-
I can now search across all my 5k Github starred repo’s from my own site :) I still need to finetune the search feature and perhaps add filtering based on my Github lists but it’s usable for now.
-
Working on a new feature for my GitHub activity page — a searchable starred repositories browser. The idea is to visualize all my GitHub stars with filtering by language, topic, and description, making it easy to find that one repo you starred months ago. Building it as part of the @rmdes/indiekit-endpoint-github plugin.
-
Exploring the idea of self-hosting a Bluesky PDS alongside my Indiekit instance — turning it into a dual-protocol server that federates over both ActivityPub and AT Protocol simultaneously. Inspired by Wafrn’s approach, adapted to Indiekit’s plugin architecture and Cloudron deployment. The goal: own your AT Protocol identity and data on your own infrastructure, not on bsky.social. Plan drafted, implementation to follow.
status.claude.com
birchtree.me
techdirt.com
blog.tedivm.com