Describe Extension

Just finished creating my second Safari Extension using Safari 27’s Describe Extension feature. And it just works on the first try. 1😳 This one will save the selected text of the webpage to my bookmarking web app, including the page title, page URL and author. I wonder how much more complex an extension can be.


  1. My first try was successful, right away, too. ↩︎

A New Foursquare Is Born

I’m making great progress with my new web app. It’s already 90% feature complete and ready for my next trip to Paris, starting next week. When I started this project, I had a fairly clear idea of what I wanted, but as I made progress, it became easy to experiment with new features I didn’t think would even be possible. One such feature is the ability to securely share my check-ins publicly so you can follow me! It’s my only custom-built web app with a public-facing view.

The Helper

This morning, after reading and asking Kagi Summarizer for a summary of this article, I wanted to write a response and attempted to craft a counterargument, first using Kagi Summarizer, then using Claude AI. I reviewed numerous versions but remained unsatisfied with the results. After reviewing my options, I ultimately decided to create this version, entirely my own. I still have a feeling that AI helped forge my thoughts.

The Solution Was to Double Down on my AI Subscription

Since reading David’s article, “the solution might be cancelling my AI subscription”, I cannot stop thinking about how different our experiences are.

Six months ago, right before subscribing to Anthropic’s Claude AI, none of the following custom-built apps existed: a useful, personally fitting bookmark manager; a purpose-built RSS reader that works hand in hand with my bookmark manager; and a simplified task manager that also works in conjunction with the other two. As an experienced user of many RSS readers, bookmark managers, and task managers, knowing my friction points with these apps, I have always dreamed of what would be perfect-for-me versions of them. So I built those, one by one.

Thanks to Claude Code and my vision for what would make the perfect versions of each of these apps, I could build them without being constrained by not knowing Next.js, TypeScript, CSS, etc. I don’t plan to make commercial versions of these nor open-source them. There are a few, and I can tweak them as I see fit and as my needs evolve; this is where I’ll keep focusing. AI empowered me and will continue to do.

You see, the solution for me is to keep iterating and keep my subscription. Two different stories, two different outcomes. Maybe there is something that I didn’t catch in David’s experience.

Under the Hood

I don’t remember the last time I built a full automation workflow from the ground up in n8n, thanks to Claude AI and MCP support. I started manually before knowing n8n had MCP support integrated, which makes me feel more competent in understanding what’s going on. It reminds me of when I bought an iPad touch so that I could learn to build apps with Objective-C and Xcode; I like to understand what’s going on under the hood, in the digital world, at least.

Archiving Micro.blog Bookmarks

I just completed a new workflow: automatically saving new bookmarks stored on Micro.blog to my custom-built bookmark manager web app running on Vercel. Since Micro.blog doesn’t support webhook calls, I had to resort to a scheduled n8n workflow that pulls any newly saved bookmarks via Micro.blog APIs and saves each one using a new API route on my bookmark manager web app on Vercel. It’s much more efficient than asking Claude AI to do this using a skill (which was working perfectly, by the way) to save into a Craft Collection block entry.

So Many Questions, Still So Few Answers

Report: Apple Plans to Make On-Device AI a Key WWDC Focus:

The arrangement represents a noticeable departure from Apple’s original Apple Intelligence announcement, in which the company said all cloud-bound queries would be handled exclusively by its own Private Cloud Compute infrastructure running on Apple silicon. Apple is likely to retain the Private Cloud Compute branding despite the change, people familiar with the partnership told The Information.

There is much left unanswered in this article. How much of Private Cloud Compute is in use today and for what purpose? How much of this capacity will be running the new Apple Intelligence? Will Apple expand PCC into Google’s datacenters? If so, what is Apple’s own infrastructure going to serve? And how much of an improvement can we expect to run local models on our devices compared to the original Apple Intelligence model?