Carlo Zottmann

TIL how to auto-move Xcode DEBUG builds to Applications

Sat, 24 Jan 2026 01:12:20 +0100

TIL a neat Xcode trick!

So my apps contain app intents. Those won’t show up in Shortcuts unless the app is anywhere in /Applications. For months now I’ve been using a post-build scheme script to move the DEBUG build there, w/ a symlink to the app in its original place in derived data.

This worked well but was a whole thing because I had to make sure cleaning the build would wipe the moved app etc.

Turns out I was overthinking it! All I needed to do was to add this in the right .xcconfig:

DEPLOYMENT_LOCATION = YES
DSTROOT = /Applications/Dev Builds
INSTALL_PATH = /

Now Xcode takes care of all the things, I don’t need those scripts anymore, and Xcode even correctly cleans the built when necessary.

So that’s that. The more you know!

Thu, 22 Jan 2026 18:18:06 +0100

83% aller deutschsprachigen Kommentare zu jedwedem Thema sind “Das haben wir noch nie so gemacht”, “Sie können hier nicht parken” und “Hier wird nicht gerannt”, nur halt mit Hut und Trenchcoat und aufgeklebtem Schnauzbart.

Thu, 01 Jan 2026 21:40:41 +0100

Quoting Craig Mod, on the correct way of handling the garbage we create:

A funny thing happens when a Snickers bar goes from whole to eaten — the wrapper transmogrifies from useful to toxic. Suddenly, this thing that was keeping germs and dirt off your chocolate sugar log is now “useless” and with this comes the heaviest burden a modern person unencumbered by genocide or famine can hold: garbage responsibility. […]

There are no garbage cans in Kamakura, and, indeed, if you are buying a coffee to go, you will be responsible for that receptacle for, potentially, a very long time. This is your grandé-sized hair shirt to bear. […]

This obsession with the immediate “unburdening” of a thing you created is common in non-Japanese contexts, but I posit: The Japanese way is the correct way. Be an adult. Own your garbage. Garbage responsibility is something we’ve long since abdicated not only to faceless cans on street corners (or just all over the street, as seems to be the case in Manhattan or Paris), but also faceless developing countries around the world. Our oceans teem with the waste from generations of averted eyes. And I believe the two — local pathologies and attendant global pathologies — are not not connected.

I’m slowly starting to believe I’m secretly Japanese.

Toleranz ist kein moralisches Gebot, sondern ein Friedensvertrag

Thu, 01 Jan 2026 14:36:01 +0100

Das Essay Tolerance is not a moral precept von Yonatan Zunger ist eines, das ich regelmäßig auf Mastodon teile, denn es ist sehr gut. Yonatan löst das scheinbare Paradoxon der Toleranz sehr elegant auf, indem er das Framing zurechtrückt, und das Konzept “Toleranz” schärfer definiert.

Da ich es als sehr klug empfinde, aber keine Möglichkeit gefunden habe, den Autor zu kontaktieren¹, um ihn zu fragen, ob ich es liebevoll ins Deutsche übersetzen darf, möchte ich hier auf seinen frei zugänglichen Post in der (sehr lesbaren) Auto-Übersetzung hinweisen.²

→ Toleranz ist kein moralisches Gebot | von Yonatan Zunger:

Toleranz ist kein absoluter moralischer Wert, sondern ein Friedensvertrag. Toleranz ist eine soziale Norm, weil sie es verschiedenen Menschen ermöglicht, friedlich zusammenzuleben. Sie bedeutet, dass wir akzeptieren, dass Menschen anders sein können als wir – in ihren Bräuchen, ihrem Verhalten, ihrer Kleidung, ihrem Sexualleben – und dass uns das nichts angeht, solange es unser Leben nicht direkt betrifft. Doch das Modell eines Friedensvertrags unterscheidet sich von einem moralischen Gebot in einem einfachen Punkt: Der Schutz eines Friedensvertrags gilt nur für diejenigen, die bereit sind, sich an seine Bedingungen zu halten. Es ist eine Vereinbarung, in Frieden zu leben, nicht eine Vereinbarung, unabhängig vom Verhalten anderer friedlich zu sein. Ein Friedensvertrag ist kein Selbstmordpakt.

Ich wünsche Euch ein gutes neues Jahr. Bleibt tolerant, aber nicht passiv.

#FCKNZS `#FCKAFD

Links:

Tolerance is not a moral precept. | by Yonatan Zunger
- archive.is
- web.archive.org

Ausserhalb LinkedIn, und meinen LI-Account habe ich vor Jahren schon gelöscht. Tja. ↩︎
Mit Umweg über den freedium-Mirror des originalen Medium-Posts. ↩︎

Cities are organisms

Thu, 25 Dec 2025 00:21:33 +0100

An interesting question posed by Sam Holden:

Robert Macfarlane’s Is A River Alive? asks what would it mean for our understanding of the natural world and our relationship to it if we saw rivers not just as ecosystems containing life, but as truly alive. In beautifully animistic prose, Macfarlane ventures to the frontier of the rights of nature movement, where rivers are treated as subjective entities that think, feel and are endowed with legal protections. The book also inspires a related thought experiment: is a city alive?

My personal view, one that I held for years, is that a city is an organism – so yes, it is alive. Its citizens are its cells, its genome, its flesh, its live blood. Remove those, and the organism will die and wither. Remove the stones, however, the steel and glass, the asphalt, and you’re left with half an organism quickly regrowing the missing parts of its body.

Sun, 07 Dec 2025 22:51:59 +0100

Quoting Jon Worth from a Bluesky thread:

After […] Musk’s statement to abolish the EU (after the Commission fined X), let’s ask ourselves simply:

HOW ARE EUROPEAN COMMISSIONERS USING X NOW? […]

If European Digital Sovereignty is to mean anything, it ought to mean NOT posting on a platform owned and run by a fascist intent on undermining the EU!

And don’t give me the bullshit you have to be there for “balance” or “reach” - the rules are stacked against you from the outset

Tue, 02 Dec 2025 13:22:34 +0100

Quoting Louis Rosenberg:

In other words, we are not watching a bubble expand with blustery vapors. We are watching a planet form from churning magma, and it will solidify into a new framework for society. Denial will only make us unprepared. This is not an AI bubble. This is real.

I agree with several of his points, but I also take the whole post with a grain of salt, mind. The guy is a computer scientist but also the CEO of a AI company which I suspect colors/ informs his POV and predictions.

