With my blog’s new custom design in place, I’m considering my next project: developing an email summarizer using Gmail, n8n workflows, Claude AI, and Discord. I don’t plan to use this often, but I do have some emails that I get that I wish could be summarized just by sending them to a dedicated email address.

Inoreader announced support for third-party AI providers for articles summarization. Anthropic and OpenAI are supported among others. Just enter your own API key and voilà! But there is a big catch: even if available for Pro plans, you need an add-on upgrade to enable this! That, I don’t understand because in this scenario, Inoreader is in fact delegating the LLM so they incur not additional costs. I find this perplexing to say the least. Or I might be missing something. I hope someone at Inoreader will catch this comment.

Hacker News’s article “Ransomware Is Growing Three Times Faster Than the Spending Meant to Stop It”:

Ransomware leak-site claims surged 30.7% year-over-year in 2025 to reach 7,760 incidents, significantly outpacing the 10.1% growth in worldwide security spending ($213 billion), indicating a widening gap between observable threat volume and security investment.

The article doesn’t say what is causing this surge, and if AI has anything to do with it. I would bet that AI might be helping hacker groups.

Even if I use an automation (via n8n) for my Micro.blog timeline summarization, I still come here to read my timeline, although less frequently than before. It’s a good way to gauge how well or poorly LLM can be at summarizing such content. ☝🏻

Quoting Bryan Cantrill — Simon Willison

Work costs nothing to an LLM, and LLMs do not feel a need to optimize for their own (or anyone’s) future time, and will happily dump more and more onto a layercake of garbage.

Until recently, thanks to rising chip prices, human developers were too lazy to optimize their software stacks, leading to bloated software requiring much more memory than necessary to run. Now there is an incentive to rethink how they allocate development time, but it will probably be delegated to LLMs… we’re doomed.

With the blog redesign, I decided to remove the /archive page. I add an issue with Micro.blog / Hugo handling of long list of blog posts. Because I couldn’t figure out how to fix it (nor Claude AI apparently), it was removed. I bet that nobody really look into this page anyway1.

  1. Except AI bots. ↩︎

M.G. Siegler about Apple’s AI competitiveness in Serious About Computing? You Should Build Your Own AI. — Spyglass

While they may look smart at some point for not pouring hundreds of billions into CapEx spend, that could come back to bite them in ways that are more tangential. Including, culturally, if the DNA of the company is never rewired to operate in the Age of AI. “People who are really serious about software should make their own hardware,” Alan Kay famously declared in 1982. What if the modern day version is something like: “People who are really serious about computing should make their own AI”?

I think we are still in the early days of generative AI. Siri’s failures apart, generative AI being so different than anything Apple did with Siri in the past, they can (and should) outsource their AI infrastructure. Eventually, they might bring it in, just like they did for Qualcomm modems, for example.

Forcing Micro.blog to rebuild the entire website to enable a design change is so slow; close to 30 minutes each time. 😳 One of the challenges is that not all design changes require a full rebuild; some do, some don’t, and I don’t always know in advance which ones do. Claude AI is not very good at predicting this either.