Congratulations!

[Valid Atom 1.0] This is a valid Atom 1.0 feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://www.tbray.org/ongoing/ongoing.atom

  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <feed xmlns='http://www.w3.org/2005/Atom'
  3.      xmlns:thr='http://purl.org/syndication/thread/1.0'
  4.      xml:lang='en-us'>
  5. <title>ongoing by Tim Bray</title>
  6. <link rel='hub' href='http://pubsubhubbub.appspot.com/' />
  7. <id>https://www.tbray.org/ongoing/</id>
  8. <link href='https://www.tbray.org/ongoing/' />
  9. <link rel='self' href='https://www.tbray.org/ongoing/ongoing.atom' />
  10. <link rel='replies'       thr:count='101'       href='https://www.tbray.org/ongoing/comments.atom' />
  11. <logo>rsslogo.jpg</logo>
  12. <icon>/favicon.ico</icon>
  13. <updated>2025-10-12T16:11:05-07:00</updated>
  14. <author><name>Tim Bray</name></author>
  15. <subtitle>ongoing fragmented essay by Tim Bray</subtitle>
  16. <rights>All content written by Tim Bray and photos by Tim Bray Copyright Tim Bray, some rights reserved, see /ongoing/misc/Copyright</rights>
  17. <generator uri='/misc/Colophon'>Generated from XML source code using Perl, Expat, Emacs, Mysql, Ruby, and ImageMagick. Industrial-strength technology, baby.</generator>
  18.  
  19. <entry>
  20. <title>Social Media Provenance Challenge</title>
  21. <link href='https://www.tbray.org/ongoing/When/202x/2025/10/01/C2PA-For-Social-Media' />
  22. <link rel='replies'        thr:count='13'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/10/01/C2PA-For-Social-Media#comments' />
  23. <id>https://www.tbray.org/ongoing/When/202x/2025/10/01/C2PA-For-Social-Media</id>
  24. <published>2025-10-01T12:00:00-07:00</published>
  25. <updated>2025-10-06T10:15:26-07:00</updated>
  26. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Identity' />
  27. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  28. <category scheme='https://www.tbray.org/ongoing/What/' term='Identity' />
  29. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Social Media' />
  30. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  31. <category scheme='https://www.tbray.org/ongoing/What/' term='Social Media' />
  32. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>At a     <a href='https://iptc.org/news/iptc-photo-metadata-conference-2025-recordings-now-available/'>a recent     online conference</a>, I said that we      can “change the global Internet conversation for the better, by making it harder for liars to lie and easier for truth-tellers     to be believed.” I was talking about media<span class="dashes"> —</span> images, video, audio.      We can make it <em>much</em> easier to tell when media is faked and when it’s real.     There’s work to do, but it’s straightforward stuff and we could get there soon. Here’s how</div></summary>
  33. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  34.    <p>At a
  35.    <a href="https://iptc.org/news/iptc-photo-metadata-conference-2025-recordings-now-available/">a recent
  36.    online conference</a>, I said that we
  37.    can “change the global Internet conversation for the better, by making it harder for liars to lie and easier for truth-tellers
  38.    to be believed.” I was talking about media<span class='dashes'> —</span> images, video, audio.
  39.    We can make it <em>much</em> easier to tell when media is faked and when it’s real.
  40.    There’s work to do, but it’s straightforward stuff and we could get there soon. Here’s how.</p>
  41.    <h2 id='p-8'>The Nadia story</h2>
  42.    <p>This is a vision of what success looks like.</p>
  43.    <p>Nadia lives in LA.
  44.    She has a popular social-media account with a reputation for stylish pictures of urban
  45.    life. She’s not terribly political, just a talented street photog. Her handle is “CoolTonesLA@hotpix.example”.</p>
  46.    <p>She’s in Venice Beach the afternoon of Sunday August 9, 2026, when federal agents take down a vendor selling
  47.    cheap Asian ladies’ wear. She gets a great shot
  48.    of an enforcer carrying away an armful of pretty dresses while two more bend the merchant over his countertop.
  49.    None of the agents in the picture are in uniform, all are masked.</p>
  50.    <p>She signs into her “CoolTonesLA” account on <code>hotpix.example</code> and drafts a post saying “Feds raid Venice
  51.    Beach”. When she uploads
  52.    the picture, there’s a pop-up asking “Sign this
  53.    image?” Nadia knows what this means, and selects “Yes”. By midnight her post has gone viral.</p>
  54.    <img src="cr.png" alt="Content Credentials glyph" class="inline"/>
  55.    <p>As a result of Nadia agreeing to “sign” the image, anyone who sees her post, whether in a browser or mobile app,  also
  56.    sees that little “Cr” badge in the photo’s top right corner.
  57.    When they mouse over it, a little pop-up says something like:</p>
  58.    <blockquote class="popup"><p style="font-family: sans-serif">Signature is valid.<br/>Media was posted by <span
  59.    class="fakelink">@CoolTonesLA</span><br/>on
  60.    <span class="fakelink">hotpix.example</span><br/>at 5:40 PM PDT, August 9th, 2026.</p></blockquote>
  61.    <p>The links point to Nadia’s feed and her instance’s home page. Following them can give the reader a feeling
  62.    for what kind of person she is, the nature of her server, and the quality of her work. Most people are inclined to believe the
  63.    photo is real.</p>
  64.    <p>Marco is a troublemaker. He grabs Nadia’s photo and posts it to his social-media account with the caption
  65.    “Criminal illegals terrorize local business. Lock ’em up!”  He’s not technical and doesn’t strip the metadata. Since the
  66.    picture is already signed, he doesn’t get the “Sign this picture?” prompt.
  67.    Anyone who sees his post will see the “Cr” badge and mousing over it makes it pretty clear that it isn’t what he says it
  68.    is. Commenters gleefully point this out.  By the time Marco takes the post down, his credibility is
  69.    damaged.</p>
  70.    <p>Maggie is a more technical troublemaker. She sees Marco’s post and likes it, strips the picture’s metadata, and reposts it.
  71.    When she gets the “Sign this picture?” prompt, she says “No”, so it doesn’t get
  72.    a “Cr” badge. Hostile commenters accuse her of posting a fake, saying “LOL badge-free zone”. It is less likely that her
  73.    post will go viral.</p>
  74.    <p>Miko isn’t political but thinks the photo would be more dramatic if she Photoshopped it to add a harsh dystopian lighting
  75.    effect. When she reposts her version, the “Cr” badge won’t be there because the pixels have changed.</p>
  76.    <p>Morris follows Maggie. He grabs the stripped picture and, when he posts it, says “Yes”
  77.    to signing. In his post the image will show up with the “Cr” and credit it to him, with a “posted” timestamp later than Nadia’s initial
  78.    post. Now, the
  79.    picture’s believability will depend on Morris’s. Does he have a credible track record?
  80.    Also, there’s a chance that someone will notice what Morris did and point out that he stole Nadia’s picture.</p>
  81.    <p>(In fact, I wouldn’t be surprised if people ran programs against the social-network firehose looking for media signed by more than
  82.    one account, which would be easy to detect.)</p>
  83.    <p>That’s the Nadia story.</p>
  84.    <h2 id='p-2'>How it’s done</h2>
  85.    <p>The rest of this piece explains in some detail how the Nadia story can be supported by technology that
  86.    already exists, with a few adjustments. If jargon like “PKIX” and “TLS” and “Nginx” is foreign to you, you’re unlikely to
  87.    enjoy the following. Before you go, please consider: Do you think making the Nadia story come true
  88.    would be a good investment?</p>
  89.    <p>I’m not a really deep expert on all the bits and pieces, so it’s possible that I’ve got something wrong. Therefore, this
  90.    blog piece will be a living document in that I’ll correct any convincingly-reported errors, with the goal that it
  91.    accurately describes a realistic technical roadmap to the Nadia story.</p>
  92.    <p>By this time I’ve posted enough times about C2PA that I’m going to assume people know what it is and how it works. For my long,
  93.    thorough explainer, see
  94.    <a href="https://www.tbray.org/ongoing/When/202x/2023/10/28/C2PA-Workflows">On C2PA</a>. Or, check out the
  95.    <a href="https://contentcredentials.org/">Content Credentials Web site.</a></p>
  96.    <p>Tl;dr: C2PA is a list of assertions about a media object, stored in its metadata, with a digital signature that includes the
  97.    assertions and the bits of the picture or video.</p>
  98.    <p>This discussion assumes the use of C2PA and also an in-progress specification from the
  99.    <a href="https://cawg.io">Creator Assertions Working Group</a> (CAWG) called
  100.    <a href="https://cawg.io/identity/1.2-draft">Identity Assertion</a>.</p>
  101.    <p>Not all the pieces are quite ready to support the Nadia story. But there’s a clear path forward to closing each gap.</p>
  102.    <h2 id='p-3'>“Sign this picture?”</h2>
  103.    <p>C2PA and CAWG specify many assertions that you can make about a piece of media. For now let’s focus just on what we
  104.    need for provenance.
  105.    When the media is uploaded to a social-network service, there are two facts that the server knows,
  106.    absolutely and unambiguously: Who uploaded it (because they’ve had to sign in) and when it happened.</p>
  107.    <p>In the current state of
  108.    the specification drafts, “Who” is the <code>cawg.social_media</code> property from the draft
  109.    <a href="https://cawg.io/identity/1.2-draft/#vc-credentialsubject-verifiedidentity-type">Identity Assertion spec, section
  110.    8.1.2.5.1</a>, and “When” is the <code>c2pa.time-stamp</code> property from the
  111.    <a href="https://spec.c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html#_requirements_2">C2PA
  112.    specification, section 18.17.3</a>.</p>
  113.    <p>I think these two are all you need for a big improvement in social network  media provenance,
  114.    so let’s stick with them.</p>
  115.    <h2 id='p-4'>What key?</h2>
  116.    <p>Let’s go back to the Nadia story.
  117.    It needs the Who/When assertions to be digitally signed in a way that will convince a tech-savvy human or a PKIX validation
  118.    library that the signature could only have been applied by the server at <code>hotpix.example</code>.</p>
  119.    <p>The C2PA people have been thinking about this. They are working on a
  120.    <a href="https://iptc.org/verified-news-publishers-list/">Verified News Publishers List</a>, to be maintained and managed by,
  121.    uh, that’s not clear to me. The idea is that C2PA software would, when validating a digital signature, require
  122.    that the PKIX cert is one of those on the Publishers List.</p>
  123.    <p>This isn’t going to work for a decentralized social network, which has tens of thousands of independent servers
  124.    run by co-ops, academic departments, municipal governments, or just a gaggle of friends who kick in on Patreon. And anyhow,
  125.    Fediverse instances don’t claim to be “News Publishers”, verified or not.</p>
  126.    <p>So what key can <code>hotpix.example</code> sign with?
  127.    Fortunately, there’s already a keypair and PKIX certificate in place on every social-media server, the one it uses to
  128.    support TLS connections. The one at <code>tbray.org</code>, that’s being used right now to protect your interaction
  129.    with this blog, is in <code>/etc/letsencrypt/live/</code> and the private key is obviously not generally readable.</p>
  130.    <p>That cert will contain the public key corresponding to the host’s private key, the cert's ancestry, and the host name.
  131.    It’s all that any PKIX library needs to verify that yes, this could only have been signed by
  132.    <code>hotpix.example</code>. However, there will be objections.</p>
  133.    <p><b>Objection</b>: “<code>hotpix.example</code> is not a Verified News Publisher!” True enough, the C2PA validation libraries would
  134.    have to accept X.509 certs. Maybe they do already? Maybe this requires an extension of the current specs? In any
  135.    case, the software’s all open-source, could be forked if necessary.</p>
  136.    <p><b>Objection</b>: “That cert was issued for the purpose of encrypting TLS connections, not for some weird photo provenance
  137.    application. Look at the
  138.    <a href="https://en.wikipedia.org/wiki/Object_identifier">OID</a>!” OK, but seriously, who cares?
  139.    The math does what the math
  140.    does, and it works.</p>
  141.    <p><b>Objection</b>: “I have to be super-careful about protecting my private key and I don’t want to give a copy to the hippies
  142.    running the social-media server.” I sympathize but, in most cases, social media is all that
  143.    server’s doing.</p>
  144.    <p>Having said that, it would be great if there were extensions to Nginx and Apache httpd where you could request
  145.    that they sign the assertions for you. Neither would be rocket science.</p>
  146.    <p>OK, so we sign Nadia’s Who/When assertions and her photo’s pixels  with our host’s TLS key, and ship it off into the
  147.    world. What’s next?</p>
  148.    <h2 id='p-5'>How to validate?</h2>
  149.    <p>Verifying these assertions, in a Web or mobile app, is going to require a C2PA library to pick apart the assertions and
  150.    a PKIX library for the signature check.</p>
  151.    <p>We already have
  152.    <a href="https://github.com/contentauth/c2pa-rs">c2pa-rs</a>, Rust code with MIT and Apache licenses.
  153.    Rust libraries can be called
  154.    from some  other programming languages but in the normal course of affairs I’d expect there soon to be native implementations.
  155.    Once again, all these technologies are old as dirt, absolutely no rocket science required.</p>
  156.    <p>How about validating the signatures?  I was initially puzzled about this one because, as a
  157.    programmer, certs only come into the picture when I do something like <code>http.Get()</code> and the
  158.    library takes care of all that stuff. So I can’t speak from experience.</p>
  159.    <p>But I think the infrastructure is there.  Here’s a Curl blogger praising
  160.    <a href="https://eissing.org/icing/posts/curl-apple-sectrust/">Apple SecTrust</a>. Over on Android, there’s
  161.    <a href="https://developer.android.com/reference/javax/net/ssl/X509ExtendedTrustManager">X509ExtendedTrustManager</a>.
  162.    I assume Windows has something. And if
  163.    all else fails, you could just download a trusted-roots file from the
  164.    <a href="https://curl.se/docs/caextract.html">Curl</a> or
  165.    <a href="https://android.googlesource.com/platform/system/ca-certificates/+/master/files/">Android</a> projects and refresh it
  166.    every week or two.</p>
  167.    <h2 id='p-7'>What am I missing?</h2>
  168.    <p>This feels a little too easy, something that could be done in months not years. Perhaps I’m oversimplifying.
  169.    Having said that, I think the most important thing to get right is the scenarios, so we know what effect we want to achieve.</p>
  170.    <p>What do you think of the Nadia story?</p>
  171. </div></content></entry>
  172.  
  173. <entry>
  174. <title>GenAI Predictions</title>
  175. <link href='https://www.tbray.org/ongoing/When/202x/2025/09/26/GenAI-Predictions' />
  176. <link rel='replies'        thr:count='7'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/09/26/GenAI-Predictions#comments' />
  177. <id>https://www.tbray.org/ongoing/When/202x/2025/09/26/GenAI-Predictions</id>
  178. <published>2025-09-26T12:00:00-07:00</published>
  179. <updated>2025-10-02T09:16:45-07:00</updated>
  180. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
  181. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  182. <category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
  183. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I’m going to take a big chance here and make predictions about GenAI’s future.     Yeah, I know, you’re feeling overloaded on this stuff and me too, but it     seems to have sucked the air out of all the other conversations. I would so like to return to     arguing about Functional Programming or Free Trade.  This is risky and there’s a pretty good chance that I’m     completely wrong. But I’ll try to entertain while prognosticating</div></summary>
  184. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  185.    <p>I’m going to take a big chance here and make predictions about GenAI’s future.
  186.    Yeah, I know, you’re feeling overloaded on this stuff and me too, but it
  187.    seems to have sucked the air out of all the other conversations. I would so like to return to
  188.    arguing about Functional Programming or Free Trade.  This is risky and there’s a pretty good chance that I’m
  189.    completely wrong. But I’ll try to entertain while prognosticating.</p>
  190.    <h2 id='p-6'>Reverse Centaurs</h2>
  191.    <p>That’s the title of a
  192.    <a href="https://locusmag.com/feature/commentary-cory-doctorow-reverse-centaurs/">Cory Doctorow</a> essay, which I think is spot
  193.    on. I’m pretty sure anyone who’s read even this far would enjoy it and it’s not long, and it’d help understand this.
  194.    Go have a look, I’ll wait.</p>
  195.    <h2 id='p-4'>Hallucinations won’t get fixed</h2>
  196.    <p>I have one good and one excellent argument to support this prediction. Good first: While my understanding of LLMs is not
  197.    that deep, it doesn’t have to be to understand that it’s really difficult (as in, we don’t know how) to connect the model’s
  198.    machinations to our underlying reality, so as to fact-check.</p>
  199.    <p>The above is my non-expert intuition at work. But then there’s
  200.    <a href="https://arxiv.org/pdf/2509.04664">Why Language Models Hallucinate</a>, three authors from OpenAI and one from Georgia
  201.    Tech, which seems to show that hallucinations are an inevitable result of current training practices.</p>
  202.    <p>And here’s the excellent argument: If there were a way to eliminate the hallucinations, <em>somebody already would
  203.    have</em>. An army of
  204.    smart, experienced people, backed by effectively infinite funds, have been hunting this white
  205.    whale for years now without much success. My conclusion is, don’t hold your breath waiting.</p>
  206.    <p>Maybe there’ll be a surprise breakthrough next Tuesday. Could happen, but I’d be really surprised.</p>
  207.    <p>(When it comes to LLMs and code, the picture is different; see below.)</p>
  208.    <h2 id='p-1'>The mass layoffs won’t happen</h2>
  209.    <p>The central goal of GenAI is the elimination of tens of millions of knowledge workers.
  210.    That’s the only path to the profits that can cover the costs of training and
  211.    running those models.</p>
  212.    <p>To support this scenario the AI has to run in Cory’s “reverse centaur” mode, where the models do the work and the
  213.    humans tend them. This allows the production of several times more work per human, generally of lower quality, with inevitable
  214.    hallucinations. There are two problems here: First, that at least some of the output is
  215.    <a href="https://hbr.org/2025/09/ai-generated-workslop-is-destroying-productivity">workslop</a>, whose cleanup costs eat away at
  216.    the productivity wins.
  217.    Second, that the lower quality hurts your customers and your business goes
  218.    downhill.</p>
  219.    <p>I just don’t see it. Yeah, I know, every CEO is being told that this will work and they’ll be heroes to their
  220.    shareholders. But the data we have so far keeps refusing to support those productivity claims.</p>
  221.    <p>OK then, remove the “reverse” and run in centaur mode, where smart humans use AI tools judiciously to improve productivity
  222.    and quality. Which might be a good idea for some people in some jobs.
  223.    But in that scenario neither the output boost nor the quality gain get you to where you can dismiss enough
  224.    millions of knowledge workers to afford the AI bills.</p>
  225.    <h2 id='p-2'>The financial damage will be huge</h2>
  226.    <p>Back to Cory, with <a href="https://pluralistic.net/2025/09/27/econopocalypse/#subprime-intelligence">The real (economic) AI
  227.    apocalypse is nigh</a>. It’s good, well worth reading, but at this point pretty well conventional wisdom as seen by everyone who
  228.    isn’t either peddling a GenAI product or (especially) fundraising to build one.</p>
  229.    <p>To pile on a bit, I’m seeing things every week like for example this:
  230.    <a href="https://fortune.com/2025/09/23/ai-boom-unsustainable-tech-spending-parabolic-deutsche-bank/">The AI boom is
  231.    unsustainable unless tech spending goes ‘parabolic,’ Deutsche Bank warns: ‘This is highly unlikely’</a>.</p>
  232.    <p>The aggregate investment is ludicrous. The only people who are actually making money are the ones
  233.    <a href="https://www.ft.com/content/e93e56df-dd9b-40c1-b77a-dba1ca01e473">selling the gold-mining equipment</a> to the peddlers.
  234.    Like they say,
  235.    <a href="https://en.wikipedia.org/wiki/Herbert_Stein#Stein's_Law">“If something cannot go on forever, it will stop.”</a> Where
  236.    by “forever”, in the case of GenAI, I mean “sometime in 2026, probably”.</p>
  237.    <h2 id='p-3'>… But the economy won’t collapse</h2>
  238.    <p>Cory forecasts existential disaster, but I’m less worried.
  239.    Those most hurt when the bubble collapses will be the investing classes who, generally speaking, can afford it.
  240.    Yeah, if the S&amp;P 500 drops by a third, the screaming will shake the heavens, but I honestly don’t see it hitting as hard as
  241.    2008 and don’t see how the big-picture economy falls apart. That work that the genAI shills say would be automated away is still
  242.    gonna have to be done, right?</p>
  243.    <h2 id='p-5'>The software profession will change, but not <em>that</em> much</h2>
  244.    <p>Here’s where I get in trouble, because a big chunk of my professional peers, including people I admire, see
  245.    GenAI-boosted coding as pure poison:
  246.    <a href="https://anthonymoser.github.io/writing/ai/haterdom/2025/08/26/i-am-an-ai-hater.html">“In a kind of nihilistic symmetry,
  247.    their dream of the perfect slave machine drains the life of those who use it as well as those who turn the gears.”</a> (The
  248.    title of that essay is “I Am An AI Hater.”)</p>
  249.    <p>I’m not a hater.
  250.    I argued above that LLMs generating human discourse have no way to check their output for consistency with
  251.    reality. But if it’s code, “reality” is approximated by what will compile and build and pass the tests. The agent-based systems
  252.    iteratively generate code, reality-check it, and don’t show it to you until it passes. One consequence is that the
  253.    quality of help you get from the model should depend on the quality of your test framework. Which warms my
  254.    <a href="/ongoing/When/202x/2021/05/15/Testing-in-2021">testing-fanatic</a> heart.</p>
  255.    <p>So, my first specific prediction: Generated code will be a routine thing in the toolkit, going forward from here. It’s pretty
  256.    obvious that LLMs are better at predicting code sequences than human language.</p>
  257.    <p>In <a href="https://sourcegraph.com/blog/revenge-of-the-junior-developer">Revenge of the junior developer</a>, Steve Yegge
  258.    says, more or less, “Resistance is useless. You will be assimilated.” But he’s wrong; there are going to be places where we
  259.    put the models to work, and others where we won’t. We don’t know which places those are and aren’t, but I have (weaker)
  260.    predictions; let’s be honest and just say “guesses”.</p>
  261.    <p>Where I suspect generated code will likely appear:</p>
  262.    <ul>
  263.      <li><p>Application logic: “Depreciate the values in the <code>AMOUNT</code> field of the <code>INSTALLED</code> table forward
  264.      ten years and write the <code>NAME</code> field and the depreciated value into a CSV.” Or “Look at JIRA ticket 248975 and
  265.      create a fix.”</p>
  266.      <p>(By the way, this is a high proportion of what actual real-world programmers do every day.)</p></li>
  267.      <li><p>Glorified StackOverflow-style lookups like I did in
  268.      <a href="/ongoing/When/202x/2025/07/01/First-AI-Code">My First GenAI Code</a>.</p></li>
  269.      <li><p>Drafting code that needs to run against interfaces too big and complex to hold in your head, like for example the
  270.      Android and AWS APIs (“When I shake the phone, grab the location from GPS and drop it in the <code>INCOMING</code> S3 bucket”). Or
  271.      CSS (“Render that against a faded indigo background flush right, and hold it steady while scrolling so the text slides around
  272.      it”).</p></li>
  273.      <li><p>SQL. This feels like a no-brainer. So much klunky syntax and so many moving pieces.</p></li>
  274.    </ul>
  275.    <p>Where I suspect LLM output won’t help much.</p>
  276.    <ul>
  277.      <li><p>Interaction design. I mean, c’mon, it requires predicting how humans understand and behave.</p></li>
  278.      <li><p>Low level infrastructure code, the kind I’ve spent my whole life on, where you care a whole lot about about conserving
  279.      memory and finding sublinear algorithms and shrinking code paths and having good  benchmarks.</p></li>
  280.    </ul>
  281.    <p>Here are areas where I don’t have a prediction but would like to know whether and how LLM fits in (or not).</p>
  282.    <ul>
  283.      <li><p>Help with testing: Writing unit and integration tests, keeping an eye on coverage, creating a bunch of BDD tests from a
  284.      verbal description of what a function is going to do.</p></li>
  285.      <li><p>Infrastructure as code: CI/CD, Terraform and peers, all that stuff. There are so many ways to get it wrong.</p></li>
  286.      <li><p>Bad old-school concurrency that uses explicit mutexes and <code>java.lang.Thread</code> where you have to understand
  287.      language memory models and suchlike.</p></li>
  288.    </ul>
  289.    <h2 id='p-7'>The real reason not to use GenAI</h2>
  290.    <p>Because it’s being sold by a panoply of grifters and chancers and financial engineers who know that the world where their dreams
  291.    come true would be generally shitty, and they don’t care.</p>
  292.    <p>(Not to mention the environmental costs and the poor folk in the poor countries where the QA and safety work is
  293.    outsourced.)</p>
  294.    <p>Final prediction: After the air goes out of the assholes’ bubble, we won’t have to live in the world they imagine. Thank
  295.    goodness.</p>
  296. </div></content></entry>
  297.  
  298. <entry>
  299. <title>C2PA Investigations</title>
  300. <link href='https://www.tbray.org/ongoing/When/202x/2025/09/18/C2PA-Investigations' />
  301. <link rel='replies'        thr:count='5'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/09/18/C2PA-Investigations#comments' />
  302. <id>https://www.tbray.org/ongoing/When/202x/2025/09/18/C2PA-Investigations</id>
  303. <published>2025-09-18T12:00:00-07:00</published>
  304. <updated>2025-09-30T15:06:15-07:00</updated>
  305. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Identity' />
  306. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  307. <category scheme='https://www.tbray.org/ongoing/What/' term='Identity' />
  308. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>This is the blog version of my talk at the IPTC’s online     <a href='https://iptc.org/events/photo-metadata-conference-2019/'>Photo Metadata Conference</a> conference.     Its title is the one the conference organizers slapped on my session without asking; I was initially going to     object but then I thought of the big guitar riff in Dire Straits’ <cite>Private Investigations</cite> and snickered.     If you want, instead of reading, to watch me present,     <a href='https://www.youtube.com/watch?si=BMfVGUQNcJOR1w2z&amp;amp;t=1610&amp;amp;v=wRjExw8OMUc&amp;amp;feature=youtu.be'>that’s on YouTube</a>.     Here we go</div></summary>
  309. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  310.    <p>This is the blog version of my talk at the IPTC’s online
  311.    <a href="https://iptc.org/events/photo-metadata-conference-2019/">Photo Metadata Conference</a> conference.
  312.    Its title is the one the conference organizers slapped on my session without asking; I was initially going to
  313.    object but then I thought of the big guitar riff in Dire Straits’ <cite>Private Investigations</cite> and snickered.
  314.    If you want, instead of reading, to watch me present,
  315.    <a href="https://www.youtube.com/watch?si=BMfVGUQNcJOR1w2z&amp;t=1610&amp;v=wRjExw8OMUc&amp;feature=youtu.be">that’s on YouTube</a>.
  316.    Here we go.</p>
  317.    <p>Hi all, thanks for having me. Today I represent… nobody, <em>officially</em>. I’m not on any of the committees nor am I an
  318.    employee of any of the providers. But I’m a photographer and software developer and social-media activist and have written a lot about
  319.    C2PA. So under all those hats this is a subject I care about.</p>
  320.    <p>Also, I posted this on Twitter back in 2017.</p>
  321.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/2017-twitter.png" alt="Twitter post from 2017 presaging C2pA" />
  322.    <p>I’m not claiming that I was the first with this idea, but I’ve been thinking about the issues for quite a while.</p>
  323.    <p>Enough self-introduction. Today I’m going to look at C2PA in practice right now in 2025. Then I’m going to talk about what I
  324.    think it’s for. Let’s start with a picture.</p>
  325.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/L1000004.png" alt="Picture of a shopping mall storefront" />
  326.    <div class='caption'><p>This smaller version doesn’t have C2PA,<br/>but if you click on it, the larger version you get does.
  327.    <br/>Photo credit: Rob Pike</p></div>
  328.    <p>I should start by saying that a few of the things that I’m going to show you are, umm, broken. But I’m still a C2PA fan. Bear
  329.    in mind that at this point everything is beta or preview or whatever, at best v1.0. I think we’re in glass-half-full mode.</p>
  330.    <p>This photo is entirely created and processed by off-the-shelf commercial products and has content credentials, and let me say
  331.    that I had a freaking hard time finding such a photo. There are very few Content Credentials out there on the Internet. That’s
  332.    because nearly every online photo is delivered either via social media or by professional publishing software. In both cases, the
  333.    metadata is routinely stripped, bye-bye C2PA. So one of the big jobs facing us in putting Content Credentials to work is to stop
  334.    publishers from deleting them.</p>
  335.    <p>Of course, that’s complicated. Professional publishers probably want the Content Credentials in place, but on social media
  336.    privacy is a key issue and stripping the metadata is arguably a good default choice. So there are a lot of policy discussions to
  337.    be had up front of the software work.</p>
  338.    <p>Anyhow, let’s look at the C2PA. </p>
  339.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/ca-glyphs-1.png" alt="Picture with two Content Credentials glyphs and one drop-down" />
  340.    <p>I open up that picture in Chrome and there are little “Cr” glyphs at both the top left and top right corners; that’s because
  341.    I’ve installed multiple C2PA Chrome plug-ins. Turns out these seem to only be available for Chrome, which is irritating. Anyhow,
  342.    I’ve clicked on the one in the top left.</p>
  343.    <p>That’s a little disappointing. It says the credentials were recorded by Lightroom, and gives my name, but I think it’s hiding
  344.    way more than it’s revealing. Maybe the one on the top right will be more informative?</p>
  345.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/ca-glyphs-2.png" alt="Picture with two Content Credentials glyphs and one drop-down" />
  346.    <p>More or less the same info. A slightly richer presentation But both displays have an “inspect” button and both do the same
  347.    thing. Let’s click it!</p>
  348.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/broken-inspector.png" alt="Content Credentials inspector page, failing to retrieve a page for review" />
  349.    <p>This is the Adobe Content Credentials inspector and it’s broken. That’s disappointing. Having said that, I was in a Discord
  350.    chat with a senior Adobe person this morning and they’re aware of the problem.</p>
  351.    <p>But anyhow, I can drag and drop the
  352.    picture like they say.</p>
  353.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/2-phase-c2pa.png" alt="Content credentials as displayed by the Inspector" />
  354.    <p>Much much better. It turns out that this picture was originally taken with a Leica M11-P. The photographer is a famous software
  355.    guy named Rob Pike, who follows me on Mastodon and wanted to help out.</p>
  356.    <p>So, thanks Rob, and thanks also to the Leica store in Sydney, Australia, who loaned him the M11. He hasn’t told me how he
  357.    arranged that, but I’m curious.</p>
  358.    <p>I edited it in Lightroom, and if you look close, you can see that I cropped it down and brightened it up. Let’s zoom in on
  359.    the content credentials for the Leica image.</p>
  360.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/leica-cc.png" alt="Leica-generated C2PA display" />
  361.    <p>There’s the camera model, the capture date (which is wrong because Rob didn’t get around to setting the camera’s date before
  362.    he took the picture.) The additional hardware (R-Adapter-M), the dimensions, ISO, focal length, and shutter speed.</p>
  363.    <p>Speaking as a photographer, this is kind of cool. There’s a problem in that it’s partly wrong. The focal length isn’t zero,
  364.    and Rob is pretty sure he didn’t have an adapter on. But Leica is trying to do the right thing and they’ll get there.</p>
  365.    <p>Now let’s look at the assertions that were added by Lightroom.</p>
  366.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/lr-cc.png" alt="Lightroom-generated C2PA display" />
  367.    <p>There’s a lot of interesting stuff in here, particularly the provenance. Lightroom lets you manage your identities, using
  368.    what we call “OAuth flows”, so it can ask Instagram (with my permission) what my Instagram ID is. It goes even further with
  369.    LinkedIn; it turns out that LinkedIn has an integration with the Clear ID people, the ones who fast-track you at the airport. So
  370.    I set up a Clear ID, which required photos of my passport, and went through the dance with LinkedIn to link it up, and then with
  371.    Lightroom so it knew my LinkedIn ID. So to expand, what it’s really saying is: “Adobe says that LinkedIn says that Clear says
  372.    that the government ID of the person who posted this says that he’s named Timothy Bray”.</p>
  373.    <p>I don’t know about you, but this feels like pretty strong provenance medicine to me. I understand that the C2PA committee and
  374.    the
  375.    <a href="https://cawg.io">CAWG</a> people are re-working the provenance assertions. To them: Please don’t screw this particular
  376.    style of provenance up.</p>
  377.    <p>Now let’s look at what Lightroom says it did. It may be helpful to know what I in fact did.</p>
  378.    <ol>
  379.      <li><p>Cropped the picture down.</p></li>
  380.      <li><p>Used Lightroom’s “Dehaze” tool because it looked a little cloudy.</p></li>
  381.      <li><p>Adjusted the exposure and contrast, and boosted the blacks a bit.</p></li>
  382.      <li><p>Sharpened it up.</p></li>
  383.    </ol>
  384.    <p>Lightroom knows what I did, and you might wonder how it got from those facts to that relatively content-free
  385.    description that reads like it was written by lawyers.
  386.    Anyhow, I’d like to know. Since I’m a computer geek, I used the open-source “c2patool” to dump what the assertions
  387.    actually are.  I apologize if this hurts your eyes.</p>
  388.    <p>It turns out that there is way more data in those files than the inspector shows. For example, the Leica claims included 29
  389.    EXIF values, here are three I selected more or less at random:</p>
  390.    <div class="highlight"><pre><span></span><span class="p"></span><span class="w">          </span><span class="nt">&quot;exif:ApertureValue&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;2.79917&quot;</span><span class="p">,</span>
  391. <span class="w">          </span><span class="nt">&quot;exif:BitsPerSample&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;16&quot;</span><span class="p">,</span>
  392. <span class="w">          </span><span class="nt">&quot;exif:BodySerialNumber&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;6006238&quot;</span><span class="p">,</span>
  393. </pre></div>
  394.    <p>Some of these are interesting: In the Leica claims, the serial number. I could see that as a useful provenance claim. Or as a
  395.    potentially lethal privacy risk. Hmmm.</p>
  396.        <div class="highlight"><pre><span></span><span class="p"></span><span class="w">            </span><span class="p">{</span>
  397. <span class="w">              </span><span class="nt">&quot;action&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;c2pa.color_adjustments&quot;</span><span class="p">,</span>
  398. <span class="w">              </span><span class="nt">&quot;parameters&quot;</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
  399. <span class="w">              </span><span class="nt">&quot;action&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;c2pa.color_adjustments&quot;</span><span class="p">,</span>
  400. <span class="w">              </span><span class="nt">&quot;parameters&quot;</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
  401. <span class="w">                </span><span class="nt">&quot;com.adobe.acr.value&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;60&quot;</span><span class="p">,</span>
  402. <span class="w">                </span><span class="nt">&quot;com.adobe.acr&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;Exposure2012&quot;</span>
  403. <span class="w">              </span><span class="p">}</span>
  404. <span class="w">            </span><span class="p">},</span>
  405. <span class="w">            </span><span class="p">{</span>
  406. <span class="w">              </span><span class="nt">&quot;action&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;c2pa.color_adjustments&quot;</span><span class="p">,</span>
  407. <span class="w">              </span><span class="nt">&quot;parameters&quot;</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
  408. <span class="w">                </span><span class="nt">&quot;com.adobe.acr&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;Sharpness&quot;</span><span class="p">,</span>
  409. <span class="w">                </span><span class="nt">&quot;com.adobe.acr.value&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;52&quot;</span>
  410. <span class="w">              </span><span class="p">}</span>
  411. <span class="w">            </span><span class="p">},</span>
  412. <span class="w">            </span><span class="p">{</span>
  413. <span class="w">              </span><span class="nt">&quot;action&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;c2pa.cropped&quot;</span><span class="p">,</span>
  414. <span class="w">              </span><span class="nt">&quot;parameters&quot;</span><span class="p">:</span><span class="w"> </span><span class="p">{</span>
  415. <span class="w">                </span><span class="nt">&quot;com.adobe.acr.value&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;Rotated Crop&quot;</span><span class="p">,</span>
  416. <span class="w">                </span><span class="nt">&quot;com.adobe.acr&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;Crop&quot;</span>
  417. <span class="w">              </span><span class="p">}</span>
  418. <span class="w">            </span><span class="p">}</span>
  419. </pre></div>
  420.    <p>And in the Lightroom section, it actually shows exactly what I did, see the sharpness and exposure values.</p>
  421.    <p>My feeling is that the inspector is doing either too much or too little. At the minimal end you could just say “hand
  422.    processed? Yes/No” and “genAI? Yes/No”.  For a photo professional, they might like to drill down and see what I actually did. I
  423.    don’t see who would find the existing presentation useful. There’s clearly work to do in this space.</p>
  424.    <p>Oh wait, did I just say “AI”? Yes, yes I did. Let’s look at another picture, in this case a lousy picture.</p>
  425.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/TXT55638.png" alt="Picture of an under-construction high-rise behind leaves" />
  426.    <p>I was out for a walk and thought the building behind the tree was interesting. I was disappointed when I pulled it up on the
  427.    screen, but I still liked the shape and decided to try and save it.</p>
  428.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/TXT55638-good.png" alt="Picture of an under-construction high-rise behind leaves, improved" />
  429.    <p>So I used Lightroom’s “Select Sky” to recover its color, and “Select Subject” to pull the building details out of the
  430.    shadows. Both of these Lightroom features, which are pretty magic and I use all the time, are billed as being AI-based. I
  431.    believe it.</p>
  432.    <p>Let’s look at what the C2PA discloses.</p>
  433.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/lr-tower.png" alt="Lightroom C2PA assertions with automation AI" />
  434.    <p>Having said all that, if you look at the C2PA (or at the data behind it) Lightroom discloses only “Color or Exposure”,
  435.    “Cropping”, and “Drawing” edits. Nothing about AI.</p>
  436.    <p>Hmm. Is that OK? I personally think it is, and highlights the distinction between what I’d call “automation” AI and
  437.    Generative AI. I mean, selecting the sky and subject is something that a skilled Photoshop user could accomplish with a lot of
  438.    tinkering, the software is just speeding things up. But I don’t know, others might disagree.</p>
  439.    <p>Well, how about that generative AI?</p>
  440.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/chatgpt.png" alt="Turtle in shallow water, generated by ChatGPT" />
  441.    <div class='caption'><p>Fails <code>c2patool</code> validation, “DigitalSourceType” is <code>trainedAlgorithmicMedia</code></p></div>
  442.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/budai.png" alt="Desktop with decorations, Magic Erase has been applied" />
  443.    <div class='caption'><p>“DigitalSourceType” is <code>compositeWithTrainedAlgorithmicMedia</code></p></div>
  444.    <p>The turtle is 100% synthetic, from ChatGPT, and on the right is a Pixel 10 shot on which I did a few edits including “Magic
  445.    Eraser”.  Both of these came with Content Credentials; chatGPT’s is actually invalid, but on the glass-half-full front, the
  446.    Pixel 10’s were also invalid up until a few days ago, then they fixed it. So this stuff does get fixed.</p>
  447.    <p>I’m happy about the consistent use of C2PA terminology, they are clearly marking the images as genAI-involved.</p>
  448.    <p>I’m about done talking about the state of the Content Credentials art generally but I should probably talk about this
  449.    device.</p>
  450.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/pixel-10.png" alt="Blue Pixel 10" />
  451.    <p>Because it marks the arrival of Content Credentials on the mass consumer market. Nobody knows how many Pixels Google actually
  452.    sells but I guarantee it’s a lot more than Leica sells M11’s. And since Samsung tends to follow Google pretty closely, we’re
  453.    heading for tens then hundreds of millions of C2PA-generating mobile devices. I wonder when Apple will climb on board?</p>
  454.    <p>Let’s have a look at that C2PA.</p>
  455.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/p10-c2pa.png" alt="C2PA associated with Magic Eraser image" />
  456.    <p>This view of the C2PA is from the Google Photos app.  It’s very limited.  In particular, there is nothing in there to support
  457.    provenance. In fact, it’s the opposite, Google is bending over backward to avoid anything that could be interpreted as breaking the
  458.    privacy contract by sharing information about the user.</p>
  459.    <p>Let’s pull back the covers and dig a little deeper. Here are a few notes</p>
  460.    <ul>
  461.      <li><p>The device is identified just as “Pixel camera”. There are lots of different kinds of those!</p></li>
  462.      <li><p>The C2PA inclusion is Not optional!</p></li>
  463.      <li><p>DigitalSourceType:  <code>computationalCapture</code>