November Sale! 25% off of BarCuts and Browser Actions

Thu, 27 Nov 2025 14:07:10 +0100

I recently released updates to both my contextual macOS Shortcuts launcher, BarCuts, and Browser Actions, which let you automate Google Chrome, Vivaldi, Microsoft Edge, and other browsers. 🚀

And since it’s November, I’ve also decided to join the fray and run a sale for them:

✨They’re 25% off with code FCKNZS2025 until end of the month!✨

(People asked me whether Actions For Obsidian will go on sale, but given it’s been “Pay What You Think Is Fair” since the very beginning, I feel like it’s kind of always been on sale.😉)

🖖🏼

A quick story about how a LLM saved me €100+ today

Wed, 19 Nov 2025 19:18:05 +0100

I have this setup: XLR mic → ext. USB audio interface → Mac. The name of the audio interface (UMC22) has a trailing space, which macOS gets confused by every other day. It sanitizes the stored name, can’t find the device anymore, removes it, then finds a “new” device it doesn’t know and re-adds it. The mic works fine, but setting the audio interface as the default for anything doesn’t, because macOS keeps forgetting it.

This has been going on forever, but it has gotten progressively worse with every major macOS update. (Don’t at me; I’ll keep using macOS because I write software for it-this is how I make my money.) Since macOS 26 rolled around, it happens every two days — basically every time I dock the MBP.

I finally got fed up and started looking into a new USB mic — €100+ for quality products, naturally — which pissed me off because I like my existing mic; it’s good, and it works. It’s just that shitty interface issue + macOS, damn it.

In the past, I’d tried setting up an aggregate (virtual) audio device that contained the audio interface, but that didn’t change anything. The interface would vanish and reappear as a new device, and the aggregate device wouldn’t know about it. I had to manually add the new device to the aggregate — no good.

Anyway. Today I asked Claude to research that problem for me. It did and came back with a lot of technical detail, which boiled down to “Carlo, you were right about what’s going on."

But all my describing the issue, plus the research, gave Claude a metric shit-ton of insight, so I then asked it to write me a Swift CLI tool that would let me add a named device to an existing aggregate device. And it did! When it was almost done, the 5-hour limit window struck, so I handed the prototype script over to Kimi K2 Thinking¹, and it hammered out the rest for me.

Frens, I was tickled fancy, let me tell you.

Now I have a script that runs automatically in the background every time the USB device is connected. And since the aggregate doesn’t change (it’s just updated!), I can use that as the default device.

Sure, without Claude and K2, I could’ve written that script myself, but it probably would have taken several days of my free time (since I have a day job) for research, trial, and error. This way, it took less than an hour to fix this specific issue.

And I can keep using my old stuff. Win!

It’s a monster! A slow, slow monster. ↩︎

Sun, 16 Nov 2025 20:16:58 +0100

Why Solarpunk is already happening in Africa:

What’s happening across Sub-Saharan Africa right now is the most ambitious infrastructure project in human history, except it’s not being built by governments or utilities or World Bank consortiums. It’s being built by startups selling solar panels to farmers on payment plans. And it’s working.

Over 30 million solar products sold in 2024. 400,000 new solar installations every month across Africa. 50% market share captured by companies that didn’t exist 15 years ago. Carbon credits subsidizing the cost. IoT chips in every device. 90%+ repayment rates on loans to people earning $2/day.

And if you understand what’s happening in Africa, you understand the template for how infrastructure will get built everywhere else for the next 50 years.

Really, really cool.

Restarting macOS/iOS Continuity & Handoff

Sat, 15 Nov 2025 12:19:23 +0100

After updating both my Mac and iPhone to the latest OS 26 versions, Continuity/Handoff wasn’t working anymore, meaning no more cross-device copy-n-paste etc. Rebooting either device didn’t change anything.

15 mins of searching brought me to a Reddit post by /u/shesabadone which suggested resetting macOS' useractivityd:

defaults delete com.apple.coreservices.useractivityd
killall useractivityd

It did the trick!

Linearis v2025.11.2

Wed, 12 Nov 2025 14:38:25 +0100

Yesterday, I released Linearis v2025.11.2, a new version of my CLI tool¹ that lets you (and your LLM) work with the very good project management and ticketing system, Linear². The headliner features for this update are:

support for cycles³
support for project milestones⁴
issues now specify their sub-issues and parents

Shout-out to @ryanrozich for the patch that added both cycles and project milestones. 🤘🏼

Also, I’m happy to announce that the tool is now a standard npm package, meaning that it’s installable with a simple npm install -g linearis call. (Up until now, you could only install it directly from the GitHub repo, but that brought some issues with updating.)

And ICYMI: the previous update, v2025.11.1, added support for downloading screenshots and documents that are embedded in a ticket description or a comment. So now your agent of choice gets to look everything! For example, to read one of my test tickets, it’d do this:

