Microblog

I lost the ability handwrite for years now. It’s chief among the things I miss (blakewatson.com/journal/things).

I was thinking of collecting scans of old writing samples (I think I have enough) and creating a font as a way to restore my lost handwriting, in a way.

I really don’t know where to start or how difficult it would be to accomplish given that I can’t produce new samples.

If anyone has resources or direction to giv me, I’d appreciate it!

social.lol/@bw/112633801727117613

Watching MKBHD’s interview with Tim Cook at WWDC24. In it, Tim says “Our model is one where we want to empower you to be able to do things you couldn’t do otherwise.”

I feel this really hard. Apple’s accessibility features are S-tier and I can’t overstate how much they impact my life for the better.

social.lol/@bw/112605620720424696

I’m not saying the term “user” is always bad, but the old joke goes that only industries that call their patrons “users” are drug dealers and tech.

I’ve found myself searching for other words when it makes sense. Are they reading my article? They’re readers. Or if I need to be generic—they’re visitors. Are they paying me? They’re customers or patrons.

social.lol/@bw/112498737493468251

I’m working on a beginner HTML tutorial series and I’m just finding out that YouTube embeds won’t work in a non-ssl context like a local web server.

Do I have any good option for getting around this? I’m not gonna make a beginner deal with self-signed certs.

social.lol/@bw/112457331530161835

I’m so happy about a longstanding bug that was fixed in macOS Accessibility Keyboard, the built-in onscreen keyboard.

The accessibility keyboard has word prediction similar to how an iPhone does. Problem is, it usually crapped out in browser-based editors (probably because of how weird `contenteditable` regions are).

But in the latest version of Sonoma it’s working beautifully! That means I can now easily write in apps like Obsidian and my own write.omg.lol.

social.lol/@bw/112446512449361417

The latest version of macOS fixed a longstanding bug in the Accessibility Keyboard that prevented word prediction from working properly in browser-based text-editing environments (I’m assuming it’s something to do with contenteditable regions). Because of that behavior, I was never able to give Obsidian a a proper try—word prediction is a must for me if I’m writing anything more than a sentence or two.

So I’ve installed Obsidian, exported all my Bear notes into a folder in Dropbox, and I’m giving it a shot. A nice benefit of Obsidian operating on a “folder of files” is that I can draft blog posts (like this one) directly in my site’s src folder. Kinda neat.