(if no genAI)</p></li>
  464.      <li><p>Timestamp is “untrusted”</p></li>
  465.    </ul>
  466.    <p>The C2PA not being optional removes a lot of UI issues but still, well, I’m not smart enough to have fully thought through
  467.    the implications. That Digital Source Type looks good and appropriate, and the untrusted-ness of the timestamp is
  468.    interesting.</p>
  469.    <p>You notice that my full-workflow examples featured a Leica rather than the Pixel, and that’s because the toolchain is
  470.    currently broken for me: Neither Lightroom nor Photoshop can handle the P10 C2PA. I’ll skip the details, except to say that
  471.    Adobe is aware of the bug, a version mismatch, and they say they’re working on it.</p>
  472.    <p>Before we leave the Pixel 10, I should say that there are plenty of alternate camera apps in Android and iOS, some quite
  473.    good, and it’d be perfectly possible for them to ship much richer C2PA, notably including provenance, location, and so on.</p>
  474.    <p>I guess that concludes my look at the current state of the Content Credentials art. Now I’d like to talk about what Content
  475.    Credentials are for.  To start with, I think it’d be helpful to sort the assertions into three baskets.</p>
  476.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/3-baskets-1.png" alt="C2PA assertions in Capture, Processing, and Provenance baskets" />
  477.    <p>Capture, that’s like that Leica EXIF stuff we showed earlier. What kind of camera and lens, what the shooting parameters
  478.    were. Processing, that’s like the Lightroom report: How was the image manipulated, and by what software. Provenance: Which
  479.    person or organization produced this?</p>
  480.    <p>But I think this picture has an important oversimplification, let me fix that.</p>
  481.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/3-baskets-2.png" alt="C2PA assertion baskets with the addition of GenAI" />
  482.    <p>Processing is logically where you’d disclose the presence of GenAI.  And in terms of what people practically care about,
  483.    that’s super important and deserves special consideration.</p>
  484.    <p>Now I’m going to leave the realm of facts and give you opinions. As for the Capture data there on the left… who cares?
  485.    Really, I’m trying to imagine a scenario in which anyone cares about the camera or lens or F stop.  I guess there’s an exception
  486.    if you want to prove that the photo was taken by one of Annie Liebowitz’s cameras, but that’s really provenance.</p>
  487.    <p>Let’s think about a professional publication scenario. They get photos from photographers, employees or agencies or
  488.    whatever. They might want to be really sure that the photo was from the photographer and not an imposter. So having C2PA
  489.    provenance would be nice. Then when the publisher gets photos, they do a routine check of the provenance and if it doesn’t check
  490.    out, they don’t run the picture without a close look first.</p>
  491.    <p>They also probably want to check for the “is there genAI?” indicator in the C2PA, and, well, I don’t know what they might do,
  492.    but I’m pretty sure they’d want to know.</p>
  493.    <p>That same publisher might want to equip the photos they publish with C2PA, to demonstrate that they are really the ones who
  494.    chose and provided the media. That assertion should be applied routinely by their content management system.  Which should be
  495.    easy, on the technology side anyhow.</p>
  496.    <p>So from the point of view of a professional publisher, provenance matters, and being careful about GenAI matters, and in the
  497.    C2PA domain, I think that’s all that really matters.</p>
  498.    <p>Now let’s turn to Social Media, which is the source of most of the images that most people see most days.  Today, all the
  499.    networks strip all the photo metadata, and that decision involves a lot of complicated privacy and intellectual-property
  500.    thinking.  But there is one important FACT that they know: For any new piece of media, they know which account uploaded the damn
  501.    thing, because that account owner had to log in to do it. So I think it’s a no-brainer that IF THE USER WISHES, they can have a
  502.    Content Credentials assertion in the photo saying “Initially uploaded by Tim Bray at LinkedIn” or whoever at wherever.</p>
  503.    <p>What we’d like to achieve is that if you see some shocking or controversial media, you’d really want to know who originally
  504.    posted it before you decided whether you believed it, and if Content Credentials are absent, that’s a big red flag. And if the
  505.    picture is of the current situation in Gaza, your reaction might be different depending on whether it was originally from an
  506.    Israeli military social-media account, or the Popular Front for the Liberation of Palestine, or by the BBC, or by
  507.    igor282356057@popular.online.</p>
  508.    <p>Anyhow, here’s how I see it:</p>
  509.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/18/3-baskets-3.png" alt="C2PA assertion baskets inflated according to their relative importance" />
  510.    <p>So for me, it’s the P and A in C2PA that matter – provenance and authenticity. I think the technology has the potential to
  511.    change the global Internet conversation for the better, by making it harder for liars to lie and easier for truth-tellers to be
  512.    believed. I think the first steps that have been taken so far are broadly correct and the path forward is reasonably clear. All
  513.    the little things that are broken, we can fix ’em.</p>
  514.    <p>And there aren’t that many things that matter more than promoting truth and discouraging lies.</p>
  515.    <p>And that’s all, folks.</p>
  516. </div></content></entry>
  517.  
  518. <entry>
  519. <title>Maritime Wrap-up</title>
  520. <link href='https://www.tbray.org/ongoing/When/202x/2025/09/13/Maritime-Wrap' />
  521. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/09/13/Maritime-Wrap#comments' />
  522. <id>https://www.tbray.org/ongoing/When/202x/2025/09/13/Maritime-Wrap</id>
  523. <published>2025-09-13T12:00:00-07:00</published>
  524. <updated>2025-09-15T22:22:33-07:00</updated>
  525. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Maritimes' />
  526. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  527. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  528. <category scheme='https://www.tbray.org/ongoing/What/' term='Maritimes' />
  529. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Only a few more pictures to share from     <a href='/ongoing/When/202x/2025/08/27/Maritime-Vacation'>our vacation</a>, which I’ll wrap up in conventional tourism     advice</div></summary>
  530. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  531.    <p>Only a few more pictures to share from
  532.    <a href="/ongoing/When/202x/2025/08/27/Maritime-Vacation">our vacation</a>, which I’ll wrap up in conventional tourism
  533.    advice.</p>
  534.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55876.png" alt="Looking down off a cliff at a tiny boat far below" />
  535.    <div class='caption'><p>It’s mostly about the oceanfront, and what you can see from it.</p></div>
  536.    <h2 id='p-1'>Food and drink</h2>
  537.    <p>I recommend all of the following.</p>
  538.      <p><a href="https://www.schoolhousebrewery.ca">Schoolhouse Brewery</a> in Windsor, NS; nice space, decent food, the Vice Principal is
  539.      a good IPA.  Maybe the  beer that I enjoyed most was “Exile on North Street” from
  540.      <a href="https://unfuckingfiltered.com/beer/">unfiltered brewing</a>; you might want to follow that link and also check out
  541.      the URL.</p>
  542.      <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/PXL_20250815_230941783.png" alt="sunset through grasses" />
  543.      <p>I didn’t love Halifax that much but it has this charming little neighborhood called
  544.      <a href="https://en.wikipedia.org/wiki/Hydrostone">Hydrostone</a>, where
  545.      <a href="https://www.thebrownhound.ca">The Brown Hound</a> offered very solid food and beer.
  546.      We didn’t spend that much time in New Brunswick, but Moncton’s
  547.      <a href="https://www.pumphousebrewpub.ca">Pump House</a> was cheery and competent; a cool space; I can’t remember which of
  548.      their IPAs I had, but it was good. The other peak New Brunswick goodness was
  549.      <a href="https://www.adorablechocolat.ca">Adorable Chocolat</a> in Shediac, where everyone was effortlessly bilingual and the
  550.      pastries just divine. Don’t miss it if you’re anywhere near.</p>
  551.      <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55910.png" alt="Cape Breton coastline, people swimming, houses on the slopes" />
  552.      <div class='caption'><p>People live by the sea, and swim in it.</p></div>
  553.      <p>Charlottetown’s not that rich in dining options, but got a really excellent lunch at
  554.      <a href="https://www.thecorkandcast.com">The Cork &amp; Cast</a>.
  555.      Maybe our best meal of the trip was at
  556.      <a href="https://wheelhouseseafoodpasta.ca/menu#SEAFOOD">The Wheelhouse</a>, in Digby. Scallops all around, seared is the best
  557.      option.
  558.    </p>
  559.    <h2 id='p-5'>Cities, towns, and other tourists</h2>
  560.    <p>Every good tourist spot in the world seems to suffer from increasingly intense and persistent overcrowding, and the Maritimes
  561.    are no exception.  On top of which, they’re thinly populated, fewer than two million souls in three provinces. The biggest city,
  562.    Halifax (and the entire province of Prince Edward Island) are both smaller than individual Vancouver suburbs. It’s not a place
  563.    for savouring urban flavors.</p>
  564.    <p>In Nova Scotia, Halifax has too many cruise ships; stay away from its so-called “farmers market” unless you love cruise
  565.    culture. Lunenberg is big enough to soak up its waves of visitors and still offer unique visuals.</p>
  566.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55847.png" alt="Tourists at Peggy’s Cove" />
  567.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55848.png" alt="The cove at Peggy’s Cove" />
  568.    <div class='caption'><p>Overcrowded but has nice bits.</p></div>
  569.    <p>Peggy’s Cove I just can’t recommend; beautiful but jam-packed
  570.    with cars looking for parking and people risking their lives on the rocks.</p>
  571.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/PXL_20250822_163228719.png" alt="Fort Anne in Annapolis Royal" />
  572.    <div class='caption'><p>These were once defences but now just a pleasant walk.</p></div>
  573.    <p>I do recommend visiting <a href="https://en.wikipedia.org/wiki/Annapolis_Royal">Annapolis Royal</a>; it’s got that great garden
  574.    and Fort Anne, despite its lengthy and chequered military history, is lovely and peaceful.</p>
  575.    <p>In PEI, Charlottetown makes an effort and it has a beautiful basilica, but just isn’t big enough to reward a whole day’s
  576.    visit.</p>
  577.    <p>In NB, Moncton is OK but its biggest tourist attraction is the tide going in and out.</p>
  578.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55961.png" alt="Crowded tidal flat at Hopewell Provincial Park" />
  579.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT55966.png" alt="Clifftop forest at Hopewell Provincial Park" />
  580.    <div class='caption'><p>Hopewell Provincial Park, NB. The clifftop trees are exceptional.</p></div>
  581.    <h2 id='p-3'>Lodging</h2>
  582.    <p>The hotels and Airbnbs and VRBOs were OK, mostly. The
  583.    <a href="https://www.theharbourviewinn.com">Harbourview Inn</a>, near Digby, is a charmingly-traditional guest-house. The rooms
  584.    are OK, but the downstairs is warmly welcoming, drinks available when the host’s there to man the bar, lots of space to sink
  585.    into a comfy chair and conversation or your laptop. Also the breakfast was solid.</p>
  586.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/PXL_20250813_113114060.png" alt="Sky drama over Lake Ainsley" />
  587.    <div class='caption'><p>Excited clouds over Lake Ainsley, NS.</p></div>
  588.    <p>But the trip’s lodging highlight was this VRBO called
  589.    <a href="https://www.vrbo.com/en-ca/cottage-rental/p9830781">Forest Lake House</a> on Lake
  590.    Ainsley, the Maritimes’ biggest. Isolated, comfortable, outstanding grounds, your own private forest walk; everything anyone
  591.    could want. We stopped traveling and had a chill-out day there, enjoying every minute of it.</p>
  592.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/PXL_20250817_152127492.png" alt="Swimming at Cavendish, PEI" />
  593.    <div class='caption'><p>Lots of people but plenty at room at Cavendish beach.</p></div>
  594.    <h2 id='p-4'>Otherwise</h2>
  595.    <p>We only swam once, at Cavendish Beach in PEI’s Anne of Green Gables territory, very nicely set up.  But what looked
  596.    most appealing to me was
  597.    <a href="https://www.lockeport.ns.ca/index.php/tourism-recreation/crescent-beach-vic">Crescent Beach</a> in Lockeport, Nova
  598.    Scotia; I wish we’d made time to have a swim there.</p>
  599.    <p>Turns out all three vacationers had farming or agriculture-adjacent roots. If you care about that stuff, driving around PEI
  600.    is a treat; the agriculture is super-intensive and, to my eye, pleasingly well-done.</p>
  601.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT56060.png" alt="A farm field with hay bales by the seaside" />
  602.    <div class='caption'><p>The farmlands extend to the seaside.</p></div>
  603.    <p>But if you have the time, get away from PEI’s farms and head northwest, drive
  604.    down the coast from Tignish to West Point; that ride is full of colors and sea-fronts that aren’t like anywhere else I’ve
  605.    seen.</p>
  606.    <p>Since it’s the New World there’s plenty of nasty history around the indigenous folk, the
  607.    <a href="https://en.wikipedia.org/wiki/Mi%27kmaq">Mi'kmaq</a> nation. But you really have to look to find it. We visited the
  608.    <a href="https://www.millbrookheritagecentre.ca">Millbrook Cultural &amp; Heritage Centre</a> in Truro, which is much better
  609.    than nothing.</p>
  610.    <p>You gotta drive; we put 3,742km on a basic rented Kia. The roads are way better taken care of than here out West.</p>
  611.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT56014.png" alt="Maritime sunset" />
  612.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/PXL_20250824_214226484.png" alt="The ocean near Liverpool, NS" />
  613.    <div class='caption'><p>Bye-bye, Maritimes.</p></div>
  614.    <p>We didn’t run across a single human Maritimer who was anything less than friendly and welcoming.</p>
  615.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/13/TXT56069.png" alt="A white house perched on rocks above the sea-side" />
  616.    <p>Nice people living along
  617.    beautiful oceanfronts, plenty good enough for me.</p>
  618. </div></content></entry>
  619.  
  620. <entry>
  621. <title>Maritime Colors</title>
  622. <link href='https://www.tbray.org/ongoing/When/202x/2025/09/01/Maritime-Colors' />
  623. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/09/01/Maritime-Colors#comments' />
  624. <id>https://www.tbray.org/ongoing/When/202x/2025/09/01/Maritime-Colors</id>
  625. <published>2025-09-01T12:00:00-07:00</published>
  626. <updated>2025-09-05T22:48:59-07:00</updated>
  627. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Maritimes' />
  628. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  629. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  630. <category scheme='https://www.tbray.org/ongoing/What/' term='Maritimes' />
  631. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos/Cameras' />
  632. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  633. <category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
  634. <category scheme='https://www.tbray.org/ongoing/What/' term='Cameras' />
  635. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>When someone (<a href='/ongoing/When/202x/2025/08/27/Maritime-Vacation'>like us</a>)     comes back from a trip to the Maritimes, they’re apt to have pictures of     brightly-colored houses. This is to show those colors off and not just in houses. Plus a camera color     conundrum</div></summary>
  636. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  637.    <p>When someone (<a href="/ongoing/When/202x/2025/08/27/Maritime-Vacation">like us</a>)
  638.    comes back from a trip to the Maritimes, they’re apt to have pictures of
  639.    brightly-colored houses. This is to show those colors off and not just in houses. Plus a camera color
  640.    conundrum.</p>
  641.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/TXT55945.png" alt="A trailer park with small building covered by bright colored fenders" />
  642.    <div class='caption'><p>On the northwest coast of PEI, probably near Cape Wolfe.</p></div>
  643.    <p>In that picture above, glance at the bit of beach showing left of the little lighthouse. There’s a color story there
  644.    too.</p>
  645.    <h2 id='p-1'>Residentials</h2>
  646.    <p>As it happens, our very first outing on the vacation was to
  647.    <a href="https://en.wikipedia.org/wiki/Lunenburg,_Nova_Scotia">Lunenberg</a>, which features those cheerful houses.</p>
  648.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/TXT55826.png" alt="Brightly colored houses in Lunenberg" />
  649.    <p>It wasn’t just tourist magnets like Lunenberg; anywhere in the Maritimes you’re apt to see exuberantly-painted
  650.    residences, a practice I admire. While the Maritimes are a long way from my home in Vancouver, we share a long, dim, grey
  651.    winter, and any splash of color can help with that Seasonal Affective Disorder.</p>
  652.    <p>Also, we
  653.    <a href="/ongoing/When/202x/2025/02/28/Moved">recently bought a house</a> and, while we like it, it’s an undistinguished
  654.    near-grey, so we’re looking for color schemes to steal.
  655.    Thus I took lots of pictures of bright houses.</p>
  656.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/PXL_20250822_180516990.png" alt="Apricot-and-brown house" />
  657.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/TXT55828.png" alt="Blue house in Lunenberg" />
  658.    <p>A couple years back we painted our cabin a cheery blue based on sampling photos of the shutters on Mykonos. A few
  659.    neighbors rolled their eyes but nobody’s actually complained.</p>
  660.    <h2 id='p-2'>Red</h2>
  661.    <p>That’s the other color you have to talk about down east; I mean the color of the soil and sand and rocks. PEI in
  662.    particular is famous for its red dirt, when you come in the on the ferry from Nova Scotia the first thing you notice is the
  663.    island’s red fringe. I took a million pictures and maybe this is the closest to capturing it.</p>
  664.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/TXT55948.png" alt="Red sand and dirt on a PEI beachfront" />
  665.    <div class='caption'><p>Not far from that first picture.</p></div>
  666.    <h2 id='p-3'>Green Conundrum</h2>
  667.    <p>One of Nova Scotia’s attractions is the
  668.    <a href="https://en.wikipedia.org/wiki/Cabot_Trail">Cabot Trail</a>, a 300km loop around Cape Breton, stretching northeast out
  669.    into the Atlantic. This one scenic turn-off has you looking at a big, densely-forested mountainside.
  670.    It’s more chaotic than our West-Coast temperate rain forests, with many tree species jumbled together. The
  671.    spectrum of greens under shifting clouds was a real treat for the eyes. Here are two of the pictures I came away with.
  672.    Have a look at them for a moment.</p>
  673.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/PXL_20250813_161053505.png" alt="Forested mountainside" />
  674.    <img src="https://www.tbray.org/ongoing/When/202x/2025/09/01/TXT55881.png" alt="Forested mountainside" />
  675.    <p>Above is by my Pixel 7, below a modern Fujifilm camera.  When I unloaded them on the
  676.    big outboard screen, I was disappointed with the Fujifilm take, which seemed a little flat and boring; was thinking the Pixel had
  677.    done better. But then I started feeling uneasy; my memory kept telling me that that mountainside just
  678.    didn’t include that yellow flavor in the Pixel’s highlights. I mean, those highlights look great, but I’m pretty sure they’re lies.</p>
  679.    <p>After a while, I edited the Fujifilm version just a teeny bit, gently bumping Lightroom’s “exposure” and “Vibrance” sliders, and
  680.    I thought what
  681.    I got was very close to what I remembered. The Pixel photo is entirely un-touched.</p>
  682.    <p>I’m not sure what to think. Mobile-phone cameras in general and the Pixel in particular proudly boast their “computational
  683.    photography” and “AI” chops and, yeah, the Pixel produced a photo that it’s hard not to like.</p>
  684.    <p>And quite a few of the pictures I publish in this space have have been adjusted pretty heavily in Lightroom. I stand by my
  685.    claim that I’m mostly trying to make something that looks like what I saw. But increasingly, I suspect the Pixel is showing
  686.    colors people like, as opposed to what’s real.</p>
  687. </div></content></entry>
  688.  
  689. <entry>
  690. <title>Maritime Birds and Bees</title>
  691. <link href='https://www.tbray.org/ongoing/When/202x/2025/08/30/Maritime-Wildlife' />
  692. <link rel='replies'        thr:count='0'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/08/30/Maritime-Wildlife#comments' />
  693. <id>https://www.tbray.org/ongoing/When/202x/2025/08/30/Maritime-Wildlife</id>
  694. <published>2025-08-30T12:00:00-07:00</published>
  695. <updated>2025-08-31T09:05:08-07:00</updated>
  696. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Maritimes' />
  697. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  698. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  699. <category scheme='https://www.tbray.org/ongoing/What/' term='Maritimes' />
  700. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Nova Scotia and New Brunswick each have plenty of wilderness; PEI not so much. So pictures of bears and cougars and so on     would be plausible, as would marine mammals. But no. Herewith, from our     <a href='/ongoing/When/202x/2025/08/27/Maritime-Vacation'>recent vacation</a>, birds and bees, with a little     lens-geek side trip</div></summary>
  701. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  702.    <p>Nova Scotia and New Brunswick each have plenty of wilderness; PEI not so much. So pictures of bears and cougars and so on
  703.    would be plausible, as would marine mammals. But no. Herewith, from our
  704.    <a href="/ongoing/When/202x/2025/08/27/Maritime-Vacation">recent vacation</a>, birds and bees, with a little
  705.    lens-geek side trip.</p>
  706.    <h2 id='p-1'>Birds</h2>
  707.    <p>Having touristed around Charlottetown, we drove down a series of smaller and smaller back roads and ended up
  708.    at Canceaux Cove near Rocky Point, which I thought might present a nice vista of the city. It did, but the city looks boring.
  709.    By way of consolation, there were these cute little birds running around on the beach and then flying loops in formation over the
  710.    water.</p>
  711.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT55982.png" alt="Small birds on a beach" />
  712.    <div class='caption'><p>Pretty sure these are
  713.    <a href="https://en.wikipedia.org/wiki/Semipalmated_plover">Semipalmated plovers</a>.</p></div>
  714.    <p>I wanted to get a picture of them in the air so I sauntered down the beach, assuming
  715.    they’d fly away picturesquely. They studiously ignored me and eventually I had to jump and down and wave my arms and even then
  716.    they took off grudgingly.</p>
  717.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT55984.png" alt="small birds flying over the ocean" />
  718.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT55987.png" alt="small birds flying over the ocean" />
  719.    <p>They were graceful and did this mysterious thing that birds can do, staying in formation with no obvious leader.
  720.    I’ve had the pleasure, very occasionally, of being in engineering teams like that.</p>
  721.    <h2 id='p-2'>Bees</h2>
  722.    <p>We went to
  723.    <a href="https://en.wikipedia.org/wiki/Annapolis_Royal">Annapolis Royal</a> because of its
  724.    <a href="https://historicgardens.wordpress.com">Historic Gardens</a> and wow, what a treat. I think even those who don’t see
  725.    themselves as garden fans would enjoy an hour or more sauntering around in there.  I like taking pictures of flowers and a lot
  726.    of these flowers had bees in them.</p>
  727.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56034-2.png" alt="Three orange flowers, one with bee" />
  728.    <p>This one was cute enough to reward a close-up.</p>
  729.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56034.png" alt="Close-up of bee in orange flower." />
  730.    <div class='caption'><p>Aren’t her wings cute?</p></div>
  731.    <p>And I ask, what could be better than a cute bee in a pretty flower? Obviously, <em>two</em> bees.</p>
  732.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56040.png" alt="Two bees in an orange flower" />
  733.    <p>And again, a closer look.</p>
  734.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56040-2.png" alt="Two bees in an orange flower, close-up" />
  735.    <p>Bees are admirable creatures and I don’t want to make fun of them, but this surprised-looking little citizen makes me
  736.    laugh. (She’s just navigating from one blossom to the next.)</p>
  737.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56045.png" alt="bee caught in flight among the blossoms" />
  738.    <h2 id='p-3'>Lens</h2>
  739.    <p>All of these are shot with Fujifilm’s
  740.    <a href="https://www.fujifilm-x.com/en-ca/products/lenses/xf55-200mmf35-48-r-lm-ois/">55-200mm</a> lens, which I’ve had for at
  741.    least eleven years. Up till now, I’ve always pointed it at faraway things, but wow, I think I’ll be taking this to more gardens
  742.    in future.</p>
  743.    <p>I mention the lens partly so I can link to this
  744.    <a href="https://www.lensrentals.com/blog/2016/02/the-long-awaited-scary-and-amazing-fuji-lens-teardown/?srsltid=AfmBOorQfgob6drIXwtTJ9xuixBbnSvZE2F8x7Jba0AA3U60uoFAB3gY">awesome
  745.    (and funny) teardown piece</a> from Lensrentals.</p>
  746.    <p>And, on the way out, let’s let that lens show off with a couple of roses.</p>
  747.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56057.png" alt="Yellow rose and bud" />
  748.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/30/TXT56058.png" alt="Pink roses, black background" />
  749.    <p>Remember, pink and black are the colors of rock &amp; roll.
  750.    And if you’re anywhere near Annapolis Royal, stop and visit that garden.</p>
  751. </div></content></entry>
  752.  
  753. <entry>
  754. <title>Maritime Vacation</title>
  755. <link href='https://www.tbray.org/ongoing/When/202x/2025/08/27/Maritime-Vacation' />
  756. <link rel='replies'        thr:count='0'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/08/27/Maritime-Vacation#comments' />
  757. <id>https://www.tbray.org/ongoing/When/202x/2025/08/27/Maritime-Vacation</id>
  758. <published>2025-08-27T12:00:00-07:00</published>
  759. <updated>2025-08-28T12:36:15-07:00</updated>
  760. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Maritimes' />
  761. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  762. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  763. <category scheme='https://www.tbray.org/ongoing/What/' term='Maritimes' />
  764. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>The sound of the wind surging through birchy Eastern woods isn’t like the same coastal gusts in my own Pacific rain     forest; around you not above you, alto not baritone. The colors differ too: Forests, houses, soil, and sea. And everywhere     little white churches, each with its cemetery. A scattering of forts, far too many cannons.  And everything faces the sea</div></summary>
  765. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  766.    <p>The sound of the wind surging through birchy Eastern woods isn’t like the same coastal gusts in my own Pacific rain
  767.    forest; around you not above you, alto not baritone. The colors differ too: Forests, houses, soil, and sea. And everywhere
  768.    little white churches, each with its cemetery. A scattering of forts, far too many cannons.  And everything faces the sea.</p>
  769.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/PXL_20250814_142523016.png" alt="Cape Breton forest" />
  770.    <div class='caption'><p>Birchy Cape Breton forest.</p></div>
  771.    <p>For the first time since Covid and, more important, since Lauren’s 2½-year battle with Long Covid, we went on the road for
  772.    pleasure; Lauren and I and our dear friend Sally from Warragul, Australia. To my shame, all my decades’ travel had never taken
  773.    me to Canada east of Montreal, so we spent a couple of weeks poking around Nova Scotia and Prince Edward Island, plus a bit of
  774.    New Brunswick. I took many pictures and it’ll take a few blog pieces to share those that I think deserve it.</p>
  775.    <p>No part of Canada’s settler culture is old by European or Asian standards, but ten generations of white people
  776.    lived and died here before the first rough town organized itself near what’s now Vancouver. They had to be buried someplace, thus the
  777.    graveyards everywhere you go. These were captured near Whycocomagh.</p>
  778.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT55871.png" alt="Gravestone of Lillian S. DeWolfe, 1876-1958" />
  779.    <div class='caption'><p>Lillian S. DeWolfe, Oct 1876 Sept 1958.</p></div>
  780.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT55874.png" alt="A simple grave marker saying only “sleeping”" />
  781.    <p>How long will it still matter that my hometown is one of the world’s youngest big cities?</p>
  782.    <p>Many graveyards are church attachments, but many more greet you at a random turn in the road; always framed by forest.
  783.    The density of churches is remarkable; all built of wood, mostly white, mostly well-kept. This one was attached to the graves
  784.    above and is untypically faded (but lovely inside).</p>
  785.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT55869.png" alt="Square white wooden church, it needs a paint job" />
  786.    <p>Some of the churches have become boutiques and breweries, but those that haven’t still occur more densely than in any other
  787.    New World jurisdiction I’ve seen. Why should faith hold stronger down East?</p>
  788.    <p>Another church, St Dunstan’s Basilica in Charlottetown, offered perhaps the most intense experience of the whole trip,
  789.    because a singer and organist were practicing elaborate hymn treatments. Both were great, the organ is a magnificent Casavant,
  790.    and parish organist
  791.    <a href="https://en.wikipedia.org/wiki/Leo_Marchildon">Leo Marchildon</a> was having fun, putting lots of wind through those
  792.    pipes including the 32’ bass monsters.  My ears and I were smiling when we left.</p>
  793.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT55925.png" alt="Stained glass in St. Dunstan’s Basilica, Charlottetown" />
  794.    <div class='caption'><p>The stained glass is nothing special<br/>but I liked the opened panes at the bottom.</p></div>
  795.    <p>Forts and cannons, I said; the Maritimes’ messy history included repeated captures and recaptures by the forces of France and
  796.    Britain and the USA, and quite a few of the forts had been put to their intended use, repelling or falling to one invader or
  797.    another.</p>
  798.    <p>The locals, at least the ones who set things up for tourists, seem to take their history seriously; I don’t pretend
  799.    expertise or even much interest in it, but I have to say that some cannons have good typography.</p>
  800.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/PXL_20250824_214613137.png" alt="Engraving on metal: Crown and “VR”" />
  801.    <div class='caption'><p>“VR” is Victoria Regina of course,<br/>so sometime in the second half of the 19<sup>th</sup>
  802.    century.</p></div>
  803.    <p>The colors are different, and an entry later in this series will dip in gleefully and give me a platform for camera geekery.
  804.    One expects changes in houses and vegetation when you travel four timezones away, but nothing prepared
  805.    me for the shockingly red soil in Prince Edward Island (hereinafter PEI).</p>
  806.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT55937.png" alt="red and blue see, red soil, wind turbines" />
  807.    <div class='caption'><p>Past Tignish at PEI’s northern extremity,<br/>well off the paved-roads part.</p></div>
  808.    <p>I opened with words about everything facing the sea. Not entirely true, sometimes you’re looking at a lake.</p>
  809.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/PXL_20250823_162017189.png" alt="Kids in a large calm lake, circular ripples" />
  810.    <div class='caption'><p>Those kids don’t know how lucky they are.</p></div>
  811.    <p>This is in the wonderful Kejimkujik National Park in central Nova Scotia, mostly closed due to extreme wildfire peril.</p>
  812.    <p>All across the Maritimes, drought was in effect; crops failing, forest trails closed. Which reminds me; near that lake there was a
  813.    birch-bark-canoe workshop. I asked the guy making the canoe how long it took. He said “My great-grandpa could do it in seven days,
  814.    because back then there were birch trees big enough that you could make the whole hull out of a single piece.”  It’s very
  815.    difficult to find any aspect of life on earth that isn’t exhibiting Anthropocene damage.</p>
  816.    <p>Usually, it’s the sea that you’re looking at.</p>
  817.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/TXT56066.png" alt="Nova Scotia coastline near Annapolis Royal" />
  818.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/PXL_20250822_223613924.png" alt="rocky beach at low tide" />
  819.    <div class='caption'><p>Above, coastline near Annapolis Royal.<br/>Below, low tide near Chipman Brook.</p></div>
  820.    <p>From one end of Canada to the other; to me, the surprise was not so much the difference in the landscapes but the similarity
  821.    of the people; they spoke my accent, shopped in my stores, obeyed my road signs. More on that later. For now, this.</p>
  822.    <img src="https://www.tbray.org/ongoing/When/202x/2025/08/27/PXL_20250825_141305938.png" alt="Trees frame the seawater and a couple of oceanfront houses" />
  823.    <div class='caption'><p>On Bell Island, among the LaHaves.</p></div>
  824. </div></content></entry>
  825.  
  826. <entry>
  827. <title>RFC 9839 and Bad Unicode</title>
  828. <link href='https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839' />
  829. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/08/14/RFC9839#comments' />
  830. <id>https://www.tbray.org/ongoing/When/202x/2025/08/14/RFC9839</id>
  831. <published>2025-08-14T12:00:00-07:00</published>
  832. <updated>2025-08-23T03:17:06-07:00</updated>
  833. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Text' />
  834. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  835. <category scheme='https://www.tbray.org/ongoing/What/' term='Text' />
  836. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain     Unicode characters encoded in UTF-8. There’s another question, though:     “<em>Which</em> Unicode characters?” The      answer is “Not all of them, please exclude some.”</div></summary>
  837. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  838.    <p>Unicode is good. If you’re designing a data structure or protocol that has text fields, they should contain
  839.    Unicode characters encoded in UTF-8. There’s another question, though:
  840.    “<em>Which</em> Unicode characters?” The
  841.    answer is “Not all of them, please exclude some.”</p>
  842.    <p>This issue keeps coming up, so Paul Hoffman and I put together an individual-submission draft
  843.    to the IETF and now (where by “now” I mean “two years later”) it’s been published as
  844.    <a href="https://www.rfc-editor.org/rfc/rfc9839.html">RFC 9839</a>. It explains which characters are bad, and why, then offers
  845.    three plausible less-bad subsets that you might want to use.
  846.    Herewith a bit of background, but…</p>
  847.    <h2 id='p-2'>Please</h2>
  848.    <p>If you’re actually working on something new that will have text fields, please read the RFC. It’s only ten pages long, and that’s
  849.    with all the IETF boilerplate. It’s written specifically for software and networking people.</p>
  850.    <h2 id='p-3'>The smoking gun</h2>
  851.    <p>The badness that 9839 focuses on is “problematic characters”, so let’s start with a painful example of what that means.
  852.    Suppose you’re designing a protocol that uses JSON and one of your constructs has a <code>username</code> field.
  853.    Suppose you get this message (I omit all the non-<code>username</code> fields). It’s
  854.    a perfectly legal JSON text:</p>
  855.    <div class="highlight"><pre><span></span><span class="p">{</span>
  856.  <span class="w">  </span><span class="nt">&quot;username&quot;</span><span class="p">:</span><span class="w"> </span><span class="s2">&quot;\u0000\u0089\uDEAD\uD9BF\uDFFF&quot;</span>
  857. <span class="p">}</span>    </pre></div>
  858.    <p>Unpacking all the JSON escaping gibberish reveals that the value of the <code>username</code> field contains four
  859.    numeric “code points” identifying Unicode characters:</p>
  860.    <ol>
  861.      <li><p>The first code point is zero, in Unicode jargon <code>U+0000</code>. In human-readable text it
  862.      has no meaning, but it will interfere with the operation of certain programming languages.</p></li>
  863.      <li><p>Next is Unicode <code>U+0089</code>, official name “CHARACTER TABULATION WITH JUSTIFICATION”. It’s what Unicode calls a
  864.      <a href="https://en.wikipedia.org/wiki/C0_and_C1_control_codes">C1
  865.      control code</a>, inherited from ISO/IEC 6429:1992, adopted from
  866.      <a href="https://www.ecma-international.org/wp-content/uploads/ECMA-48_5th_edition_june_1991.pdf">ECMA 48</a> (1991), which calls it
  867.      “HTJ” and says: <i>HTJ causes the contents of the active field (the field in the presentation component that contains the
  868.      active presentation position) to be shifted forward so that it ends at the character position preceding the
  869.      following character tabulation stop. The active presentation position is moved to that following character
  870.      tabulation stop. The character positions which precede the beginning of the shifted string are put into the
  871.      erased state.</i></p>
  872.      <p>Good luck with that.</p></li>
  873.      <li><p>The third code point, <code>U+DEAD</code>, in Unicode lingo, is an “unpaired surrogate”.  To understand,
  874.      you’d have to learn how Unicode’s much-detested
  875.      <a href="https://en.wikipedia.org/wiki/UTF-16">UTF-16</a> encoding works.
  876.      I recommend not bothering.</p>
  877.      <p>All you need to know is that surrogates are only meaningful when they come in pairs in UTF-16 encoded text. There is
  878.      effectively no such text on the wire and thus no excuse for tolerating surrogates in your data. In fact, the UTF-8 specification
  879.      says that you mustn’t use UTF-8 to encode surrogates. But the real problem is that different libraries in different
  880.      programming languages don’t always do the same things when they encounter this sort of fœtid interloper.</p>    </li>
  881.      <li><p>Finally, <code>\uD9BF\uDFFF</code> is JSON for the code point <code>U+7FFFF</code>.
  882.      Unicode has a category called “noncharacter”, containing a few dozen code points that, for a variety of
  883.      reasons, some good,
  884.      don’t represent anything and must not be interchanged on the wire. <code>U+7FFFF</code> is one of those.</p></li>
  885.    </ol>
  886.    <p>The four code points in the example are all clearly problematic.
  887.    The just-arrived RFC 9839 formalizes the notion of “problematic” and
  888.    offers easy-to-cite language saying which of these problematic types you want to
  889.    exclude from your text fields. Which, if you’re going to use JSON, you should probably do.</p>
  890.    <h2 id='p-6'>Don’t blame Doug</h2>
  891.    <p>Doug Crockford I mean, the inventor of JSON.  If he (or I or really anyone careful) were inventing JSON now that Unicode is
  892.    mature, he’d have been fussier about its character repertoire. Having said that, we’re stuck with JSON-as-it-is forever, so we
  893.    need a good way to say which of the problematic characters we’re going to exclude even if JSON allows them.</p>
  894.    <h2 id='p-5'>PRECISion</h2>
  895.    <p>You may find yourself wondering why the IETF waited until 2025 to provide help with Bad Unicode.
  896.    It didn’t; here’s
  897.    <a href="https://www.rfc-editor.org/rfc/rfc8264.html">RFC 8264</a>: <cite>PRECIS Framework: Preparation, Enforcement, and
  898.    Comparison of Internationalized Strings in Application Protocols</cite>; the first PRECIS predecessor was published in 2002.
  899.    8264 is 43 pages long, containing a <em>very</em>
  900.    thorough discussion of many more potential Bad Unicode issues than 9839 does.</p>
  901.    <p>Like 9839, PRECIS specifies subsets of the Unicode character repertoire and goes further, providing a mechanism for defining
  902.    more.</p>
  903.    <p>Having said that, PRECIS doesn’t seem to be very widely used by people who are defining new data structures and protocols. My
  904.    personal opinion is that there are two problems which make it hard to adopt. First, it’s large and
  905.    complex, with many moving parts, and requires careful study to understand. Developers are (for good reason) lazy.</p>
  906.    <p>Second, using PRECIS ties you to a specific version of Unicode. In particular, it forbids the use of the (nearly a million)
  907.    unassigned code points. Since each release of Unicode includes new code point assignments, that means that a sender and receiver
  908.    need to agree on exactly which version of Unicode they’re both going to use if they want reliably interoperable behavior. This
  909.    makes life difficult for anyone writing a general-purpose code designed to be used in lots of different applications.</p>
  910.    <p>I personally think that the only version of Unicode anybody wants to use is “as recent as possible”, so they can be confident
  911.    of having all the latest emojis.</p>
  912.    <p>Anyhow, 9839 is simpler and dumber than PRECIS. But I think some people will find it useful and now the IETF agrees.</p>
  913.    <h2 id='p-7'>Source code</h2>
  914.    <p>I’ve written a little Go-language library to validate incoming text fields against each of the three subsets that 9839
  915.    specifies,
  916.    <a href="https://github.com/timbray/RFC9839">here</a>.  I don’t claim it’s optimal, but it is well-tested.</p>
  917.    <p>It doesn’t have a version number or release just yet, I’ll wait till a few folk have had a chance to spot any dumb mistakes I
  918.    probably made.</p>
  919.    <h2 id='p-9'>Details</h2>
  920.    <p>Here’s a compact summary of the world of problematic Unicode code points and data formats and standards.</p>
  921.    <table>
  922.      <tr valign="top" align="center"><td class="empty"></td><th colspan="3">Problematic classes excluded?</th></tr>
  923.      <tr valign="top"><td class="empty"></td><th>Surrogates</th><th>Legacy controls</th><th>Noncharacters</th></tr>
  924.      <tr align="center"><td>CBOR</td><td class="happy">yes</td><td class="unhappy">no</td><td class="unhappy">no</td></tr>
  925.      <tr align="center"><td>I-JSON</td><td class="happy">yes</td><td class="unhappy">no</td><td class="happy">yes</td></tr>
  926.      <tr align="center"><td>JSON</td><td class="unhappy">no</td><td class="unhappy">no</td><td class="unhappy">no</td></tr>
  927.      <tr align="center"><td>Protobufs</td><td class="unhappy">no</td><td class="unhappy">no</td><td class="unhappy">no</td></tr>
  928.      <tr align="center"><td>TOML</td><td class="happy">yes</td><td class="unhappy">no</td><td class="unhappy">no</td></tr>
  929.      <tr align="center"><td>XML</td><td class="happy">yes</td><td class="neutral">partial [1]</td><td class="neutral">partial [2]</td></tr>
  930.      <tr align="center"><td>YAML</td><td class="happy">yes</td><td class="neutral">mostly [3]</td><td class="neutral">partial [2]</td></tr>
  931.      <tr valign="top" align="center"><td class="empty"></td><th colspan="3">RFC 9839 Subsets</th></tr>
  932.      <tr align="center"><td>Scalars</td><td class="happy">yes</td><td class="unhappy">no</td><td class="unhappy">no</td></tr>
  933.      <tr align="center"><td>XML</td><td class="happy">yes</td><td class="neutral">partial</td><td class="neutral">partial</td></tr>
  934.      <tr align="center"><td>Assignables</td><td class="happy">yes</td><td class="happy">yes</td><td class="happy">yes</td></tr>
  935.    </table>
  936.    <p>Notes:</p>
  937.    <p><b>[1]</b> XML allows C1 controls.</p>
  938.    <p><b>[2]</b> XML and YAML don’t exclude the noncharacters outside the Basic Multilingual Pane.</p>
  939.    <p><b>[3]</b> YAML excludes all the legacy controls except for the mostly-harmless <code>U+0085</code>, another version of
  940.    <code>\n</code> used in IBM mainframe documents.</p>
  941.    <h2 id='p-8'>Thanks!</h2>
  942.    <p>9839 is not a solo production. It received an extraordinary amount of discussion and improvement from a lot of smart and
  943.    well-informed people
  944.    and the published version, 15 draft revisions later, is immensely better than my initial draft. My sincere thanks go to my
  945.    co-editor Paul Hoffman and to all those mentioned in the RFC’s “Acknowledgements” section.</p>
  946.    <h2 id='p-4'>On individual submissions</h2>
  947.    <p>9839 is the second “individual submission” RFC I’ve pushed through the IETF (the other is
  948.    <a href="https://datatracker.ietf.org/doc/html/rfc7725">RFC 7725</a>, which registers the HTTP 451 status code).  While it’s nice
  949.    to decide something is worth standardizing and eventually have that happen, it’s really a lot of work. Some of that work is
  950.    annoying.</p>
  951.    <p>I’ve been involved in
  952.    other efforts as Working-Group member, WG chair, and WG specification editor, and I can report authoritatively that creating an
  953.    RFC the traditional way, through a Working Group, is easier and better.</p>
  954.    <p>I feel discomfort advising others not to follow in my footsteps, but in this case I think it’s the right advice.</p>
  955. </div></content></entry>
  956.  
  957. <entry>
  958. <title>Long Links</title>
  959. <link href='https://www.tbray.org/ongoing/When/202x/2025/08/04/Long-Links' />
  960. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/08/04/Long-Links#comments' />
  961. <id>https://www.tbray.org/ongoing/When/202x/2025/08/04/Long-Links</id>
  962. <published>2025-08-04T12:00:00-07:00</published>
  963. <updated>2025-08-07T11:14:33-07:00</updated>
  964. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  965. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  966. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>All of these <cite>Long Links</cite> pieces have begun with more or less the same words, so why     stop now?  This is an annotated parade of links to long-form pieces. Most people won’t have the time     (nor the weird assortment of interests) to consume them all, but I hope that most readers will find one     or two      reward a visit</div></summary>
  967. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  968.    <p>All of these <cite>Long Links</cite> pieces have begun with more or less the same words, so why
  969.    stop now?  This is an annotated parade of links to long-form pieces. Most people won’t have the time
  970.    (nor the weird assortment of interests) to consume them all, but I hope that most readers will find one
  971.    or two
  972.    reward a visit.</p>
  973.    <h2 id='p-2'>Radisson (and Groseilliers)</h2>
  974.    <p>I don’t know if it is still the case, but in my youth, Canadian elementary education included several overexcited units
  975.    about the
  976.    <a href="https://en.wikipedia.org/wiki/Coureur_des_bois"><i>Coureurs des bois</i></a>, early European settlers
  977.    in “New France” (now Québec) who ventured, by foot and canoe, far to the north and west, mostly engaged in trading with the
  978.    indigenous peoples: trinkets (and later, serious hardware including guns) for furs.</p>
  979.    <p>The names I remembered were Radisson and Groseilliers, but I don’t recall learning much about who they were and what
  980.    they did. Then I ran across the 2019 book
  981.    <a href="https://www.biblioasis.com/shop/non-fiction/bush-runner-the-life-and-times-of-pierre-esprit-radisson/">Bush Runner:
  982.    The Adventures of Pierre-Esprit Radisson</a> and, wow… The writing is pedestrian but who cares because what a
  983.    story! Radisson lived an absolutely astonishing life. He went as deep into the bush as anyone of his era, interacted intensely
  984.    with the indigenous people as business partner, friend, and foe, worked for Charles of England and Louis of France (changing
  985.    sides several times), in 1670 founded the Hudson’s Bay Company (recently, 355 years later, deceased), and fortunately took
  986.    notes, a copy of which was preserved by Samuel Pepys.</p>
  987.    <p>I learned more from this book’s pages about the early history of Upper and Lower Canada than all those elementary-school
  988.    units had to offer, and had loads of fun doing so.  I guess this is a fairly Canadian-specific Long Link, but I think anyone
  989.    interested in the early history of Europeans in North America would find much to enjoy.</p>
  990.    <h2 id='p-4'>Music</h2>
  991.    <p>It’s rare these days that I discover interesting new musicians, but here are two of those rarities.</p>
  992.    <p><a href="https://luciehorsch.com">Lucie Horsch</a> plays recorder, you know, the cheap plastic thing they use to introduce
  993.    second-graders to music. It’s actually a lovely instrument and I wish we would switch to its German name,
  994.    “Blockflöte”, which to my ear sounds a bit like the instrument does. Anyhow, check out this YouTube entitled only
  995.    <a href="https://www.youtube.com/watch?v=LJyl2D16PZY&amp;list=RDLJyl2D16PZY&amp;start_radio=1">Lucie Horsch - Bach</a>,
  996.    annoyingly omitting any mention of <em>which</em> Bach. Annoyance aside, it’s a pretty great performance, Ms Horsch is the real
  997.    deal, full of virtuosity and grace.</p>
  998.    <p>I got an unusual mid-week message from Qobuz, all excited about
  999.    <a href="https://transgressiverecords.com/artist/the-new-eves/">The New Eves’</a> new record <cite>The New Eve Is
  1000.    Rising</cite>. So I played it in the car on a long crosstown drive and now I’m all excited too. The New Eves are
  1001.    talented, musically surprising, and above all, insanely brave.</p>
  1002.    <p>Their music doesn’t sound like anything else and
  1003.    flies in the face of all conventional wisdom concerning popular music. They take absurd chances and yeah, the album has klunkers
  1004.    amid the bangers, but when I got to its end I went back and started at the beginning again. I found myself
  1005.    smiling ear-to-ear over and over. Maybe I’m being a bit over-the-top here, but check them out:
  1006.    <a href="https://www.youtube.com/watch?v=l9Q9ge6j_O4&amp;list=RDl9Q9ge6j_O4&amp;start_radio=1">Mother</a> is live.
  1007.    <a href="https://www.youtube.com/watch?v=MovNWuNPXXE&amp;list=RDMovNWuNPXXE&amp;start_radio=1">Cow Song</a> is off the new
  1008.    album and strong albeit with forgettable video.</p>
  1009.    <h2 id='p-3'>Life online</h2>
  1010.    <p>Every Long Links has hardcore-geek threads and there is no harder core imaginable than Filippo Valsordi’s
  1011.    <a href="https://words.filippo.io/assembly-mutation/">Go Assembly Mutation Testing</a>. I have always admired (but never
  1012.    actually used) mutation testing, and Filippo offers a convincing argument that it moves catching certain classes of bug from
  1013.    nearly impossible to pretty easy. Good stuff!</p>
  1014.    <p>And of course we can’t ignore genAI and programming. Most of you are likely aware of
  1015.    <a href="https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/">Measuring the Impact of Early-2025 AI on
  1016.    Experienced Open-Source Developer Productivity</a>, but I’m linking again to boost its visibility, because hard
  1017.    quantitative research on methodology is damn rare in our profession. I will confess to being a little (but just a little)
  1018.    surprised at the conclusions.</p>
  1019.    <p>It is apparently quite possible that Intel will exit the business of making high-end chips, leaving TSMC with a global
  1020.    monopoly:
  1021.    <a href="https://d2d.substack.com/p/d2d-contd-intel-and-the-wide-open">Intel and the Wide Open Barn Doors</a>.
  1022.    This is an unsettling prospect.
  1023.    Not, I have to say, surprising though. I’ve sneered at Intel leadership cluelessness for years and years, see
  1024.    <a href="/ongoing/When/200x/2006/01/14/On-Intel">here</a> and
  1025.    <a href="/ongoing/When/200x/2006/02/16/Viiv-Jive">here</a>.</p>
  1026.    <p>Finally, here’s the charmingly-titled
  1027.    <a href="https://www.raptitude.com/2025/06/how-to-surf-the-web-in-2025-and-why-you-should/">How to Surf the Web in 2025, and
  1028.    Why You Should</a>. I love this piece.</p>
  1029.    <h2 id='p-1'>Class Reductionism</h2>
  1030.    <p>The news keeps making me want to build something around the <code>classreductionist.org</code> domain name I’ve owned for
  1031.    years.</p>
  1032.    <p>The tl;dr on Class Reductionism is something like “In the best possible world it’ll take generations to disassemble the
  1033.    global tangle of intersectional oppression, but we could treat the symptoms effectively <em>right now this year</em> by sending
  1034.    money to the poor. I’m talking about Universal Basic Income or suchlike. I wrote a
  1035.    <a href="/ongoing/When/202x/2023/01/16/Class-Reductionism">couple thousand words</a> on the subject back in 2023, and there are
  1036.    complexities, and I probably won’t put up that site. But I still do maintain that a very high proportion of our societal pain is
  1037.    rooted in the egregious inequality, and consequent poverty, that seems a baked-in feature of Late Capitalism.</p>
  1038.    <p>Let’s start with Nobelist Paul Krugman, who’s been writing an “Understanding Inequality” series on his paywalled newsletter
  1039.    and then republishing a gratis version, start
  1040.    <a href="https://stonecenter.gc.cuny.edu/tag/focus-inequality/">here</a>.  Very data-dense and educational.
  1041.    Hmm, that site is slow; there’s a livelier table of contents
  1042.    <a href="https://paulkrugman.substack.com/p/i-coulda-made-a-better-deal">here</a>.</p>
  1043.    <p>Don’t kid yourself that this is just an American problem, see
  1044.    <a href="https://www.nytimes.com/2025/06/23/business/china-upward-mobility-inequality.html?unlocked_article_code=1.cE8.Ptfc.XicZ0XVgHPsJ&amp;smid=url-share">‘The Better Life Is Out of Reach’: The Chinese Dream Is Slipping Away</a>.</p>
  1045.    <p>Let’s pull the impersonal veil of facts and figures aside and focus on the human experience of what we used to call Class Struggle.
  1046.    <a href="https://macleans.ca/society/confessions-of-the-working-poor/">Confessions of the Working Poor</a> is beautifully
  1047.    written and opened my eyes to lifestyle choices that I didn’t even know some people have to make.</p>
  1048.    <p>But hey, there are people who are just fine with this:
  1049.    <a href="https://finance.yahoo.com/news/deltas-premium-play-is-taking-advantage-of-the-growing-economic-split-100044776.html">Delta's
  1050.    premium play is taking advantage of the growing economic split</a>.</p>
  1051.    <p>Look, being class-determinist-adjacent doesn’t mean you should ignore intersectional awfulness:
  1052.    <a href="https://www.newyorker.com/magazine/2025/08/04/the-plunder-of-black-america-calvin-schermerhorn-book-review">What We
  1053.    Miss When We Talk About the Racial Wealth Gap</a>.</p>
  1054.    <h2 id='p-5'>No more sections</h2>
  1055.    <p>The remaining Long Links refused to be organized so I had to turn them loose; call it the Long Tail.</p>
  1056.    <p><a href="https://articles.c-a-s-t.com/the-venetian-origins-of-roman-type-a856eb3f0cb">The Venetian origins of roman
  1057.    type</a>. You might think you don’t care about typography but still enjoy the pictures and descriptions here.</p>
  1058.    <!--
  1059.    <p><a href="https://www.newyorker.com/magazine/2025/07/28/mary-had-schizophrenia-then-suddenly-she-didnt">Mary Had
  1060.    Schizophrenia—Then Suddenly She Didn’t</a></p>-->
  1061.    <p>This guy is a full-time
  1062.    <a href="https://urbancoyoteresearch.com/researcher/stanley-d-gehrt-phd">Coyote researcher</a>. What a great gig! I’m an admirer
  1063.    of those animals and how they’ve carved themselves a comfy niche in most of North America’s big cities.  (Even if it means that
  1064.    you better not let your cat out at night.) They’re also remarkably attractive.</p>
  1065.    <p>Here’s another long list of Long Links, and many of you will wonder why anyone would choose to browse it:
  1066.    <a href="https://petapixel.com/2025/07/18/the-best-camera-stores-in-tokyo-the-ultimate-guide/">The Best Camera Stores in
  1067.    Tokyo: The Ultimate Guide</a>. Some of the interiors are remarkable.</p>
  1068.    <p>Oh, while we’re on the subject of photography:
  1069.    <a href="https://petapixel.com/2025/07/22/a-photojournalist-took-a-fujifilm-instax-camera-to-a-cartel-wedding/">A
  1070.    Photojournalist Took a Fujifilm Instax Camera to a Mexican Cartel Wedding</a>.</p>
  1071.    <p>GLP-1’s (i.e. Ozempic and friends) would probably dominate a large section of the news if weren’t for all the political
  1072.    craziness. Here’s one small example:
  1073.    <a href="https://www.glp1digest.com/p/how-glp-1s-are-breaking-life-insurance">How GLP-1s Are Breaking Life Insurance</a>.</p>
  1074.    <p>Science is hard. There are lots of largely-unsolved areas, and “gap-map.org” tries to organize them:
  1075.    <a href="https://www.gap-map.org/?sort=rank&amp;utm_source=substack&amp;utm_medium=email&amp;fields=astrophysics">Fundamental
  1076.    Development Gap Map v1.0</a>. The UI is a little klunky but the thing still sucked me right in.</p>
  1077.    <p>I’m going to give the last word to Laurie Penny. I don’t know what we’d do without her.
  1078.    <a href="https://lauriepenny.substack.com/p/in-a-time-of-monsters-do-we-have">In a time of monsters: do we have any ideas for
  1079.    surviving the zombie apocalypse that aren’t nightmare patriarchy?</a></p>
  1080. </div></content></entry>
  1081.  
  1082. <entry>
  1083. <title>De-Google Project Update</title>
  1084. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/29/DeGoogling' />
  1085. <link rel='replies'        thr:count='20'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/29/DeGoogling#comments' />
  1086. <id>https://www.tbray.org/ongoing/When/202x/2025/07/29/DeGoogling</id>
  1087. <published>2025-07-29T12:00:00-07:00</published>
  1088. <updated>2025-07-31T12:06:18-07:00</updated>
  1089. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Life Online/De-Google' />
  1090. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1091. <category scheme='https://www.tbray.org/ongoing/What/' term='Life Online' />
  1092. <category scheme='https://www.tbray.org/ongoing/What/' term='De-Google' />
  1093. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I     <a href='/ongoing/When/202x/2024/03/09/DeGoogling'>introduced this family project</a> in the spring of 2024.     I won’t reproduce those arguments for why we’re working on this, but in the current climate I feel like I hardly need to.     Since that post, our aversion to Google dependency has only grown stronger. Progress has been non-zero but not fast</div></summary>
  1094. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1095.    <p>I
  1096.    <a href="/ongoing/When/202x/2024/03/09/DeGoogling">introduced this family project</a> in the spring of 2024.
  1097.    I won’t reproduce those arguments for why we’re working on this, but in the current climate I feel like I hardly need to.
  1098.    Since that post, our aversion to Google dependency has only grown stronger. Progress has been non-zero but not fast.</p>
  1099.    <p>Here’s the table, with progress notes below.</p>
  1100.    <table>
  1101.      <tr valign="top"><th>Need</th><th>Supplier</th><th>Alternatives</th></tr>
  1102.      <tr valign="top">
  1103. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-3">Office</a></td>
  1104. <td class="unhappy">Google Workspace</td>
  1105. <td>Proton?</td>
  1106.      </tr>
  1107.      <tr valign="top">
  1108. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-17">Data sharing</a></td>
  1109. <td class="happy">Dropbox</td>
  1110.      <td></td></tr>
  1111.      <tr valign="top">
  1112. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-17">Photos</a></td>
  1113. <td class="unhappy">Google Photos</td>
  1114.      <td>Dropbox?</td></tr>
  1115.      <tr valign="top">
  1116. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-16">Video meetings</a></td>
  1117. <td class="unhappy">Google
  1118. Meet</td>
  1119.      <td>Jitsi, Signal?</td></tr>
  1120.      <tr valign="top">
  1121. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-10">Maps</a></td>
  1122. <td class="unhappy">Google Maps</td>
  1123.      <td>Magic Earth, Here, something OSM-based?</td></tr>
  1124.      <tr valign="top">
  1125. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-4">Browser</a></td>
  1126. <td class="happy">Safari, Firefox, Vivaldi, LibreWolf</td>
  1127.      <td></td></tr>
  1128.      <tr valign="top">
  1129. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-12">Search</a></td>
  1130. <td class="unhappy">Google</td>
  1131.      <td>Bing-based options, Kagi?</td></tr>
  1132.      <tr valign="top">
  1133. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-5">Chat</a></td>
  1134. <td class="happy">Signal</td>
  1135.      <td></td></tr>
  1136.      <tr valign="top">
  1137. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-6">Photo editing</a></td>
  1138. <td class="neutral">Adobe
  1139. Lightroom &amp; Nik</td>
  1140.      <td>Capture One, Darktable, ?</td></tr>
  1141.      <tr valign="top">
  1142. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-7">In-car interface</a></td>
  1143. <td class="neutral">Google Android Auto</td>
  1144.      <td>Automaker software</td></tr>
  1145.      <tr valign="top">
  1146. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-8">Play my music</a></td>
  1147. <td class="happy">Plex, USB</td>
  1148.      <td></td></tr>
  1149.      <tr valign="top">
  1150. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-9">Discover music</a></td>
  1151. <td class="happy">Qobuz</td>
  1152. <td></td></tr>
  1153.      <tr valign="top">
  1154. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-13">TV</a></td>
  1155. <td class="neutral">Roku, Apple, migration</td>
  1156.      <td></td></tr>
  1157.    </table>
  1158.    <p>Pink indicates a strong desire to get off the incumbent service, green means we’re happy-ish with what we’re using, and blue
  1159.    means that, happy or not, it’s not near the top of the priority list.</p>
  1160.    <p>I’ll reproduce the metrics we care about when looking to replace Google products, some combination of:</p>
  1161.    <ol>
  1162.      <li><p>Not ad-supported</p></li>
  1163.      <li><p>Not VC-funded</p></li>
  1164.      <li><p>Not Google, Microsoft, or Amazon</p></li>
  1165.    </ol>
  1166.    <p>The list used to include “Open Source” but I decided that while that’s good, it’s less important than the other three criteria.</p>
  1167.    <p>Now let’s walk down the chart.</p>
  1168.    <h2 id='p-3'>Office</h2>
  1169.    <p>This is going to be a wrenching transition; we’ve been running the family on Google stuff forever, and I anticipate
  1170.    muscle-memory pain. But increasingly, using Google apps feels like being in enemy territory. And, as I said last time, I
  1171.    will not be sorry to shake the dust of Google Drive and Docs from my heels, I find them clumsy and am
  1172.    always having trouble finding something that I know is in there.</p>
  1173.    <p>While I haven’t dug in seriously yet, I keep hearing reasonably-positive things about Proton, and nothing substantive to
  1174.    scare me away.  Wish us luck.</p>
  1175.    <h2 id='p-17'>Data sharing (progress!)</h2>
  1176.    <p>Dropbox is, eh, OK. It doesn’t seem actively evil, there’s no advertising, and the price is low.</p>
  1177.    <h2 id='p-21'>Photos</h2>
  1178.    <p>We’re a four-Android family including a couple of prolific photographers, and everything just gets pumped into Google and
  1179.    then it fills up and then they want more money.  If we could configure the phones to skip Google and go straight to Dropbox,
  1180.    that would be a step forward.</p>
  1181.    <h2 id='p-16'>Video meetings</h2>
  1182.    <p>Google meet isn’t painful but I totally suspect it of data-mining what should be private conversations. I’m getting the
  1183.    feeling that the technical difficulty of videoconferencing is going steadily down, so I’m reasonably optimistic that
  1184.    something a little less evil will come along with a fair price.</p>
  1185.    <h2 id='p-10'>Maps</h2>
  1186.    <p>The fear and loathing that
  1187.    <a href="/ongoing/When/201x/2017/06/29/Fear-Google-Reviews">I started feeling in 2017</a> grows only stronger.  But replacements
  1188.    aren’t obvious.
  1189.    It’s a pity, maps
  1190.    and directions and reviews feel like a natural monopoly that should be a public utility or something, rather than a corporate moat.</p>
  1191.    <h2 id='p-4'>Browser (progress!)</h2>
  1192.    <p>Chrome has seriously started making my flesh crawl; once again, enemy territory. Fortunately, there are lots of good options.
  1193.    Even people like us who have multiple lives we need to keep separate can find enough better browsers out there.</p>
  1194.    <p>Maybe I’ll have a look at one of the new genAI-company browsers ha ha just kidding.</p>
  1195.    <h2 id='p-12'>Search</h2>
  1196.    <p>The reports on Kagi keep being positive and giving it a try is definitely on the To-Do list.</p>
  1197.    <h2 id='p-5'>Chat</h2>
  1198.    <p>Signal is the only sane choice at this point in history for personal use.</p>
  1199.    <h2 id='p-6'>Photo editing</h2>
  1200.    <p>Adobe’s products are good, and I’m proficient and happy with Lightroom, but they are definitely suffering from bad genAI
  1201.    craziness. Also the price is becoming unreasonable.</p>
  1202.    <p>I’ve had a few Lightroom software failures in recent months and if that
  1203.    becomes a trend, looking seriously at the alternatives will move to the top of the priority list.</p>
  1204.    <h2 id='p-7'>In-car interface</h2>
  1205.    <p>It’s tough, Android Auto is a truly great product. I think I’m stuck here for now, particularly given that I plan to be
  1206.    driving a <a href="/ongoing/What/The%20World/Jaguar%20Diary/">2019-model-year car</a> for the foreseeable future. Also, it
  1207.    supports my music apps.</p>
  1208.    <h2 id='p-9'>Discover music and play mine (progress!)</h2>
  1209.    <p>Progress here. I’ve almost completely stopped using YouTube Music in favor of Plex and Qobuz. Really no downside; YTM has
  1210.    more or less completely lost the ability to suggest good new stuff.</p>
  1211.    <h2 id='p-13'>TV</h2>
  1212.    <p>Video continues morphing itself into Cable TV redux. We have an old Roku box that works fine and I think I’ve managed to find
  1213.    its don’t-spy-on-us settings. We’ll keep subscribing to Apple+ as long as they keep shipping great shows.  I have zero regrets
  1214.    about having
  1215.    <a href="/ongoing/When/202x/2025/03/06/Canceled-Prime">left Prime behind</a>.</p>
  1216.    <p>As for the rest, we’ve become migrants,
  1217.    exclusively month-at-a-time subscriptions for the purpose of watching some serial or sports league, unsubscribe after the season
  1218.    finale or championship game. The good news is that I
  1219.    haven’t encountered much friction in unsubscribing, just a certain amount of earnest pleading.</p>
  1220.    <h2 id='p-20'>Looking forward</h2>
  1221.    <p>I have yet to confront any of the really hard parts of this project, but the sense of urgency is increasing. Let’s see.</p>
  1222. </div></content></entry>
  1223.  
  1224. <entry>
  1225. <title>QRS: Finite-state Struggles</title>
  1226. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/21/Automaton-merge-war' />
  1227. <link rel='replies'        thr:count='2'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/21/Automaton-merge-war#comments' />
  1228. <id>https://www.tbray.org/ongoing/When/202x/2025/07/21/Automaton-merge-war</id>
  1229. <published>2025-07-21T12:00:00-07:00</published>
  1230. <updated>2025-07-22T09:10:25-07:00</updated>
  1231. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
  1232. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1233. <category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
  1234. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Software' />
  1235. <category scheme='https://www.tbray.org/ongoing/What/' term='Software' />
  1236. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I just posted a big     <a href='https://github.com/timbray/quamina'>Quamina</a> PR representing months of work, brought on     by the addition of a small basic regular-expression feature.  This ramble doesn’t exactly have a smooth story arc but I’m     posting it anyhow because I know there are people     out there interested in state-machine engineering and they are my people</div></summary>
  1237. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1238.    <p>I just posted a big
  1239.    <a href="https://github.com/timbray/quamina">Quamina</a> PR representing months of work, brought on
  1240.    by the addition of a small basic regular-expression feature.  This ramble doesn’t exactly have a smooth story arc but I’m
  1241.    posting it anyhow because I know there are people
  1242.    out there interested in state-machine engineering and they are my people.</p>
  1243.    <p>As far as I can tell, a couple of the problems I’m trying to solve
  1244.    haven’t been addressed before, at least not by anyone who published their findings.
  1245.    Partly because of that, I’m starting to wonder if all
  1246.    <a href="/ongoing/What/Technology/Quamina%20Diary/">these disorderly Quamina postings</a> might
  1247.    be worked into a small book or monograph or something. State machines are really freaking useful software constructs!
  1248.    So yeah, this is a war story not an essay, but if you like finite automata you’ll likely be interested in bits of it.</p>
  1249.    <h2 id='p-1'>The story thus far</h2>
  1250.    <p>Prior to beginning work on Regular Expressions, I’d already wired shell-style “<code>*</code>” wildcards into Quamina, which
  1251.    forced me to start working with NFAs and ε-transitions. The implementation wasn’t crushingly difficult, and
  1252.    the performance was… OK-ish.</p>
  1253.    <p>Which leads me to The Benchmark From Hell.
  1254.    I wondered how the wildcard functionality would work under heavy stress, so I pulled in a list of 12,959 five-letter strings
  1255.    from the Wordle source code, and inserted a “<code>*</code>” at a random position in each. Here are the first ten:</p>
  1256.    <blockquote><pre><code>aalii*
  1257. *aargh
  1258. aar*ti
  1259. abaca*
  1260. a*baci
  1261. a*back
  1262. ab*acs
  1263. ab*aft
  1264. abak*a</code></pre></blockquote>
  1265.    <p>I created an NFA for each and merged them together
  1266.    <a href="/ongoing/When/202x/2024/07/28/Union-of-Finite-Automata">as described here</a>. Building and merging the automata were
  1267.    plenty fast enough, and the merged NFA had 46,424 states, which felt reasonable.
  1268.    Matching strings against it ran at under ten thousand per second, which is pretty poor given that Quamina can do a million or
  1269.    two per second on patterns encoded in a DFA.</p>
  1270.    <p>But, I thought, still reasonably usable.</p>
  1271.    <h2 id='p-2'>The cursed “<code>?</code>”</h2>
  1272.    <p>Last year, my
  1273.    <a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series">slow grind through the regexp features</a> had led me
  1274.    to the zero-or-one quantifier “<code>?</code>”.  The state machine for these things is not rocket science; there’s a discussion
  1275.    with pictures in my recent
  1276.    <a href="/ongoing/When/202x/2025/07/07/Epsilon-Wrangling#p-3">Epsilon Wrangling</a>.</p>
  1277.    <p>So I implemented that and fired off the unit tests, most of which
  1278.    <a href="/ongoing/When/202x/2024/12/12/QRS-Parsing-Regular-Expressions#p-1">I didn’t have to write</a>, and they all failed.
  1279.    Not a surprise I guess.</p>
  1280.    <p>It turned out that the way I’d implemented ε-transitions for the wildcards
  1281.    <a href="/ongoing/When/202x/2024/07/28/Union-of-Finite-Automata#p-9">was partially wrong</a>, as in it worked for the tight-loop
  1282.    state-to-itself ε-transitions, but not for more general-purpose things like “<code>?</code>” requires.</p>
  1283.    <p>In fact, it turns out that merging NFAs is hard (DFAs are easy), and I found precious little help online.
  1284.    <a href="https://en.wikipedia.org/wiki/Thompson%27s_construction">Thompson’s construction</a> does give an answer: Make an
  1285.    otherwise-empty state with two ε-transitions, one to each of the automata, and it’ll do the right thing. Let’s call that
  1286.    a “splice state”. It’s easy to implement, so I did. Splicing is hardly “merging” in the Quamina sense, but still.</p>
  1287.    <p>Unfortunately, the performance was hideously bad, just a few matches per second while pegging the CPU.
  1288.    A glance at the final NFA was sobering; endless chains of splice states, some thousands long.</p>
  1289.    <p>At this point
  1290.    I became very unhappy and got stalled for months dealing with real-life issues while this problem lurked at the back
  1291.    of my mind, growling for attention occasionally.</p>
  1292.    <p>Eventually I let the growler out of the cave and started to think through approaches. But first…</p>
  1293.    <h2 id='p-4'>Worth solving?</h2>
  1294.    <p>Is it, really? What sane person is going to want to search for the union of thousands of regular expressions in general or
  1295.    wild-carded strings in particular?</p>
  1296.    <p>I didn’t think about this problem at all, because of my experience with Quamina’s parent,
  1297.    <a href="https://github.com/aws/event-ruler">Ruler</a>. When it became popular among several AWS and Amazon teams, people
  1298.    sometimes found it useful to match the union of not just thousands but a million or more different patterns. When you write
  1299.    software that anyone actually uses, don’t expect the people using it to share your opinions on what is and isn’t
  1300.    reasonable. So I wasn’t going to get any mental peace until I cracked this nut.</p>
  1301.    <p>I eventually decided that three approaches were worth trying:</p>
  1302.    <ol>
  1303.      <li><p>Figure out a way really to merge, not just splice, the wildcarded patterns, to produce a simpler automaton.</p></li>
  1304.      <li><p>Optimize the NFA-traversal code path.</p></li>
  1305.      <li><p>Any NFA can be transformed into a DFA, says computer-science theory. So do that, because Quamina is really fast at
  1306.      DFA-based matching.</p></li>
  1307.    </ol>
  1308.    <h2 id='p-5'>Nfa2Dfa</h2>
  1309.    <p>I ended up doing all of these things and haven’t entirely given up on any of them.
  1310.    The most intellectually-elegant was the transform-to-DFA approach, because if I did that, I could remove the fairly-complex
  1311.    NFA-traversal logic from Quamina.</p>
  1312.    <p>It turns out that the Net is rich with textbook extracts and YouTubes and slide-shows about how to do the NFA-to-DFA
  1313.    conversion. It ended up being quite a pleasing little chunk of code, only a couple hundred lines.</p>
  1314.    <p>The bad news: Converting each individual wildcard NFA to a DFA was amazingly fast, but then as I merged them in one by one,
  1315.    the number of automaton states started increasing explosively and the process slowed down so much that I never had the patience
  1316.    to let it finish. Finite-automata theory warns that this can happen, but it’s hard to characterize the cases where it does.
  1317.    I guess this one of them.</p>
  1318.    <p>Having said that, I haven’t discarded the <code>nfa2Dfa</code> code, because perhaps I ought to offer a Quamina option to
  1319.    apply this if you have some collection of patterns that you want to run really super fast and are willing to wait for a while
  1320.    for the transformation process to complete. Also, I may have missed opportunities to optimize the conversion; maybe it’s making
  1321.    more states than it needs to?</p>
  1322.    <h2 id='p-6'>Faster NFA traversal</h2>
  1323.    <p>Recently in
  1324.    <a href="/ongoing/When/202x/2025/07/07/Epsilon-Wrangling">Epsilon wrangling</a> I described how NFA traversal has to work,
  1325.    relying heavily on implementing a thing called an ε-closure.</p>
  1326.    <p>So I profiled the traversal process and discovered, unsurprisingly, that most of the time was going into memory allocation
  1327.    while computing those ε-closures. So now Quamina has an ε-closure cache and will only compute each one once.</p>
  1328.    <p>This helped a lot but not nearly enough, and the profiler was still telling me the pain was in Go’s allocation and
  1329.    garbage-collection machinery. Whittling away at this kind of stuff is not rocket science. The standard Go trick I’ve seen over
  1330.    and over is to keep all your data in slices, keep re-using them then chopping them back to <code>[:0]</code>
  1331.    for each request.  After a while they’ll have grown to the
  1332.    point where all the operations are just copying bytes around, no allocation required.</p>
  1333.    <p>Which also helped, but the speed wasn’t close to what I wanted.</p>
  1334.    <h2 id='p-7'>Merging wildcard automata</h2>
  1335.    <p>I coded multiple ways to do this, and they kept failing. But I eventually found a way to build those
  1336.    automata so that any two of them, or any one of them and a DFA, can merged and generate dramatically
  1337.    fewer ε-transition chains.  I’m not going to write this up here for two reasons: First of all, it’s not <em>that</em>
  1338.    interesting, and second, I worry that I may have to change the approach further as I go on implementing new regxp operators.</p>
  1339.    <p>In particular, at one point I was looking at the code while it wasn’t working, and I could see that if I added a particular
  1340.    conditional it would work, but I couldn’t think of a principled reason to do it. Obviously I’ll have to sort this out
  1341.    eventually. In the meantime, if you’re the sort of um special person who is now burning with curiosity, check out my branch from
  1342.    that PR and have a look at the <code>spinout</code> type.</p>
  1343.    <p>Anyhow, I added that conditional even though it puzzled me a bit, and now you can add wildcard patterns to Quamina at 80K/second,
  1344.    and my 12.9K wildcards generate an NFA with with almost 70K states, which can scan events at almost 400K/second. And that’s good
  1345.    enough to ship the <code>“?”</code> feature.</p>
  1346.    <p>By the way, I tried feeding that 70K-state automaton to the DFA converter, and gave up after it’d burned an hour of CPU and
  1347.    grown to occupy many GB of RAM.</p>
  1348.    <h2 id='p-8'>Next steps</h2>
  1349.    <p>Add “<code>+</code>” and “<code>*</code>”, and really hope I don’t have to redesign the NFA machinery again.</p>
  1350.    <p>Also, figure out the explanation for that puzzling <code>if</code> statement.</p>
  1351.    <h2 id='p-9'>And I should say…</h2>
  1352.    <p>Despite the very narrow not to say obsessive focus of this series, I’ve gotten a few bits and pieces of positive feedback. So
  1353.    there are a few people out there who care about this stuff. To all of you, thanks.</p>
  1354. </div></content></entry>
  1355.  
  1356. <entry>
  1357. <title>Memory in Saskatchewan</title>
  1358. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/09/Saskatchewan' />
  1359. <link rel='replies'        thr:count='9'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/09/Saskatchewan#comments' />
  1360. <id>https://www.tbray.org/ongoing/When/202x/2025/07/09/Saskatchewan</id>
  1361. <published>2025-07-09T12:00:00-07:00</published>
  1362. <updated>2025-07-16T10:11:34-07:00</updated>
  1363. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Saskatchewan' />
  1364. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1365. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  1366. <category scheme='https://www.tbray.org/ongoing/What/' term='Saskatchewan' />
  1367. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos' />
  1368. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  1369. <category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
  1370. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I just came back from Canada’s     <a href='https://en.wikipedia.org/wiki/Saskatchewan'>only rectangular province</a>. I was there to help out my 95-year-old     mother while her main      caregiver took vacation. It’s an unhappiness that my family has splashed itself across Canada in such a way that we have to get     on an airplane (or take drives measured in days) to see each other, but that’s where we are. I came back with pictures and     stories</div></summary>
  1371. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1372.    <p>I just came back from Canada’s
  1373.    <a href="https://en.wikipedia.org/wiki/Saskatchewan">only rectangular province</a>. I was there to help out my 95-year-old
  1374.    mother while her main
  1375.    caregiver took vacation. It’s an unhappiness that my family has splashed itself across Canada in such a way that we have to get
  1376.    on an airplane (or take drives measured in days) to see each other, but that’s where we are. I came back with pictures and
  1377.    stories.</p>
  1378.    <p>Let me set the stage with a couple of photos. Everyone knows that Saskatchewan is flat and brown and empty, right?</p>
  1379.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/TXT55665.png" alt="Flowers, intensely colored in near-black purple and yellow" />
  1380.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/TXT55710.png" alt="Trees and lawns, behind a still body of water and somewhat reflected in it" />
  1381.    <p>Mom lives in
  1382.    <a href="https://en.wikipedia.org/wiki/Regina,_Saskatchewan">Regina</a>, the provincial capital, a city built round a huge
  1383.    park that contains the Legislature (the flowers are from its front lawn), a sizeable lake, and an artificial
  1384.    mini-mountain (the water and trees are from its tip).
  1385.    Have no fear, I’ll get to some no-kidding prairie landscapes.</p>
  1386.    <h2 id='p-1'>Health-care drama</h2>
  1387.    <p>The night I arrived, after my Mom went to bed she got up again, tripped on something and fell hard. Her right arm was
  1388.    swollen, bruised, and painful. The skin and adjacent blood vessels of very old people become thin and fragile; her whole
  1389.    forearm was a bruise. I tried to get her to go to Emergency but she wasn’t having any of it: “You wait for hours and then they
  1390.    give you a pain-killer, which is constipating.”  Since she could twist her wrist and wiggle her fingers and give my hand a firm
  1391.    grasp, I didn’t push too hard.</p>
  1392.    <p>A couple days later on Saturday she got her regular twice-a-week visit from the public
  1393.    <a href="https://www.saskatchewan.ca/residents/health/accessing-health-care-services/care-at-home-and-outside-the-hospital/home-care">HomeCare</a>
  1394.    nurse, a friendly and highly competent Nigerian immigrant, to check her meds and
  1395.    general condition.
  1396.    She looked at Mom’s wrist and said “Get her an appointment with her doctor, they’ll probably want an X-Ray.”</p>
  1397.    <p>I called up her doctor at opening time Monday. The guy who answered the phone said
  1398.    “Don’t have any appointments for a couple weeks but come on over, we’ll squeeze her in.” So we went in after morning coffee and
  1399.    waited less than an hour.
  1400.    The doctor looked at her arm for 45 seconds and said “I’m writing a prescription for an X-Ray” and there was a
  1401.    radiologist around the corner and she was in ten minutes later. The doctor called me back that afternoon and said “Your
  1402.    mother’s got a broken wrist, I got her an 8AM appointment tomorrow at Regina General’s Cast Clinic.”</p>
  1403.    <p>The doctor at the clinic looked at her wrist for another 45 seconds and said “Yeah, put on a cast” so they did and we were
  1404.    home by ten. I’d pessimistically overpaid a couple bucks for hospital parking.</p>
  1405.    <p>The reason I’m including this is because I notice that this space has plenty of American readers. Did you notice that the
  1406.    story entirely omits insurance companies and money (except parking)? In Canada your health-care comes with your taxes (granted,
  1407.    higher than Americans’) and while the system is far from perfect, it can fix up an old lady’s broken wrist pretty damn fucking
  1408.    quick without any bureaucratic bullshit. Also, Canada spends a huge amount less per head on health-care than the US does.</p>
  1409.    <p>And Mom told me not to forget that Saskatchewan is the birthplace of Canadian single-payer universal healthcare.
  1410.    <a href="https://en.wikipedia.org/wiki/Tommy_Douglas">Tommy Douglas</a>, the Social Democrat who made that happen, has been
  1411.    named
  1412.    <a href="https://en.wikipedia.org/wiki/The_Greatest_Canadian">The Greatest Canadian</a>.</p>
  1413.    <h2 id='p-2'>Gentle surface</h2>
  1414.    <p>Oh, did I say “flat and brown and empty”? Wrong, wrong, and wrong. The Prairies, in Canada and the US too, have textures and
  1415.    colors and hills and valleys, it’s just that the slopes are gentle.  There are really flat parts and they make farmers’ lives easier, but
  1416.    more or less every square inch that’s not a town or a park is farmed.
  1417.    I took Mom for a drive out in the country southeast of Regina, from whence these views:</p>
  1418.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/TXT55698.png" alt="A road leading slightly uphill, brilliant yellow canola on both sides" />
  1419.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/TXT55700.png" alt="Yellow canola flowers under a blue sky" />
  1420.    <div class='caption'><p>Note that in both shots we’re looking up a gentle slope. In the second, there’s farm infrastructure on
  1421.    the distant horizon.<br/>Also consider the color of the sky.</p></div>
  1422.    <p>In Canada that yellow-flowering crop is called “Canola”, which Wikipedia claims refers to a particular cultivar of
  1423.    <i>Brassica napus</i>, commonly known as rapeseed or just rape, so you can see why when Canada’s
  1424.    agribiz sector wanted to position its oil as the thing to use while cooking they went for the cultivar not the species
  1425.    name. I’m old enough to remember when farmers still said just “rapeseed”. Hmm, Wikipedia also claims that the OED claims this:
  1426.    The term “rape” derives from the Latin word for turnip, <i>rāpa</i> or <i>rāpum</i>, cognate with the Greek word ῥάφη,
  1427.    <i>rhaphe</i>.</p>
  1428.    <p>Let’s stick with canola.</p>
  1429.    <h2 id='p-4'>Pixelated color</h2>
  1430.    <p>After I’d taken those two canola-field shots I pulled out my Pixel and took another, but I’m not gonna share it because the
  1431.    Pixel decided to turn the sky from what I thought was a complex and interesting hue into its opinion of “what a blue sky looks
  1432.    like” only this sky didn’t.</p>
  1433.    <p>Maybe it’s just me, but I think Google’s camera app is becoming increasingly opinionated about color, and not in a good
  1434.    way. There are plenty of alternative camera apps, I should check them out.</p>
  1435.    <p>In case it’s not obvious, I love photographing Saskatchewan and think it generally looks pretty great, especially when you
  1436.    look up. On the province’s license plates it says “Land of living skies”, and no kidding.</p>
  1437.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/PXL_20250704_032320050.png" alt="Saskatchewan’s living skies" />
  1438.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/PXL_20250704_032334240.png" alt="Saskatchewan’s living skies" />
  1439.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/TXT55717.png" alt="Saskatchewan’s living skies"/>
  1440.    <div class='caption'><p>The first two are from the park behind Mom’s place,<br/>the third from that mini-mountain mentioned
  1441.    above.</p></div>
  1442.    <h2 id='p-6'>Experience and memory</h2>
  1443.    <p>My Mom’s doing well for a nonagenerian. She’s smart. When I visited early last fall and we talked about the US election I was
  1444.    bullish on Kamala Harris’s chances. She laughed at me and said “The Americans won’t elect a woman.” Well then.</p>
  1445.    <p>But she’s forgetful in the short term. I took her to the Legislature’s
  1446.    garden and to the top of the mini-mountain and for a drive out in the country and another adventure we’ll get to; she
  1447.    enjoyed them all. But maybe she won’t remember them.</p>
  1448.    <p>“Make memories” they say, but what if you show someone you love a good time and maybe they won’t remember it the
  1449.    next day? I’m gonna say it’s still worthwhile and has a lesson to teach about what matters. There endeth the lesson.</p>
  1450.    <h2 id='p-5'>The gallery</h2>
  1451.    <p>Indigenous people make up 17% of Regina’s population, the highest share in any significant Canadian city. By “indigenous” I
  1452.    mean the people that my ancestors stole the land from.  It’s personal with me; Around 1900, my Dad’s family, Norwegian
  1453.    immigrants, took over some pretty
  1454.    great farmland southeast of Edmonton by virtue of “homesteading”, such a <em>nice</em> word isn’t it?</p>
  1455.    <p>Regina tries to honor its indigenous heritage and my favorite expression of that is its
  1456.    <a href="https://mackenzie.art">Mackenzie Art Gallery</a>, a lovely welcoming space in the
  1457.    <a href="https://www.saskatchewan.ca/government/directory?ou=a8e54600-77d6-4b7e-9702-f07a3dac1b47">T.C.Douglas building</a> (for
  1458.    “T.C.” read “Tommy”. (Did I mention him?) Mom and I walked around it and had lunch in its very decent café.</p>
  1459.    <p>Every time I’ve been there the big exhibitions in the big rooms have been indigenous-centered, and generally excellent.
  1460.    I try to go every time I visit and I’ve never been disappointed.</p>
  1461.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/PXL_20250708_172437441.png" alt="Indigenous art at Regina’s Mackenzie Gallery" />
  1462.    <p>In 2025, anything I have to say about this piece would be superfluous.</p>
  1463.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/PXL_20250708_173041377.png" alt="Every American Flag Is A Warning Sign" />
  1464.    <p>I love modern-art galleries, especially with big rooms full of big pieces, even if I don’t like all the art.
  1465.    Because it feels good to be in the presence of the work of people who are pouring out
  1466.    what they have to offer, especially at large scale. If the task wasn’t hard enough that failures
  1467.    are common then it wouldn’t be worthwhile, would it?</p>
  1468.    <p>They’re especially great when there’s someone I love there enjoying it with me. Here’s Mom.</p>
  1469.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/09/PXL_20250708_172836385.png" alt="Jean Bray considers indigenous art" />
  1470.    <p>These days, any visit might be the last. I hope this wasn’t.</p>
  1471. </div></content></entry>
  1472.  
  1473. <entry>
  1474. <title>QRS: Epsilon Wrangling</title>
  1475. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/07/Epsilon-Wrangling' />
  1476. <link rel='replies'        thr:count='0'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/07/Epsilon-Wrangling#comments' />
  1477. <id>https://www.tbray.org/ongoing/When/202x/2025/07/07/Epsilon-Wrangling</id>
  1478. <published>2025-07-07T12:00:00-07:00</published>
  1479. <updated>2025-07-09T19:41:00-07:00</updated>
  1480. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Quamina Diary' />
  1481. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1482. <category scheme='https://www.tbray.org/ongoing/What/' term='Quamina Diary' />
  1483. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Software' />
  1484. <category scheme='https://www.tbray.org/ongoing/What/' term='Software' />
  1485. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I haven’t shipped any new features for     <a href='https://github.com/timbray/quamina'>Quamina</a> in many months, partly due to a flow of real-life distractions, but     also I’m up against tough performance problems in implementing     <a href='/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series'>Regular Expressions at massive scale</a>.     I’m still looking for a breakthrough, but have learned things about building and executing finite automata     that I think are worth sharing. This piece has to do with     <a href='https://en.wikipedia.org/wiki/Nondeterministic_finite_automaton#NFA_with_ε-moves'>epsilons</a>; anyone who has studied     finite automata will know about them already, but I’ll offer background for those people to skip</div></summary>
  1486. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1487.    <p>I haven’t shipped any new features for
  1488.    <a href="https://github.com/timbray/quamina">Quamina</a> in many months, partly due to a flow of real-life distractions, but
  1489.    also I’m up against tough performance problems in implementing
  1490.    <a href="/ongoing/When/202x/2024/12/12/Quamina-Regular-Expression-Series">Regular Expressions at massive scale</a>.
  1491.    I’m still looking for a breakthrough, but have learned things about building and executing finite automata
  1492.    that I think are worth sharing. This piece has to do with
  1493.    <a href="https://en.wikipedia.org/wiki/Nondeterministic_finite_automaton#NFA_with_ε-moves">epsilons</a>; anyone who has studied
  1494.    finite automata will know about them already, but I’ll offer background for those people to skip.</p>
  1495.    <p>I’ve written about this before in
  1496.    <a href="/ongoing/When/202x/2024/06/17/Epsilon-Love">Epsilon Love</a>. A commenter pointed out that the definition of “epsilon”
  1497.    in that piece is not quite right per standard finite-automata theory, but it’s still a useful in that it describes how
  1498.    epsilons support constructs like the shell-style “<code>*</code>”.</p>
  1499.    <h2 id='p-2'>Background</h2>
  1500.    <p>Finite automata come in two flavors: Deterministic (DFA) and Nondeterministic (NFA).  DFAs move from state to state one input
  1501.    symbol at a time: it’s simple and easy to understand and to implement.
  1502.    NFAs have two distinguishing characteristics: First, when you’re in a
  1503.    state and an input symbol arrives, you can transfer to more than one other state. Second, a state can have “epsilon transitions”
  1504.    (let’s say “ε” for epsilon), which can happen any time at all while you’re in that state, input or no input.</p>
  1505.    <p>NFAs are more complicated to traverse (will discuss below) but you need them if you want to
  1506.    implement regular expressions with <code>.</code> and <code>?</code> and <code>*</code> and so on. You can turn any NFA into a
  1507.    DFA, and I’ll come back to that subject in a future piece.</p>
  1508.    <p>For implementing NFAs, I’ve been using
  1509.    <a href="https://en.wikipedia.org/wiki/Thompson%27s_construction">Thompson's construction</a>, where
  1510.    “Thompson” is
  1511.    <a href="https://en.wikipedia.org/wiki/Ken_Thompson">Ken Thompson</a>, co-parent of Unix. This technique is also nicely
  1512.    described by Russ Cox in
  1513.    <a href="https://swtch.com/~rsc/regexp/regexp1.html">Regular Expression Matching Can Be Simple And Fast</a>. You don’t need to
  1514.    learn it to understand this piece, but I’ll justify design
  1515.    choices by saying “per Thompson”.</p>
  1516.    <p>I’m going to discuss two specific issues today, ε-closures and a simpler NFA definition.</p>
  1517.    <h2 id='p-3'>ε-closures</h2>
  1518.    <p>To set the stage, consider this regexp: <nobr><code>A?B?C?X</code></nobr></p>
  1519.    <p>It should match “X” and “BX” and “ACX” and so on, but not “CAX” or “XX”.
  1520.    Thompson says that you implement <code>A?</code> with a
  1521.    transition to the next state on “A” and another ε-transition to that next state; because if you see an “A” you should transition,
  1522.    but then you can transition anyhow even if you don’t.</p>
  1523.    <p>The resulting NFA looks like this:</p>
  1524.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/07/AcmBcmCcmX.png" alt="NFA matching A?B?C?X" />
  1525.    <p> In finite-automaton
  1526.    math, states are usually represented by the letter “q” followed by a number (usually italicized and subscripted, like
  1527.    <i>q<sub>0</sub></i>, but not here, sorry). Note <code>q4</code>’s double circle which means it’s
  1528.    a goal state, i.e. if we get here we’ve matched the regexp.
  1529.    I should add that this was produced with
  1530.    <a href="https://draw.io">draw.io</a>, which seems to make this sort of thing easy.
  1531.    </p>
  1532.    <h2 id='p-5'>Back to that NFA</h2>
  1533.    <p>So, here’s a challenge: Sketch out the traversal code in your head. Think about the input strings “AX” and “BCX” and just “X”
  1534.    and how you’d get through the NFA to the Q4 goal state.</p>
  1535.    <p>The trick is what’s called the ε-closure. When you get to a state, before you look at the next input symbol, you have to set
  1536.    up to process it. In this case, you need to be able to transition on an A or B or C. So what you do is pull together the
  1537.    start state <code>q0</code> and also any other states you can reach from there through ε-transitions. In this case, the ε-closure
  1538.    for the start state is <code>{q0, q1, q2, q3}</code>.</p>
  1539.    <p>Suppose, then, that you see a “B” input symbol. You apply it to all the states in the ε-closure. Only <code>q1</code> matches,
  1540.    transitioning you to
  1541.    <code>q2</code>. Before you look at the next input symbol, you compute the ε-closure for <code>q2</code>, which turns
  1542.    out to be <code>{q2, q3}</code>. With this ε-closure, you can match “C” or “X”. If you get a “C”, you”ll step to
  1543.    <code>q3</code>, whose ε-closure is just itself, because “X” is the only path forward.</p>
  1544.    <p>So your NFA-traversal algorithm for one step becomes something like:</p>
  1545.    <ol>
  1546.      <li><p>Start with a list of states.</p></li>
  1547.      <li><p>Compute the ε-closure of that list.</p></li>
  1548.      <li><p>Read an input symbol.</p></li>
  1549.      <li><p>For each state in the ε-closure, see if you can traverse to another state.</p></li>
  1550.      <li><p>If so, add it to your output list of states.</p></li>
  1551.      <li><p>When you’re done, your output list of states is the input to this algorithm for the next step.</p></li>
  1552.    </ol>
  1553.    <h2 id='p-6'>Computation issues</h2>
  1554.    <p>Suppose your regular expression is <code>(A+BC?)+</code>. I’m not going to sketch out the NFA, but just looking at it tells
  1555.    you that it has to have loopbacks; once you’ve matched the parenthetized chunk you need to go back to a state where you can
  1556.    recognize another occurrence.
  1557.    For this regexp’s NFA, computing the ε-closures can lead you into an infinite loop. (Should be obvious, but I didn’t realize it until
  1558.    after the first time it happened.)</p>
  1559.    <p>You can have loops and you can also have dupes. In practice, it’s not that uncommon for a state to have more than one
  1560.    ε-transition, and for the targets of these transitions to overlap.</p>
  1561.    <p>So you need to watch for loops and to dedupe your output. I think the only way to avoid this is with a cookie-crumbs
  1562.    “where I’ve been” trail, either as a list or a hash table.</p>
  1563.    <p>Both of these are problematic because they require allocating memory, and that’s something you really don’t want to do when
  1564.    you’re trying to match patterns to events at Quamina’s historic rate of millions per second.</p>
  1565.    <p>I’ll dig into this problem in a future Quamina-Diary outing, but obviously, caching computed
  1566.    epsilon closures would avoid re-doing this computation.</p>
  1567.    <p>Anyhow, bear ε-closures in mind, because they’ll keep coming up as this series goes on.</p>
  1568.    <h2 id='p-7'>And finally, simplifying “NFA”</h2>
  1569.    <p>At the top of this piece, I offered the standard definition of NFAs: First, when you’re in a
  1570.    state and an input symbol arrives, you can transfer to more than one other state. Second, you can have ε-transitions.
  1571.    Based on my recent work, I think this definition is redundant. Because if you need to transfer to two different states on some
  1572.    input symbol, you can do that with ε-transitions.</p>
  1573.    <p>Here’s a mini-NFA that transfers from state <code>q0</code> on “A” to both <code>q1</code> and <code>q2</code>.</p>
  1574.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/07/Splice-1.png" alt="An NFA transferring to two different states on an input symbol" />
  1575.    <p>And here’s how you can achieve the same effect with ε-transitions:</p>
  1576.    <img src="https://www.tbray.org/ongoing/When/202x/2025/07/07/Splice-2.png" alt="Transferring to two destinations using ε-transitions" />
  1577.    <p>In that NFA, in <code>qS</code> the “S” stands for “splice”, because it’s a state that exists to connect
  1578.    two threads of finite-automaton traversal.</p>
  1579.    <p>I’m pretty sure that this is more than just a mathematical equivalence. In my regexp implementation, so far at least,
  1580.    I’ve never encountered a need to do that first kind of dual transition. Furthermore, the “splice” structure is how Thompson
  1581.    implements the regular-expression “<code>|</code>” operator.</p>
  1582.    <p>So if you’re building an NFA, all the traversal stuff you need in a state is a simple map from input symbol to next state,
  1583.    and a list of ε-transitions.</p>
  1584.    <h2 id='p-8'>Next up</h2>
  1585.    <p>How my own implementation of NFA traversal collided head-on into the Benchmark From Hell and still hasn’t recovered.</p>
  1586. </div></content></entry>
  1587.  
  1588. <entry>
  1589. <title>The Real GenAI Issue</title>
  1590. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/06/AI-Manifesto' />
  1591. <link rel='replies'        thr:count='10'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/06/AI-Manifesto#comments' />
  1592. <id>https://www.tbray.org/ongoing/When/202x/2025/07/06/AI-Manifesto</id>
  1593. <published>2025-07-06T12:00:00-07:00</published>
  1594. <updated>2025-07-06T12:06:43-07:00</updated>
  1595. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
  1596. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1597. <category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
  1598. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Last week I published a     <a href='/ongoing/When/202x/2025/07/01/First-AI-Code'>featherweight narrative</a> about applying GenAI in a real-world context, to     a tiny programming problem.  Now I’m regretting that piece because I totally ignored the two central issues with     AI: What it’s meant to do, and how much it really costs</div></summary>
  1599. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1600.    <p>Last week I published a
  1601.    <a href="/ongoing/When/202x/2025/07/01/First-AI-Code">featherweight narrative</a> about applying GenAI in a real-world context, to
  1602.    a tiny programming problem.  Now I’m regretting that piece because I totally ignored the two central issues with
  1603.    AI: What it’s meant to do, and how much it really costs.</p>
  1604.    <h2 id='p-1'>What genAI is for</h2>
  1605.    <p>The most important fact about genAI in the real world is that there’ve been literally
  1606.    <a href="https://finance.yahoo.com/news/how-nvidia-played-a-central-role-in-the-306-billion-ai-startup-boom-195741749.html?guccounter=1">hundreds
  1607.    of billions</a> of dollars invested in it; that link is just startups, and ignores a comparable torrent of cash pouring out of Big
  1608.    Tech.</p>
  1609.    <p>The business leaders pumping all this money of course don’t understand the technology. They’re doing this for exactly one
  1610.    reason: They think they can discard armies of employees and replace them with LLM services, at the cost of
  1611.    shipping shittier products.  Do you think your management would spend that kind of money to help you with a quicker first draft or
  1612.    a summarized inbox?</p>
  1613.    <p>Adobe said the quiet part out loud:
  1614.    <a href="https://petapixel.com/2024/05/03/adobe-throws-photographers-under-the-bus-again-skip-the-photoshoot/">Skip the
  1615.    Photoshoot</a>. </p>
  1616.    <p>At this point someone will point out that previous technology waves have generated as much employment as they’ve eliminated.
  1617.    Maybe so, but that’s not what business leaders think they’re buying. They think they’re buying smaller payrolls.</p>
  1618.    <p>Maybe I’m overly sensitive, but thinking about these truths leads to a mental stench that makes me want to stay away from
  1619.    it.</p>
  1620.    <h2 id='p-2'>How much does genAI cost?</h2>
  1621.    <p>Well, I already mentioned all those hundreds of billions. But that’s pocket change. The investment community in general and
  1622.    Venture Capital in particular will whine and moan, but the people who are losing the money are people who can afford to.</p>
  1623.    <p>The first real cost is hypothetical: What if those business leaders are correct and they can gleefully dispose of millions of
  1624.    employees? If you think we’re already suffering from egregious levels of inequality, what happens when a big chunk of the
  1625.    middle class suddenly becomes professionally superfluous?  I’m no economist so I’ll stop there, but you don’t have to be a
  1626.    rocket scientist to predict severe economic pain.</p>
  1627.    <p>Then there’s the other thing that nobody talks about, the massive greenhouse-gas load that all those data centers are going
  1628.    to be pumping out. This at a time when we we blow past one atmospheric-carbon metric after another and David Suzuki says
  1629.    <a href="https://www.ipolitics.ca/2025/07/02/its-too-late-david-suzuki-says-the-fight-against-climate-change-is-lost/">the
  1630.    fight against climate change is lost</a>, that we need to hunker down and work on survival at the local level.</p>
  1631.    <h2 id='p-3'>The real problem</h2>
  1632.    <p>It’s the people who are pushing it.  Their business goals are quite likely, as a side-effect, to make
  1633.    the world a worse place, and they don’t give a fuck.  Their technology will inevitably worsen the onrushing climate catastrophe,
  1634.    and they don’t give a fuck.</p>
  1635.    <p>It’s probably not as simple as “They’re just shitty people”<span class='dashes'> —</span> it’s not exactly easy to escape the
  1636.    exigencies of modern capitalism. But they are people who are doing shitty things.</p>
  1637.    <h2 id='p-4'>Is genAI useful?</h2>
  1638.    <p>Sorry, I’m having trouble even thinking about that now.</p>
  1639. </div></content></entry>
  1640.  
  1641. <entry>
  1642. <title>My First GenAI Code</title>
  1643. <link href='https://www.tbray.org/ongoing/When/202x/2025/07/01/First-AI-Code' />
  1644. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/07/01/First-AI-Code#comments' />
  1645. <id>https://www.tbray.org/ongoing/When/202x/2025/07/01/First-AI-Code</id>
  1646. <published>2025-07-01T12:00:00-07:00</published>
  1647. <updated>2025-07-01T11:38:00-07:00</updated>
  1648. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
  1649. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1650. <category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
  1651. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Software' />
  1652. <category scheme='https://www.tbray.org/ongoing/What/' term='Software' />
  1653. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>At the moment, we have no idea what the impact of genAI on software development is going to be. The impact of     <em>anything</em> on coding     is hard to measure systematically, so we rely on anecdata and the community’s eventual consensus.     So, here’s my anecdata. Tl;dr: The AI was not useless</div></summary>
  1654. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1655.    <p>At the moment, we have no idea what the impact of genAI on software development is going to be. The impact of
  1656.    <em>anything</em> on coding
  1657.    is hard to measure systematically, so we rely on anecdata and the community’s eventual consensus.
  1658.    So, here’s my anecdata. Tl;dr: The AI was not useless.</p>
  1659.    <h2 id='p-1'>The problem</h2>
  1660.    <p>My current work on
  1661.    <a href="/ongoing/What/Technology/Quamina%20Diary/">Quamina</a> involves dealing with collections of finite-automata states,
  1662.    which, in the Go programming language, are represented as slices of pointers to state instances:</p>
  1663.    <blockquote><p><code>[]*faState</code></p></blockquote>
  1664.    <p>The problem I was facing was deduping them, so that there would be only one instance corresponding to any particular
  1665.    collection. This is what, in Java, the <code>intern()</code> call does with strings.</p>
  1666.    <p>The algorithm isn’t rocket science:</p>
  1667.    <ol>
  1668.      <li><p>Dedupe the states, i.e. turn the collection into a set.</p></li>
  1669.      <li><p>For each set of states, generate a key.</p></li>
  1670.      <li><p>Keep a hash table of sets around, and use the key to see whether you’ve already got such a set, and if so return
  1671.      it. Otherwise, make a new entry in the hash table and return that.</p></li>
  1672.    </ol>
  1673.    <p>I’m out of touch with the undergrad CS curriculum, but this feels like a second-year assignment or thereabouts? Third?</p>
  1674.    <h2 id='p-2'>Enter Claude</h2>
  1675.    <p>So I prompted Claude thus:</p>
  1676.    <blockquote><p>I need Go code to provide a "intern"-like function for lists of pointers. For example, if I have several
  1677.    different []*int arrays, which may contain duplicates, I want to call intern() on each of them and get back a single canonical
  1678.    pointer which is de-duplicated and thus a set.</p></blockquote>
  1679.    <p>Claude did pretty well. It got the algorithm right, the code was idiomatic and usefully commented, and it also provided a
  1680.    decent unit test (but in a <code>main()</code> stanza rather than a proper Go test file).
  1681.    I didn’t try actually running it.</p>
  1682.    <p>The interesting part was the key computation. I, being lazy, had just done a Go <code>fmt.Sprintf("%p")</code>
  1683.    incantation to get a hex string representing each state’s address, sorted them, joined them, and that was the key.</p>
  1684.    <p>Claude worked with the pointers more directly.</p>
  1685.    <pre><code> // Sort by pointer address for consistent ordering
  1686. sort.Slice(unique, func(i, j int) bool {
  1687. return uintptr(unsafe.Pointer(unique[i])) &lt; uintptr(unsafe.Pointer(unique[j]))
  1688. })</code></pre>
  1689.    <p>Then it concatenated the raw bytes of the map addresses and lied to Go by claiming it was a string.</p>
  1690.    <pre><code> // Create key from pointer addresses
  1691. key := make([]byte, 0, len(slice)*8)
  1692. for _, ptr := range slice {
  1693. addr := uintptr(unsafe.Pointer(ptr))
  1694. // Convert address to bytes
  1695. for i := 0; i &lt; 8; i++ {
  1696. key = append(key, byte(addr>>(i*8)))
  1697. }
  1698. }
  1699. return string(key)</code></pre>
  1700. <p>This is an improvement in that the keys will be half the size of my string version.
  1701. I didn’t copy-paste Claude’s code wholesale, just replaced ten or so lines of key construction.</p>
  1702.    <h2 id='p-3'>Take-away</h2>
  1703.    <p>I dunno. I thought the quality of the code was fine, wouldn’t have decomposed the functions in the same way but wouldn’t have
  1704.    objected on review. I was pleased with the algorithm, but then I would be since it was the same one I’d written, and, having
  1705.    said that, quite possibly that’s the only algorithm that anyone has used. It will be <em>super</em> interesting if someone
  1706.    responds to this write-up saying “You and Claude are fools, here’s a much better way.”</p>
  1707.    <p>Was it worth fifteen minutes of my time to ask Claude and get a slightly better key computation?
  1708.    Only if this ever turns out
  1709.    to be a hot code path and I don’t think anybody’s smart enough to know that in advance.</p>
  1710.    <p>Would I have saved time by asking Claude first? Tough to tell; Quamina’s data structures are a bit non-obvious and I would
  1711.    have had to go to a lot of prompting work to get it to emit code I could use directly.
  1712.    Also, since Quamina is low-level performance-critical infrastructure code, I’d be nervous about having any volume of code
  1713.    that I didn’t really <em>really</em> understand.</p>
  1714.    <p>I guess my take-away was that in this case, Claude knew the Go idioms and APIs better than I did; I’d never looked at the
  1715.    <a href="https://pkg.go.dev/unsafe">unsafe</a> package.</p>
  1716.    <p>Which reinforces my
  1717.    suspicion that genAI is going to be especially useful at helping generate code to talk to big complicated
  1718.    APIs that are hard to remember all of.  Here’s an example: Any moderately competent Android developer could add a feature to an
  1719.    app where it strobes the flash and surges the vibration in sync with how fast you’re shaking the device back and forth,
  1720.    probably in an afternoon. But it would require a couple of dozen calls into the dense forest of Android APIs, and I suspect a
  1721.    genAI might get you there a lot faster by just filling the calls in as prompted.</p>
  1722.    <p>Reminder: This is just anecdata.</p>
  1723. </div></content></entry>
  1724.  
  1725. <entry>
  1726. <title>Qobuz and Mac</title>
  1727. <link href='https://www.tbray.org/ongoing/When/202x/2025/06/22/Qobuz-and-Others' />
  1728. <link rel='replies'        thr:count='0'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/06/22/Qobuz-and-Others#comments' />
  1729. <id>https://www.tbray.org/ongoing/When/202x/2025/06/22/Qobuz-and-Others</id>
  1730. <published>2025-06-22T12:00:00-07:00</published>
  1731. <updated>2025-06-26T13:13:08-07:00</updated>
  1732. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Music' />
  1733. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  1734. <category scheme='https://www.tbray.org/ongoing/What/' term='Music' />
  1735. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Back in March I offered     <a href='/ongoing/When/202x/2025/03/27/Music-Plus-Qobuz'>Latest Music (feat. Qobuz)</a>, describing all the ways I listen to     music (Tl;dr: YouTube Music, Plex, Qobuz, record player). I stand by my opinions there but wanted to write more on two subjects:     First Qobuz, because it suddenly got a lot better. And a recommendation, for people with fancy A/V setups, that you include a cheap     Mac Mini</div></summary>
  1736. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1737.    <p>Back in March I offered
  1738.    <a href="/ongoing/When/202x/2025/03/27/Music-Plus-Qobuz">Latest Music (feat. Qobuz)</a>, describing all the ways I listen to
  1739.    music (Tl;dr: YouTube Music, Plex, Qobuz, record player). I stand by my opinions there but wanted to write more on two subjects:
  1740.    First Qobuz, because it suddenly got a lot better. And a recommendation, for people with fancy A/V setups, that you include a cheap
  1741.    Mac Mini.</p>
  1742.    <h2 id='p-1'>Qobuz</h2>
  1743.    <p>That other piece had a list of the reasons to use Qobuz, but times have changed, so let’s revise it:</p>
  1744.    <ol>
  1745.      <li><p>It pays artists more per stream than any other service, by a wide margin.</p></li>
  1746.      <li><p>It seems to have as much music as anyone else.</p></li>
  1747.      <li><p>It’s album-oriented, and I appreciate artists curating their own music.</p></li>
  1748.      <li><p>Classical music is a first-class citizen.</p></li>
  1749.      <li><p>It’s actively curated; they highlight new
  1750.      music regularly, and pick a “record of the week”. To get a feel, check out
  1751.      <a href="https://www.qobuz.com/ca-en/magazine">Qobuz Magazine</a>; you don’t have to be a subscriber.</p></li>
  1752.      <li><p>It gives evidence of being built by people who love music.</p></li>
  1753.      <li><p>They’re obsessive about sound quality, which is great, but only makes a difference if you’re listening through quality
  1754.      speakers.</p></li>
  1755.      <li><p>A few weeks ago, the mobile app quality switched from adequate to
  1756.      excellent.</p></li>
  1757.    </ol>
  1758.    <h2 id='p-2'>That app</h2>
  1759.    <p>I want to side-trip a bit here, starting with a question. How long has it been since an app you use has added a feature that
  1760.    was genuinely excellent and let you do stuff you couldn’t before and didn’t get in your way and created no suspicion that it was
  1761.    strip-mining your life for profit?  I’m here to tell you that this can still happen, and it’s a crushing criticism
  1762.    of my profession that it so rarely does.</p>
  1763.    <p>I’m talking about
  1764.    <a href="https://www.qobuz.com/ca-en/connect">Qobuz Connect</a>. I believe there are other music apps that can do this sort of
  1765.    stuff, but it feels like magic to me.</p>
  1766.    <p>It’s like this. I listen to music at home on an audiophile system with big speakers, in
  1767.    <a href="/ongoing/What/The%20World/Jaguar%20Diary/">our car</a>, and on
  1768.    <a href="/ongoing/When/201x/2019/08/06/Jeanneau-795">our boat</a>.  The only app I touch is the
  1769.    <a href="https://play.google.com/store/apps/details?id=com.qobuz.music">Qobuz Android app</a>. The only time it’s actually
  1770.    receiving and playing the music itself is in the car, with the help of Android Auto.  In the other scenarios it’s talking to
  1771.    Qobuz running on a Mac, which actually fetches the music and routes it to the audio system.
  1772.    Usually it figures out what player I want it to control automatically, although there’ve been a couple
  1773.    times when I drove away in the car and it got confused about where to send the music. Generally, it works great.</p>
  1774.    <p>The app’s music experience is rich and involving.</p>
  1775.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/22/Screenshot_20250622-230116.png" alt="Qobuz Android app screenshot" />
  1776.    <p>It has New Releases and curated playlists and a personalized stream for
  1777.    me and a competent search function for those times I absolutely must listen to Deep Purple or Hania Rani or
  1778.    whoever.</p>
  1779.    <p>I get a chatty not-too-long email from Qobuz every Friday, plugging a few of the week’s new releases, with sideways and
  1780.    backward looks too. (This week: A Brian Wilson stream.) The app has so much stuff, especially among the themed streams, that I
  1781.    sometimes get lost. But somehow it’s not irritating; what’s on the screen remains musically interesting and you can always hit
  1782.    the app’s Home button.</p>
  1783.    <p>Qobuz has its own musical tastes that guide its curation. They’re not always compatible with
  1784.    mine<span class='dashes'> —</span> my tolerance for EDM and mainstream Hip-hop remains low. And I wish they were
  1785.    stronger on Americana. But the intersection is broad enough to provide plenty of enjoyable new-artist experiences. Let me share
  1786.    one with you:
  1787.    <a href="https://kwashibu.bandcamp.com/album/love-warrior-s-anthem">Kwashibu Area Band</a>, from Ghana.</p>
  1788.    <p>Oh, one complaint: Qobuz was eating my Pixel’s battery. So I poked around online and it’s a known problem; you have to use the
  1789.    Android preferences to stop it from running in the background. Huh? What was it doing in the background anyhow?! But it seems to
  1790.    work fine even when it’s not doing it.</p>
  1791.    <h2 id='p-3'>A Mac, you say?</h2>
  1792.    <p>The music you’re listening to is going to be stored on disk, or incoming from a streaming service. Maybe you want to serve
  1793.    some of the stored music out to listen to it in the car or wherever. There are a variety of audio products in the
  1794.    “Streamer” category that do some of these things in various combinations. A lot of them make fanciful claims about the
  1795.    technology inside and are thus expensive, you can easily spend thousands.</p>
  1796.    <p>But any reasonably modern computer can do all these things and more, plus it also can drive a big-screen display, plus it will
  1797.    probably run the software behind whatever next year’s New Audio Hotness is.</p>
  1798.    <p>At this point the harder-core geeks will adopt a superior tone of voice to say “I do all that stuff with FreeBSD and a bunch of
  1799.    open-source packages running on a potato!”</p>
  1800.    <p>More power to ’em. But I recommend a basic Apple Silicon based Mac Mini, M1 is fine, which you can get for like $300 used on
  1801.    eBay. And if you own a lot of music and video you can plug in a 5T USB drive for a few more peanuts. This will run Plex and
  1802.    Qobuz and almost any other imaginable streaming software. Plus you can plug it into your home-theater screen and it has a modern
  1803.    Web browser so you can also play anything from anywhere on the Web.</p>
  1804.    <p>I’ve been doing this for a while but I had one big gripe. When I wanted to stream music from the Mac, I needed to use a
  1805.    keyboard and mouse, so I keep one of each, Bluetooth-flavored, nearby. But since I got Qobuz running that’s become a very rare
  1806.    occurrence.</p>
  1807.    <h2 id='p-4'>You’re forgetting something</h2>
  1808.    <p>Oh, and yeah, there’s the record player. Playing it requires essentially no software at all, isn’t that great?</p>
  1809. </div></content></entry>
  1810.  
  1811. <entry>
  1812. <title>Long Links</title>
  1813. <link href='https://www.tbray.org/ongoing/When/202x/2025/06/21/Long-Links' />
  1814. <link rel='replies'        thr:count='6'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/06/21/Long-Links#comments' />
  1815. <id>https://www.tbray.org/ongoing/When/202x/2025/06/21/Long-Links</id>
  1816. <published>2025-06-21T12:00:00-07:00</published>
  1817. <updated>2025-06-21T11:56:27-07:00</updated>
  1818. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1819. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1820. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>“Wow, Tim, didn’t you do a      <a href='/ongoing/When/202x/2025/05/06/Long-Links'>Long Links</a> just last month? Been spending too much time doomscrolling,     have we?” Maybe. There sure are a lot of tabs jostling each other along the top of that browser. Many     are hosting works that are both long and good. So here they are; you probably don’t have time for all of ’em but my hope     is that one or two might reward your visit</div></summary>
  1821. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1822.    <p>“Wow, Tim, didn’t you do a
  1823.    <a href="/ongoing/When/202x/2025/05/06/Long-Links">Long Links</a> just last month? Been spending too much time doomscrolling,
  1824.    have we?” Maybe. There sure are a lot of tabs jostling each other along the top of that browser. Many
  1825.    are hosting works that are both long and good. So here they are; you probably don’t have time for all of ’em but my hope
  1826.    is that one or two might reward your visit.</p>
  1827.    <p>Let’s start with a really important subject: Population growth oh actually these days it’s population shrinkage.
  1828.    For a short-sharp-shock-flavored introduction I recommend
  1829.    <a href="https://www.youtube.com/watch?v=Ufmu1WD2TSk">South Korea Is Over</a>
  1830.    which explains the brick wall societies with fertility rates way below the replacement rate of 2.1 children per woman per
  1831.    lifetime are hurtling toward. South Korea, of course, being the canonical example. But also Japan and Taiwan and Italy and Spain
  1832.    and so on.</p>
  1833.    <p>And, of course, the USA, where the numbers aren’t <em>that</em> much higher:
  1834.    <a href="https://www.macrotrends.net/global-metrics/countries/usa/united-states/fertility-rate">U.S. Fertility Rate
  1835.    (1950-2025)</a>. Even so, the population still grows (because of immigration), albeit at less than 1% per annum:
  1836.    <a href="https://www.macrotrends.net/global-metrics/countries/usa/united-states/population-growth-rate">U.S. Population Growth
  1837.    Rate</a>. If the MAGAs get their way and eventually stop all non-white immigration, the US will be in South Korea
  1838.    territory within a generation or two. </p>    
  1839.    <p>A reasonable person might ask why. It’s not really complicated, as you can read here:
  1840.    <a href="https://www.nytimes.com/2025/06/15/opinion/birth-rate-parenting-natalism.html?unlocked_article_code=1.Pk8.OBam.dOi0UpP-8-DV&amp;smid=url-share">A Bold Idea to Raise the Birthrate: Make Parenting Less Torturous</a>.
  1841.    From which I quote: “To date, no government policies have significantly improved their nation’s birthrates for a sustained
  1842.    period.” The essay argues convincingly that it’s down to two problems: Capitalism and sexism. Neither of which offers an easy
  1843.    fix. </p>
  1844.    <p>Speaking of the travails of late capitalism, here’s how bad it’s getting:
  1845.    <a href="https://www.nytimes.com/2025/03/01/opinion/crisis-working-homeless.html?unlocked_article_code=1.Qk8.jsTO.aUBSAMHw7Op2&amp;smid=url-share">America
  1846.    Is Pushing Its Workers Into Homelessness</a>.</p>
  1847.    <p>For a refreshingly different take on the business world, here’s Avery Pennarun, CEO of Tailscale:
  1848.    <a href="https://apenwarr.ca/log/20250530">The evasive evitability of enshittification</a>. Not sure I buy what he’s saying, but
  1849.    still worth reading.</p>
  1850.    <p>Most people who visit these pages are geeks or geek-adjacent. If you’re one of those, and especially if you enjoy the small
  1851.    but vibrant genre of Comical Tech War Stories, I recommend
  1852.    <a href="https://yeet.cx/blog/lock-free-rust/">Lock-Free Rust: How to Build a Rollercoaster
  1853.    While It’s on Fire</a></p>
  1854.    <p>And here’s write-up on an AWS product which has one of the best explanations I’ve ever read of the different flavors modern
  1855.    databases come in: <a href="https://www.redshift-observatory.ch/white_papers/downloads/introduction_to_the_fundamentals_of_amazon_redshift.html">Introduction to the Fundamentals of Amazon Redshift</a></p>
  1856.    <p>Of course, the geek conversation these days is much taken up with the the impact of genAI as in “vibe coding”. To
  1857.    summarize the conversation: A few people, not obviously fools,  are saying “This stuff seems to help me” and many others, also
  1858.    apparently sensible, are shouting back “You’re lying to yourself, it can’t be helping!”  Here is some of the testimony:
  1859.    Kellan on <a href="https://laughingmeme.org//2025/05/25/vibe-coding-for-teams.html">Vibe
  1860.    coding for teams, thoughts to date</a>, Armin Ronacher on
  1861.    <a href="https://lucumr.pocoo.org/2025/6/12/agentic-coding/">Agentic Coding Recommendations</a>,
  1862.    Harper on <a href="https://harper.blog/2025/05/08/basic-claude-code/">Basic Claude Code</a>, and
  1863.    Klabnik on
  1864.    <a href="https://steveklabnik.com/writing/a-tale-of-two-claudes/">A tale of two Claudes</a></p>
  1865.    <p>I lean to believing narratives of personal experience, but on the other hand the skeptics make good points. Another
  1866.    random piece of evidence: Because I’m lazy, I tend to resist adopting technologies that have steep learning curves, which genAI
  1867.    currently does. On many occasions, this has worked out well because those technologies have turned out not to pay off very
  1868.    well. Am I a canary in the coal mine?</p>
  1869.    <h2 id='p-2'>*cough*</h2>
  1870.    <p>Since I introduced myself into the narrative, I’ll note that today is my 70th birthday. I am told that this means
  1871.    that my wisdom has now been maximized, so you’re safe in believing whatever you read in this space.  I don’t have anything
  1872.    special to say to commemorate the occasion,
  1873.    so here’s a picture of my neighborhood’s network infrastructure, which outlines the form of a
  1874.    cathedral’s nave. I’m sure there’s a powerful metaphor lurking in there.</p>
  1875.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/21/TXT55659.png" alt="Many electrical and data wires festoon a back alley" />    
  1876.    <p>Oh, and here’s a photography Long Link: <a href="https://www.lux.camera/what-is-hdr/">What is HDR, anyway?</a>
  1877.    It’s actually a pitch for a nice-looking mobile camera app, but it offers real value on things that can
  1878.    affect the quality of your pictures.</p>
  1879.    <p>Regular readers will know that I’m fascinated by the many unsolved issues and open questions in cosmology, which are by
  1880.    definition the largest problems facing human consciousness. The ΛCDM-vs-MOND controversy, i.e. “Is there really dark
  1881.    matter or does gravity get weird starting at the outer edges of galaxies?”, offers great entertainment value. And, there is
  1882.    news!</p>
  1883.    <p>First of all, here’s a nice overview on the controversy:
  1884.    <a href="https://arxiv.org/pdf/2505.21638v1">Modified Newtonian Dynamics: Observational Successes and Failures</a>.</p>
  1885.    <p>Which points out that the behavior of “wide binary” star systems ought to help resolve the issue, but that people who
  1886.    study it keep coming up with contradictory findings. Here’s the latest, from Korean researchers: Press release
  1887.    <a href="http://www.sejongpr.ac.kr/sejongnewspaperview.do?currentPage=1&amp;searchField=&amp;searchValue=&amp;boardType=3&amp;pkid=73549&amp;utm_source=beehiiv&amp;utm_medium=newsletter&amp;utm_campaign=mediamobilize&amp;_bhlid=3e40dce99e536f4015a1dd2c6afd193a465d17ea">New method of measuring gravity with 3D velocities of wide binary stars is developed and confirms modified gravity</a>
  1888.    and peer-reviewed paper:
  1889.    <a href="https://iopscience.iop.org/article/10.3847/1538-4357/adce09">Low-acceleration Gravitational Anomaly
  1890.    from Bayesian 3D Modeling of Wide Binary Orbits: Methodology and Results with Gaia Data Release 3</a>.
  1891.    Spoiler: They think the gravity gets weird. I have a math degree but cosmology math is generally way over my head. Having said
  1892.    that, I think those South Koreans may be a bit out over their skis; I generally distrust heroic statistical methods. We’ll
  1893.    see.</p>
  1894.    <p>Let’s do politics. It turns out that the barbaric junta which oppresses the people of China does not limit its barbarism
  1895.    to its own geography:
  1896.    <a href="https://www.cbc.ca/news/politics/china-targets-dissidents-canada-1.7543745?cmp=rss">Followed, threatened and smeared
  1897.    — attacks by China against its critics in Canada are on the rise</a>.</p>
  1898.    <p>More politics: The MAGAs are always railing against “elites”. Here are two discussions of what they mean:
  1899.    <a href="https://www.theatlantic.com/ideas/archive/2025/04/class-money-finances/682301/">What the Comfort Class Doesn’t
  1900.    Get</a> and <a href="https://siderea.dreamwidth.org/1865048.html">When They Say Elites, They Mean Us</a>.</p>
  1901.    <p>The world’s biggest political issue <em>should</em> be the onrushing climate crisis. When Trump and his toadies
  1902.    are justly condemned and ridiculed by future historians, it is their malevolent cluelessness on this subject that
  1903.    may burn the hottest. Who knows, maybe they’ll pay attention to this:
  1904.    <a href="https://www.bloomberg.com/news/newsletters/2025-06-18/insurers-want-businesses-to-wake-up-to-costs-of-extreme-heat">Insurers Want Businesses to Wake Up to Costs of Extreme Heat</a>.</p>
  1905.    <h2 id='p-1'>The list of Long Links is too long</h2>
  1906.    <p>So I’ll try to end cheerfully.</p>
  1907.    <p>A graceful essay about an old camera and a dreamy picture:
  1908.    <a href="https://petapixel.com/2025/05/27/a-bridge-across-time-for-sebastiao-salgado/">A Bridge Across Time: For
  1909.    Sebastião Salgado</a></p>
  1910.    <p>Latin Wikipedia has 140,000 articles; consider the delightful discussion of
  1911.    <a href="https://la.wikipedia.org/wiki/Equus_asinus"><cite>Equus asinus</cite></a>.</p>
  1912.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/21/equus-asinus.png" alt="Asinus in opere tesselato Byzantino" />
  1913.    <div class='caption'><p>Asinus in opere tesselato Byzantino</p></div>
  1914.    <p>Here’s a lovely little song from TORRES and Julien Baker:
  1915.    <a href="https://www.youtube.com/watch?v=TurU_Jn-LEg">The Only Marble I’ve Got Left</a>.</p>
  1916.    <p>Finally, a clear-eyed if lengthy essay on why and how to think:
  1917.    <a href="https://www.newyorker.com/culture/open-questions/should-you-question-everything">Should You Question
  1918.    Everything?</a></p>
  1919. </div></content></entry>
  1920.  
  1921. <entry>
  1922. <title>June 2025 C2PA News</title>
  1923. <link href='https://www.tbray.org/ongoing/When/202x/2025/06/17/More-C2PA' />
  1924. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/06/17/More-C2PA#comments' />
  1925. <id>https://www.tbray.org/ongoing/When/202x/2025/06/17/More-C2PA</id>
  1926. <published>2025-06-17T12:00:00-07:00</published>
  1927. <updated>2025-06-19T09:20:16-07:00</updated>
  1928. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Identity' />
  1929. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1930. <category scheme='https://www.tbray.org/ongoing/What/' term='Identity' />
  1931. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Things are happening in the C2PA world; here are a couple of useful steps forward, plus cheers and boos for Adobe.     Plus a live working C2PA demo you can try out</div></summary>
  1932. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1933.    <p>Things are happening in the C2PA world; here are a couple of useful steps forward, plus cheers and boos for Adobe.
  1934.    Plus a live working C2PA demo you can try out.</p>
  1935.    <p>Refresher: The
  1936.    <a href="https://c2pa.org/">C2PA</a> technology is driven by the
  1937.    <a href="https://contentauthenticity.org/">Content Authenticity Initiative</a> and usually marketed as “Content Credentials”.
  1938.    I’ve written before about it, an
  1939.    <a href="/ongoing/When/202x/2023/10/28/C2PA-Workflows">introduction in 2023</a> and a
  1940.    <a href="/ongoing/When/202x/2024/10/29/Lane-Provenance">progress report</a> last October.</p>
  1941.    <p>Let’s start with a picture.</p>
  1942.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/17/TXT55648.png" alt="A dark picture full of vague swirls and jiggly lights" />
  1943.    <div class='caption'><p>I was standing with the camera by the ocean at dusk and accidentally left it in the “B” long-exposure
  1944.    setting, so this isn’t really a picture <em>of</em> anything but I thought it was kinda pretty.</p></div>
  1945.    <h2 id='p-1'>Validating Content Credentials</h2>
  1946.    <p>As I write this, there are now at least two C2PA-validator Chrome extensions: the
  1947.    <a href="https://chromewebstore.google.com/detail/contentlens-c2pa-validato/gdejpnjeepoffhkbcgnjdbkgpohdhmln?hl=en">ContentLens
  1948.    C2PA Validator</a> from
  1949.    <a href="https://www.contentlens.ai/">ContentLens</a> and
  1950.    <a href="https://chromewebstore.google.com/detail/c2pa-content-credentials/mjkaocdlpjmphfkjndocehcdhbigaafp?hl=en">C2PA Content
  1951.    Credentials</a> from
  1952.    <a href="https://www.digimarc.com/">Digimarc</a>.</p>
  1953.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/17/cc-readout.png" alt="C2PA verifier display" class="inline" />
  1954.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/17/cc2-readout.png" alt="C2PA verifier display" class="inline" />
  1955.    <p>If you install either of them, and then you click on that picture just above in Chrome to get the larger version, then you
  1956.    right-click on the larger picture, the menu will offer Content-Credentials validation.</p>
  1957.    <p>Doing this will produce a little
  1958.    “CR” logo at the top right corner, meaning that the C2PA data has been
  1959.    verified as being present and signed by a trusted certificate issuer, in this case Adobe.</p>
  1960.    <p>Then there’s a popup; the two extensions’ are on the right. They’re different, in interesting ways. Let’s walk through the
  1961.    second one.</p>
  1962.    <p>The little thumbnail at the top of the popup is what the image looked like when the C2PA was added. Not provided by the other
  1963.    verifier.</p>
  1964.    <p>The paragraph beginning “Displaying credentials…” says that the C2PA manifest was embedded in the JPG as opposed to stored
  1965.    out on the
  1966.    cloud; The cloud works fine, and is perhaps a good idea because the C2PA manifest can be quite large. I’m not clear on what the
  1967.    “watermark” is about.</p>
  1968.    <p>“Issued by Adobe” means that the Chrome extension verified the embedded C2PA against Adobe’s public key and can be
  1969.    confident that yes, this was really signed by them.</p>
  1970.    <p>“<b>Produced by</b> Timothy Bray” is interesting. How can it know? Well, it turns out that it used LinkedIn’s API to verify
  1971.    that I am
  1972.    <a href="https://www.linkedin.com/in/timbraysoftwareguy/">timbraysoftwareguy</a> over on LinkedIn. But it goes further; LinkedIn
  1973.    has an integration with
  1974.    <a href="https://www.clearme.com">Clear</a>, the airport-oriented identity provider. To get a Clear account you have to upload
  1975.    government-issued ID, it’s not trivial.</p>
  1976.    <p>So this short sentence expands to (take a deep breath) “The validator extension verified that Adobe said that
  1977.    LinkedIn said that Clear said that the government ID of the person who posted this says that he’s named Timothy Bray.”</p>
  1978.    <p>Note that the first extension’s popup also tells you that Adobe has verified what my LinkedIn and Instagram accounts
  1979.    are. This seems super-useful and I wonder why the other omits it.</p>
  1980.    <p>“<b>App or device used</b>…” is simple enough, but I’m not actually sure how it works; I guess Adobe has embedded a keypair
  1981.    in my Lightroom installation? If I’d taken the picture with a C2PA-equipped camera this is where that history would be
  1982.    displayed.</p>
  1983.    <p>“<b>AI tool used</b> None”. Interesting and useful, since Adobe provides plenty of genAI-powered tools. Of course, this
  1984.    relies on Lightroom telling the truth, but still.</p>
  1985.    <p>The “View More” button doesn’t currently work; it takes you to the interactive
  1986.    <a href="https://contentcredentials.org/verify/">contentcredentials.org/verify</a> page,
  1987.    which seems to fail in retrieving the JPG. If you download the picture then upload it into the verify page (go ahead, it’s
  1988.    free)
  1989.    that seems to work fine. In addition to the info on the popup, the verify page will tell you (nontechically i.e. vaguely) what I
  1990.    did to the picture with Lightroom.</p>
  1991.    <h2 id='p-3'>What’s good about this?</h2>
  1992.    <p>Well, it’s here and it works! There’s all this hype about how cool it will be when the C2PA includes info about what model
  1993.    of camera and lens it used and what the shutter speed was and so on, but eh, who cares really? What matters to me (and
  1994.    should matter to the world) is <em>provenance</em>: Who posted this thing?</p>
  1995.    <p>As I write this, supporters of Israel and Iran are
  1996.    <a href="https://www.404media.co/the-ai-slop-fight-between-iran-and-israel/?ref=daily-stories-newsletter">having an AI Slop
  1997.    Fight</a> with fake war photos and videos.
  1998.    In a C2PA-rich world, you could check; If some clip doesn’t have Content Credentials you should
  1999.    probably be suspicious, and if it does, it matters whether it was uploaded by someone at
  2000.    <a href="https://www.idf.il/en/">IDF.il</a> versus
  2001.    <a href="https://www.bbc.com">BBC.co.uk</a>.</p>
  2002.    <h2 id='p-2'>What’s wrong with this?</h2>
  2003.    <p>Look, I hate to nitpick. I’m overwhelmingly positive on this news, it’s an existence proof that C2PA can be made to work in
  2004.    the wild.
  2005.    My impression is that most of the money and muscle comes from Adobe; good on ’em.
  2006.    But there are things that would make it more useful, and usable by more Web sites. These are not listed in
  2007.    any particular order.</p>
  2008.    <h2 id='p-7'>Identity!</h2>
  2009.    <p>Adobe, it’s nice that you let me establish my identity with LinkedIn, Instagram, and Clear. But what I’d
  2010.    <em>really</em> like is if you could also verify and sign my Fediverse and Bluesky handles. And, Fediverse and ATProto
  2011.    developers, would you please, first of all, stop stripping C2PA manifests from uploaded photo EXIF, and secondly, add your own
  2012.    link to the C2PA chain saying something like “Originally posted by @timbray@cosocial.ca.”</p>
  2013.    <p>Because having verifiable media provenance in the world of social media would be a strong tool against disinformation
  2014.    and slop.</p>
  2015.    <p>Oh, and another note to Adobe: When I export a photo, the embed-manifest also offers me the opportunity, under the heading
  2016.    “Web3”, to allow the image “be used for NFT creative attribution on supported marketplaces” where the supported marketplaces are
  2017.    Phantom and MetaMask. Seriously, folks, in 2025? Please get this scammy cryptoslime out of my face.</p>
  2018.    <h2 id='p-4'>Browsers please…</h2>
  2019.    <p>This was done with Chrome extensions. There are people working on extensions for Firefox and
  2020.    Safari, but they’re not here yet. Annoyingly, the extensions also don’t seem to work in mobile Chrome, which is where most
  2021.    people look at most media.</p>
  2022.    <p>I would love it if this were done directly and automatically by the browser.
  2023.    The major browsers aren’t perfect, but their creators are known to take security seriously, and I’d be much happier trusting
  2024.    one of them, rather than an extension from a company I’d never previously heard of.</p>
  2025.    <h2 id='p-8'>… or maybe JavaScript?</h2>
  2026.    <p>The next-best solution would be a nice JS package that just Does The Right
  2027.    Thing. It should work like the way I do fonts: If you look in the source for the page you are now reading, the splodge of JS at
  2028.    the top includes a couple of lines
  2029.    that mention “typekit.com”. Typekit (since acquired by Adobe) offers access to a huge selection of excellent fonts.
  2030.    Those JS invocations result in the text you are now reading being displayed in
  2031.    <a href="/ongoing/When/201x/2011/07/17/Tisa">FF Tisa Web Pro</a>.</p>
  2032.    <p>Which<span class='dashes'> —</span> this is important<span class='dashes'> —</span> is not free. And to be clear, I am
  2033.    willing to pay to get Content Credentials for the pictures on this blog. It feels exactly like paying a small fee for access to
  2034.    a professionally-managed font library.
  2035.    Operating a Content-Credentials service wouldn’t be free, it’d require running a
  2036.    server and wrangling certs. At scale, though, it should be pretty cheap.</p>
  2037.    <p>So here’s an offer: If someone launches a service that allows me to straightforwardly include the
  2038.    fact that this picture was sourced from tbray.org in my Content Credentials, my wallet is (modestly) open.</p>
  2039.    <p>By the way, the core JavaScript code is already under construction; here’s
  2040.    <a href="https://github.com/microsoft/c2pa-extension-validator">Microsoft</a> and the
  2041.    <a href="https://opensource.contentauthenticity.org/docs/introduction">Content Authority Initiative</a> itself.
  2042.    There’s also a Rust crate for server-side use, and a “c2patool” command-line utility based on it..</p>
  2043.    <h2 id='p-6'>Open-Source issues</h2>
  2044.    <p>You’ll notice that the right-click-for-Content-Credentials doesn’t work on the smaller version of the picture embedded in the
  2045.    text you are now reading; just the larger one.  This is because the decades-old Perl-based <span class='o'>ongoing</span>
  2046.    publishing software runs the main-page pictures through
  2047.    <a href="https://imagemagick.org/index.php">ImageMagick</a>, which doesn’t do C2PA. I should find a way to route around this.</p>
  2048.    <p>In fact, it wouldn’t be rocket science for ImageMagick (or open-source packages generally) to write C2PA manifests and insert
  2049.    them in the media files they create.  But how should they sign them? As noted, that requires a server that provides cert-based
  2050.    signatures, something that nobody would expect from even well-maintained open-source packages.</p>
  2051.    <p>I dunno, maybe someone should provide a managed-ImageMagick service that (for a small fee) offers signed-C2PA-manifest
  2052.    embedding?</p>
  2053.    <h2 id='p-9'>What’s next?</h2>
  2054.    <p>The work that needs to be done is nontrivial but, frankly, not that taxing. And the rewards would be high.
  2055.    Because it feels like a no-brainer that knowing who posted something is a big deal. Also the inverse: Knowing that you
  2056.    <em>don’t</em> know who posted it.</p>
  2057.    <p>Where is it an especially big deal? On social media, obviously. It’s really time for those guys to start climbing on board.</p>
  2058. </div></content></entry>
  2059.  
  2060. <entry>
  2061. <title>AI Angst</title>
  2062. <link href='https://www.tbray.org/ongoing/When/202x/2025/06/06/My-AI-Angst' />
  2063. <link rel='replies'        thr:count='14'        type='application/xhtml+xml'        href='/ongoing/When/202x/2025/06/06/My-AI-Angst#comments' />
  2064. <id>https://www.tbray.org/ongoing/When/202x/2025/06/06/My-AI-Angst</id>
  2065. <published>2025-06-06T12:00:00-07:00</published>
  2066. <updated>2025-06-08T15:39:49-07:00</updated>
  2067. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/AI' />
  2068. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  2069. <category scheme='https://www.tbray.org/ongoing/What/' term='AI' />
  2070. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>My input stream is full of it: Fear and loathing and cheerleading and prognosticating on what generative AI means and whether     it’s Good or Bad and what we should be doing. All the channels: Blogs and peer-reviewed papers and social-media posts and     business-news stories. So there’s lots of AI angst out there, but this is mine.     I think the following is a bit unique because it focuses on cost, working backward from there. As for the     genAI tech itself, I guess I’m a moderate; there is a there there, it’s not all slop. But first…</div></summary>
  2071. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  2072.    <p>My input stream is full of it: Fear and loathing and cheerleading and prognosticating on what generative AI means and whether
  2073.    it’s Good or Bad and what we should be doing. All the channels: Blogs and peer-reviewed papers and social-media posts and
  2074.    business-news stories. So there’s lots of AI angst out there, but this is mine.
  2075.    I think the following is a bit unique because it focuses on cost, working backward from there. As for the
  2076.    genAI tech itself, I guess I’m a moderate; there is a there there, it’s not all slop. But first…</p>
  2077.    <h2 id='p-5'>The rent is too damn high</h2>
  2078.    <p>I promise I’ll talk about genAI applications but let’s start with money. <em>Lots</em> of money, big numbers! For example,
  2079.    venture-cap startup money pouring into AI, which as of now apparently adds up to
  2080.    <a href="https://finance.yahoo.com/news/how-nvidia-played-a-central-role-in-the-306-billion-ai-startup-boom-195741749.html">$306
  2081.    billion</a>. And that’s just startups; Among the giants, Google alone
  2082.    <a href="https://www.ciodive.com/news/google-cloud-generative-ai-data-center-capacity-buildouts/739357/">apparently plans
  2083.    $75B</a> in capital expenditure on AI
  2084.    infrastructure, and they represent maybe a quarter at most of cloud capex. You think those are big numbers? McKinsey offers
  2085.    <a href="https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-cost-of-compute-a-7-trillion-dollar-race-to-scale-data-centers">The cost of compute: A $7 trillion race to scale data centers</a>.</p>
  2086.    <p>Obviously, lots of people are
  2087.    wondering when and where the revenue will be to pay for it all. There’s one thing we know for sure:
  2088.    The pro-genAI voices are fueled by hundreds of billions of dollars worth of fear and desire; fear that it’ll
  2089.    never pay off and desire for a piece of the money. Can you begin to imagine the pressure for revenue that investors and
  2090.    executives and middle managers are under?</p>
  2091.    <p><a href="https://cosocial.ca/@timbray/114572118905328515">Here’s an example</a> of the kind of debate that ensues.</p>
  2092.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/06/Anil-MCP.png" alt="Anil Dash on Mastodon, on MCP vs the Fediverse" />
  2093.    <div class='caption'><p>“MCP” is
  2094.    <a href="https://en.wikipedia.org/wiki/Model_Context_Protocol">Model Context Protocol</a>, used for communicating between LLM
  2095.    software and other systems and services.<br/>I have no opinion as to its quality or utility.</p></div>
  2096.    <p>I suggest that when you’re getting a pitch for genAI technology, you should have that greed and
  2097.    fear in the back of your mind. Or maybe at the front.</p>
  2098.    <h2 id='p-7'>And that’s just the money</h2>
  2099.    <p>For some reason, I don’t hear much any more about the environmental cost of genAI, the gigatons of carbon pouring out of the
  2100.    system, imperilling my children’s future. Let’s please not ignore that; let’s read things like
  2101.    <a href="https://www.eesi.org/articles/view/data-center-energy-needs-are-upending-power-grids-and-threatening-the-climate">Data
  2102.    Center Energy Needs Could Upend Power Grids and Threaten the Climate</a> and let’s make sure every freaking conversation about
  2103.    genAI acknowledges this grievous cost.</p>
  2104.    <p>Now let’s look at a few sectors where genAI is said to be a big deal: Coding, teaching, and professional
  2105.    communication. To keep things balanced, I’ll start in a space where I have kind things to say.</p>
  2106.    <h2 id='p-2'>Coding</h2>
  2107.    <p>Wow, is my tribe ever melting down. The pro- and anti-genAI factions are hurling polemical thunderbolts at each
  2108.    other, and I mean extra hot and pointy ones. For example, here are 5600 words entitled
  2109.    <a href="https://blog.glyph.im/2025/06/i-think-im-done-thinking-about-genai-for-now.html">I Think I’m Done Thinking About genAI
  2110.    For Now</a>. Well-written words, too.</p>
  2111.    <p>But, while I have a lot of sympathy for the contras and am sickened by some of the promoters, at the moment
  2112.    I’m mostly in tune with Thomas Ptacek’s
  2113.    <a href="https://fly.io/blog/youre-all-nuts/">My AI Skeptic Friends Are All Nuts</a>. It’s long and (fortunately) well-written
  2114.    and I (mostly) find it hard to disagree with.</p>
  2115.    <p>it’s as simple as this: I keep hearing talented programmers
  2116.    whose integrity I trust tell me “Yeah, LLMs are helping me get shit done.” The probability that they’re all lying or being
  2117.    fooled seems very low.</p>
  2118.    <p>Just to be clear, I note an absence of concern for cost and carbon in these conversations. Which is unacceptable. But let’s
  2119.    move on.</p>
  2120.    <p>It’s worth noting that I learned two useful things from Ptacek’s essay that I hadn’t really understood. First, the “agentic”
  2121.    architecture of programming tools: You ask the agent to create code and it asks the LLM, which will sometimes
  2122.    hallucinate; the agent will observe that it doesn’t compile or makes all the unit tests fail, discards it, and re-prompts. If
  2123.    it takes the agent module 25 prompts to generate code that while imperfect is at least correct, who cares?</p>
  2124.    <p>Second lesson, and to be fair this is just anecdata: It feels like the Go programming language is especially well-suited to
  2125.    LLM-driven automation. It’s small, has a large standard library, and a culture that has strong shared idioms for doing almost
  2126.    anything. Anyhow, we’ll find out if this early impression stands up to longer and wider industry experience.</p>
  2127.    <p>Turning our attention back to cost, let’s assume that eventually all or most developers become somewhat LLM-assisted. Are
  2128.    there enough of them, and will they pay enough, to cover all that investment?  Especially given that models that are both
  2129.    open-source and excellent are certain to proliferate? Seems dubious.</p>
  2130.    <p>Suppose that, as Ptacek suggests, LLMs/agents allow us to automate the tedious low-intellectual-effort parts of our
  2131.    job. Should we be concerned about how junior developers learn to get past that “easy stuff” and on the way to senior skills?
  2132.    That seems a very good question, so…</p>
  2133.    <h2 id='p-10'>Learning</h2>
  2134.    <p>Quite likely you’ve already seen Jason Koebler’s
  2135.    <a href="https://www.404media.co/teachers-are-not-ok-ai-chatgpt/?ref=daily-stories-newsletter">Teachers Are Not OK</a>, a
  2136.    frankly horrifying survey of genAI’s impact on secondary and tertiary education. It is a tale of unrelieved grief and pain
  2137.    and wreckage. Since genAI isn’t going to go away and students aren’t going to stop being lazy,
  2138.    it seems like we’re going to re-invent the way people teach and learn.</p>
  2139.    <p>The stories of students furiously deploying genAI to avoid the effort of actually, you know,
  2140.    learning, are sad. Even sadder  are those of genAI-crazed administrators leaning on faculty to become more efficient and
  2141.    “businesslike” by using it.</p>
  2142.    <p>I really don’t think there’s a coherent pro-genAI case to be made in the education context.</p>
  2143.    <h2 id='p-11'>Professional communication</h2>
  2144.    <p>If you want to use LLMs to automate communication with your family or friends or lovers, there’s nothing I can say that will
  2145.    help you. So let’s restrict this to conversation and reporting around work and private projects and voluntarism and so on.</p>
  2146.    <p>I’m
  2147.    pretty sure this is where the people who think they’re going to make big money with AI think it’s going to come from.
  2148.    If you’re interested in that thinking,
  2149.    <a href="https://docs.google.com/presentation/d/1Der8WWGeVxdOWx37bMV_nj9N1tUAVcvSSRa6qxKx75g/edit?slide=id.p1#slide=id.p1">here’s
  2150.    a sample</a>; a slide deck by a Keith Riegert for the book-publishing business which, granted, is a bit stagnant and a whole lot
  2151.    overconcentrated these days. I suspect scrolling through it will produce a strong emotional reaction for quite a few readers here.
  2152.    It’s also useful in that it talks specifically about costs.</p>
  2153.    <p>That is for corporate-branded output. What about personal or internal professional communication; by which I mean emails and
  2154.    sales reports and committee drafts and project pitches and so on? I’m pretty negative about this. If your email or pitch
  2155.    doc or whatever needs to be summarized, or if it has the colorless affectless error-prone polish of 2025’s LLMs, I would
  2156.    probably discard it unread.
  2157.    I already found the switch to turn off Gmail’s attempts to summarize my emails.</p>
  2158.    <p>What’s the genAI world’s equivalent of “Tl;dr”? I’m thinking “TA;dr” (A for AI)
  2159.    or “Tg;dr” (g for genAI) or just “LLM:dr”.</p>
  2160.    <p>And this vision of everyone using genAI to amplify their output and everyone else using it to summarize and filter
  2161.    their input feels simply perverse.</p>
  2162.    <p>Here’s what I think is
  2163.    <a href="https://infosec.exchange/@codinghorror/114606355212363074">an important finding</a>, ably summarized by Jeff Atwood:</p>
  2164.    <img src="https://www.tbray.org/ongoing/When/202x/2025/06/06/Dare-Jeff.png" alt="Dare Obasanjo and Jeff Atwood on how to survive AI" />
  2165.    <p>Seriously, since LLMs by design emit streams that are optimized for plausibility and for harmony with the model’s
  2166.    training base, in an AI-centric world there’s a powerful incentive to say things that are implausible, that are out of tune,
  2167.    that are, bluntly, weird. So there’s one upside.</p>
  2168.    <p>And let’s go back to cost. Are the prices in Riegert’s slide deck going to pay for trillions in capex?
  2169.    Another example: My family has a Google workplace account, and the price just went up from $6/user/month to
  2170.    $7. The announcement from Google emphasized that this was related to the added value provided by Gemini. Is $1/user/month gonna
  2171.    make this tech make business sense?</p>
  2172.    <h2 id='p-13'>What I can and can’t buy</h2>
  2173.    <p>I can sorta buy the premise that there are genAI productivity boosts to be had in the code space and maybe some other
  2174.    specialized domains.  I can’t buy for a second that genAI is anything but toxic for anything education-related.  On the
  2175.    business-communications side, it’s damn well gonna be tried because billions of dollars and many management careers depend on
  2176.    it paying off. We’ll see but I’m skeptical.</p>
  2177.    <p>On the money side? I don’t see how the math and the capex work. And all the time, I think about the carbon that’s poisoning
  2178.    the planet my children have to live on.</p>
  2179.    <p>I think that the best we can hope for is the eventual financial meltdown leaving a few useful islands of things that
  2180.    are actually useful at prices that make sense.</p>
  2181.    <p>And in a decade or so, I can see business-section stories about all the big data center shells that were never filled in,
  2182.    standing there empty, looking for another use. It’s gonna be tough, what can you do with buildings that have no windows?</p>
  2183. </div></content></entry>
  2184.  
  2185. </feed>
  2186.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid Atom 1.0" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//www.tbray.org/ongoing/ongoing.atom

Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda