Unauthoritative Pronouncements

Scharon Harding’s post for ArsTechnica starts with the UK, but it gets around the globe.

For the US, the recommendation garnering the most attention is one calling for a 5 percent levy on UK subscriber revenue from streaming video on demand services, such as Netflix. That’s because if streaming services face higher taxes in the UK, costs could be passed onto consumers, resulting in more streaming price hikes. The CMS committee wants money from the levy to support HETV production in the UK and wrote in its report:

The industry should establish this fund on a voluntary basis; however, if it does not do so within 12 months, or if there is not full compliance, the Government should introduce a statutory levy.

Calls for a streaming tax in the UK come after 2024’s 25 percent decrease in spending for UK-produced high-end TV productions and 27 percent decline in productions overall, per the report. Companies like the BBC have said that they lack funds to keep making premium dramas.

This is all very ironic if you have been following the generous tax rebates that the UK provided to lure global production to the UK for pre-production, filming, post-production, etc. They are very generous subsidies that have all kinds of little rules and loopholes that get updated over time.

Instead of lowering those hefty rebates for international productions in the UK they want to tax subscriptions of international streaming services.

In a statement, the CMS committee called for streamers, “such as Netflix, Amazon, Apple TV+, and Disney+, which benefit from the creativity of British producers [Joe: and our enormous tax rebates], to put their money where their mouth is by committing to pay 5 percent of their UK subscriber revenue into a cultural fund to help finance drama with a specific interest to British audiences.[Joe: Unlike the content that they are paying to subscribe to which is definitely of no interest whatsoever to British audiences.]” The committee’s report argues that public service broadcasters and independent movie producers are “at risk,” due to how the industry currently works [Joe: We’re all trying to find the guy who did this!]. More investment into such programming would also benefit streaming companies by providing “a healthier supply of [public service broadcaster]-made shows that they can license for their platforms [Joe: Is there a term when something goes beyond double-dipping?],” the report says.

As Scharon notes, the same applies to Canada, which has eye-watering tax rebates in Montreal and Vancouver, but at the federal level, Canada wants to slap a 5% levy on streaming services. It’s just wild.

I know it’s rich for me, a guy in a country that turned tariffs on and off like a child playing with a light switch, to comment on the affairs of other countries, but I do feel at least a little affected by it.

It’s been one year since I was laid off from my VFX studio job after being furloughed for six months due to the dual labor strikes in the US, and a possible third. What production has resumed has mostly resumed abroad. Sound stages in LA are only at 63% capacity. Post production is even easier to do outside of the US, with my former employer exclusively hiring in other countries for positions like the one I did –but I did it in LA. This is a little less like trying to bring back coal mining jobs. I’m talking about jobs that were there 18-24 months ago.

It’s darkly funny (to me, anyway) to distort a market through tax rebates on foreign productions, then swoop in and demand money from subscriptions to foster locally-owned production. If a government wants to fund the production of local culture then they should funnel their money there to begin with by appropriately taxing foreign productions instead of trying to capture the revenue, after the fact, of the foreign system they’re supporting.

Adobe has a new blog post up outlining their vision for “agentic AI” in Adobe’s products.

At Adobe, our approach to agentic AI is clear, and it mirrors our approach to generative AI: The best use of AI is to give people more control and free them to spend more time on the work they love – whether that’s creativity, analysis or collaboration.

We’ve always believed that the single most powerful creative force in the world is the human imagination. AI agents are not creative, but they can empower people – enabling individuals to unlock insights and create content that they wouldn’t otherwise be able to and enabling creative professionals to scale and amplify their impact more than ever. For people at all levels, agentic AI’s potential makes starting from templates feel stale and old-fashioned. For professionals, it offers a pathway to growing their careers by freeing up time to do more of the things only they can do.

From Abby Ferguson’s post on DPReview covering this:

Last week, Adobe announced that a handful of AI-based features would be moving out of Premiere Pro beta. Now, the company is teasing even more AI tools for Premiere Pro and Photoshop ahead of Adobe Max London on April 24. In a blog post, the company provides a basic overview of what’s coming, promising even faster edits and helpful tools for learning.

We certainly see “agentic” used a lot these days, but most of the time it’s the retail-fantasy scenario that an LLM agent will buy or book things on your behalf. Capitalism, bebe.

This is more like GitHub Copilot in VSCode where there is a back and forth, with a result that is still something the user has control over if they choose to. The work is in layers, with edits applied in a non-destructive fashion in many cases.

Back to Abby Ferguson:

Adobe says this isn’t exclusively about speeding up the editing process. Instead, it also envisions the creative agent as a way to learn Photoshop. Given how complex and overwhelming the software can be for new users, such a resource could be helpful. Plus, Adobe says it could also handle repetitive tasks like preparing files for export.

One of the major problems I have with generative AI for images and video is that the output is basically clip-art or stock footage. It’s smearing together associated patterns it was trained on and delivering a final result. The only way to continue to edit or refine the result is through text commands which can have sweeping changes on things you did not want to change, and have no easy way to control yourself.

Solutions that integrate with an image, or video, editing workflow allow for the level of control a person might need for their job. In many cases, where some doofus on LinkedIn is asking AI to make them look like an action figure package, or for Ghibli art of their dog, they don’t care about control at all, but that’s because it’s not a job. They don’t answer to a client that wants something nudged, not replaced.

There’s no easy way to directly link to the videos from Adobe’s blog post previewing these things, but the video you want to watch is the second one under the Photoshop subhead.

There are, of course, all of the other issues with generative AI, but this type of work from Adobe is far more interesting than making the smearing machine smear better, or adding new “styles” to the smearing machine so we can all have exactly the same “art”.

It’s important to remember that if everyone can “make” the same stuff, and they all have the same level of non-control over it then there’s nothing that really distinguishes that stuff. Here’s the potential to learn and decide on the changes being made branching off using your own brain and your own skills.

My blog is made by a rube, if you will. This site is a static blog generator that’s basically a single 300-ish line Python script from 2014. I was “inspired” to make it when static site generators were all the rage and I figured it would help me with my Python skills, as Python is a language often used in VFX software. I don’t recommend people use any of my code, or write their own site like this. There are better ways to spend your time.

I’ve periodically written about the changes to my site over time, like when I made the jump from Python 2 to 3, and transitioned servers back in October of 2023. We’re overdue for an update. Especially as I have been tinkering quite a bit, and it happens to coincide nicely with ATP’s recent episode member’s-only episode on their own sites. I might as well start from the top.

Caddy

Caddy serves the files. I had originally used Twisted on my old server, because it’s in Python, but I could never figure out how to get the certificates working in Twisted and Caddy just works. I don’t even have to know Go. I can’t recommend it highly enough if you’re looking for a simple solution to just serve files.

Yakbarber3

The python script that makes this whole mess is yakbarber.py, and then when I converted it to Python 3, I named it yakbarber3.py so I could run the two versions to make sure the output was the same (it was close enough).