❯ linearis issues read ZCO-1569
{
  "id": "de732438-8ae2-4f9e-95a9-85a614b04816",
  "identifier": "ZCO-1569",
  "title": "File embed testing grounds",
  "description": "The Earth was small, light blue, and so touchingly alone, our home that must be defended like a holy relic. The Earth was absolutely round. I believe I never knew what the word round meant until I saw Earth from space.\n\nThe dreams of yesterday are the hopes of today and the reality of tomorrow.\n\n![Confident Man and Futuristic Car.png](https://uploads.linear.app/7df2165d-5920-4338-950f-f2b7152a3c02/8a8adc83-0609-4bb7-9c2d-6450bd2e20a5/db4145e5-6499-45cd-b35c-9aa621bfde51?signature=<signature_omitted>)\n\nIt suddenly struck me that that tiny pea, pretty and blue, was the Earth. I put up my thumb and shut one eye, and my thumb blotted out the planet Earth. I didn't feel like a giant. I felt very, very small.\n\n![i-swear-to-god-connor.gif](https://uploads.linear.app/7df2165d-5920-4338-950f-f2b7152a3c02/571bf0bf-3586-4f92-9427-a88c13d3c7e4/00d4a028-2053-452c-8da4-a55930943868?signature=<signature_omitted>)",
  "embeds": [
    {
      "label": "Confident Man and Futuristic Car.png",
      "url": "https://uploads.linear.app/7df2165d-5920-4338-950f-f2b7152a3c02/8a8adc83-0609-4bb7-9c2d-6450bd2e20a5/db4145e5-6499-45cd-b35c-9aa621bfde51?signature=<signature_omitted>",
      "expiresAt": "2025-11-12T14:19:59.963Z"
    },
    {
      "label": "i-swear-to-god-connor.gif",
      "url": "https://uploads.linear.app/7df2165d-5920-4338-950f-f2b7152a3c02/571bf0bf-3586-4f92-9427-a88c13d3c7e4/00d4a028-2053-452c-8da4-a55930943868?signature=<signature_omitted>",
      "expiresAt": "2025-11-12T14:19:59.963Z"
    }
  ],
  "state": {
    "id": "0d744059-bc97-4dc2-82d0-5bac53673c26",
    "name": "Done"
  },
  "assignee": {
    "id": "cef0517b-cd50-48d9-80d6-8ad34007458a",
    "name": "Carlo Zottmann"
  },
  "team": {
    "id": "413e044c-d008-4bcb-b48d-1ef45ada89f4",
    "key": "ZCO",
    "name": "ZCo"
  },
  "project": {
    "id": "904984cc-eb35-4e4d-9caf-aa21f9f7daa7",
    "name": "Linearis"
  },
  "cycle": {
    "id": "bbde6b5b-c5fe-4319-9bbc-9081746e6660",
    "name": null,
    "number": 110
  },
  "projectMilestone": {
    "id": "38cb29af-af9e-493c-b935-205b31396a4b",
    "name": "2025.11.1",
    "targetDate": "2025-11-06"
  },
  "priority": 0,
  "labels": [],
  "parentIssue": {
    "id": "d2d0ad4d-8ad6-4e6d-8ab0-cb9b748d21e8",
    "identifier": "ZCO-1441",
    "title": "Implement Linear API File Download Capabilities"
  },
  "subIssues": [],
  "comments": [],
  "createdAt": "2025-11-06T16:09:46.447Z",
  "updatedAt": "2025-11-09T18:45:35.964Z"
}

What’s great about that is that e.g. Claude is clever enough to understand that result without any further explanations. For me, that means that I had to teach Claude four things:

My ticket IDs sport the prefix “ZCO-”.
Use linearis to work with tickets.
Before doing that, run linearis usage once to learn how to use it.
If you come across embeds, fetch and read them as well.

And that’s it. The output is structured enough, and Claude knows how to extract what it needs and how to look up anything else related to that ticket using linearis!

No MCP server eating 16k tokens at rest, just a CLI tool. (I recommend that approach in general.)

Fri, 07 Nov 2025 13:19:26 +0100

Quoting HN user yanhangyhy’s comment about Kimi K2 Thinking:

[…] China’s open-source strategy has many significant effects—not only because it aligns with the spirit of open source. For domestic Chinese companies, it also prevents startups from making reckless investments to develop mediocre models. Instead, everyone is pushed to start from a relatively high baseline. Of course, many small companies in the U.S., Japan, and Europe are also building on Qwen. Kimi is similar: before DeepSeek and others emerged, their model quality was pretty bad. Once the open-source strategy was set, these companies had no choice but to adjust their product lines and development approaches to improve their models.

Moreover, the ultimate competition between models will eventually become a competition over energy. China’s open-source models have major advantages in energy consumption, and China itself has a huge advantage in energy resources. They may not necessarily outperform the U.S., but they probably won’t fall too far behind either.

(Emphasis mine.)

Wed, 05 Nov 2025 18:15:00 +0100

Wild Wild Space: “HBO Original Documentary that chronicles the fierce competition to tackle humanity’s next great frontier and the dark side of capitalism’s insatiable appetite for profit”

YouTube Video

A cool documentary to watch if you’re interested in the current commercial space race (like I am), showing some key players, and telling the story how it came to be. Based on Ashlee Vance’s book “When the Heavens Went on Sale” which I’ve yet to read.

Wed, 05 Nov 2025 18:04:12 +0100

BBC Radio 5 Live - Bugzy Malone’s Grandest Game

A loving look at the GTA series by BBC’s Chris Warburton and UK rapper Bugzy Malone. “It’s the game that shocked and thrilled the world: Grand Theft Auto. Its rise to domination is an incredible story." They look at how GTA came to be, how it grew, its controversies, and what it meant to different people. They talked with ex-Rockstar devs, modders, games journalists, players. Seven episodes, nicely produced, ace little treats right before bed time.

Mon, 03 Nov 2025 00:22:24 +0100

Peter Leyden: Why 2025 is the single most pivotal year in our lifetime

YouTube Video

That was an interesting 15 min watch. What I liked a lot was that it briefly touched on massive inequality, too, it didn’t just ignore it – in fact, I think inequality’s very much part of Mr Leyden’s prediction:

The economic system […] that has worked for essentially the top 10% for sure and certainly for the top 1% has not been working for 80%. And it’s gotten to the point where they just have had it.

Adding some Vygotsky to my LLM system prompt

Sat, 25 Oct 2025 11:52:19 +0100

Anders Thoresson came up with a good addition to LLM system prompts (Claude, Codex, GLM et al). I’ve been using it for the last few weeks, and it definitely feels like I get better interactions out of Claude when tasking it with research, helping me think things through, or have it explain new concepts to me.

The prompt:

Meet me where I am (Vygotsky’s theory of zone of proximal development): Gauge my understanding from what I write. If unclear, ask one question about my current knowledge level, then proceed.

Since Anders' post is a good read which explains the theory and how he arrived at the prompt, I think you should just go there to learn more.

Sun, 12 Oct 2025 18:34:16 +0100

Quoting Craig Mod once more:

Everyone was uniquely nuts. Each human contained their own special crazy. This was humanity’s gift to the universe. Humans were the “sensory organs” of the cosmos. The walker liked this framing — the purpose of humans was to meta-cognitize the universe itself. So to be, to observe, was to fulfill. If you thought about it like that, things were a lot less pressing.

Another excerpt from his ongoing (and lovely) pop-up newsletter, Between Two Mountains.

BTW, I think the origin of that framing is Carl Sagan: “We are a way for the universe to know itself”.

I am also reminded of a video short by Jason Silva that I watched about ten years ago (and which lived rent-free in my mind ever since for some reason), “Humans are the Sex Organs of Technology”. Different topic, sure, yet equally wild.

The ideas of humanity as a witness, or a parent/ midwife for something else to emerge are kind of mindbending.

Sun, 05 Oct 2025 18:56:58 +0100

