Going to Amsterdam. brb
People and blogs involved with and about the IndieWeb community, the fediverse, and/or the open web in general.
Long day but really good day. Felt like it had a little bit of everything. Still coming down after that Spurs game, really good. Tomorrow need to unpack a little more of what I glossed over during the WWDC announcements.
Go Spurs Go! Big game in NY. Found a sports bar to watch a little while in San Jose. Mostly Knicks fans here but a few Spurs fans here. đ
OpenAI announces draft S-1 in an oddly direct, brief blog post:
We recently submitted a confidential S-1. We expect it to leak so weâre just announcing it. We have not decided on timing yet; it may be a while because there are things we want to do that are likely easier as a private company.
Catching up from yesterdayâs post from John Gruber about SwiftUI:
Thereâs something really wrong with SwiftUI. Amongst the apps I use, the best example is Apple Journal. Basic stuff thatâs worked reliably for decadesâââsome things that heretofore had worked foreverâââare dangerously broken.
Apple shouldâve unified AppKit and UIKit years ago. SwiftUI could be purely a wrapper for the core framework, plus support for watchOS. Maybe too late to correct this now.
Sometimes you write a post and when you're editing it you realize you no longer support what you wrote. This is one of those times.
Monday session
Monday session
Pulled several short straws in the office World Cup sweep stake: Turkey, Panama and Austria.
Seeing this screenshot on Mastodon from Finn Voorhees, sounds like Apple doesnât want big companies to use private cloud compute. Which means it probably wonât even work with Mac apps like mine that are distributed outside the App Store. Appleâs going to lock this down.
I seem to be microblogging a little more than usual for the keynote, so decided to create a category on my blog for WWDC 2026 posts.
9to5Mac confirming what I thought I heard during the keynote: 8 GB devices are out for on-device AI. I think itâs the right call⌠Appleâs old models were just too small. But itâs weird that my pretty expensive iPhone 16 Pro Max canât run local AI.
Expanding Apple Foundation Models to support image inputs and running in private cloud compute is a huge upgrade. The old models really werenât capable enough for me, which is why Iâm experimenting with bundling Gemma 4 directly in the Micro.blog app.
I feel bad saying this for all the Apple employees who dedicated so many hours preparing for WWDC, but I lose interest after an hour. Perfect keynote length would be about 70 minutes, not 100.
Apple didnât try to take on too much with Siri AI. Only features they could actually ship. It looks good, but long term I still think using apps is the wrong strategy for assistants, because they canât work well across platforms. Itâll work for now, and for privacy some people will prefer it.
I like in these Siri AI demos that they are doing things âliveâ (though recorded). Itâs not fast, but it seems much more clearly actually working without edits.
A little surprised Apple is spending so much time in the keynote on safety for kids. Itâs good, though! Thinking it helps set the stage for all the age-related laws from states, and weâll return to safety and privacy during the Siri section later.
In my apps Inkwell and Micro.blog 4.0, I put a semi-opaque view under the toolbar to improve readability on macOS 26. Maybe wonât be needed in macOS Golden Gate. Expecting weâll need little tweaks for each OS now.
Looks like good refinements to Liquid Glass on Mac. Also, feels almost bold to name this release Golden Gate. Maybe thisâll be a big one.
Coffee this morning at Voltaire in San Jose. For a moment, I considered walking back to the hotel with my laptop cracked open to let AI finish what it was working on⌠That would be too perfectly Silicon Valley. âď¸
Om Malik with a great blog post exploring Anthropicâs naming for Mythos and Project Glasswing:
Project Glasswing is the same move. The name suggests something fragile and transparent, a butterfly with see-through wings. The project is opaque. Only the trusted can see it. The name performs openness so the structure does not have to.