It takes markdown files from /content converts them to HTML and uses mustache templates to wrap the HTML with the necessary headers, and such. Also to generate the RSS/Atom feed. The results went into /output. That’s more or less how it worked for over 10 years, and is basically how it continues to work. You can see the commits for everything as I worked through various parts of it over the past month.

The site settings live in another file and were imported with the imp module. Yes, that module is deprecated in Python 3 and it would generate a warning every time it ran, even though it would run successfully. I asked Gemini or Copilot, I can’t remember which and it suggested switching it out for importlib.util.module_from_spec() and it’s fine.

That’s another thing that’s changed in 11 years. I used to have to search StackOverflow for a problem that matched the problem that I had, or was close enough, and then try to kludge together something that fit my needs. I never figured out how to properly replace imp but I’m sure someone wrote about it somewhere. Now I can query LLMs that have paid StackOverflow and they synthesize something that more closely matches my situation.

They’ve been total horseshit at making things from scratch, and I don’t just blindly accept their output, but they do help me when I get stuck on something I don’t know. More importantly, I can look at their solution and then figure out there’s a better way to do this. I’m not “vibe coding” but it is more of a back and forth.

My feelings on LLMs are nuanced, especially where creativity is concerned. Being able to get me through a roadblock is not the same thing as “make my whole web site” which I think is a valueless proposition. Indeed, I did ask it to write a static blog generator using the same specs as my blog and it wasn’t what I wanted. I don’t see the appeal in just letting LLMs dictate the whole thing.

Watchdog

Case in point: I wanted to add support for yakbarber3.py to monitor for changes to the /content directory, or the mustache templates, and then regenerate the site automatically without me having to run the script. The solutions were to either use inotify outside of my script to run it when files were changed, or to use watchdog (a python module which would be inside the script itself) to monitor for changes. I decided on watchdog because I want to continue to refine what files are read and written to disk in the future, and this seemed like the best way to achieve that.

I used Copilot in VSCode — everyone’s raving about the thing so why not try it? It did a decent job constructing what I asked for. It would monitor those directories for changes, and only for the specified file types.

class ChangeHandler(FileSystemEventHandler):
     def on_modified(self, event):
         if event.src_path.startswith(contentDir) and (event.src_path.endswith('.md') or event.src_path.endswith('.markdown')):
             print(f"Detected change in {event.src_path}. Re-running main()...")
             main()
         elif event.src_path.startswith(templateDir):
             print(f"Detected change in {event.src_path}. Re-running main()...")
             main()

     def on_created(self, event):
         if event.src_path.startswith(contentDir) and (event.src_path.endswith('.md') or event.src_path.endswith('.markdown')):
             print(f"Detected new file {event.src_path}. Re-running main()...")
             main()
         elif event.src_path.startswith(templateDir) and (event.src_path.endswith('.html') or event.src_path.endswith('.xml')):
             print(f"Detected new file {event.src_path}. Re-running main()...")
             main()

I needed to refine the sleep interval between times it started, and I also wanted to make sure that a bunch of successive changes that happened quickly wouldn’t cause the main() loop to be triggered. Copilot suggested a debounce timer.

    def schedule_main(self):
         global debounce_timer
         if debounce_timer is not None:
             debounce_timer.cancel()
         debounce_timer = threading.Timer(3.0, self.run_main)  # 3-second debounce window
         debounce_timer.start()

     def run_main(self):
         global is_running
         if not is_running:
             is_running = True
             try:
                 main()
             finally:
                 is_running = False

Like I could study reference materials about how to implement this, but again, I wouldn’t really know where to start or what I was trying to do without a lot of other programming experience that was not going to be relevant to the rest of my life. This tool doesn’t make me a professional programmer, it just helped me with a hobby project, and I know just enough about it to understand and edit it.

Oops, All Loops

One big problem that I had not anticipated was that the script was original written to modify variables as they fell down through the functions. That meant that when watchdog would start the loop over that several variables wouldn’t be reset and would behave in an unexpected manner. Copilot was no use for debugging this. It suggested I put print statements everywhere, but it was entire blog posts, so that’s too much printing to be useful.

However, I correctly diagnosed that the problem was my poorly written code from my original script. I separated out the parts that were writing over data, and I also reduced the number of places that data was being sorted. That was tricky, like untangling cables from that box of cables that you 100% keep meaning to individually bundle.

I couldn’t have vibe-coded my way through this, but it was useful to be able to highlight a specific line and ask Copilot what the change I made would do, just to double check my work.

Async

One of the recommendations Copilot provided —you can just ask for its “opinion” on things— was that I should asynchronously render the blog post pages (not the index or the RSS feed). This was my first time using Python’s async library so I got to see how my serial scripting turned into async scripting.

It’s mostly the same, but I get to use fun words like with lock and asyncio.gather. Instead of def I get to use async def. This was not as intimidating as I thought it was going to be, and I knew exactly where it would be applied.

Changes I Rejected

There were a lot of changes that Gemini and Copilot suggested that I just didn’t feel like implementing. Gemini would just rewrite swaths of it to where the code was unrecognizable. Copilot had a few occasions where it barfed on a change (it started to reprint the imports all over again in the middle of the file).

Both of them really wanted me to move from mustache templating to jinja2. They don’t really “want” it, exactly. There’s a higher probability that someone recommended jinja2 templating, which means that I get to have that suggested. I saw plenty of people say this online in 2014 when I picked mustache over jinja2. Mustache templating suits my needs and is very easy.

Rejecting the change is simple, but it’s interesting that dogma about template preferences could steer someone who didn’t know what they wanted to jinja2. No shade no lemonade on jinja2, but it can be overkill if your templating needs are relatively simple.

Sync_to_serve

Previously, I used a bash script named site_build.sh to run yakbarber3.py and then copy all the files from output and the template resources to the directory that actually serves the files. I don’t write the files my site generates to the directory that serves them because I want to reduce the chances that something will break and then my site won’t serve any files. Also I didn’t have the mime type and redirect set up correctly for joe-steel.com/feed so the old way I did it was to make a copy of the feed.xml file that just didn’t have a file extension. Very hacky.

This superstition about keeping site generation and site serving separate meant that I wanted to replace the bash script for the always-running, always-looping yakbarber3.py to monitor for changed files to copy over. Since I was already using watchdog to do that in the site generator script, it seemed natural for me to continue with that. Thus, I put together sync_to_serve.py.

import os
import shutil
import time
from watchdog.observers import Observer
from watchdog.events import FileSystemEventHandler
import fnmatch

SYNC_DIRECTORIES = {
    "output/path": "server/path",
    # Add more source-destination pairs as needed
}

FILE_PATTERNS = ["*.html", "*.css", "*.xml"]

class FileSyncHandler(FileSystemEventHandler):
    def __init__(self, source_directory, destination):
        super().__init__()
        self.source_directory = source_directory
        self.destination = destination

    def on_modified(self, event):
        if not event.is_directory and self.matches(event.src_path):
            self.sync_file(event.src_path)

    def on_created(self, event):
        if not event.is_directory and self.matches(event.src_path):
            self.sync_file(event.src_path)

    def matches(self, src_path):
        filename = os.path.basename(src_path)
        for pattern in FILE_PATTERNS:
            if fnmatch.fnmatch(filename, pattern):
                return True
        return False

    def sync_file(self, src_path):
        try:
            relative_path = os.path.relpath(src_path, self.source_directory)
            dest_path = os.path.join(self.destination, relative_path)
            os.makedirs(os.path.dirname(dest_path), exist_ok=True)
            shutil.copy2(src_path, dest_path)
            print(f"Synced: {src_path} -> {dest_path}")

            # Special case for feed.xml
            if os.path.basename(src_path) == "feed.xml":
                feed_dest_path = os.path.join(self.destination, os.path.dirname(relative_path), "feed")
                shutil.copy2(src_path, feed_dest_path)
                print(f"Synced: {src_path} -> {feed_dest_path}")

        except Exception as e:
            print(f"Error syncing {src_path}: {e}")

if __name__ == "__main__":
    observers = []
    for source_dir, destination_dir in SYNC_DIRECTORIES.items():
        event_handler = FileSyncHandler(source_dir, destination_dir)
        observer = Observer()
        observer.schedule(event_handler, source_dir, recursive=True)
        observer.start()
        observers.append(observer)

    try:
        while True:
            time.sleep(1)
    except KeyboardInterrupt:
        for observer in observers:
            observer.stop()
        for observer in observers:
            observer.join()

This is significantly longer than the bash script, of course, but pretty straight forward in that it does a one-way copy, like the older script did. It just does it continuously.

CSS and JavaScript

The other thing that I’ve changed on the site is the CSS and some JavaScript. I hate JS. It’s this weird thing that looks sort of like python, but behaves in different ways. I had a very specific thing that I wanted to do, which was format the date and time displayed on each post to be localized, and also pleasant to look at. Gemini instantly kicked out the code I needed and I added it to my template.

 function localizeDates() {
  const dateElements = document.querySelectorAll('.date date');

  dateElements.forEach(dateElement => {
    const datetimeString = dateElement.getAttribute('datetime');
    if (datetimeString) {
      const date = new Date(datetimeString);
      if (!isNaN(date)) {
        const localizedString = date.toLocaleString(undefined, {
          year: 'numeric',
          month: 'long',
          day: 'numeric',
          hour: 'numeric',
          minute: 'numeric',
        });
        dateElement.textContent = localizedString;
      } else {
        console.error("Invalid date format:", datetimeString);
      }
    }
  });
}

// Call the function when the DOM is loaded
document.addEventListener('DOMContentLoaded', localizeDates);

That only took me a decade to get around to. It’s much better now.

Likewise the CSS problems on my site were always around. I had separate font-sizes for mobile and desktop. Sometimes people would reach out to tell me that my site was rendering incorrectly, for example when they used StopTheMadness in Safari. The developer, Jeff Johnson, helped me figure out what the problem was. I had never set:

<meta name="viewport" content="initial-scale=1.0">

So in a regular mobile Safari browser it had some weird scale which I had worked around, and now needed to undo that. It felt like a huge relief to clean that up.

Post Formatting Automations

Now that I had a site that could monitor for changes and regenerate itself without me having to sign in through SSH, I needed to make posting easier. One of the irritations with posting is that I have YAML front matter in my blog posts that needs to have certain information present.

Title: My Clever Title Here
Date: YYYY-MM-DD 24:00:00
Author: joe-steel
Category: text

There are optional YAML entries for Link which formats the post as a link-blog post with a permalink, and makes the header point to the original source. The other YAML is Image which sets an opengraph image to use for the post if I want one.

The date and time are the annoying part as the rest of it is just copy and paste. I have repeatedly made silly mistakes when I format the date and time just due to human error.

I don’t want the blog generation to write the date and time for me because I don’t want it to accidentally overwrite things in the files —right now it’s read-only when it works with the markdown.

I do want this to be multi-platform so I can write posts when I’m not with my computer. That means I need iOS support. That means Shortcuts. Sigh.

That was what that whole post complaining about time zone conversion was about. I finally conquered it and it could produce the formatted date and time on command, but it was a pain. Also I couldn’t figure out how to easily do it for a file that I had already written. It was easy to write out this stub, but I didn’t want to do that when I started writing or the date and time would be off by the time I had finished.

Drafts

That’s when I turned to Drafts. Greg Pierce does an amazing job with Drafts, but I use approximately 0.1% of its full potential. I had never successfully automated anything in it before.

Fortunately, Drafts can run JavaScript, and while I hate JavaScript, I know JavaScript can very easily handle the date logic. To protect all of the little babies, Apple doesn’t let us run JavaScript in Shortcuts unless it’s JS on an active page in Safari.

I also know that I don’t even have to write the JS. Just explain the logic to Gemini, or whatever. I also know JS can split the lines to turn the top line of the draft text into the title, and then everything else goes below as the body. It’s also amended so that it can handle the extra YAML, or if I run it again on a file that already has a header.

let options = { timeZone: 'America/Los_Angeles', year: 'numeric', month: '2-digit', day: '2-digit', hour: '2-digit', minute: '2-digit', second: '2-digit', hour12: false };
let now = new Date();

// Round to the nearest 5-minute interval
let minutes = now.getMinutes();
let remainder = minutes % 5;

if (remainder < 3) {
  now.setMinutes(minutes - remainder);
} else {
  now.setMinutes(minutes + (5 - remainder));
}

now.setSeconds(0, 0); // Reset seconds and milliseconds

let date = now.toLocaleString('sv-SE', options).replace(/:[0-9]{2}$/, ':00');

let title = draft.title;
let body = draft.content;
let lines = body.split('\n');

let yamlTitle = null;
let yamlDate = null;
let yamlAuthor = null;
let yamlCategory = null;
let yamlLink = null;
let yamlImage = null;
let nonYamlLines = [];

// Check for existing YAML-like lines
for (let i = 0; i < lines.length; i++) {
  let line = lines[i].trim();
  if (line.startsWith('Title: ')) {
    yamlTitle = line;
  } else if (line.startsWith('Date: ')) {
    yamlDate = `Date: ${date}`; // Update Date
  } else if (line.startsWith('Author: ')) {
    yamlAuthor = line;
  } else if (line.startsWith('Category: ')) {
    yamlCategory = line;
  } else if (line.startsWith('Link: ')) {
    yamlLink = line;
  } else if (line.startsWith('Image: ')) {
    yamlImage = line;
  } else {
    nonYamlLines.push(lines[i]); // Keep all other lines, including empty ones
  }
}

// Remove leading empty lines from nonYamlLines
while (nonYamlLines.length > 0 && nonYamlLines[0].trim() === '') {
    nonYamlLines.shift();
}

// Construct the new YAML section
let newYaml = [];
if (yamlTitle) {
  newYaml.push(yamlTitle);
} else {
  newYaml.push(`Title: ${title}`);
}
if (yamlDate) {
  newYaml.push(yamlDate);
} else {
  newYaml.push(`Date: ${date}`);
}
if (yamlAuthor) {
  newYaml.push(yamlAuthor);
} else {
  newYaml.push(`Author: joe-steel`);
}
if (yamlCategory) {
  newYaml.push(yamlCategory);
} else {
  newYaml.push(`Category: text`);
}
if(yamlLink){
    newYaml.push(yamlLink);
}
if(yamlImage){
    newYaml.push(yamlImage);
}

// Combine YAML and non-YAML lines
let newBody = newYaml.join('\n') + '\n\n' + nonYamlLines.join('\n');

draft.content = newBody;
draft.update();

This took significantly less time than trying to get Shortcuts to do this. It does mean that I have to use Drafts if I want access to this, but if I’m on the go, I’d likely be writing a short post, which could be in Drafts. Then I save that to my /content folder in Dropbox, yakbarber3.py sees the file, and regenerates the site, which sync_to_serve.py copies to the directory that serves the static files. It’s a simple 5-ish step process with most of it automated.

The moment where all this worked was when I wrote my link-blog post yesterday. I was a few thousand feet in the air and it published. I even had a mistake, where there was an errant new-line that pushed the Link: YAML down a line and it processed it as a regular post. I fixed the file, and it just regenerated as the expected link-blog style post it was supposed to be.

Future Plans

In the future, I want to handle draft posts with status in the YAML for draft or published. Then it can generate the page so I can check formatting without it adding to the RSS or index.

I also want to have YAML defaults for certain tags, like author, and category. It is extremely unlikely that anyone else will be writing on my blog, or I’ll use a category other than text. This YAML is a legacy of my original export and import process where I used Pelican to get my very old Tumblr posts. It’s superfluous.

I also want to handle scheduled posts with the date YAML. Where it will hold the site generation step until the time stamp is reached. Sometimes I finish writing something at night but I know no one’s going to read it, and it’ll get buried under new posts in the morning. For that to work, I really can’t have human error in the stamps.

Mastodon integration would also be nice where the blog has its own account. I might use Robb Knight’s echofeed. I couldn’t even explain why I’m not using it already.

Lastly, I need to come up with a better system to handle images. Whenever there are images on this blog I have manually uploaded them to directories on my server and then copied the paths back to put into the blog posts. It’s a very annoying step. I don’t want to just throw a bunch of images into /images because that will just be a mountain of clutter. I can always make more YAML —more YAML, more problems. I could have named subdirectories in /images that use a relative path so I could see the images in draft previews, and count on them to be copied correctly. That creates two copies of all my images though.

The important thing is that I can keep screwing around with this. It is very satisfying when I get some part of this working the way I want it to, and that makes all the frustrations worthwhile.

Again, I don’t recommend anyone do any of this, or use anything that’s here. Use Ghost, or even another off-the-shelf platform that has support so you don’t have things standing in the way of you writing your blog. Think of all the blog posts I could have written if I wasn’t trying to make sure my mustache was asynchronous?

Jason Snell wrote about how he rejoined Netflix on the ad-supported tier, and it was a poor experience for him. Not only because he’s not used to seeing TV shows with ads these days, but because Netflix shows aren’t always made with ads in mind.

While the ads played on, I began creating a thought experiment: There’s a $10 difference between the ad and ad-free plans. If Mr. Netflix (he wears a top hat) came to my house and said, “Jason, I’ve got a great deal for you. I’m going to pay you $120 a year, and all you have to do is watch ads while you watch Netflix,” what would I do? When I started thinking about it, I thought it might be an interesting intellectual question. What would I accept in exchange for having Mean Mr. Netflix beam ads into every show I watch?

It’s worth also thinking about every other streamer too. I know Jason’s not singling out Netflix as if it’s the only one doing it, but it certainly charges the highest premium to escape its ads.

I absolutely have to pay for YouTube Premium because the quality of the ads is so poor, not because the cuts don’t fit with the drama. Other people are used to the ads in YouTube because that’s what that experience has “always been” for them.

Also consider the gentle buzzing of incessant ads slotted into old reruns made for ad-supported broadcast and cable TV on FAST and AVOD services. It can have a very different feel because of what your personal expectations are, and your level of engagement with the programming. You’re folding laundry, so who cares how many times that Skyrizi jingle runs on the Gunsmoke channel? It’s very different from a show like Adolescence.

We know Mean Mr. Apple (he has a mostly unbuttoned shirt) might offer an ad-supported tier too, and their programming hasn’t been made with that in mind. The Apple brand isn’t really about advertising other products, companies, and services. I remain curious what that experience will be like one day when a tense moment in Silo transitions to an ad for a local accident attorney or pharmaceuticals.

Here’s another “Joe complains about Shortcuts” post for you. Last time I complained about not being able to reverse a list. This time I’m complaining about how Shortcuts handles time zones. I know time zones are the bane of every programmer’s existence, but I’m not going to give the Shortcuts team a break because they have all the time zone data, they just implemented it in the worst way they could think of.

First, let’s talk briefly about the part that’s not Shortcuts so you can understand where it will slot in.

I automated part of the Python script that generates my blog to do so without me having to log in over SSH and run the script myself. More on that in a future post. This was so I could write posts on-the-go. Here I am, posting al fresco, from my iPhone. The thing is, I wanted it to generate the date and time that I include in the YAML front matter of my blog.

Here’s an example of the YAML, a yample, if you will:

Title: [Title Here] Date: 2025-03-30 14:55:00 Author: joe-steel Category: text

It’s not a wild date and time format. It’s ISO 8601, and the system is expects it localized to my home time zone, which is in Los Angeles. That can either be PDT or PST, and it’s handled flawlessly by Python’s pytz library without any fiddly intervention from me. I want to be able to write the time out myself by hand if I so choose, and have the time and date be recognizable for me.

Shortcuts can generate the current date and time from the Date action. It can even be formatted to ISO8601 with the Format Date actions built-in “ISO8601” setting. Except there’s one teeny tiny issue: There is no way to get the current time in Los Angeles.

The Convert Time Zone action can only convert from cities in the predefined list of cities that are either capitals, or important cities. It doesn’t understand named time zones, like PST or PDT. So if you thought you were going to be clever about this by using the named time zone from the Format Date’s “Z” output then you’re going to be disappointed. It’ll say EST or EDT and there’s nothing you can do with that information at all in Convert Time Zone.

Who cares about named time zones, amirite? Picking cities is way better. Except, Convert Time Zone can’t understand or interpret just any city either. For example: If I was in Orlando, that is not in the list or preprogrammed cities, and can’t be used, but Miami, New York, Washington D.C., etc can be used. You can’t feed it Orlando as text input or anything. It will fail.

This is extremely unhelpful.

To get around this I used Date which was fed to Format Date, that was set to just get the GMT offset from the current time date-time output with “Z” and then regex (shudders) to get only the hour. That gets multiplied by -1, and fed to Adjust Date which adjusts the original Date object to remove the offset. I now have a date-time object with no offset.