Ein wirklich interessantes Interview mit dem Autoren Thomas Chatterton Williams beim ZEITmagazin: “Ein Klima, in dem viele lieber schwiegen. Das machte Woke so wirksam”. Ich finde es in Gänze sehr lesenswert, und hätte die Hälfte des gesamten Artikels zitieren können, daher hier nur ein kurzer Auszug:

ZEITmagazin: Was war das Gute an Wokeness?

Williams: Wokeness benannte vieles richtig. Ein Beispiel ist MeToo: Als heterosexueller Mann hatte ich nie darüber nachgedacht, mit welchen subtilen Hürden Frauen am Arbeitsplatz konfrontiert sind, etwa beim Netzwerken oder Bewerben. Wokeness machte solche Unsichtbarkeiten sichtbar. […] Problematisch wurde Wokeness dort, wo sie über das Ziel hinausschoss: Wenn Unschuldige durch bloße Anschuldigungen ruiniert wurden und das als Preis fürs größere Ganze galt. Ein Kurator des San Francisco Museum of Modern Art wurde zum Rückzug gedrängt, nachdem er gesagt hatte, er wolle weiterhin Kunst von weißen Künstlern kaufen. Der Präsident und der Vorstandsvorsitzende der Poetry Foundation mussten zurücktreten, weil sie zwar Black Lives Matter unterstützten, aber nicht entschieden genug.

ZEITmagazin: Black Lives Matter war der sichtbarste Ausdruck dieser neuen Sensibilität. Wo genau hat sich die Bewegung aus Ihrer Sicht verrannt?

Williams: Der ursprüngliche Impuls von Black Lives Matter war berechtigt. Die Zahl der tödlichen Polizeieinsätze in den USA ist skandalös. Aber schnell verlagerte sich der Fokus von der Gewalt selbst auf die Gruppenzugehörigkeit der Opfer. Das hat viele Menschen entfremdet. Es gibt etwa den Fall von Tony Timpa, einem weißen Mann, der 2016 in Dallas fast auf dieselbe Weise starb wie George Floyd: Polizisten knieten auf ihm, während er um Atem rang, sie lachten – und er starb. Doch das Video ging nicht viral. Warum? Weil der identitätspolitische Fokus fehlte. Genau das war langfristig kontraproduktiv: Statt sich gemeinsam gegen Polizeigewalt zu wenden, wurde alles durch eine identitätspolitische Brille betrachtet.

Fri, 03 Oct 2025 18:02:49 +0100

Quoting Craig Mod:

Tiny men with big sticks upend sanity the world ‘round and all you can do is try to find your footing and push back.

From the first missive of his current pop-up newsletter, Between Two Mountains.

iOS iCloud Drive Synchronization Deep Dive

Mon, 08 Sep 2025 19:20:37 +0100

Today I was pondering a feature idea for my macOS/iOS app Actions For Obsidian. That idea is loosely related to iCloud Drive. But ever since AFO’s release a few years back, I have received dozens of support requests from people who ran into issues while attempting to use iCloud Drive as a means of synchronizing their Obsidian vaults between their devices.

Usually my one-word answer to these questions is “Don’t”, followed by a link to a FAQ entry that I wrote a while back: “Can I use iCloud Sync with Obsidian and Actions for Obsidian?" (Spoiler: Yes, you can, but it’ll be painful at one point or another… or several.)

I had a pretty good mental model of iCloud Drive’s behavior built up already, but as I was thinking about that aforementioned feature idea, I figured that Claude Opus 4.1’s “research mode” might speed up the process a bit. So I tasked it to dive deep into researching how iCloud Drive synchronization works, particularly focusing on iOS behavior and specific scenarios with Obsidian vaults and the “Keep Downloaded” feature.

The resulting doc is what you’ll find below. Enjoy. #sharingIsCaring

iOS iCloud Drive Synchronization Deep Dive

Apple’s iCloud Drive synchronization on iOS operates as a system-controlled process that prioritizes device performance and battery life over real-time sync, fundamentally changing how third-party apps like Obsidian must approach data synchronization. Unlike traditional file sync services, iOS maintains strict control over when, how, and under what conditions synchronization occurs, creating both powerful integration opportunities and significant technical challenges for developers and users.

The core architectural principle revealed through Apple’s official documentation is that applications cannot force synchronization¹ - the iOS system decides all sync timing based on complex algorithms that consider network conditions, battery state, thermal management, and learned user behavior patterns²³. This system-first approach means that apps like Obsidian must work within iOS’s scheduling constraints rather than implementing direct sync control.

System-controlled sync architecture governs all operations

Apple’s iCloud Drive uses a sophisticated two-stage synchronization process where files move from app containers to system-managed directories, then propagate to iCloud servers “as soon as possible”⁴ - but timing remains entirely system-controlled. All file operations must use NSFileCoordinator objects to prevent conflicts between applications and the sync daemon, creating a coordination layer that acts as a locking mechanism⁵⁶⁷.

The system implements intelligent throttling mechanisms designed to protect both device resources and server infrastructure. CloudKit throttles requests when it determines the request rate is too high, with 30-second minimum intervals between rapid operations⁵⁶⁷. This throttling serves as protection against overwhelming system resources and maintains server stability.

File coordination requirements create significant technical complexity for developers. Every file access requires coordination to prevent race conditions, and file presenters are “very expensive objects” requiring extensive inter-process communication⁸. Context switches occur between the reading process, presenting process, and file coordination daemon, risking depletion of system resources if too many presenters are registered.

Synchronization triggers operate on multiple system levels

Automatic triggers include app foreground events, network state changes, system resource availability, and device wake cycles. When an app comes to the foreground, especially on macOS, sync often triggers immediately⁹. Network connectivity changes - particularly switching from cellular to WiFi - initiate sync attempts. The system also monitors storage conditions, pausing sync when iCloud storage is full or device storage is constrained¹⁰¹¹.

Manual sync triggers are limited but exist through specific user actions. Users can force sync by toggling iCloud Drive settings off and on, signing out and back into iCloud accounts, or using app-specific refresh mechanisms like pull-to-refresh in Contacts and Calendar apps¹⁰¹¹. However, these methods don’t guarantee immediate sync - they merely request that the system prioritize sync operations.

Background app refresh plays a critical enabling role for sync operations. Apps must be granted Background App Refresh permission, and iOS uses machine learning to determine optimal sync timing based on user behavior patterns, available system resources, network quality, battery level, and time-of-day patterns¹²¹³¹⁴. The system can take “seven days for Apple’s on-device ML to pick up that the user really wants to use the app,"¹⁵ affecting sync frequency during this learning period.

