Food for Thought on a Rainy Friday

What if, as soon as we shared content on the Internet, you couldn’t remove it as soon as someone was referring to it or embedded it in some other content? I’m thinking about the open web here… would this hypothetical web be called the open web anyway? Would we be more intentional when sharing content having this rule baked in? This chain of thoughts was triggered when I came across a website with a blog post with some embedded content from YouTube. Some videos were no longer available and made the blog post more or less diminished.

I saw Matt Birchler’s work in his latest Quick Read application here and thought it was nice UI work. I wanted to see if I could do something similar for the color configuration for tags in my task manager. It was much harder than I thought, but I’m happy with the results.

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?

Daydreaming All The Time

While moving my tasks out of Things 3, I noticed that many possible projects or tasks were really just daydreams. Migration is an ideal opportunity to reevaluate everything with a fresh perspective. Then, the new digital home will host a new set of daydreaming projects and tasks that I’ll revisit with a smile and kill right off the bat.

Switching DB Backend Easily

After largely completing the transition from Things.app to a version built with vibe coding on Next.js and hosted on Vercel, I decided to switch from Airtable to a Postgres backend. The free-tier on Airtable only allows 1000 public API calls, which wasn’t sufficient. To avoid hitting this cap constantly, I, with the help of Codex, migrated to a Postgres database called Neon, available through Vercel’s marketplace. I already use Neon for my bookmarking web app, so the change was quite smooth. I didn’t need to move any data since I am still in the late development phase. Now returning to other fine-tuning tasks.

Making Progress

Well, well, well, it seems to be happening much quicker than originally thought. I’m about 70% done with this already! I still like Claude Code more, but Codex is more efficient at testing the UI in its browser than Claude Code. And the in-browser cursor, which is 100% independant than the Mac cursor, is super cool to see in action.