I knew “Los Angeles” was in my previous list of cities so I could now use a Convert Time Zone action to convert to Los Angeles but I couldn’t pick “London” - it has it’s own time shenanigans, and there’s no Greenwich, or GMT. I asked Gemini which city has no offset, and it’s Accra, Ghana.

Save that little nugget for your next trivial pursuit game. Now that it was converted by math to GMT I could convert by “user friendly” Convert Time Zone from Accra to Los Angeles and then format the output any way I liked.

More like Apple Longcuts, amirite?

When I posted about all this on Mastodon, Elliot Shank pointed out that there was no need to use Accra because GMT was an ancient relic and I should be using UTC. There is, in the list of cities, UTC. Sure, when you search GMT it should probably return UTC, but that’s probably incredibly difficult to implement in a search function.

However, all that I got from that was that I could change Accra to UTC. I still needed to do all the rest of this bologna to get the current time in Los Angeles. So… my complaint stands.

Stephen Robles had another suggestion to use a web site’s api, but it’s just another approach that uses as many round-rect blocks of user-friendly time wasting as mine.

Am I asking for too much? Am I reaching for the stars here? Shortcuts is our only first-party automation platform on iOS, and only cross-platform one that can work on all of Apple’s platforms and it’s still lacking in the basics. You can’t find anything you’re looking for, and because of its nature you can’t easily find help.

Shortcuts has the thin veneer of user-friendliness applied to it, but under that it’s not just unfriendly many things simply aren’t possible and there’s no way of knowing. You just have to build a thing and grope around for anything that seems remotely applicable. I can’t believe the future of automation is tied to App Intents which are tied to Shortcuts and Siri. How will any of that help when Shortcuts can’t get the basics right?

I know, linking to myself is very Obama-awards-Obama meme. This post is relevant if you’ve been keeping tabs on what I’ve been writing about on my blog recently. Those posts here helped me see a pattern. I’m not sure if anyone else sees a pattern, or if I’ve just made a mess with red string and a pile of mashed potatoes that looks like Devil’s Tower, but I like to think it makes sense.

So here’s a thought for those who might suddenly find themselves in charge of Siri: Search is a foundational element of smart assistants, and the current state of Apple’s search technologies leaves much to be desired.

While all today’s web search engines are placing sparkly and unreliable AI-synthesized answers above everything else, they still generally deliver solid search results underneath. Refining Siri without bolstering the foundation is a recipe for disaster.

Everyone’s making the magic box on top of their results, and Apple’s trying to only make the magic box, sans search results. Let’s get some ye olde heuristics in here first.

Matt Birchler has a tangentially related blog post about LLMs that he put up yesterday while this was being edited. I’ll link to it here for this passage:

This is one example, but I’ve also seen people try to use ChatGPT as a calculator or Claude to give them the weather at their current location, and I sigh because these aren’t the right tools for the jobs. That said, the Google search box has been super powerful at training people to expect search similar fields to behave the same. It’s not exactly better when these LLM search boxes often look like Google and have “ask anything” as the placeholder text.

The simple fact of the matter is that not everything is best solved by an LLM, but LLM chatbots give the impression that they are good for everything. A further problem is that LLMs have a hard time saying they don’t know something, so they’ll always give you an answer whether it’s right or not. This is why I find Google to be in such a spectacular position to have the best of all worlds. It knows where you are (if you let it) and can tell you the weather right now, it scrapes the web constantly so it can give you news that literally broke a few minutes ago, it can show a calculator if you ask it to do some math, and yes, it can detect if an LLM would be best suited to respond to your query and use the LLM for that specific case. That LLM is also backed by the most powerful search engine ever and can parse real time data just like ChatGPT or Perplexity, but with even better search results.

Substitute LLM for Siri and you have something akin to what I’m saying, so I don’t feel like a total crank.

I’m proud of my post as I think it makes the case well (no string and mashed potatoes). The advantage of writing for Six Colors is that Jason Snell, as Editor Supreme, can tell me what’s not working, especially when it’s the whole thing.

I totally rewrote my piece based on his feedback on an earlier draft that was too scattered and didn’t make the point I was going for. He did a nip and tuck on that draft too. I kept getting bogged down with this example and that example, and it just didn’t need it. If you think I don’t have enough examples then, oh boy do I have a folder full of screenshots for you. I’m always glad to go through this process. Hopefully it’ll make me a better writer someday, and not just a guy who rants on the internet.

A while ago Jason Snell said that he would do a streamer box/dongle shoot-out on an episode of Upgrade, and today’s the day he hit publish. It’s well worth your time to read it, particularly if you aren’t as familiar with “the state of the art” in the streaming landscape. The last time I did a “device shoot-out” was in 2016, and none of the platforms are the same. I certainly stopped recommending Fire TVs, and only recommend Apple TVs.

My usage of the Fire TV completely fell by the wayside as they overhauled the interface to include more and more advertising. Prime Video also has ads. Everything. Has. Ads.

That Jason Snell was able to get an ad for a local mattress retailer is a pretty clear indicator that Amazon’s insatiable appetite for advertising has only increased. I even thought about reconnecting my Fire TV 4K stick so see how bad it’s gotten, but as Jason pointed out, no one’s paying me to use one.

I’ve never had personal experience with Google’s platform, and that is perhaps the most interesting section in Snell’s overview —from the perspective of someone that mostly uses Apple products. It’s not that I’m considering picking one up, but it’s just interesting.

I would caution Apple fans from skimming this and coming away with only the comforting affirmation that the Apple TV is the frontrunner in TV streaming boxes/dongles. Snell’s clearly demonstrated that the Apple TV isn’t a laggard, but he also outlined where the competition has a leg-up on Apple. Mark Gurman’s original racing analogy doesn’t work when you’re talking about devices with many features that each can excel or fall behind.

Jason’s conclusions about organizing apps and media in the same place, and about the need for a comprehensive live-guide are hardly shocking to me since that’s basically the drum I’ve been banging on for years. Maybe someone at Apple will be receptive to Jason’s comparisons?

While it’s easy for Apple fans (who are predisposed to not like, or expect ads) to point to the ads in Apple’s competition as a sign of poor quality in and of themselves, it’s worth remembering that people have different thresholds for frustration and trade-offs they will tolerate. Like I outlined in my piece for Six Colors about FAST, some people accept ads in an array of forms if their TV viewing experience is easy or inexpensive.

On a person-by-person basis there are certainly lines for what’s too much advertising, but no agreed upon quantitative or qualitative metric. Each person knows the “too much” line when they see it, and the companies all see numbers go up, or down, against other dollar signs, and engagement patterns before they decide to pull back, or push forward.

You know what they say: One man’s trash is another Mancini’s Sleep World.

It certainly took me by surprise when Apple contacted me, of all people, to be the sole news outlet to run the story about the fifth MacBook Air color being added to the recently updated line-up. Certainly they were contacting me out of deep respect, and not as a prank, right? Second, I didn’t know why this color was released so soon after the line was refreshed.