Timing patterns follow intelligent resource management

Synchronization frequency varies dramatically based on system conditions rather than following fixed intervals. Apple’s documentation explicitly states that “CloudKit synchronization isn’t real time” and timing is “as-designed to better balance the use of system resources and achieve the best overall user experience."¹⁶ The system implements no guaranteed timing - sync operates on an opportunistic basis when conditions are favorable¹⁷¹.

Priority scheduling follows a clear hierarchy: foreground app operations receive highest priority, followed by critical system functions, user-initiated sync requests, scheduled background sync tasks, and finally opportunistic background sync. iOS uses BGTaskScheduler (iOS 13+) to replace legacy background fetch with more sophisticated scheduling based on device usage patterns learned over time¹⁸¹⁹²⁰.

Background execution limitations significantly impact sync behavior. Background App Refresh provides only limited execution time - typically 30 seconds for BGAppRefreshTask and longer durations for BGProcessingTask, but only when external power is available for heavy operations²¹²². Apps cannot force specific sync intervals and must work within iOS scheduling constraints where background execution is “cooperative” and can be terminated at any time.

App-specific behavior creates unique integration challenges

Obsidian’s vault synchronization exemplifies the challenges third-party apps face with iCloud Drive integration. User reports consistently describe unidirectional sync failures where “creating new notes in macOS syncs immediately to iOS, but editing notes in iOS doesn’t sync back to macOS."²³²⁴²⁵ Files frequently get “stuck uploading” with cloud icons showing indefinitely, and the app lacks native conflict resolution, leading to silent overwrites when notes are edited on multiple devices while offline.

Developer implementation challenges stem from iCloud’s low-level API requirements. Developers report that “the iCloud API is too low level,” requiring extensive code for basic operations with no single function for putting files into or removing them from iCloud²⁶. The asynchronous, cooperative, lock-based nature creates “implications that are often not easy to grasp,"²⁷ leading many developers to prefer alternatives like Dropbox for reliability.

Document-based versus file-based sync creates different user experiences. Document-based apps using NSDocument/UIDocument protocols benefit from automatic conflict resolution, while file-based sync (like Obsidian) relies on basic iCloud Drive file synchronization without built-in conflict handling²⁸. Advanced apps must implement custom conflict resolution UIs to match user expectations²⁹.

Sync interruption patterns follow predictable system states

Network-dependent behavior shows strong WiFi preference with cellular serving as a heavily throttled fallback. Even with cellular enabled, iOS implements intelligent throttling where sync only occurs over cellular when WiFi hasn’t been available for extended periods³⁰³¹. Low Data Mode specifically pauses iCloud sync operations³²³³, and users report that iCloud Drive downloads often fail over cellular connections even when uploads work³⁴.

Power management creates definitive sync boundaries. Low Power Mode automatically pauses all iCloud sync operations when battery drops below 20% and remains paused even when the device is charged until manually disabled³⁵³⁶³⁷. iOS displays “Optimizing Battery Power” messages when pausing sync to preserve battery life, and thermal management pauses operations when devices overheat with “Device Needs to Cool Down” messages³⁸.

Storage conditions create hard stops for synchronization. Sync completely halts when iCloud storage quota is exceeded, and iOS pauses sync when device storage drops below critical thresholds³⁹⁴⁰. The system displays specific status messages including “Low Data Mode,” “Poor Network Connection,” and “Device Needs to Cool Down” to communicate sync pause reasons⁴¹.

File prioritization follows system-managed algorithms

“Keep Downloaded” versus normal cloud storage creates two distinct sync behaviors. Files marked “Keep Downloaded” remain local even when storage optimization is active, while normal cloud storage uses on-demand download where files exist as placeholders until accessed⁴²⁴³. The system provides visual indicators through cloud/download status icons, and users can manually set Keep Downloaded status via context menus.

Sync prioritization algorithms aren’t fully documented by Apple, but research reveals patterns: the system prioritizes based on system resources first, then user experience considerations, data integrity requirements, and server load management. Large files are often deprioritized in favor of smaller, more critical data, and iOS may selectively sync metadata before file contents when storage is constrained.

Background versus foreground sync behavior creates dramatically different user experiences. Foreground sync typically works “within seconds” with immediate updates, while background sync can take “minutes or even up to an hour” depending on iOS scheduling decisions⁴⁴. macOS apps sync continuously while running, but iOS apps depend entirely on system wake-ups that follow learned usage patterns.

Network and battery conditions shape sync behavior

WiFi versus cellular sync patterns show strong system bias toward WiFi connections. Users must explicitly enable cellular data for iCloud Drive in Settings > Cellular > iCloud Drive⁴⁵⁴⁶⁴⁷⁴⁸, but even with cellular enabled, iOS implements aggressive throttling. The “Documents & Sync” system service can consume substantial cellular data (1-8GB reported cases)⁴⁹⁵⁰, leading iOS to discourage cellular sync through power management restrictions.

Battery state management creates multiple intervention points. Beyond Low Power Mode’s complete sync pause, iOS implements “Optimizing System Performance” states that pause sync to prioritize foreground tasks⁵¹. The system preferentially schedules heavy sync operations when devices are connected to power, with iCloud Photos specifically requiring power connection, WiFi, and locked screen for backup operations⁵².

Thermal management adds another layer of sync control where operations pause automatically when devices overheat. System-level thermal protection takes priority over sync completion, and users report that sync issues can persist even after cooling if the thermal event triggered system resource reallocation.

Background app refresh fundamentally enables sync functionality

Background execution architecture through BGTaskScheduler provides the foundation for non-foreground sync operations. The system grants limited execution time with tasks running when iOS determines optimal conditions exist: device charging, stable WiFi, learned usage patterns, and available system resources⁵³⁵⁴⁵⁵. Machine learning algorithms determine which apps deserve background execution time, with new devices requiring iOS to “relearn” app usage patterns⁵⁶.

App-specific background sync behavior varies significantly between foreground and background states. Active apps can immediately respond to file changes and trigger downloads, while backgrounded apps rely on silent push notifications and Background App Refresh scheduling⁵⁷. Suspended apps cannot perform any sync operations, and force-quit apps will not receive background wake-ups at all⁵⁸.

Background sync limitations create user experience challenges where sync can appear unreliable or delayed. iOS provides “opportunistic” scheduling rather than guaranteed execution, and background tasks are treated as “low priority” with delivery not guaranteed⁵⁹. Some apps implement “Incremental Sync” strategies to be more energy-efficient within these constraints.

