Sometimes, I start writing a blog post on Micro.blog but then switch to Scribble.pages at the last minute to post it there. 🤷🏻‍♂️

When posting a new photo on Glass, I always look at my previous posts on my profile page to see my previous posts. I like to create a nice visual rhythm in my feeds for those who follow me.

With my new job, I get to use a Windows 11 laptop. It’s not a powerhouse, but it is decent—except when it’s not plugged in. As a Mac user at home, I take for granted the speed and battery life that an Apple Silicon Mac offers. It’s night and day. I don’t notice any difference when using the Mac on battery; I never hear the fan because there isn’t one. It’s night and day. We should always remember that.

The Notification Center on macOS is a mess. It’s ugly and needlessly hard to use. I don’t understand this design. If you want to clear it from all the notifications, you have to go way down the list and hit this little circled “x”. Then again on another section. I do understand the difference between immediate time sensitive notifications, but man this is bad. I much prefer the Windows 11’s take on it.

Update: added an example of confusing design decision: two places to clear notifications.

I began my writing project for the Apple Journal review. For this project, I will try a different approach1. I started experimenting with the Perplexity Comet browser to survey past reviews. I use genAI to create quick summaries of previous articles. I save text highlights in Inoreader for the most interesting past reviews. I use Craft to compile all my knowledge and copy-paste the genAI summaries. However, I’m unsure where this will lead.

  1. Dare I say ‘modern approach’? ↩︎

I’ve been using Apple Journal this summer to record my experience at a chalet by a small, beautiful lake. It’s really an inspiring place. Now that I fully experienced Apple Journal, and Apple’s vision of personal journaling, it’s probably time for me to put together a write-up. Spoiler alert: Apple Journal is full of paper cuts.

Here is a strange issue in Photomator: during photo editing, an .XMP file is created, which likely contains the editing steps applied to the photo. Additionally, a Photomator native file is also generated. Some of these files are very small, while others are quite large. For example, one file is less than 300 KB, while another is nearly 120 MB. Despite using the same editing process, the file sizes vary significantly. These files aren’t package files, it’s impossible to peek inside them. This is strange.