When I hopped on the WebEx call with Apple (my first, and probably only, ever time using WebEx so I savored it) I asked directly why there was a gap in product releases. I’m unclear on what part of their response I’m supposed to say since I just scribbled “Is this on background???” in the margin and never asked. It would seem that Apple wanted to release this color in celebration of St. Patrick’s Day, or possibly as a condition of their settlement with the European Commission over using Ireland to dodge taxes. Or maybe it was just a coincidence? As an aside, I told them that I was one quarter Irish on my dad’s side of the family, but they didn’t have much of a reaction.

There was a mild smile, and tiny shake of the head side-to-side when I asked if this was just because people thought all the silvers are too similar. They didn’t say anything though. It was just very tense.

When I looked at the product photos Apple provided me I had to ask if they hue shifted the background and screen to be green in Photoshop or if it really was green. They assured me that there’s no mistaking this “gorgeous new shamrock”. That part they definitely told me to write down.

They were also excited to tell me that there is also a color-matched charging cable for the new hint o’ mint. All of which is available today through the Apple Store to customers.

I wondered if buyers who recently purchased a sky blue MacBook Air would feel left out, and need to trade-in their product soon, but that’s when Apple surprised me with their latest green initiative. Apple said that while a midnight M4 MacBook Air buyer would have to use the traditional product exchange process any customer who bought a M4 MacBook Air will be able to instantly exchange it for shamrock. They won’t have to go to the Apple Store, ship products, or deal with wasteful packaging.

This product swap is entirely carbon neutral and done with energy offsets only. It seemed too good to be true, but any customer that purchased their M4 MacBook Air in sky blue, starlight, or silver will receive a new receipt by email that shows that they bought a shamrock MacBook Air, and also a new green desktop wallpaper. I don’t effectively know how that changes the color, but they said it definitely does, and then said “carbon neutral” again.

I look forward to seeing the machine in person, and especially in the vicinity of other colors, so that the bold new hue will hopefully pop —or seem like it’s more than a fourth silver.

Today I needed to scan a document I received in the mail and email it to someone. Nothing arduous, I just don’t do it very often so I forgot where the “Scan Document” function lived.

I’m glad that Scan Document function exists, and it works just fine. Bravo to the people at Apple that made it.

First, I opened the Camera app —because this is the app that takes photographs— and it wasn’t there. It’s because I’m thinking Camera -> Photo -> Attachment, when the way it works is Attachment -> Camera -> Photo.

I searched “scan a document” with Duck Duck Go, and it took me to the Apple Support document titled: How to scan documents on your iPhone or iPad. The support document started with detailed instructions on how to scan with the Notes app, and then there were instructions at the bottom for the Files app.

I followed the instructions and then went to attach it to my email with the paperclip icon, where I saw another Scan Document, which that Apple Support document neglected to mention and would have cut out intermediary steps in this instance.

Oh well, I got there in the end.

Thinking back to Apple’s statement to John Gruber boasting about Siri product knowledge, and Gruber rightfully pointing out on Mastodon that product knowledge isn’t very accurate, or helpful. I figured this was a time where I should at least try to use it. I already knew there was a support document, so it should at least send me to that.

That is what product knowledge is, after all, it’s a thing that displays part of the Apple Support document. It’s only display one thing, but it’ll do it with absolute certainty. A deep-link to the Tips app will take you right to the documentation, but you can’t share the document from the Tips app even though it also exists online at Apple’s own website. Also, for some reason, there are differences between Tips and the web, like the part about the Files app is in the web version of the document, but absent from Tips even in the latest iOS 18.3.2. If you’re looking up something on behalf of someone else and plan to send instructions to them it’s better to do that from the web, using a real search engine.

I typed my request to Siri on my iPhone and started typing “Scan” where it presented three suggestions above before I even typed “a document”. Open Simple Scan (an app I forgot I installed which would have done exactly what I wanted, sorry Greg), Open Scan+ (another app I forgot I installed, but appears to be abandoned), and Scan Document with the Files icon. That last one opens the Files app and puts you right in the document scanning interface.

As I already mentioned, that is but one of many routes built in to iOS to scan a document. There’s no way I can discover to request Notes for scanning. Any mention of “note” or “notes” makes Siri start the interface for composing a note with Siri completely ignoring the instruction to scan a document. The same thing happens if you say “mail” or “email” where it will just go right into the on-screen email composition wizard. Neither allow for attachments, which means you can’t get to the menu to scan a document for Notes or Mail.

It was taking everything I typed as a command to act on. It disregarded anything it couldn’t act on in favor of specific keywords. That’s why the mere use of “note” or “mail” made it ignore the rest of what I had said.

Speaking of keywords, in case you’re curious, from Spotlight, “Scan” shows you actions, such as directly scan in Simple Scan (which Siri does not), or directly scan into the Files app (which Siri does). Spotlight has nothing for Mail or Files. There is, however, “Scanned Documents” deep-link in notes to take you directly to things you have previously scanned.

Back to Siri: When I put the word “How” at the start of my request it went through Siri product knowledge and relayed instructions to me on how to accomplish those steps. “How to scan a document” returns the top part of the aforementioned Apple Support document, showing instructions only for Scan Document inside of Notes.

Phrasing the question this way omits the fact that Siri can open Scan Document in Files directly, or even the rest of the support page mentioning at all Files, or any other support page like you’d see if you did a web search.

If I typed “How to scan and email a document?” it gave me some abbreviated, generic instructions from the world famous scannmore.com to open any email app, and add an attachment. This is quite useless because it isn’t relevant.

If I typed “How to scan a document in Mail?” I got the incredibly verbose instructions to do that from a different Apple Support document: Add email attachments in Mail on iPhone.

I don’t know why the instructions aren’t the same, “tap the paperclip” like they are in the document, and Tips. Do any of you know the “>” is called the Expand Toolbar button? I know you know that the “>” moves back and forth every time you tap it and that it takes three taps of that shifting “>” to get to the Attach File button. There also isn’t an “Insert Attachments Action Button” but there is an Attach File, which is not what you want because the Files browser pop-over can’t Scan Documents like the Files app can. Instead of anything with “Attach” in the name you want “Scan Document” which is another tap of “>” —sorry, Expand Toolbar button.

If you scroll down in that original Siri overlay you can tap the “iPhone User Guide” (2 topics)” which shows a pop-up over the modal with truncated titles for the Apple Support documents in Tips. The first is allegedly what Siri is pulling from but the text is totally different, as I said, and the second one contains the Notes app instructions. I have no idea where Siri pulled this from. Did the team that added product knowledge do some weird logic to turn icons into words and thus mess up the meaning?

I mapped out many variations of the request here:

It occurred to me that this is why I so seldom see any of Siri’s product knowledge. I’m typing in the box like it’s a Google or DuckDuckGo search. However it accepts the text as a command, where the overriding logic is to do something —anything— even if it partially ignores the keywords in the rest of the request because certain keywords, like “how”, flip the logic gate and make it behave in a completely different way.