Network connectivity creates distinct behavioral patterns

WiFi versus cellular behavior differences extend beyond data usage to sync reliability and speed. WiFi connections enable full-featured sync with immediate file downloads and uploads, while cellular connections often experience partial sync where uploads succeed but downloads fail. Users report that toggling between airplane mode and cellular can sometimes restart stalled uploads, suggesting iOS manages cellular sync more conservatively.

VPN and network security impacts create additional sync complications. Some VPN configurations block iCloud traffic entirely, and network security applications may interfere with sync operations⁶⁰. Enterprise MDM profiles often include restrictions that disable cloud sync⁶¹⁶², and corporate firewalls can selectively block iCloud synchronization traffic.

Network transition handling reveals system sophistication in managing connectivity changes. iOS automatically pauses sync during poor network conditions and resumes when connectivity improves. The system displays “Poor Network Connection” status messages and implements intelligent retry algorithms that avoid overwhelming weak connections⁶³.

Developer documentation reveals architectural constraints

Apple’s official technical documentation emphasizes that iCloud Drive operates as a system-managed service rather than application-controlled sync. WWDC sessions explicitly state “the system decides when to synchronize data” and “there is no API for app developers to force an iCloud Drive synchronization."⁶⁴ This architectural decision prioritizes overall device performance over individual app sync requirements.

File coordination requirements mandate that all iCloud operations use NSFileCoordinator objects and NSFilePresenter protocols. Apple’s Technical Note TN3162 reveals that CloudKit throttles applications when request rates are too high, with 30-second minimum intervals between rapid operations⁶⁵⁶⁶. These constraints protect system resources but create complexity for developers building sync-dependent applications.

Conflict resolution frameworks provide automatic handling for document-based apps but require custom implementation for file-based sync. Apple mandates that apps resolve conflicts “quietly whenever possible” and only prompt users when automatic resolution isn’t feasible⁶⁷⁶⁸⁶⁹. The system provides NSFileVersion frameworks for conflict detection but requires app-level logic for resolution⁷⁰.

Common sync issues follow predictable patterns

Most frequent problems include “Syncing with iCloud Paused” errors⁷¹, files stuck “Waiting to Upload/Download,"⁷² partial sync where some files sync while others remain pending, and “Zero KB of XGB” upload progress displays⁷³. Users also report missing files across devices, duplicate files with number suffixes during conflicts, and grayed-out files with exclamation mark cloud icons⁷⁴⁷⁵⁷⁶.

Diagnostic approaches range from basic connectivity checks to advanced terminal commands on macOS. Users can check sync status in Photos app status messages, monitor iCloud storage usage, verify app-specific sync settings, and test with small files to verify basic functionality. Mac power users employ terminal commands like brctl log -w --shorten for real-time sync monitoring and brctl status for container sync status⁷⁷⁷⁸⁷⁹.

Recovery strategies include both official Apple solutions and community-developed workarounds. Official methods involve device restarts, iCloud Drive setting toggles, and complete iCloud account refresh⁸⁰⁸¹⁸². Community solutions include VPN cycling, router restarts, time zone changes, and systematic network cycling routines⁸³. Advanced users employ mass file download scripts and automated sync health checks using command-line tools⁸⁴⁸⁵.

Third-party app interaction reveals system limitations

Apps like Obsidian face inherent challenges working within iOS sync constraints. The vault-based file structure requires reliable bidirectional sync, but iCloud Drive’s system-controlled timing creates user experience issues where edits made on iOS devices don’t propagate reliably to other platforms⁸⁶⁸⁷⁸⁸⁸⁹. Users frequently report directional sync failures and recommend keeping apps in foreground during critical sync operations.

Developer alternatives often include migrating away from iCloud Drive toward more predictable sync solutions. Many developers prefer Dropbox for its reliability and traditional file/folder approach, while others migrate to CloudKit for better control over structured data⁹⁰. Third-party sync solutions like Simperium offer more predictable behavior but require custom infrastructure.

Integration best practices that emerge from developer experiences include designing UIs to gracefully handle sync delays and failures, providing manual sync triggers for user-initiated operations, implementing proper state restoration for interrupted sync processes, and educating users about iOS sync limitations and optimal usage patterns⁹¹⁹².

Conclusion

iCloud Drive synchronization on iOS represents a sophisticated system-managed approach that prioritizes device performance, battery life, and user experience over application-controlled real-time sync. While this creates powerful integration capabilities within Apple’s ecosystem, it fundamentally changes how developers and users must approach cloud synchronization.

The key insight is that iOS treats sync as a system service rather than an application feature, implementing intelligent scheduling, resource management, and conflict prevention that operates beyond direct application control. This approach succeeds in protecting device resources and providing generally reliable sync for most users, but creates significant challenges for applications requiring predictable, real-time synchronization behavior.

For users of apps like Obsidian, understanding these system limitations helps set appropriate expectations and develop workflows that work within iOS constraints rather than against them. The future of iOS sync will likely continue emphasizing system intelligence over application control, making adaptation to these patterns essential for both developers and users relying on iCloud Drive synchronization.

Linearis, A Linear CLI Tool Built for Humans (and LLM Agents)

Wed, 03 Sep 2025 10:02:00 +0100

TL;DR: I built a CLI tool for Linear.app with JSON output, smart ID resolution, and optimized GraphQL queries; designed for LLM agents and humans who prefer structured data.

I use Linear daily, in all my projects. It just such a nice piece of thoughtful software. It’s fast, well-laid out, flexible without being overwhelming, and respectful of my time both as a planner and a dev. And it looks good.

It’s the anti-JIRA.

The last few months I’ve also been using Claude Code, sst/opencode, and charmbracelet/crush a lot. (Primarily CC.) And naturally, during that time, I wanted to be able to tell the agent to work on this ticket or update that ticket, so I used the official Linear MCP server. It worked great, no complaints.

The Problem(s)

Then one day I discovered the /context command in Claude, Code which gives a nice overview of what’s currently occupying its memory. Of the available 200k tokens, roughly 13k were taken up by the Linear MCP server alone – just by connecting and providing its tool definitions.

Now 13k tokens isn’t much if you’re working with models that have million-token context windows (hello, Gemini Pro). But when you’re dealing with 100k or 200k token limits, that’s a significant chunk of your available context – gone before you even start doing actual work.

