If you've had trouble unsubscribing from the nightly email, I fixed a big problem there this morning, so please try again. If the problem persists, here's a place to report.
People and blogs involved with and about the IndieWeb community, the fediverse, and/or the open web in general.
Ben Werdmuller
• Ben Werdmuller
A 2026 checklist
A way to build a habit out of what's important.
Leveraging The Super Keyword In Custom Elements
Making the most of inheritance when extending custom element classes.
Found myself unexpectedly with a day to spend in Phoenix, so I went to the excellent Musical Instruments Museum and ogled the mandolins.
Found myself unexpectedly with a day to spend in Phoenix, so I went to the excellent Musical Instruments Museum and ogled the mandolins.
Lights on the San Antonio River Walk.
Universal driving directions: Go straight. Turn left or right whenever you need to.
Seriously, I’m trying to use turn-by-turn directions less often. I can’t decide if it introduces some subconscious extra stress with or without it.
King William River Park. 🌳
Manton Reece explains why Micro.blog uses Markdown. I use Markdown because Manton does. It's for interop.
If I had billions of dollars I'd divest. And if my country did a good job of investing in education, health, voting rights, stuff like that, I'd just give most of it back to the country. Thanks for the education, and saving my life with medicine not just once but twice. Thanks for being such a cool country. If only we lived up to the promise, but now we'd certainly need to come up with another way of distributing the benefits to the country and its people.
2016: Your human-size life.
A few months ago I turned off fediverse publishing for my blog. Some of my posts still trickle out to the fediverse, via conversations, which is fine. I haven’t missed it. I still get replies on Micro.blog and from Bluesky. I’m going to turn the fediverse back on and see how things are in 2026. 👋
Screenshot teaser for something I’ve been working on over the holidays, for launch next year. I think this could be a big deal. Can’t share the details yet! Perfectly fits with the Micro.blog and IndieWeb principle of pluralism: multiple protocols, platforms, anything that makes the open web better.
Ben Werdmuller
• Ben Werdmuller
2025: a personal year in review
Highlights and hopes for the new year.
No one got any sleep in these parts last night, was like a non-stop tornado, but I did watch a couple of artsy movies that were really good. And this morning power was out and internet, and I thought for sure some trees had to be down, but only one was, a huge one, and I had to walk to the post office to use their phone to call a friend with a big saw and truck, and I wondered how he'd get rid of the tree, and this is how. First he chopped it up into bits with a saw, and then used the same plow he uses to get rid of the snow to push the tree parts off to the side of the road. And when I got home the internet was back on and I'm going to spend most of the rest of the day sleeping, maybe or drinking a load of coffee and trying to stay on a normal schedule.,
I’ve been testing some new features with Ghost. I can see the appeal of it, it’s robust and beautiful, but personally I could never use Ghost for my own blog. I would feel trapped in its design. Trying to articulate part of this, I wrote a new help page: Why Micro.blog uses Markdown.
Following on my post about the fediverse for next year, I’m going to be doing some work to clean out never-used or spammy accounts in Micro.blog. Micro.blog is currently 6th most popular fediverse software for total users, but will fall off after more housekeeping.
January 2026 IndieWeb Hackathon Kickoff
How To Dynamically Install Custom Elements
A reusable pattern for custom elements installation
Castle to Wemby dunk. 🏀
The Future of Software Development is Software Developers – Codemanship’s Blog
codemanship.wordpress.com/2025/11/25/the-future-of-software-development-is-software-developers/
The hard part of computer programming isn’t expressing what we want the machine to do in code. The hard part is turning human thinking – with all its wooliness and ambiguity and contradictions – into computational thinking that is logically precise and unambiguous, and that can then be expressed formally in the syntax of a programming language.
That was the hard part when programmers were punching holes in cards. It was the hard part when they were typing COBOL code. It was the hard part when they were bringing Visual Basic GUIs to life (presumably to track the killer’s IP address). And it’s the hard part when they’re prompting language models to predict plausible-looking Python.
The hard part has always been – and likely will continue to be for many years to come – knowing exactly what to ask for.