It doesn’t have the logic to know that it isn’t capable of fulfilling my request to both scan and email a document. It can’t revert to displaying the entirety of the support documents. The support documents are inexplicably severed into one that has Notes and Files, and one that has Mail instructions. There’s no way to formulate a request to get instructions to Scan Document in Files, but it’s also the only one that be directly opened by Siri, if you say the incantation exactly so.

This isn’t LLM-AI-AGI-GPT-Multi-Modal stuff. This isn’t trillions in funding and melting a glacier. It’s the kind of logic you’d use in a search engine where relevance comes into play. This doesn’t require years of research into a new field of study. Typing this in the blank address bar of a web browser is the level of technological advancement that outpaces Siri. Siri can’t be this picky about syntax when no one else is.

Sure, typing “Scan” and seeing “Scan Document” which launches the Scan Document function in Files is something only Apple can do, but it’s not what I needed or wanted to do in this particular case, and it is ultimately inflexible. I wanted to scan and email a document, which it can’t do, and won’t tell me about unless I use the magic word: How.

Apple’s statement to John Gruber last week that they are delaying “More Personalized Siri” has certainly sparked some conversation. With Gruber himself going on to write a pretty scathing post about this whole debacle. People certainly took note. A key part of what John wrote was that he believed in the company’s claims, because it would be unlike Present Day Apple to promote something that they couldn’t ship.

Readers of this blog, and my writing for Six Colors, might recall that I’ve been skeptical of Apple’s promises all along. I don’t get to take a victory lap for that skepticism. I’m certainly not cheering myself on for not getting useful software. Woo-hoo, look at me not getting the good stuff!

The announcement about “More Personalized Siri” fit perfectly with my expectations, which has possibly made me the person who is the least rattled by this news. The reason my expectations were so low wasn’t just because of my initial wariness, but because that wariness was confirmed by what Apple has been shipping.

Gruber details some of those features, and how there were demos, which meant that there was some reality to them. I look at it from the other side, where I’m evaluating the quality of what’s available to poke and prod at in public releases to gauge not just those features but Apple’s ability to deliver on future features.

Apple very rarely has the time to refine anything they ship. Version one of a thing tends to stick around for a long time with only extras bolted on, or omitted, because the people involved are simply too busy for a second pass. Because the bar to ship quality software is so low, and the need to revise quickly is nearly nonexistent, there was never any chance that they’d meet expectations for the robust features Apple was promising.

Let’s review what Apple actually shipped as Apple Intelligence.

Text-Based Tools

The scandal that’s received the most attention, prior to this, was the notification summary debacle. Apple tried to defend themselves from criticism by hiding behind the beta label on Apple Intelligence. Jason Snell wrote:

Beta software contains an implicit promise that the developer will actively work to squash bugs and make the product better before it goes final. Adding a warning label in the interim is an easy band-aid, but it doesn’t address the underlying problem. Apple needs to do much more work here, and if it can’t, it needs to turn this feature off until it can release a version it can stand behind.

You’ll never believe it, but the only thing Apple could do was turn the feature off for News & Entertainment apps. There’s no way to refine this to produce the result Apple had promised.

In iOS 18.1 Apple added Priority Mail, which would often prioritize scams because it registered anything with money or a date to be a priority messsage. I saw someone complain about it again today, in March, as a matter of fact.

In 18.2 Apple added categories to mail, which were not really about Apple Intelligence but kinda sorta? Cumulatively, all the changes to Mail have been pretty bad, and it hasn’t been improved. It is a feature that I have turned off. It’s only been recently shipped to the Mac and iPad, and they aren’t any better off with for it. But hey, promise to ship it is fulfilled, amirite?

Then there are Writing Tools, which is something I never think about until I go to use a context menu on iOS to copy, or translate text. Writing Tools is always there. I’ve tried to use it to proofread my writing, but it just spits back out my input and doesn’t explain why it didn’t change anything. It’s also slow, the UI is weird, it’s in a context menu, and it’s only on my iPhone because my Mac can’t run Apple Intelligence. Apple doesn’t use Private Cloud Compute to run this, but any person on earth can open a web browser and use an LLM to do the same thing Apple says you need a thousand dollar phone for.

It’s ironic that the thing that LLM’s are best suited for —mushing up some words— is pegged to hardware, stuffed into a menu, and has an awkward UI. But hey, that shipped!

Lastly, we have Swift autocompletion (which did ship) and Swift Assist (which did not). That this hasn’t shipped isn’t a huge, public-facing issue for Apple, like all the others, but it is another thing that’s damaging Apple’s relationship with developers. OpenAI shipped a ChatGPT integration with Xcode, which should be even more embarrassing. As someone that opens Xcode on occasion, and has taken stabs at writing Swift, the app is so byzantine and strange, with a bloated, overly-decorated language, that assistance isn’t the worst idea in the world.

Image-Based Tools

Image Playgrounds has received a lot of negative press, and deservedly so. The images it produces are quite bad, and because the interface prioritizes selecting photos of you, or someone you know, you get the added benefit of insulting yourself, loved ones, and friends. In fairness to Apple, this feature produces results that are very like what they demoed, because those images were just as wince-inducing. Remember Super Mom? There have been no improvements to the output in any of the styles Apple shipped. You can have “animation” which is a medium not a style, or “illustration” which always makes me look like an angry Willem Dafoe.

Believe it or not, but the image at the top of this post is from Image Playground and it was produced with the playful, bubble inputs of “chickens roosting” and “home”. This is a feature Apple demoed, put in betas, and shipped without every course-correcting. There is absolute confidence that this is what consumers want, and that it benefits them.

The same can be said of Magic Wand, which has a “sketch” style absent from Image Playgrounds. I don’t know why you can’t use sketch in Image Playgrounds, and I don’t know why you can’t draw in Image Playgrounds itself. Whatever! It shipped! It does things and went to customers! Can’t wait to see what you do with it blah blah blah!

In the grand scheme of things Image Playgrounds and Magic Wand are actually pretty insignificant because they are so deeply uncool that no one wants to use them. If you see someone post an image that looks like it came from Image Playgrounds you will judge them for it.

Genmoji, on the other hand, is what Apple has decided to lean heavily on. They can’t lean on Siri, notifications, or even the dorky awkwardness of Writing Tools. It also hasn’t improved in any noticeable way, and you can still get mangled, Cronenberg-esque images out of it, but that doesn’t matter to Apple. It shipped, put the dancing hippo on the billboard!

The feature that’s the most sound is Clean Up. It’s a decent effort from Apple. I evaluated it in a video for Six Colors. It needs more work, but it’s acceptable. As far as I know it’s not been improved since it shipped, or if it has it’s been in a way too subtle for me to notice. It will smear edges, make polygonal hashes, etc. It’s good enough, and it probably won’t be touched again for years.