Thinking about it, I realized that I am only using maybe three or four tools out of the 20+ that the Linear MCP server offers. Why spend tokens on project-management and workspace-setup features when I’m never going to use them? On top of that, I can’t use that MCP server in shell scripts.¹

My Solution: Linearis

I finally decided to scratch my own itch and build something focused on what I actually do with Linear on the command line and in agent prompts:

Create and update tickets
Add comments and labels
Search and filter issues
Manage ticket relationships

What I don’t do in these contexts is project management, workspace creation, or administrative setup. That stuff I handle manually in the UI when needed.

So I wrote Linearis, a CLI tool for Linear.app with JSON output, smart ID resolution, and optimized GraphQL queries. I designed it for LLM agents and humans who prefer structured data.

It’s a command-line tool that outputs JSON, resolves ticket IDs smartly, and keeps token usage light.

Installation

npm install -g --install-links czottmann/linearis

Once installed, authenticate yourself, and then you’re good to go.

Usage Examples

# Show usage
linearis

# Show *everything* the agent needs to know
linearis usage

# Create tickets with full context
linearis issues create "Fix login timeout" --team Backend \
  --assignee user123 --labels "Bug,Critical" --priority 1

# Create bare-bones sub-issues 
linearis issues create "Fix login timeout" --parent-ticket ABC-234

# Smart ID resolution - works with ABC-123 format
linearis issues read DEV-456
linearis issues update ABC-123 --state "In Review"

# JSON output plays nice with other tools, like jq
linearis issues list -l 5 | jq '.[] | .identifier + ": " + .title'

# Add comments to track progress
linearis comments create ABC-123 --body "Fixed in PR #456"

Using Linearis in a LLM agent

It’s agent-friendly by design. The key idea was making it dead simple for LLM agents to understand and use the tool:

linearis usage

This single command returns comprehensive yet concise usage information for all available tools. Agents can pipe this directly into their context and immediately understand everything the tool can do.

The flags and options are well-documented and consistently structured, so agents can easily call it through their Bash tools without any special integration.

So I put this in my CLAUDE.md:

We track our tickets and projects in Linear (https://linear.app), a project management tool. We use the linearis CLI tool for communicating with Linear. Use your Bash tool to call the linearis executable. Run linearis usage to see usage information.

The ticket numbers follow the format “ZCO-”. Always reference tickets by their number.

If you create a ticket, and it’s not clear which project to assign it to, prompt the user. When creating sub-issues, use the project of the parent ticket by default.

When the the status of a task in the ticket description has changed (task → task done), update the description accordingly. When updating a ticket with a progress report that is more than just a checkbox change, add that report as a ticket comment.

That’s probably overly verbose, I guess. 😉 Some examples for prompts I use daily:

“we’re working on ABC-1234 now”
later: “add a progress report to the ticket”
“mark ABC-2345 as ‘in progress’"
“make this a sub-issue of ABC-3456”
“mark ABC-4567 as a bug”

The Result

I’ve been using Linearis for a while now, both manually and with my agentic tools. It does exactly what I need it to do without the overhead I don’t need. The agents can create tickets, update them, add comments, and manage labels efficiently. And when I need to do project setup or workspace management, I just use Linear’s web UI.

Sometimes the best tool is the one that doesn’t try to do everything – just the things you actually need, done well. Linearis solves my particular requirements, but I think it might be helpful to you, too.

Check it out on GitHub.

I know I could, technically, but I’m not an insane person. 😉 ↩︎

Mon, 01 Sep 2025 15:34:27 +0100

I finally pulled the trigger on booking the Danish language course (level A1) at our fine local Dansk Centralbibliotek 🎉

2 weeks, 40h – the “pressure-cooker” version to get started!

Why? Well, Denmark is right around the corner, we moved here 3+ years ago, and at this point, me still not being able to speak the language feels rude somehow. 😉 Also, it opens up opportunities. I mean, we’re still toying with the idea of moving farther North. Who knows?

Dear creators, I am judging your Nazi-enabling

Wed, 27 Aug 2025 17:42:26 +0100

Dear creators,

Hosting your newsletter on Substack or posting on X says “I am fine with my Nazi neighbours”. Because that’s what these platforms are: Nazi bars, run by right-wing people and fascists.

Using them as a creator means that you are actively helping them grow and succeed. Your brain power and creations are propping up their Klan crosses. There’s no two sides to seeing this, there simply isn’t. Whatever your reasons, you are not only tolerating what they do, you directly and indirectly help legitimize their shit, and help them make money.

And for that I do judge you. Yes, I might dig your personal blog or tech newsletter or whathaveyou, but you are part of the problem. Both those things can be true. Because it’s 2025, and we’re way past beyond the “I didn’t know they are bad” phase. We all know. You don’t get a pass anymore.

Because the thing is: There’s no reason anymore to use those bad actors and their platforms. You do not have to. Yes, we heard your arguments about reach and whatnot, but right now, a big ass portion of your reach is bot accounts and fans of fascism.¹ There are a great many viable alternatives for pretty much all your use cases, including social media and blog + newsletter hosting – and believe me, among your friends, readers, and followers there are folks who will help you move. Just ask around, FFS.

And if you don’t find anyone, send me an email or a skeet or a toot, I’ll help you get going.

And if you happen to like this part of your fanbase, then by all means, fuck the fuck off. ↩︎

BarCuts: Building a Contextual macOS Shortcuts Launcher

Fri, 15 Aug 2025 22:00:00 +0100

Sometimes the best software comes from scratching your own itch. That’s definitely the case with BarCuts, my take on a contextual macOS Shortcuts launcher. What started as a personal annoyance turned into a proper little utility that I’m genuinely proud of – and it’s been quite the journey getting here.

The Problem That Started It All

Picture this: you’ve got dozens of Shortcuts workflows on your Mac. Some are for processing files in Finder, others for grabbing URLs from Safari, maybe a few for formatting text in your notes app. But they’re all just sitting there in the Shortcuts app, or worse: in Shortcuts' own menu bar, mixed together in one giant list with no context about when you’d actually want to use them.

I kept thinking: wouldn’t it be nice if the right workflows just appeared when you needed them? Like, when I’m in Finder, show me my file-processing workflows. When I’m in Safari, Chrome, Edge, or another browser, show me my web-related ones. Context-sensitive launching, basically.

Turns out, that’s exactly what I ended up building.

YouTube Video

(Note: The image above is a video embed. If it doesn’t load for you, here’s the video: BarCuts: A Surprisingly Useful macOS Shortcuts Launcher (2025.4).)

What BarCuts Brings To The Table

As an example, let’s pretend you have a Shortcuts workflow named “Get today’s appointments” which fetches your appointments from the calendar, and which you only ever need when working in Notes. Here it is in the Shortcuts editor:

The BarCuts Tagger panel for tagging your workflows to one or more apps. (v2025.4)

You want this workflow to be available in BarCuts whenever the Notes app is in front. So you’ll find the floating panel titled “BarCuts Tagger” next to the window, and “tag” Notes as a related app to this Shortcuts workflow, as shown above.

Now, BarCuts' menu will list the workflow when Notes is the frontmost app:

The workflow we tagged with the Notes app is shown in BarCuts' menu because Notes is in front

And that’s all there is to it!

The menu can be opened with the mouse, but you can also configure a global hotkey that will open it, in the app’s Settings tab. Alternatively, you could also hook up BarCuts to Alfred, or connect it to your Raycast.

Timeline, or: Everything’s A Journey Now

Prototype: Actions-Based Tagging

My initial approach was pretty straightforward (and, in hindsight, a bit naïve). I created a special Shortcuts action called “BarCuts Tagger” that you’d add to your workflows. You’d configure it with the app you wanted to associate the workflow with — say, “Finder” — and BarCuts would watch for when that app was active and surface the relevant workflows in its menu bar.

The BarCuts Tagger action. (v2025.1)

It worked! The concept was solid, and I was pretty pleased with the initial implementation. Little did I know there was a significant problem lurking that I wouldn’t fully appreciate until later…

The Public Beta

In February 2025, two weeks after starting the project, I launched the public beta, and the initial feedback was encouraging! People got the concept and found it useful.

Shortly thereafter, I properly launched version 2025.1. 🚀

Version 2025.2: A Reality Check

But as I was working on version 2025.2, I started hearing from more users about a problem I hadn’t fully grasped initially. To be honest, most of my own tagged workflows are macOS-only anyway, so I rarely ran into the sharing or iOS compatibility issues that were frustrating other people.

I realized there was this massive, glaring problem with my original approach: your workflows were no longer “clean.” They had this Tagger action cluttering them up, which meant:

You couldn’t share them with anyone who didn’t have BarCuts
They’d throw errors on iOS (where BarCuts obviously doesn’t exist)
Your beautiful, artisanal workflows suddenly had this extra cruft in them

My practical approach turned out to be the opposite of elegant.

Despite this workflow pollution issue, I kept working on BarCuts because the core concept was still solid. Version 2025.2 was all about “connectivity”: I added proper scripting support, built companion extensions for Alfred and Raycast, and included a CLI tool for my fellow automation nerds.

Because a launcher like that shouldn’t be a closed system. If you prefer launching workflows from Alfred or Raycast instead of the menu bar, great – you should be able to do that and still get the contextual filtering that makes the app useful.

I also finally got around to writing proper documentation.

Version 2025.3: Polish and Fixes

Better settings, fixed some annoying bugs, improved the workflow execution system. The kind of update that doesn’t look like much from the outside but makes everything feel more solid and reliable.

During that time my old #1 problem was rearing its fugly head again: building the software is actually the easy part. Getting people to notice a new Mac utility? That’s the real challenge. Turns out there are lots of great apps that barely anyone knows about because, well, marketing is hard. Who knew?

I was trying to get the tech news and pundits interested in earnest. Nobody cared. 🫤

Version 2025.4: The Present

And that brings us to the latest update, which I’m genuinely excited about because it finally got around to solving that nagging workflow pollution problem I mentioned earlier.

I completely replaced the old Shortcuts action approach. Instead, BarCuts now adds a floating “BarCuts Tagger” panel directly to the Shortcuts editor. When you’re editing a workflow and BarCuts is running, you’ll see this lovely little panel floating next to your workflow window:

Here’s the nice bit: your workflows remain “clean”. No more BarCuts actions. You can share them with anyone, run them on iOS, whatever – they’re just normal Shortcuts workflows, as they should be. Lesson learned.

To tag a workflow now, you open it in Shortcuts and use the floating panel to tag it to whichever apps you want. You can even tag a single workflow to multiple apps if it’s useful in different contexts. Or put it in a submenu for even more structure.

All existing tagged workflows get migrated automatically, and if you still have old BarCuts actions lying around, the app will help you clean them up.

How It Works Today

The current BarCuts experience is dead simple:

Install the app and grant it the necessary permissions
Open any workflow in Shortcuts
Use the floating panel to tag it to relevant applications
Switch to one of those apps, and your tagged workflows appear in the BarCuts menu bar

That’s it. No actions to configure, no workflows to modify, no compromises on shareability.

Why This Matters

Look, I know there are lots of ways to launch Shortcuts workflows. Spotlight search, the Shortcuts app itself, various launcher apps – they all work fine for what they do.

But BarCuts does something different: it surfaces the right workflows at the right time. When you’re in Finder and want to process some files, you don’t want to see your Safari bookmarking workflows cluttering up the list. When you’re writing in Notes, you want your text-processing workflows front and center, not your photo editing ones.

It’s about reducing cognitive overhead. Instead of remembering which workflow does what and hunting through lists, the relevant ones just appear when you need them.

And now, with the floating panel approach, you get all that contextual goodness without any of the workflow pollution that was holding people back.

What’s Next?

I’ve got a proper backlog of ideas for future updates. Keyboard shortcuts for the menu, bulk workflow configuration, maybe some deeper integration with other automation tools – the usual “wouldn’t it be cool if…" stuff that keeps me up at night thinking about software.

But for now, I’m pretty chuffed — chuffed!! — with where BarCuts has ended up. The core concept is the same as when I started, but its implementation is cleaner now.

Give It a Whirl

If you’re a macOS Shortcuts user who’s ever felt overwhelmed by a growing collection of workflows, BarCuts might be worth a look. There’s a 14-day trial, no strings attached, and the app works with macOS 14 and later.

You can download it from the website, and if you want to chat about automation or share your setup, the ActionsDotWork Forum is full of friendly folks who love this stuff as much as I do.

P.S. Building and launching an indie Mac app has been quite the education. If you’re curious about that journey — the technical challenges, the marketing struggles, the weird satisfaction of solving problems for yourself and maybe a few other people — drop me a line. Always happy to chat about the indie dev life!