Ok, no pressure anyway! Thanks for looking into it :)

I’m not sure if your RSS reader is getting the content through some special way. The feed itself only has the first two paragraphs:

<item>
  <title>The Linux kernel is just a program</title>
  <link>https://serversfor.dev/linux-inside-out/the-linux-kernel-is-just-a-program/</link>
  <guid isPermaLink="true">https://serversfor.dev/linux-inside-out/the-linux-kernel-is-just-a-program/</guid>
  <description>Most books and courses introduce Linux through shell commands, leaving the kernel as a mysterious black box doing magic behind the scenes. In this post, we will run some experiments to demystify it: the Linux kernel is just a binary that you can build and run.</description>
  <pubDate>Mon, 01 Dec 2025 00:00:00 GMT</pubDate>
</item>

It’s a very good explanation. I like that it is short and hands on. For me, it is pitched at the right level and the practical style keeps it very grounded.

what you’d add or change for future posts in the series

I wouldn’t change anything to do with the content! Speaking personally, I’m a fan of full text RSS feeds, so I’d love one on this blog if that’s an option :)

The consideration you should pay to other software should depend on your power and influence in the network.

If PixelFed was dominant in the fediverse, and other apps did feel the need for a dummy pic workaround, that would clearly be a problem. No client feels the need to do that because PixelFed is not dominant, but if it was, it would be fine to criticise them for not “playing nice” and helping the rest of the ecosystem.

I think there’s much more scope to criticise Mastodon for the workarounds other software have to use to be interoperable, than PixelFed, purely because of its power in the network.

We need different apps to experiment and work out what users want. It’s totally fine to experiment with different models and ways to view content. Only when you have a lot of influence over the ecosystem should you have extra responsibility.

This would kill bridges like slidge. They authenticate to WhatsApp using the web interface and that token lasts about two weeks before you have to relink it. A limit of six hours would make it unusable.

Yes Minister / Yes Prime Minister for me. Despite all the scheming the humour is so good-natured throughout.

They will use CC BY-NC-SA 4.0. Which means it’s not open source, and no-one else can sell replacement cartridges, parts etc.

It might still be a good printer and enjoyed by some, but it really annoys me when companies mix these terms up, almost certainly deliberately.

I have read so many posts like this, that try to explain why their company is a special case and why it could never happen to them, only to see the same thing happen again and again.

Tailscale are trying to insert themselves into the stack and become the go-to choice for this kind of networking. When their customers are dependent on it, of course they’ll start extracting rent and capturing as much as they can.

That’s their right, but it’s also a little condescending to pretend otherwise.