Lastly, we have Visual Intelligence, which doesn’t generate images, but will tell you about an image. This is so poorly conceived that I don’t even understand how the concept pitch for visual intelligence was green-lit. It relies on using the Camera Control —you know, that mini button/trackpad that does 48 other things you accidentally bump? What’s one more overloaded function between friends? Except if you have an older phone or iPhone 16e, which will use the Action Button.

It doesn’t make it obvious what will happen when you hit the “shutter” button which captures an image for processing, not taking a picture. If there’s text, it can summarize the text, but it will only show you the summarize button once you tap the “shutter”, and won’t indicate that ability beforehand.

The same is true for translation, which is still a better experience in Apple’s own Translate app because it will show a live text translation overlay as you’re moving the camera.

Without hitting the “shutter” it will show you buttons for Ask —which will only ever ask ChatGPT, and you must agree to their privacy permissions— or Search —which will only ever do a Google image search. Both of these are inferior to using those products independently, and neither provides any of the privacy Apple has been promising about their products.

Craig Federighi leaned heavily on Private Cloud Compute in the marketing since WWDC. No one even knows what it does on a practical, applied level. It doesn’t run private image search models, or private instances of ChatGPT.

Apple did add plants and animal recognition, which was something the Photos app could do, but Visual Intelligence could not. However I have been unable to get it to appear at all, and it also killed my iPhone Photos app’s ability to do plant and animal recognition and I don’t know why.

I can take a photo on my iPhone, sync to my Mac, which doesn’t have Apple Intelligence at all, and it will show the plant recognition leaf symbol as it has done for years. So it’s not like I’m taking photos of unrecognizable plants.

This takes us to another thing about Visual Intelligence: you can’t run Visual Intelligence on a photo that you already took. Unlike a Google image search, or similar, it will only accept your fake shutter button non-photos as input. Again, this is worse than existing products.

Promises, Promises

So, just in that little run-through, you can hopefully see what I see. The problem isn’t just “More Personalized Siri” not shipping, the problem is what did ship, and what that portends for all future releases. Software quality is out the window, so for “More Personalized Siri” to not meet the low bar of something like Visual Intelligence…

The thing about “AI” (chatbots) is that it really did take Apple by surprise, but chatbots are merely a tool that can be used. The most logical place to use it is in Siri, the thing you chat with, but people are only clamoring for that because nothing Apple has done to improve Siri has been sufficient. Let’s go back to Apple’s statement, through Jacquelin Roy to Gruber, where they left him holding their bag of empty promises:

Siri helps our users find what they need and get things done quickly, and in just the past six months, we’ve made Siri more conversational, introduced new features like type to Siri and product knowledge, and added an integration with ChatGPT.

I said on Mastodon after quoting that part:

I don’t want to minimize this effort but these have not been transformative, and I frequently see these criticized - like the ChatGPT integration getting things wrong that the ChatGPT app gets right (for those who care about ChatGPT). This hasn’t been six months of success.

What they did ship for Siri was as damning as what they didn’t. None of those things matter, or do anything significant. The only thing they did with Siri in the past year that was significant was add the new visual language for Siri. I believe every Apple pundit under the sun has been in agreement that that was a huge mistake because it signaled change where there was no meaningful change.

Last week, I asked my boyfriend what time he wanted to eat lunch. My wrist must have been elevated, and apparently Raise to Speak was enabled, even though I don’t remember turning that back on. Siri responded on my Watch with “I don’t eat or drink. But I always have an appetite for a good conversation.”

That’s conversational Siri. That’s the results of years and years of effort on Siri. That’s because of the writer’s rooms generating canned responses to questions. That’s years and years of shipping updates to Siri. That’s the full power of a fully operational Cupertino brought to bear on misunderstanding what was happening and doing what it shouldn’t.

There was never any world where “More Personalized Siri” was going to ship. Even if they had a demo, I wouldn’t have any faith it would survive in real-world use. Much like I don’t have any faith in Amazon’s Alexa+ that was very carefully announced and demoed.

I know that Apple has made many mistakes in the past —the one that this is the most similar to is Apple Maps, not AirPower— and it’s true that they have runway to continue to work on the execution.

When third party solutions fall short on Apple’s platforms it’s not a problem. When first party solutions fall short on Apple’s platforms it is a very big problem. When Copilot barfs on some code, oh well, you’ll tweak it and run it again, it’s not like it’s built into the platform. Copilot duplicating import statements also isn’t mission critical, like what time your appointment is, or when the flight with your mother arrives. There is a difference between working on a task, and living your life 24/7 with an assistant.

Threats and Partners

I don’t think that Open AI’s ChatGPT and Microsoft’s Copilot are a threat to Apple’s revenue. They’re going after reducing labor in the workplace, which means reducing the workforce so they can collect money from what would have been salaries for employees. That they have a consumer angle is only to reinforce their lead in the workplace with people asking to use those tools, which will cost more and more over time.

Neither one of them would do well with making a smartphone (Microsoft, especially, has learned this lesson). They can, however position themselves to sit in the place that Google occupies for providing services to consumers. This is why ChatGPT is integrated with Siri.

Meta, likewise, is not going to have another fiasco making a phone. They’re angling for synthetic “content” and synthetic accounts that people follow which can be tailored for engagement and advertising purposes. This will also be very lucrative for them without having to ship a phone.

Google’s Gemini is actually the one place where Apple needs to be concerned because Google is putting Gemini into phones. Which was part of the reason it was bizarre to hear Apple executives openly discuss Gemini as a possible candidate for their integration with Siri.

That takes us full circle to Google supplying the Maps data in iOS. A dependency that could be leveraged to get information about Apple customers, and to fortify Android as a competitor that offered the same mapping abilities for less than Apple.

How much of that is Apple hoping to shift its lucrative search deal with Google to a Siri Integration deal where they can capture sales revenue from compromised customer privacy? How much does Apple want to make an App Store for Siri integrations where they can one day financially benefit from being the middle-man?

I’d bet that’s something, but it’s probably mostly because they know they’d be able to ship it and it would look like Apple was doing visible things with Siri that were going out the door.

While no one is really going to take Apple at their word for any Apple Intelligence features they announce at WWDC 2025, they’ll be able to believe in work from third parties that already have products. The cupboards are pretty bare for anything Apple can ship, and they clearly can’t go back and improve anything.

Maybe Apple is hoping that their much-feared visual refresh of each OS will be enticing —just like the Siri glow was dangled in front of customers without Siri improvements to back it up. This turd is still a turd, but it now has an emphasis on transparency and depth.

What I’m mostly anticipating is a continued drop in quality and standards, as evident by what’s been shipped this year. On multiple occasions people have reported Apple Intelligence being re-enabled for them (even in macOS 15.3.2), or there was that time Image Playgrounds was advertised in Settings.

This transformative year, where everything got just a little worse in Apple Land. Where if you complained about Apple Intelligence online some drive-by commenter was as likely to tell you it would get better, or tell you to turn it off. Nothing’s getting better, and turning it off won’t make a problem of this magnitude go away.