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>2024-04-25T11:55:06-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, Java, and ImageMagick.  Industrial-strength technology, baby.</generator>
  18.  
  19. <entry>
  20. <title>Mobile Typing Pain</title>
  21. <link href='https://www.tbray.org/ongoing/When/202x/2024/04/24/Mobile-Text-Entry-Sucks' />
  22. <link rel='replies'        thr:count='2'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/04/24/Mobile-Text-Entry-Sucks#comments' />
  23. <id>https://www.tbray.org/ongoing/When/202x/2024/04/24/Mobile-Text-Entry-Sucks</id>
  24. <published>2024-04-24T12:00:00-07:00</published>
  25. <updated>2024-04-25T09:21:28-07:00</updated>
  26. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Text' />
  27. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  28. <category scheme='https://www.tbray.org/ongoing/What/' term='Text' />
  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'>I ran a Fediverse poll asking how people go about entering text on mobile devices.     The results shocked me: Half the population just taps away. Do you? Read on for details and speculation</div></summary>
  33. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  34.    <p>I ran a Fediverse poll asking how people go about entering text on mobile devices.
  35.    The results shocked me: Half the population just taps away. Do you? Read on for details and speculation.</p>
  36.    <p>This <span class='o'>ongoing</span> fragment embeds links to previous fragments, because I’ve been
  37.    worrying and writing about this problem for a long time. Which in itself is interesting, more evidence that the problem is hard.</p>
  38.    <img src="https://www.tbray.org/ongoing/When/202x/2024/04/24/mobile-text-entry-poll.png" alt="Mastodon poll on mobile text entry options" />
  39.    <div class='caption'><p>The poll post and (long) chain<br/>of responses are
  40.    <a href="https://phanpy.social/#/cosocial.ca/s/112318071899107953">here on Mastodon</a>.</p></div>
  41.    <h2 id='p-1'>People care</h2>
  42.    <p>First, 3.5K poll responses is more than I usually see on the Fediverse; evidence that plenty of people have feelings about
  43.    this.
  44.    To reinforce that impression, scroll down through the responses (there are dozens). Many say,
  45.    essentially, “Entering text on a mobile device is too hard, so I don’t.”</p>
  46.    <p>I’m one of those; I regularly start entering a message into a phone, stop, get up, and walk across the room to a
  47.    real keyboard.</p>
  48.    <h2 id='p-2'>Tap tap wow</h2>
  49.    <p>I widened my eyes when I saw that half the respondents testify to tapping along letter by letter. I could never. But then I have big
  50.    fat farmer’s fingers with soft ends, and am not terribly dextrous.</p>
  51.    <p>But, probably, I shouldn’t have been surprised; 21 years
  52.    ago in this blog I
  53.    <a href="/ongoing/When/200x/2003/04/06/Unicode">remarked</a> that “it's pretty impressive to watch a Japanese person pounding
  54.    text into their PDA at high speed using just their thumbs.” And today I watch teenage digits dance on devices like
  55.    maddened maenads; they seem not to find it tedious.</p>
  56.    <h2 id='p-3'>Swiping etc</h2>
  57.    <p>A quarter of poll respondents reported swiping words into their phones.</p>
  58.    <p>I mentioned above that people have been working on this for a long time. Check out
  59.    <a href="/ongoing/When/201x/2011/03/03/Mobile-Input">this progress report</a> from <span class='o'>ongoing</span> in 2011. It’s
  60.    worth noting that Android’s input method being replaceable was important in driving this innovation.</p>
  61.    <p>My own proposal, the
  62.    <a href="/ongoing/When/201x/2011/03/03/Mobile-Input#p-3">Digitator</a>, has failed to break through.</p>
  63.    <p>That piece concludes “Anyhow, I’m pretty sure that something will come along.” But on the evidence it hasn’t, really.</p>
  64.    <h2 id='p-4'>The AI angle: Auto-predict and voice</h2>
  65.    <p>The least popular poll options were tap-plus-autopredict and voice. I guess I’m weird, because those are what I mostly use.
  66.    I suspect many others should too but don’t, probably because they tried those things a while ago and haven’t
  67.    revisited them recently.</p>
  68.    <p>In my experience (which, granted, is almost all on Google Pixel devices) the autopredict and voice options have gotten
  69.    stronger with almost every release. Not just a little bit stronger, either.
  70.    Perhaps it’s just because I’m the white male Anglophone “canonical
  71.    human” that designers build for, but I get dramatically better results than I used to.</p>
  72.    <p>Now obviously, most reasonable people will only talk to their phone when they’re in a private place, which limits the use of
  73.    that option. But if you can find privacy, the voice option is getting remarkably good.</p>
  74.    <p>Which is to say, I can enter message or email text in at a pace that is sometimes adequate. Do I <em>enjoy</em>
  75.    doing this? No, I hate it, as I noted above, and will make a real effort to switch to a keyboard.</p>
  76.    <p>In particular if what I want to enter is important, might matter.</p>
  77.    <p>Because anything that matters deserves editing, and it’s rare indeed that I hit “Send” on a first draft. And while brute-force
  78.    text entry is edging into adequacy, <em>editing</em> remains a pool of pain.</p>
  79.    <h2 id='p-5'>Subtext</h2>
  80.    <p>Two and a half decades into this millennium, the most popular communication products are optimized for consumption
  81.    and barely adequate for creation. If I were paranoid and cynical, I might suspect that this is no accident. Oh wait, I am.
  82.    But in fact I think it’s just a hard problem.</p>
  83. </div></content></entry>
  84.  
  85. <entry>
  86. <title>Meta.ai Oh My!</title>
  87. <link href='https://www.tbray.org/ongoing/When/202x/2024/04/18/Meta-AI-oh-my' />
  88. <link rel='replies'        thr:count='6'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/04/18/Meta-AI-oh-my#comments' />
  89. <id>https://www.tbray.org/ongoing/When/202x/2024/04/18/Meta-AI-oh-my</id>
  90. <published>2024-04-18T12:00:00-07:00</published>
  91. <updated>2024-04-19T09:15:11-07:00</updated>
  92. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/ML-AI' />
  93. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  94. <category scheme='https://www.tbray.org/ongoing/What/' term='ML-AI' />
  95. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>“Meet Your New Assistant” says     <a href='https://about.fb.com/news/2024/04/meta-ai-assistant-built-with-llama-3/'>the announcement</a>, going on     with “Built With Llama 3”.     And oh my goodness has it ever got a lot of coverage. So I thought I might as well try it</div></summary>
  96. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  97.    <p>“Meet Your New Assistant” says
  98.    <a href="https://about.fb.com/news/2024/04/meta-ai-assistant-built-with-llama-3/">the announcement</a>, going on
  99.    with “Built With Llama 3”.
  100.    And oh my goodness has it ever got a lot of coverage. So I thought I might as well try it.</p>
  101.    <p>My first cut was a little unfair; I asked it about a subject on which I am unchallenged as the world’s leading expert: Tim
  102.    Bray. (That’s probably overstating it: My wife is clearly in the running.)</p>
  103.    <p>So I asked
  104.    <a href="https://meta.ai">meta.ai</a> “What does Tim Bray think of Google?” Twice; once on my phone while first exploring the idea,
  105.    and again later on my computer. Before I go on, I should remark that both user interfaces are first-rate: Friction-free and
  106.    ahead of the play-with-AI crowd. Anyhow, here are both answers; it may be relevant that I was logged into my long-lived
  107.    Facebook account:</p>
  108.    <img src="https://www.tbray.org/ongoing/When/202x/2024/04/18/meta-ai-take-1.png" alt="meta.ai on Tim Bray and Google, take 1" />
  109.    <img src="https://www.tbray.org/ongoing/When/202x/2024/04/18/meta-ai-take-2.png" alt="meta.ai on Tim Bray and Google, take 2" />
  110.    <p>The problem isn’t that these answers are really, really wrong (which they are). The problem is that they are terrifyingly
  111.    plausible, and presented in a tone of serene confidence. For clarity:</p>
  112.    <ol>
  113.      <li><p>I am not a Computer Scientist. Words mean things.</p></li>
  114.      <li><p>I worked for Google between March of 2010 and March of 2014.</p></li>
  115.      <li><p>I was never a VP there nor did I ever have “Engineer” in my title.</p></li>
  116.      <li><p>I did not write a blog post entitled “Goodbye, Google”. My exit post,
  117.      <a href="/ongoing/When/201x/2014/02/19/Leaving-Google">Leaving Google</a>, did not discuss advertising nor Google’s activities
  118.      in China, nor in fact was it critical of anything about Google except for its choice of headquarters location.
  119.      In fact, my disillusionment with Google (to be honest, with Big Tech generally) was slow to set in and really didn’t
  120.      reach critical mass until these troubling Twenties.</p></li>
  121.      <li><p>The phrase “advertising-based business model”, presented in quotes, does not appear in this blog. Quotation marks have
  122.      meaning.</p></li>
  123.      <li><p>My views are not, nor have they been, “complex and multifaceted”. I am embarrassingly mainstream. I shared the
  124.      mainstream enchantment with the glamor of Big Tech until, sometime around 2020, I started sharing the mainstream
  125.      disgruntlement.</p></li>
  126.      <li><p>I can neither recall nor find instances of me criticizing Google’s decision-making process, nor praising its Open-Source
  127.      activities.</p></li>
  128.    </ol>
  129.    <p>What troubles me is that all of the actions and opinions attributed to meta.ai’s version of Tim Bray are things that
  130.    I might well have done or said. But I didn’t.</p>
  131.    <p>This is not a criticism of Meta; their claims about the size and sophistication of their
  132.    <a href="https://ai.meta.com/blog/meta-llama-3/">Llama3 model</a> seem believable and, as I said, the interface is nifty.</p>
  133.    <p>Is it fair for me to criticize this particular product offering based on a single example? Well, first impressions are
  134.    important. But for what it’s worth, I peppered it with a bunch of other general questions and the pattern repeats: Plausible
  135.    narratives containing egregious factual errors. </p>
  136.    <p>I guess there’s no new news here; we already knew that LLMs are good at generating plausible-sounding narratives which are
  137.    wrong. It comes back to what I discussed under
  138.    <a href="/ongoing/When/202x/2024/02/25/Money-AI-Bubble#p-5">the heading of “Meaning”</a>. Still waiting for progress.</p>
  139.    <p>The nice thing about science is that it routinely features “error bars” on its graphs, showing both the finding and the degree of
  140.    confidence in its accuracy.</p>
  141.    <p>AI/ML products in general don’t have them.</p>
  142.    <p>I don’t see how it’s sane or safe to rely on a technology that doesn’t have error bars.</p>
  143. </div></content></entry>
  144.  
  145. <entry>
  146. <title>Topfew Release 0.5</title>
  147. <link href='https://www.tbray.org/ongoing/When/202x/2024/04/12/Topfew-release' />
  148. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/04/12/Topfew-release#comments' />
  149. <id>https://www.tbray.org/ongoing/When/202x/2024/04/12/Topfew-release</id>
  150. <published>2024-04-12T12:00:00-07:00</published>
  151. <updated>2024-04-13T12:37:28-07:00</updated>
  152. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Concurrency' />
  153. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  154. <category scheme='https://www.tbray.org/ongoing/What/' term='Concurrency' />
  155. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Software' />
  156. <category scheme='https://www.tbray.org/ongoing/What/' term='Software' />
  157. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Back in 2021-22, I wrote a     <a href='https://www.google.com/search?as_q=topfew&amp;amp;as_sitesearch=tbray.org'>series of blog posts</a> about a program called     “topfew” (<b>tf</b> from your shell command-line). It finds the field values (or combinations of values) which appear most often in a     stream of records. I built it to explore large-scale data crunching in Go, and to investigate how performance compared to Rust.     There was plentiful input, both ideas and code, from     <a href='https://dirkjan.ochtman.nl'>Dirkjan Ochtman</a> and <a href='https://github.com/superfell'>Simon Fell</a>.     Anyhow, I thought I was finished with it but then I noticed I was using the <b>tf</b> command more days than not,     and I have pretty mainstream command-line needs. Plus I got a couple of random pings about whether it was still live. So I cleaned     it up a bit and on April 12th, did its first actual release, 0.5.0.     <a href='https://github.com/timbray/topfew/tree/main'>Here it is</a></div></summary>
  158. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  159.    <p>Back in 2021-22, I wrote a
  160.    <a href="https://www.google.com/search?as_q=topfew&amp;as_sitesearch=tbray.org">series of blog posts</a> about a program called
  161.    “topfew” (<b>tf</b> from your shell command-line). It finds the field values (or combinations of values) which appear most often in a
  162.    stream of records. I built it to explore large-scale data crunching in Go, and to investigate how performance compared to Rust.
  163.    There was plentiful input, both ideas and code, from
  164.    <a href="https://dirkjan.ochtman.nl">Dirkjan Ochtman</a> and <a href="https://github.com/superfell">Simon Fell</a>.
  165.    Anyhow, I thought I was finished with it but then I noticed I was using the <b>tf</b> command more days than not,
  166.    and I have pretty mainstream command-line needs. Plus I got a couple of random pings about whether it was still live. So I cleaned
  167.    it up a bit and on April 12th, did its first actual release, 0.5.0.
  168.    <a href="https://github.com/timbray/topfew/tree/main">Here it is</a>.</p>
  169.    <img src="https://www.tbray.org/ongoing/When/202x/2024/04/12/topfew.png" alt="GitHub sidebar for Topfew" class="inline" />
  170.    <p>Its test coverage is much improved compared to a couple weeks ago and, expectedly, there are fewer bugs. Also, better docs.</p>
  171.    <h2 id='p-1'>Plan</h2>
  172.    <p>I think it’s stable, and fast enough (see below). Unless someone finds gross breakage or painfully-obvious improvements, I’m
  173.    going to release 1.0 in a week or so. At some point, I’ll look into Homebrew recipes and suchlike, if I get the
  174.    feeling they might be used.</p>
  175.    <p>Obviously, please send issues or PRs if you see the opportunity.</p>
  176.    <h2 id='p-2'>Who needs this?</h2>
  177.    <p>It’s mostly for log files I think. Whenever I’m poking around in one of those I find myself asking questions like “which API
  178.    call was hit most often?” or “Which endpoint?” or “Which user agent?” or “Which subnet?” </p>
  179.    <p>The conventional hammer to drive this nail has always been something along the lines of:</p>
  180.    <div class="highlight"><pre><span></span>awk<span class="w"> </span><span class="s1">&#39;{print $7}&#39;</span><span class="w"> </span><span class="p">|</span><span class="w"> </span>sort<span class="w"> </span><span class="p">|</span><span class="w"> </span>uniq<span class="w"> </span>-c<span class="w"> </span><span class="p">|</span><span class="w"> </span>sort<span class="w"> </span>-nr<span class="w"> </span><span class="p">|</span><span class="w"> </span>head<span class="w"> </span></pre></div>
  181.    <p>Which has the advantage of Just Working on any Unix-descended computer. But can be slow when the input is big, and worse than
  182.    linear too.
  183.    Anyhow, <b>tf</b> is like that, only faster. In some cases, orders of magnitude faster. Plus, it has useful options
  184.    that take care of the <code>grep</code> and <code>sed</code> idioms that often appear upstream in the pipe.</p>
  185.    <p>Topfew’s got a decent
  186.    <a href="https://github.com/timbray/topfew/blob/main/README.md">README</a> so I’m not going invest any more
  187.    words here in explaining it.</p>
  188.    <p>But it’s worth pointing out that it’s a single self-contained binary compiled from standalone Go
  189.    source code with zero dependencies.</p>
  190.    <h2 id='p-3'>Performance</h2>
  191.    <p>This subject is a bit vexed. After I wrote the first version, Dirkjan implemented it in Rust and it was way faster,
  192.    which annoyed me because it ought to be I/O-bound. So I stole his best ideas and then Simon chipped in other good ones and we
  193.    optimized more, and eventually it was at least as fast as the Rust version. Which is to say, plenty fast, and probably faster than what
  194.    you’re using now.</p>
  195.    <p>But you only get the <em>big</em> payoff from all this work when you’re processing a <em>file</em>, as opposed to a stream;
  196.    then <b>tf</b> feels shockingly fast, because it divides the file up into segments and scans them in parallel. Works remarkably
  197.    well.</p>
  198.    <p>Unfortunately that doesn’t happen too often. Normally, you’re grepping for something or teeing off another stream or
  199.    whatever.
  200.    In which case, performance is totally limited by reading the stream; I’ve profiled the hell out of this and the actual <b>tf</b>
  201.    code doesn’t show up in any of the graphs, just the I/O-related buffer wrangling and garbage collection. Maybe I’m missing
  202.    something. But I’m pretty sure <b>tf</b> will keep up with any stream you can throw at it.</p>
  203.    <h2 id='p-5'>Tooling</h2>
  204.    <p>Over the years I’ve become an adequate user of GitHub CI. It’s good to watch that ecosystem become richer and slicker; the
  205.    things you need seem to be there and for an OSS hobbyist like me, are generally free.
  206.    Still, it bothers me that Everything Is On GitHub. I need to become aware of the alternatives.</p>
  207.    <p>I still live in JetBrains-land, in this case specifically
  208.    <a href="https://www.jetbrains.com/go/">Goland</a>, albeit unfashionably in Light mode. It scratches my itches.</p>
  209.    <p>Anyhow, everything is easier if you have no dependencies. And our whole profession needs to be more thoughtful
  210.    about its dependencies.</p>
  211.    <h2 id='p-4'>Dirty secret</h2>
  212.    <p>I’ve always wanted to ship a two-letter shell command that someone might use.
  213.    Now I have. And I do think <b>tf</b>
  214.    will earn a home in a few folks’ toolboxes.</p>
  215. </div></content></entry>
  216.  
  217. <entry>
  218. <title>OSQI</title>
  219. <link href='https://www.tbray.org/ongoing/When/202x/2024/04/01/OSQI' />
  220. <link rel='replies'        thr:count='11'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/04/01/OSQI#comments' />
  221. <id>https://www.tbray.org/ongoing/When/202x/2024/04/01/OSQI</id>
  222. <published>2024-04-01T12:00:00-07:00</published>
  223. <updated>2024-04-03T09:07:53-07:00</updated>
  224. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Software' />
  225. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  226. <category scheme='https://www.tbray.org/ongoing/What/' term='Software' />
  227. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I propose the formation of one or more “Open Source Quality Institutes”. An OSQI is a public-sector organization that     employs software engineers. Its mission would be to improve the quality, and especially safety, of popular     Open-Source software</div></summary>
  228. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  229.    <p>I propose the formation of one or more “Open Source Quality Institutes”. An OSQI is a public-sector organization that
  230.    employs software engineers. Its mission would be to improve the quality, and especially safety, of popular
  231.    Open-Source software.</p>
  232.    <h2 id='p-5'>Why?</h2>
  233.    <p>The
  234.    <a href="https://en.wikipedia.org/wiki/XZ_utils_backdoor">XZ-Utils backdoor</a> (let’s just say <b>#XZ</b>) launched the train
  235.    of thought that led me
  236.    to this idea.  If you read the story, it becomes obvious that the key vulnerability wasn’t technical, it was the fact that a
  237.    whole lot of Open-Source software is on the undermaintained-to-neglected axis, because there’s no business case for paying people
  238.    to take care of it. Which is a problem, because there is a <em>strong</em> business case for paying people to attack it.</p>
  239.    <p>There are other essential human activities that lack a business case, for example tertiary education,
  240.    potable water quality, and financial regulation. For these, we create non-capitalist constructs such as Universities and
  241.    Institutes and Agencies, because society needs these things done even if nobody can make money doing them.</p>
  242.    <p>I think we need to be paying more attention to the quality generally, and safety especially, of the Open-Source software
  243.    that has become the underlying platform for, more or less, our civilization. Thus OSQI.</p>
  244.    <h2 id='p-6'>They’re out to get us</h2>
  245.    <p>For me, the two big lessons from <b>#XZ</b> were first, the lack of resources supporting crucial Open-Source infrastructure,
  246.    but then and especially, the
  247.    demonstration that the attackers are numerous, skilled <em>and patient</em>. We already knew about numerous and skilled but this
  248.    episode, where
  249.    the attacker was already well-embedded in the project
  250.    <a href="https://www.mail-archive.com/xz-devel@tukaani.org/msg00562.html">by May 2022</a>, opened a few eyes, including
  251.    mine.</p>
  252.    <p>The advantage, to various flavors of malefactor, of subverting core pieces of Open-Source infrastructure, is
  253.    incalculable.  <b>#XZ</b> was the one we caught; how many have we missed?</p>
  254.    <h2 id='p-7'>What’s OSQI?</h2>
  255.    <p>It’s an organization created by a national government. Obviously, more nations than one could have an OSQI.</p>
  256.    <p>The vast majority of the staff would be relatively-senior
  257.    software
  258.    engineers, with a small percentage of paranoid nontechnical security people
  259.    (see
  260.    <a href="OSQI#p-21">below</a>). You could do a lot with as few as 250 people, and
  261.    the burdened cost would be trivial for a substantial government.</p>
  262.    <p>Since it is a matter of obvious fact that every company in the
  263.    world with revenue of a billion or more is existentially dependent on Open Source, it would be reasonable to impose a levy of,
  264.    say, 0.1% of revenue on all such companies, to help support this work. The money needn’t be a problem.</p>
  265.    <h2 id='p-8'>Structure</h2>
  266.    <p>The selection of software packages that would get OSQI attention would be left to the organization, although there would be
  267.    avenues for anyone to request coverage. The engineering organization could be relatively flat, most people giving individual
  268.    attention to individual projects, then also ad-hoc teams forming for tool-building or crisis-handling when something like
  269.    <b>#XZ</b> blows up.</p>
  270.    <h2 id='p-10'>Why would anyone work there?</h2>
  271.    <p>The pay would be OK; less than you’d make at Google or Facebook, but a decent civil-service salary. There would be no
  272.    suspicion that your employer is trying to enshittify anything; in fact, you’d start work in the morning confident that you’re
  273.    trying to improve the world. The default work mode would be remote, so you could live somewhere a not-quite-Google salary would
  274.    support a very comfortable way of life.  There would be decent vacations and benefits and
  275.    (<em>*gasp*</em>) a pension.</p>
  276.    <p>And there is a certain class of person who would find everyday joy in peeking and poking and polishing
  277.    Open-Source packages that are depended on by millions of programmers and (indirectly) billions of humans. A couple of decades
  278.    ago I would have been one.</p>
  279.    <p>I don’t think recruiting would be a problem.</p>
  280.    <p>So, what are OSQI’s goals and non-goals?</p>
  281.    <h2 id='p-11'>Goal: Safety</h2>
  282.    <p>This has to come first. If all OSQI accomplishes is the foiling of a few <b>#XZ</b>-flavor attacks, and life becoming harder
  283.    for people making them, that’s just fine.</p>
  284.    <h2 id='p-12'>Goal: Tool-building</h2>
  285.    <p>I think it’s now conventional wisdom that Open Source’s biggest attack surfaces are dependency networks and build
  286.    tools. These are big and complex problems, but let’s be bold and set a high bar:</p>
  287.    <blockquote><p>Open-Source software should be built deterministically, verifiably, and reproducibly, from signed source-code
  288.    snapshots. These snapshots should be free of generated artifacts; every item in
  289.    the snapshot should be human-written and human-readable.</p></blockquote>
  290.    <p>For example: As
  291.    <a href="https://mastodon.social/@kornel">Kornel</a> said,
  292.    <a href="https://mastodon.social/@kornel/112187783363254917">Seriously, in retrospect, #autotools itself is a massive
  293.    supply-chain security risk.</a> No kidding!  But then everyone says “What are you gonna do, it’s wired into everything.”</p>
  294.    <p>There are alternatives; I know of
  295.    <a href="https://cmake.org">CMake</a> and
  296.    <a href="https://mesonbuild.com">Meson</a>. Are they good enough? I don’t know. Obviously, GNU AutoHell can’t be swept out of
  297.    all of the fœtid crannies where it lurks and festers, but every project from which it is scrubbed will present less
  298.    danger to the world.
  299.    I believe OSQI would have the scope to make real progress on this front.</p>
  300.    <h2 id='p-13'>Non-goal: Features</h2>
  301.    <p>OSQI should never invest engineering resources in adding cool features to Open-Source packages (with the possible exception
  302.    of build-and-test tools).  The Open-Source community is bursting with new-features energy, most coming from people who either
  303.    want to scratch their own itch or are facing a real blockage at work. They are way better positioned to make those improvements
  304.    than anyone at OSQI.</p>
  305.    <h2 id='p-23'>Goal: Maintenance</h2>
  306.    <p>Way too many deep-infra packages grow increasingly unmaintained as people age and become busy and tired and sick and dead. As I
  307.    was writing this, a
  308.    <a href="https://github.com/libexpat/libexpat/blob/R_2_6_2/expat/Changes">plea for help</a> came across my radar from Sebastian
  309.    Pipping, the excellent but unsupported and unfunded maintainer of
  310.    <a href="https://github.com/libexpat/libexpat/tree/R_2_6_2">Expat</a>, the world’s most popular XML parser.</p>
  311.    <p>And yeah, he’s part of a trend, one that notably included the now-infamous
  312.    <a href="https://en.wikipedia.org/wiki/XZ_Utils">XZ-Utils</a> package.</p>
  313.    <p>And so I think one useful task for OSQI would be taking over (ideally partial) maintenance duties for a lot of Open-Source projects
  314.    that have a high ratio of adoption to support. In some cases it would have to take a lower-intensity form, let’s call it “life
  315.    support”, where OSQI deals with vulnerability reports but flatly refuses to address any requests for features no matter how
  316.    trivial, and rejects all PRs unless they come from someone who’s willing to take on part of the maintenance load.</p>
  317.    <p>One benefit of having paid professionals doing this is that they will blow off the kind of social-engineering harassment that
  318.    the <b>#XZ</b> attacker inflicted on the XZ-Utils maintainer (see
  319.    <a href="https://research.swtch.com/xz-timeline">Russ Cox’s excellent timeline</a>) and which is unfortunately too common in the
  320.    Open-Source world generally.</p>
  321.    <h2 id='p-14'>Goal: Benchmarking</h2>
  322.    <p>Efficiency is an aspect of quality, and I think it would be perfectly reasonable for OSQI to engage in
  323.    benchmarking and optimization. There’s a non-obvious reason for this: <b>#XZ</b> was unmasked when a Postgres specialist noticed
  324.    performance problems.</p>
  325.    <p>I think that in general, if you’re a bad person trying to backdoor an Open-Source package, it’s going to
  326.    be hard to do without introducing performance glitches. I’ve
  327.    <a href="/ongoing/When/202x/2021/05/15/Testing-in-2021#p-13">long advocated</a> that unit and/or integration tests should
  328.    include a benchmark or two, just to avert well-intentioned performance regressions; if they handicap bad guys too, that’s a
  329.    bonus.</p>
  330.    <h2 id='p-15'>Goal: Education and evangelism</h2>
  331.    <p>OSQI staff will develop a deep shared pool of expertise in making Open-Source software safer and better, and
  332.    specifically in detecting and repelling multiple attack flavors. They should share it! Blogs, conferences, whatever. It even
  333.    occurred to me that it might make sense to structure OSQI as an educational institution; standalone or as a grad college of
  334.    something existing.</p>
  335.    <p>But what I’m talking about isn’t refereed JACM papers, but what my Dad, a Professor of Agriculture, called “Extension”:
  336.    Bringing the results of research directly to practitioners.</p>
  337.    <h2 id='p-16'>Non-goal: Making standards</h2>
  338.    <p>The world has enough standards organizations. I could see individual OSQI employees pitching in, though, at the IETF or IEEE
  339.    or W3C or wherever, with work on Infosec standards.</p>
  340.    <p>Which brings me to…</p>
  341.    <h2 id='p-17'>Non-goal: Litigation</h2>
  342.    <p>Or really any other enforcement-related activity. OSQI exists to fix problems, build tools, and share lessons. This is going
  343.    to be easier if nobody (except attackers) sees them as a threat, and if staff don’t have to think about how their work and
  344.    findings will play out in court.</p>
  345.    <p>And a related non-goal…</p>
  346.    <h2 id='p-18'>Non-goal: Licensing</h2>
  347.    <p>The intersection between the class of people who’d make good OSQI engineers and those who care about Open-Source
  348.    licenses is, thankfully, very small. I think OSQI should accept the license landscape that exists and work hard to avoid
  349.    thinking about its theology.</p>
  350.    <h2 id='p-19'>Non-goal: Certification</h2>
  351.    <p>Once OSQI exists, the notion of “OSQI-approved” might arise. But it’d be a mistake;
  352.    OSQI should be an <em>engineering</em> organization; the cost (measured by required bureaucracy) to perform certification would
  353.    be brutal.</p>
  354.    <h2 id='p-20'>Goal: Transparency</h2>
  355.    <p>OSQI can’t afford to have any secrets, with the sole exception of freshly-discovered but still-undisclosed
  356.    vulnerabilities. And when those vulnerabilities are disclosed, the story of their discovery and characterization needs to be
  357.    shared entirely and completely.  This feels like a bare-minimum basis for building the level of trust that will be
  358.    required.</p>
  359.    <h2 id='p-21'>Necessary paranoia</h2>
  360.    <p>I discussed above why OSQI might be a nice place to work.  There will be a downside, though; you’ll lose a certain amount of
  361.    privacy. Because if OSQI succeeds, it will become a super-high-value target for our adversaries. In the natural course of
  362.    affairs, many employees would become committers on popular packages, increasing their attractiveness as targets for bribes or
  363.    blackmail.</p>
  364.    <p>I recall once, a very senior security leader at an Internet giant saying to me “We have thousands of engineers, and my job
  365.    requires me to believe that at least one of them also has another employer.”</p>
  366.    <p>So I think OSQI needs to employ a small number of paranoid traditional-security (not Infosec) experts to keep an eye on their
  367.    colleagues, audit their finances, and just be generally suspicious. These people would also
  368.    worry about OSQI’s physical and network security. Because attackers gonna attack.</p>
  369.    <h2 id='p-22'>Pronunciation</h2>
  370.    <p>Rhymes with “bosky”, of course. Also, people who work there are OSQIans. I’ve grabbed “osqi.org” and will cheerfully donate it
  371.    in the long-shot case that this idea gets traction.</p>
  372.    <h2 id='p-24'>Are you serious?</h2>
  373.    <p>Yeah. Except for, I no longer speak with the voice of a powerful employer.</p>
  374.    <p>Look: For
  375.    better or for worse, Open Source won. <i>[Narrator: Obviously, for better.]</i> That means it has become crucial civilizational
  376.    infrastucture, which governments should actively support and maintain, just like roads and dams and power grids.</p>
  377.    <p>It’s not so much that OSQI, or something  
  378.    like it, is a good idea; it’s that <em>not</em> trying to achieve these goals, in 2024, is dangerous and insane.</p>
  379. </div></content></entry>
  380.  
  381. <entry>
  382. <title>A057X</title>
  383. <link href='https://www.tbray.org/ongoing/When/202x/2024/03/30/A057' />
  384. <link rel='replies'        thr:count='5'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/03/30/A057#comments' />
  385. <id>https://www.tbray.org/ongoing/When/202x/2024/03/30/A057</id>
  386. <published>2024-03-30T12:00:00-07:00</published>
  387. <updated>2024-04-01T09:38:38-07:00</updated>
  388. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos/Cameras' />
  389. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  390. <category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
  391. <category scheme='https://www.tbray.org/ongoing/What/' term='Cameras' />
  392. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Yes, “A057X” is cryptic, but my new lens’s official monicker is “150-500mm F/5-6.7 Di III VC VXD” so let’s stick with that     part number. It’s from      <a href='https://www.tamron.com/global/consumer/'>Tamron</a> and this is the Fujifilm X-Mount variation.     Lens-geeking is my favorite part of photo-geeking and it’s great that more manufacturers are opening up to third-party     lens builders</div></summary>
  393. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  394.    <p>Yes, “A057X” is cryptic, but my new lens’s official monicker is “150-500mm F/5-6.7 Di III VC VXD” so let’s stick with that
  395.    part number. It’s from
  396.    <a href="https://www.tamron.com/global/consumer/">Tamron</a> and this is the Fujifilm X-Mount variation.
  397.    Lens-geeking is my favorite part of photo-geeking and it’s great that more manufacturers are opening up to third-party
  398.    lens builders.</p>
  399.    <p>Last May
  400.    <a href="/ongoing/When/202x/2023/05/27/Long-Lens-Trees">I wrote that</a> I wanted a big-ass super-telephoto and
  401.    now I have one. Let’s start with a little comparo. Here is (roughly) the same 2km-away landscape shot on the decades-old
  402.    <a href="/ongoing/When/200x/2009/06/21/Tokina-SL-400-f5.6">Tokina 400mm</a> I’d been using since 2009, and on the new
  403.    Tamron.</p>
  404.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1248.png" alt="Distant waterfront, via 400mm Tokina" />
  405.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1387.png" alt="Distant waterfront, via 150-500mm Tamron" />
  406.    <div class='caption'><p>If you care about this sort of thing you might want to enlarge these. A person is visible in the bottom
  407.    picture, and another if you’re using Lightroom on a 4K screen.</p></div>
  408.    <p>Now let’s be honest; the color and flavor of the earlier picture is nicer, because the sun was just right; that’s why
  409.    I strapped on the old glass. But the new-lens picture shows that yes, we do still make progress in
  410.    analog technologies, and given the same light, there’d be more you could do with with today’s lens.</p>
  411.    <p>Anyhow, here’s what it looks like.</p>
  412.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/PXL_20240331_191648128.png" alt="Tamron 150-500mm F/5-6.7 Di III VC VXD on Fujifilm XT-2" />
  413.    <p>That’s on a Fujifilm X-T2, one of the bulkier of Fuji’s X-cameras.  What’s not instantly
  414.    obvious is that the camera and lens are sitting on the lens’s tripod shoe.  That camera is now eight years old and needs to be
  415.    replaced, but I’m not fully won over by the latest X-cams and the lens was an easier trigger to pull.</p>
  416.    <p>The reviews all said “Considering what it does, it’s amazingly small and light!”  Maybe, but in fact it’s
  417.    a big freakin’ heavy hunk of metal and glass.  A tripod really helps.</p>
  418.    <h2 id='p-2'>For the birds</h2>
  419.    <p>Tripod? But everyone seems to think that this kind of lens is for shooting birds in flight.  So I took it to
  420.    <a href="/ongoing/What/The%20World/Cottage%20Life/">our cabin</a> this weekend to test that hypothesis.
  421.    Thus I learned that you really can’t shoot birds unless you’re hand-holding the camera. And even then, you can’t
  422.    unless you’ve been practicing. I managed to get one picture
  423.    of a bird in flight, but it was just a seagull and not a terribly handsome one either.</p>
  424.    <p>Then a couple of visitors settled at the top of a nearby Douglas Fir. Here’s one. Yes, the sky was that blue.</p>
  425.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1408.png" alt="Bald eagle at the top of a cone-scattered evergreen" />
  426.    <p>Isn’t it handsome?  If you look close, though, its tail is jammed against a branch. But then it bent over to peer out at
  427.    something.</p>
  428.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1405.png" alt="Bald eagle at the top of an evergreen, leaning forward" />
  429.    <p>Aren’t those feathers beautiful?  This was a big-ass tree and I wasn’t right next to it, either. Yay Tamron.</p>
  430.    <h2 id='p-3'>Little, big</h2>
  431.    <p>Turns out this thing can focus relatively close-in for an item of its ilk, so you can do, um what would one call it,
  432.    macro-at-a-distance?</p>
  433.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1358.png" alt="Close-up of a crocus flower among tangled botanical debris" />
  434.    <p>That’s a teeny little blossom. But when I’m looking out over the water, I always end up taking pictures of the mountains on the
  435.    other side.</p>
  436.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/30/DSCF1423.png" alt="Distant mountain" />
  437.    <p>That one is a damn long way away. The picture suffers from being reduced to fit into your browser. I wish I could give
  438.    everyone in the world Lightroom and a good 4K monitor.</p>
  439.    <h2 id='p-5'>Note that…</h2>
  440.    <p>None of the pictures via this lens could have been captured on any mobile-phone camera in the world.
  441.    You have to go pretty far these days to get into that territory.</p>
  442. </div></content></entry>
  443.  
  444. <entry>
  445. <title>Bye, Allyson</title>
  446. <link href='https://www.tbray.org/ongoing/When/202x/2024/03/16/Bye-Allyson' />
  447. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/03/16/Bye-Allyson#comments' />
  448. <id>https://www.tbray.org/ongoing/When/202x/2024/03/16/Bye-Allyson</id>
  449. <published>2024-03-16T12:00:00-07:00</published>
  450. <updated>2024-03-18T08:30:28-07:00</updated>
  451. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  452. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  453. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>She’s gone. She lived well. We’ll miss her</div></summary>
  454. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  455.    <p>She’s gone. She lived well. We’ll miss her.</p>
  456.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/16/DSCF4144.png" alt="Allyson McGrane" />
  457.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/16/IMG_20201114_212122_736.png" alt="Allyson McGrane" />
  458.    <p>We’ve known Ms McGrane since 2005, when she was a co-conspirator on the wonderful little local
  459.    <a href="https://en.wikipedia.org/wiki/Northern_Voice">Northern Voice</a> blogging conference. We worked on other stuff together
  460.    and hung out now and then and carpooled to the Prairies once and I can’t remember ever getting the slightest bit upset with
  461.    her.</p>
  462.    <p><a href="https://www.facebook.com/shanebee/posts/pfbid02DwAH6rzDEayHxKrVhVMBcCbLnKf4fZPybNrnrWcMH4czFTLRzT4GQX7JUfrARWb6l">Here</a>
  463.    is a good-bye note from her partner Shane. If you want to leave a note somewhere, leave it there.</p>
  464.    <p>Ally (rhymes with “valley”) was a fine dog-parent and a strong grant-writer and a first-rate teacher and a connoisseur of
  465.    fine cooking equipment and Canadian football.  If you’ve been to
  466.    much in the way of Vancouver theatre and dance events over the years, there’s a good chance that she produced the event or
  467.    secured its funding or educated the people who did those things.</p>
  468.    <p>I remember having coffee with her a couple years ago, she advising me on one of my projects, laughing together at the
  469.    Byzantine complexities of granting bureaucracies and the childlike money-obliviousness of arts leaders and the excellence of the
  470.    coffee on that morning. Easy to be with.</p>
  471.    <p>Mesothelioma is a bitch; 8% 5-year survival rate, and there wasn’t that much they could do for her by the time they got the
  472.    diagnosis right. We visited her last week and she was herself, cynical about her situation but it seemed more or less at
  473.    peace.</p>
  474.    <p>I won’t miss her as much as the dogs will, but there’s still a gap in my life.</p>
  475.    
  476. </div></content></entry>
  477.  
  478. <entry>
  479. <title>Play My Music</title>
  480. <link href='https://www.tbray.org/ongoing/When/202x/2024/03/10/Play-My-Music' />
  481. <link rel='replies'        thr:count='8'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/03/10/Play-My-Music#comments' />
  482. <id>https://www.tbray.org/ongoing/When/202x/2024/03/10/Play-My-Music</id>
  483. <published>2024-03-10T12:00:00-07:00</published>
  484. <updated>2024-03-10T14:44:58-07:00</updated>
  485. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Life Online/De-Google' />
  486. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  487. <category scheme='https://www.tbray.org/ongoing/What/' term='Life Online' />
  488. <category scheme='https://www.tbray.org/ongoing/What/' term='De-Google' />
  489. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>When I’m away from home, I still want to listen to the music we have at home (well, I can live without the     LPs). We had well over a thousand CDs so that’s a lot of music, 12,286 tracks ripped into Apple Lossless.     Except for a few MP3s from, well, never mind.     This instalment of the     <a href='/ongoing/What/The%20World/Life%20Online/De-Google/'>De-Google Project</a> is about ways to do that with less     Big-Tech involvement</div></summary>
  490. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  491.    <p>When I’m away from home, I still want to listen to the music we have at home (well, I can live without the
  492.    LPs). We had well over a thousand CDs so that’s a lot of music, 12,286 tracks ripped into Apple Lossless.
  493.    Except for a few MP3s from, well, never mind.
  494.    This instalment of the
  495.    <a href="/ongoing/What/The%20World/Life%20Online/De-Google/">De-Google Project</a> is about ways to do that with less
  496.    Big-Tech involvement.</p>
  497.    <p>The former Google Play Music, now YouTube Music, allowed
  498.    you to load your tunes into the cloud and play them back wherever your phone or computer happened to be. Except for it used to
  499.    be easy to upload<span class='dashes'> —</span> just point the uploader at your iTunes library<span class='dashes'> —</span> and
  500.    now it’s hard, and then Google removed YouTube Music’s shuffle-your-uploads feature from Android Auto. Also they fired a bunch
  501.    of YouTube Music contractors who were trying to unionize. So screw ’em.</p>
  502.    <p>I discovered three plausible ways to do this. First and most simply, dump the tunes onto a USB drive; wherever you are in the
  503.    world, you can usually plug one in and play tunes from it.</p>
  504.    <p>Second, there’s
  505.    <a href="https://www.plex.tv">Plex</a>; you run a Plex server on one of your computers at home (in our case a recent Mac Mini)
  506.    which you point at music and video directories, and it’ll serve them to clients on the Web or on phones or on platforms like
  507.    WebOS and Roku.</p>
  508.    <p>Also, it’ll serve your media to anywhere in the world, using
  509.    <a href="https://en.wikipedia.org/wiki/Universal_Plug_and_Play">UPnP</a> to drill an outgoing hole through your firewall.
  510.    Obviously, this could make a security-sensitive person nervous and does bother me a bit, because UPnP’s history has featured
  511.    some nasty vulnerabilities. I have a to-do to check whether the version on my dumbass telco ISP router is reasonably safe.
  512.    I believe that Tailscale would offer a better security posture, but don’t want one more thing to manage.</p>
  513.    <p>Finally, Apple Music can apparently do what YouTube Music does; let you upload your tunes into the cloud and play them
  514.    anywhere. But moving from one Big-Tech provider to another doesn’t feel like progress.</p>
  515.    <h2 id='p-1'>Does it work?</h2>
  516.    <p>Setting it up on Plex was a Just-Works experience. The process even reached out through our modern Eero mesh to the
  517.    old telco router and convinced it to set up the appropriate UPnP voodoo.  If you open the Plex server admin interface it
  518.    occasionally complains about a double-NAT situation but works anyhow.</p>
  519.    <p>Getting the USB working was kind of hilarious. First of all, I bought a 512G USB stick. (My Mac says it only has 460GB, but
  520.    what’s 50G between friends?) USB-A because that’s what the car has. It took a couple of hours to copy all the music onto it.</p>
  521.    <p>Then I plugged the USB stick into the car and it showed up instantly in the “Sources” tab of the media player, but
  522.    greyed out. I snickered when I noticed that <em>all</em> the car infotainment menus were crawling and stuttering. Asking the
  523.    car’s mighty electronic brain to index that mountain of music was making it sweat.
  524.    Anyhow, after a few minutes, I could access the USB and now it works fine, mostly.</p>
  525.    <p>By “mostly”, I mean that when I tell it to play music off the USB, it takes a few seconds for the music to start, then a
  526.    minute or more to get its shit together and present a coherent picture of what it’s playing.  And on one occasion, the music
  527.    player just randomly switched over to the radio. So I suspect my inventory is pushing the poor little toy computer in the car
  528.    pretty hard. But once it’s going, the presentation is nice:</p>
  529.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/10/PXL_20240309_193242839.png" alt="Jaguar infotainment showing current music and weather" />
  530.    <p>A few items to note here:</p>
  531.    <ol>
  532.      <li><p>“Musick” is the name I gave the USB key.</p></li>
  533.      <li><p>That recording is
  534.      <a href="https://en.wikipedia.org/wiki/Jesus'_Blood_Never_Failed_Me_Yet">Jesus’ Blood Never Failed Me Yet</a>, a truly unique
  535.      piece of work by British composer Gavin Bryars. Opinions vary; I think it’s magical but it’s one of the few pieces of music
  536.      that I am absolutely forbidden to play anywhere my wife can hear it.</p></li>
  537.      <li><p>The car software is way more flexible than Android Auto; this is just one of the car’s three screens and there are a lot of
  538.      options for distributing your music and weather and maps and climate control across them.</p></li>
  539.    </ol>
  540.    <h2 id='p-2'>Which is better?</h2>
  541.    <p>It’s complicated. Obviously, the USB option doesn’t require any network bandwidth. And I think the album-art presentation is
  542.    nicer than Plex’s. (You can see that
  543.    <a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-7">here</a>).</p>
  544.    <p>The audio quality is pretty well a wash. Plex is a little louder, I suspect them of
  545.    <a href="https://en.wikipedia.org/wiki/Loudness_war">Loudness-War</a> tactics, which is probably OK in a car with its inevitable
  546.    background noise. Plex also crossfades the song transitions, clever and pleasing but really not essential.</p>
  547.    <p>Plex is really nice software and I feel a little guilty that I’m not sending them any money. They do have a “Pro” level of
  548.    service; must check it out.</p>
  549.    <p>Then of course Plex needs Android Auto. Which on the one hand I’m probably going to be running a lot if I’m driving around
  550.    town to appointments. But… Android Auto is already a little shaky some days, not sure whether it’s crashing or the car software
  551.    is creaking or it’s just yet another lousy USB-C connection (I am developing a real hate for that form factor).</p>
  552.    <p>Realistically, given that our
  553.    car (a Jaguar I-Pace EV) wasn’t a big seller and is five years old, can I really count on Google and Jaguar to do what it takes
  554.    to keep Android Auto running?</p>
  555.    <p>At this point I need to say a big “Thanks!” to everyone on Fedi/Mastodon who gave me good advice on how to approach this
  556.    problem.</p>
  557.    <p>Anyhow, as of now, we have two alternatives that work well. The De-Googling march continues forward.</p>
  558. </div></content></entry>
  559.  
  560. <entry>
  561. <title>The De-Google Project</title>
  562. <link href='https://www.tbray.org/ongoing/When/202x/2024/03/09/DeGoogling' />
  563. <link rel='replies'        thr:count='29'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/03/09/DeGoogling#comments' />
  564. <id>https://www.tbray.org/ongoing/When/202x/2024/03/09/DeGoogling</id>
  565. <published>2024-03-09T12:00:00-08:00</published>
  566. <updated>2024-03-10T13:53:47-07:00</updated>
  567. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Life Online/De-Google' />
  568. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  569. <category scheme='https://www.tbray.org/ongoing/What/' term='Life Online' />
  570. <category scheme='https://www.tbray.org/ongoing/What/' term='De-Google' />
  571. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>My family, like most, depends on a lot of online services. And again like most, a lot of those services come from Big     Tech giants in general and (in our case) Google in particular. And like many people, we are becoming less comfortable with that.     So I’m going to try to be systematic about addressing the problem. This post summarizes our dependencies and then I’ll post blog     pieces about updates as I work my way through the list. (The first is already posted, see below.)</div></summary>
  572. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  573.    <p>My family, like most, depends on a lot of online services. And again like most, a lot of those services come from Big
  574.    Tech giants in general and (in our case) Google in particular. And like many people, we are becoming less comfortable with that.
  575.    So I’m going to try to be systematic about addressing the problem. This post summarizes our dependencies and then I’ll post blog
  576.    pieces about updates as I work my way through the list. (The first is already posted, see below.)</p>
  577.    <p>I’m calling this the “De-Google” project because they’re our chief supplier of this stuff and it’s more euphonious than
  578.    “De-BigTechInGeneral”.</p>
  579.    <table>
  580.      <tr valign="top"><th>Need</th><th>Supplier</th><th>Alternatives</th></tr>
  581.      <tr valign="top">
  582. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-3">Office</a></td>
  583. <td class="unhappy">Google Workspace</td>
  584. <td>?</td>
  585.      </tr>
  586.      <tr valign="top">
  587. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-17">Data sharing</a></td>
  588. <td class="neutral">Dropbox</td>
  589.      <td>?</td></tr>
  590.      <tr valign="top">
  591. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-16">Video meetings</a></td>
  592. <td class="neutral">Google
  593. Meet</td>
  594.      <td>Jitsi, ?</td></tr>
  595.      <tr valign="top">
  596. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-10">Maps</a></td>
  597. <td class="unhappy">Google Maps</td>
  598.      <td>Magic Earth, Here, something OSM-based</td></tr>
  599.      <tr valign="top">
  600. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-4">Browser</a></td>
  601. <td class="neutral">Apple Safari</td>
  602.      <td>Firefox, ?</td></tr>
  603.      <tr valign="top">
  604. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-12">Search</a></td>
  605. <td class="unhappy">Google</td>
  606.      <td>Bing-based options</td></tr>
  607.      <tr valign="top">
  608. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-5">Chat</a></td>
  609. <td class="happy">Signal</td>
  610.      <td></td></tr>
  611.      <tr valign="top">
  612. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-6">Photo editing</a></td>
  613. <td class="neutral">Adobe
  614. Lightroom &amp; Nik</td>
  615.      <td>Capture One, Darktable, ?</td></tr>
  616.      <tr valign="top">
  617. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-7">In-car interface</a></td>
  618. <td class="neutral">Google Android Auto</td>
  619.      <td>Automaker software</td></tr>
  620.      <tr valign="top">
  621. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-8">Play my music</a></td>
  622. <td class="happy">Plex, USB</td>
  623.      <td></td></tr>
  624.      <tr valign="top">
  625. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-9">Discover music</a></td>
  626. <td class="unhappy">Google YouTube Music</td>
  627. <td>Qobuz, Tidal, Deezer,
  628.      Pandora, ?</td></tr>
  629.      <tr valign="top">
  630. <td><a href="/ongoing/When/202x/2024/03/09/DeGoogling#p-13">TV</a></td>
  631. <td class="unhappy">Prime, Roku, Apple, Netflix, TSN, Sportsnet</td>
  632.      <td>?</td></tr>
  633.    </table>
  634.    <p>The “Supplier” color suggests my feelings about what I’m using, with blue standing for neutral.</p>
  635.    <h2 id='p-15'>Criteria</h2>
  636.    <p>To replace the things that I’m unhappy with, I’m looking for some combination of:</p>
  637.    <ol>
  638.      <li><p>Open source</p></li>
  639.      <li><p>Not ad-supported</p></li>
  640.      <li><p>Not VC-funded</p></li>
  641.      <li><p>Not Google, Apple, Microsoft, or Amazon</p></li>
  642.    </ol>
  643.    <h2 id='p-3'>Office</h2>
  644.    <p>We’ve been using Gmail for a really long time and are used to it, and the integration between mail and calendar and maps
  645.    basically Just Works. The price is OK but it keeps going up, and so do our data storage requirements, what with all the cameras in
  646.    the family.  Finally, Google has stewardship of our lives and are probably monetizing every keystroke.
  647.    We’re getting a bit creeped out over that.</p>
  648.    <p>I think that calendars and email are kind of joined at the hip, so we’d want a provider that does both.</p>
  649.    <p>As for online docs, I will not be sorry to shake the dust of Google Drive and Docs from my heels, I find them clumsy and am
  650.    always having trouble finding something that I know is in there.</p>
  651.    <h2 id='p-17'>Data sharing</h2>
  652.    <p>Dropbox is OK, assuming you ignore all the other stuff it’s trying to sell you. Maybe one of these years I should look at
  653.    that other stuff and see if it’s a candidate to replace one or two other services?</p>
  654.    <h2 id='p-16'>Video meetings</h2>
  655.    <p>I dislike lots of things about Zoom and find Microsoft Teams a pool of pain, but have been pretty happy with Google
  656.    Meet. Nobody has to download or log into anything and it seems to more or less Just Work.  But I’d look at alternatives.</p>
  657.    <h2 id='p-10'>Maps</h2>
  658.    <p>As I
  659.    <a href="/ongoing/When/201x/2017/06/29/Fear-Google-Reviews">wrote in 2017</a>, Google maps aggregate directions, reviews,
  660.    descriptions, phone numbers, and office hours. They are potentially a nuclear-powered monopoly engine. I use Maps more and
  661.    more; if I
  662.    want to contact or interact with something whose location I know, it’s way quicker to pull up Maps and click on their listing than it
  663.    is to use Google search and fight through all the ads and spam.</p>
  664.    <p>The calendar integration is fabulous. If you have Android Auto and you’re going to a meeting, pull up the calendar app and
  665.    tap on the meeting and it drops you right into directions.</p>
  666.    <p>The quality of the OpenStreetMap data is very good, but obviously they don’t have the Directions
  667.    functions. Who does? Obviously,
  668.    <a href="https://www.here.com/">Here</a> does, and
  669.    <a href="https://www.tbray.org/ongoing/When/201x/2019/01/23/I-Pace-UX#p-3">I was enthused about it</a> in 2019; but Android
  670.    Auto’s music powers drew me back to Google Maps.
  671.    Aside from that, <a href="https://www.magicearth.com">Magic Earth</a> is trying, and their business model seems acceptable, but
  672.    the product was pretty rough-edged last time I tried it.</p>
  673.    <h2 id='p-4'>Browser</h2>
  674.    <p>Safari is my daily driver. These days Chrome is starting to creep me out a bit; just doesn’t feel like it’s on my side. Also,
  675.    it’s no longer faster than the competition.  I’d like to shift over to Firefox one day when I have the energy</p>
  676.    <p>Then there are the Arcs and Braves and Vivaldis of this world, but I just haven’t yet invested the time to
  677.    figure out if one of these will do, and I do not detect a wave of consensus out there.</p>
  678.    <p>By the way, DuckDuckGo has a browser, a shell over Safari on the Mac and Edge on Windows. Lauren uses it a lot.
  679.    Probably worth a closer look.</p>
  680.    <h2 id='p-12'>Search</h2>
  681.    <p>The decline of Google Search is increasingly in everyone’s face. Once again, it refuses to find things on this blog that I know
  682.    are there.</p>
  683.    <p>Others in the family have already migrated to DuckDuckGo, and I now feel like an old-school lagger for still not having
  684.    migrated off Google. I wish there were someone else taking a serious run at indexing the Web other than Bing<span
  685.    class='dashes'> —</span> from yet another tech giant<span class='dashes'> —</span> but here we are.</p>
  686.    <p>Lauren tells me to have a closer look at
  687.    <a href="https://www.ecosia.org/">Ecosia</a>, which seems very wholesome.</p>
  688.    <h2 id='p-5'>Chat</h2>
  689.    <p>At the moment you will have to pry Signal out of my cold, dead, hands. You should be using it too. ’Nuff said.</p>
  690.    <h2 id='p-6'>Photo editing</h2>
  691.    <p>I pay my monthly tribute to Adobe, about whom my feelings aren’t as negative as they are about the mega Tech
  692.    Giants.
  693.    I’d like not to pay so much, and I’d like something that runs a little faster than Lightroom, and I’d like to support open
  694.    source.  But… I really like Lightroom, and sometimes one absolutely needs Photoshop, so I’m unlikely to prioritize this
  695.    particular escape attempt.</p>
  696.    <h2 id='p-7'>In-car interface</h2>
  697.    <p>Choices are limited. I see little point in migrating between Android Auto and CarPlay, which leaves the software the auto
  698.    maker installed. Which, in my
  699.    <a href="/ongoing/What/The%20World/Jaguar%20Diary/">five-year-old Jaguar</a> is… well, not bad actually.  I think I could live
  700.    with the built-in maps and directions from Here, even with the British Received Pronunciation’s butchery of North
  701.    American place names.</p>
  702.    <p>But, I don’t know, we might stay with Android Auto. Check out this screenshot from my car.</p>
  703.    <img src="https://www.tbray.org/ongoing/When/202x/2024/03/09/PXL_20240309_024054360.png" alt="Android Auto showing non-Google applications." />
  704.    <div class='caption'><p>(Pardon the blurs and distortions.)</p></div>
  705.    <p>This is Android Auto displaying, as it normally does when I’m driving, maps and music. By default, Google Maps and YouTube
  706.    Music. But not here; on the right is
  707.    <a href="https://www.plex.tv/">Plex</a>, playing my own music stored on a Mac Mini at home.</p>
  708.    <p>On the left, it’s even more interesting: This is neither Google maps nor a competitor; it’s
  709.    <a href="https://www.gaiagps.com">Gaia GPS</a>, the app I normally use to mark trail while bushwhacking through Pacific
  710.    Northwest rain forests. Somehow I fat-fingered it into place either in the car or on my phone.</p>
  711.    <p>The lesson here is that (for the moment at least) Android Auto seems to be genuinely neutral.  It knows the general
  712.    concepts of “apps that play music” and “apps that are maps” and is happy to display whichever ones you want, not just Google’s.
  713.    (As a former Android geek who knows about Intents and Filters, I can see how this works. Clever.)</p>
  714.    <p>So far, Android Auto doesn’t show ads, but I suppose it’s monetizing me by harvesting traffic information to enrich its maps
  715.    and I guess that’s a bargain I can live with. I use that data myself when I want to go somewhere and there are multiple routes
  716.    and I can see which one is backed up by sewer work or whatever.</p>
  717.    <h2 id='p-9'>Discover music</h2>
  718.    <p>I’ve been paying for YouTube Music since before it existed, and I’m genuinely impressed with the way its algorithm fishes up
  719.    new artists that it turns out I really like. But just now Google laid off a bunch of
  720.    YouTube Music “contractors” (de facto, employees) who tried to organize a union, so screw ’em.</p>
  721.    <p>I haven’t investigated any of the alternatives in depth yet.</p>
  722.    <h2 id='p-8'>Play my music</h2>
  723.    <p>In the decades where Compact Disks were the way to acquire music, I acquired a lot. And ripped it. And pushed it up into
  724.    Google’s musical cloud. And (until recently) could shuffle my musical life on YouTube Music. But they removed that feature from
  725.    Android Auto, so screw ’em.</p>
  726.    <p>But I now have two good ways to do this. Check this out in
  727.    <a href="/ongoing/When/202x/2024/03/10/Play-My-Music">Play My Music</a>.</p>
  728.    <h2 id='p-13'>TV</h2>
  729.    <p>The same gripe as everyone else: The streaming services have re-invented Cable TV, which I only got around to dumping a
  730.    couple of years ago. The <em>right</em> solution is obvious: Pay-per-view at a reasonably low price, then the services could
  731.    compete on producing great shows that people will pay to see, rather than sucking you into yet another
  732.    subscription.</p>
  733.    <p>I suspect this column will stay red for quite a while. It’s amazing how much business leaders hate <em>simple</em> business
  734.    models where there’s a clean clear one-time price for a product and customers have a clean clear choice who they buy their
  735.    products from.</p>
  736.    <h2 id='p-11'>The path forward</h2>
  737.    <p>I don’t know if I’ll ever turn the center column all-green. And I don’t need to; progress is progress. Anyhow, doing this
  738.    sort of investigation is kind of fun.</p>
  739. </div></content></entry>
  740.  
  741. <entry>
  742. <title>Money Bubble</title>
  743. <link href='https://www.tbray.org/ongoing/When/202x/2024/02/25/Money-AI-Bubble' />
  744. <link rel='replies'        thr:count='13'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/02/25/Money-AI-Bubble#comments' />
  745. <id>https://www.tbray.org/ongoing/When/202x/2024/02/25/Money-AI-Bubble</id>
  746. <published>2024-02-25T12:00:00-08:00</published>
  747. <updated>2024-02-25T12:00:00-08:00</updated>
  748. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Business' />
  749. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  750. <category scheme='https://www.tbray.org/ongoing/What/' term='Business' />
  751. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I think I’m probably going to lose quite a lot of money in the next year or two. It’s partly AI’s fault, but not     mostly. Nonetheless I’m mostly going to write about AI, because it intersects the technosphere, where I’ve lived for     decades</div></summary>
  752. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  753.    <p>I think I’m probably going to lose quite a lot of money in the next year or two. It’s partly AI’s fault, but not
  754.    mostly. Nonetheless I’m mostly going to write about AI, because it intersects the technosphere, where I’ve lived for
  755.    decades.</p>
  756.    <p>I’ve given up having a regular job. The family still has income but mostly we’re harvesting our
  757.    savings, built up over decades in a well-paid profession. Which means that we are, willy-nilly, investors. And thus aware of the
  758.    fever-dream finance landscape that is InvestorWorld.</p>
  759.    <h2 id='p-1'>The Larger Bubble</h2>
  760.    <p>Put in the simplest way: Things have been too good for too long in InvestorWorld: low interest, high profits, the unending rocket
  761.    rise of the Big-Tech sector, now with AI afterburners. Wile E. Coyote hasn’t actually run off the edge of the cliff yet, but
  762.    there are just way more ways for things to go wrong than right in the immediate future.</p>
  763.    <p>If you want to dive a little deeper, <cite>The Economist</cite> has a sharp (but
  764.    paywalled) take in
  765.    <a href="https://www.economist.com/finance-and-economics/2024/02/25/stockmarkets-are-booming-but-the-good-times-are-unlikely-to-last">Stockmarkets
  766.    are booming. But the good times are unlikely to last</a>. Their argument is that profits are overvalued by investors because, in
  767.    recent years, they’ve always gone up. Mr Market ignores the fact that at least some of those gleaming profits are artifacts of
  768.    tax-slashing by right-wing governments.</p>
  769.    <p>That piece considers the observation that “Many investors hope that AI will ride to the rescue” and is politely
  770.    skeptical.</p>
  771.    <h2 id='p-2'>Popping the bubble</h2>
  772.    <p>My own feelings aren’t polite; closer to
  773.    <a href="https://finance.yahoo.com/news/yep-you-are-living-in-a-nvidia-led-tech-bubble-110014738.html">Yep, you are living in a
  774.    Nvidia-led tech bubble</a> by Brian Sozzi over at Yahoo! Finance.</p>
  775.    <p>Sozzi is fair, pointing out that this bubble feels different from the cannabis and crypto crazes; among other things,
  776.    chipmakers and cloud providers are reporting big high-margin revenues for real actual products. But he hammers the central point:
  777.    What we’re seeing is FOMO-driven dumb money thrown at technology by people who have no hope of
  778.    understanding it. Just because everybody else is and because the GPTs and image generators have cool demos.
  779.    Sozzi has the numbers, looking at valuations through standard old-as-dirt filters and shaking his head at what he sees.</p>
  780.    <p>What’s going to happen, I’m pretty sure, is that AI/ML will, inevitably, disappoint; in the financial sense I mean, probably
  781.    doing some useful things, maybe even a lot, but not generating the kind of profit explosions that you’d need to justify
  782.    the bubble. So it’ll pop, and my bet it is takes a bunch of the finance world with it. As bad as 2008? Nobody knows, but it
  783.    wouldn’t surprise me.</p>
  784.    <p>The rest of this piece considers the issues facing AI/ML,  with the goal of showing why I see it as
  785.    a bubble-inflator and eventual bubble-popper.</p>
  786.    <p>First, a disclosure: I speak as an educated amateur. I’ve never gone much below the surface of the technology, never
  787.    constructed a model or built model-processing software, or looked closely at the math.  But I think the discussion below still
  788.    works.</p>
  789.    <h2 id='p-3'>What’s good about AI/ML</h2>
  790.    <p>Spoiler: I’m not the kind of burn-it-with-fire skeptic that I became around anything blockchain-flavored. It is clear
  791.    that generative models manage to embed significant parts of the structure of language, of code, of pictures, of
  792.    many things where that has previously not been the case. The understanding is sufficient to reliably accomplish the objective:
  793.    <i>Produce plausible output</i>.</p>
  794.    <p>I’ve read enough Chomsky to believe that facility with language is a defining characteristic of intelligence. More than that, a
  795.    necessary but not sufficient ingredient.  I dunno if anyone will build an AGI in my lifetime, but I am confident that the task
  796.    would remain beyond reach without the functions offered by today’s generative models.</p>
  797.    <p>Furthermore, I’m super impressed by something nobody else seems to talk about: Prompt parsing. Obviously, prompts are
  798.    processed into a representation that reliably sends the model-traversal logic down substantially the right
  799.    paths. The LLMbots of this world may regularly be crazy and/or just wrong, but they do consistently if not correctly address the
  800.    substance of the prompt.
  801.    There is seriously good natural-language engineering going on here that AI’s critics aren’t paying enough attention
  802.    to.</p>
  803.    <p>So I have no patience with those who scoff at today’s technology, accusing it being a glorified Markov chain. Like the
  804.    song says:  Something’s
  805.    happening here! (What it is ain’t exactly clear.)</p>
  806.    <p>It helps that in the late teens I saw neural-net pattern-matching at work on real-world problems from close up and
  807.    developed serious respect for what that technology can do; An example is EC2’s
  808.    <a href="https://aws.amazon.com/blogs/compute/evaluating-predictive-scaling-for-amazon-ec2-capacity-optimization/">Predictive Auto
  809.    Scaling</a> (and gosh, it looks like
  810.    <a href="https://www.google.com/search?rls=en&amp;q=predictive+auto+scaling&amp;ie=UTF-8&amp;oe=UTF-8">the competition has it
  811.    too</a>).</p>
  812.    <p>And recently, Adobe Lightroom has shipped a pretty awesome “Select Sky” feature. It makes my M2 MacBook
  813.    Pro think hard for a second or two, but I rarely see it miss even an isolated scrap of sky off in the corner of the frame.  It
  814.    allows me, in a picture like this, to make the sky’s brightness echo the water’s.</p>
  815.    <img src="https://www.tbray.org/ongoing/When/202x/2024/02/25/PXL_20240111_213727870.png" alt="Brightly-lit boats on dark water under a dark sky" />
  816.    <p>And of course I’ve heard about success stories in radiology and other disciplines.</p>
  817.    <p>Thus, please don’t call me an “AI skeptic” or some such. There is a there there.</p>
  818.    <h2 id='p-4'>But…</h2>
  819.    <p>Given that, why do I still think that the flood of money being thrown at this tech is dumb, and that most of it will be lost?
  820.    Partly just because of that flood. When financial decision makers throw loads of money at things they don’t
  821.    understand, lots of it is <em>always</em> lost.</p>
  822.    <p>In the Venture-Capital business, that’s an understood part of the business
  823.    cycle; they’re looking to balance that out with a small number of 100x startup wins.
  824.    But when big old insurance companies and airlines and so on are piling in and releasing effusive statements about building
  825.    the company around some new tech voodoo, the outcome, in my experience, is very rarely good.</p>
  826.    <p>But let’s be specific.</p>
  827.    <h2 id='p-5'>Meaning</h2>
  828.    <p>As I said above, I think the human mind has a large and important language-processing system.  But that’s not all. It’s also
  829.    a (slow, poorly-understood) computer, with access to a medium-large database of facts and recollections, an ultra-slow numeric
  830.    processor, and facilities for estimation, prediction, speculation, and invention. Let’s group all this stuff together and call
  831.    it “meaning”.</p>
  832.    <p>Have a look at <a href="https://aclanthology.org/2020.acl-main.463.pdf">Climbing towards NLU:
  833.    On Meaning, Form, and Understanding in the Age of Data</a> by Emily Bender and Alexander Koller (2020). I don’t agree with
  834.    all of it, and it addresses an earlier generation of generative models, but it’s very thought-provoking. It postulates the
  835.    “Octopus Test”, a good variation on the bad old Chinese-Room analogy. It talks usefully about how human language acquisition
  836.    works. A couple of quotes: “It is instructive to look at the past to appreciate this question. Computational linguistics has
  837.    gone through many fashion cycles over the course of its history” and “In this paper, we have argued that in contrast to some
  838.    current hype, meaning cannot be learned from form alone.”</p>
  839.    <p>I’m not saying these problems can’t be solved. Software systems can be equipped with databases of facts, and who knows,
  840.    perhaps some day estimation, prediction, speculation, and invention. But it’s not going to be easy.</p>
  841.    <h2 id='p-7'>Difficulty</h2>
  842.    <p>I think there’s a useful analogy between the narratives around AI and of self-driving cars. As I write this,
  843.    Apple has apparently decided that
  844.    <a href="https://arstechnica.com/gadgets/2024/02/after-a-decade-of-stops-and-starts-apple-kills-its-electric-car-project">generative
  845.    AI is easier than shipping an autonomous car</a>. I’m particularly sensitive to this analogy because back around 2010, as the
  846.    first self-driving prototypes were coming into view, I predicted, loudly and in public, that this technology was about to become
  847.    ubiquitous and turn the economy inside out. Ouch.</p>
  848.    <p>There’s a pattern: The technologies that really do change the world tend to have strings of successes, producing obvious
  849.    benefits even in their earliest forms, to the extent that geeks load them in the back doors of organizations just to get shit
  850.    done. As they say, “The CIO is the last to know.”</p>
  851.    <p>Contrast cryptocurrencies and blockchains, which limped along from year to year, always promising a brilliant future, never
  852.    doing anything useful.  As to the usefulness of self-driving technology, I still think it’s gonna get there, but it’s surrounded
  853.    by a cloud of litigation.</p>
  854.    <p>Anyhow, anybody who thinks that it’ll be easy to teach “meaning” (as I described it above) to today’s generative AI is a fool,
  855.    and you shouldn’t give them your money.</p>
  856.    <h2 id='p-6'>Money and carbon</h2>
  857.    <p>Another big problem we’re not talking about enough is the cost of generative AI.
  858.    <cite>Nature</cite> offers    
  859.    <a href="https://www.nature.com/articles/d41586-024-00478-x">Generative AI’s environmental costs are soaring — and mostly
  860.    secret</a>. In a Mastodon thread,
  861.    <a href="https://phanpy.social/#/social.v.st/a/109360452395342558">@Quixoticgeek@social.v.st</a> says
  862.    <a href="https://phanpy.social/#/social.v.st/s/111991430750212364">We need to talk about data centres</a>, and includes a few
  863.    hard and sobering numbers.</p>
  864.    <p>Short form: This shit is <em>expensive</em>, in dollars and in carbon load. Nvidia pulled in
  865.    <a href="https://investor.nvidia.com/news/press-release-details/2024/NVIDIA-Announces-Financial-Results-for-Fourth-Quarter-and-Fiscal-2024/">$60.9
  866.    billion in 2023, up 126% from the previous year</a>, and is heading for a $100B/year run rate, while reporting a 75% margin.</p>
  867.    <p>Another thing these articles <em>don’t</em> mention is that building, deploying, and running generative-AI systems requires significant
  868.    effort from a small group of people who now apparently constitute the world’s highest-paid cadre of engineers. And good luck
  869.    trying to hire one if you’re a mainstream company where IT is a cost center.</p>
  870.    <p>All this means that for the technology to succeed, it not only has to do something useful, but people and businesses will have to
  871.    be ready to pay a significantly high price for that something.</p>
  872.    <p>I’m not saying that there’s nothing that qualifies, but I am betting that it’s not in ad-supported territory.</p>
  873.    <p>Also, it’s going to have to deal with pushback from unreasonable climate-change resisters like, for example, me.</p>
  874.    <h2 id='p-8'>Anyhow…</h2>
  875.    <p>I kind of flipped out, and was motivated to finish this blog piece, when I saw
  876.    <a href="https://www.engadget.com/uk-government-wants-to-use-ai-to-cut-civil-service-jobs-140031159.html">this</a>: “UK
  877.    government wants to use AI to cut civil service jobs: Yes, you read that right.” The idea<span class='dashes'> —</span> to have
  878.    citizen input processed and responded to by an LLM<span class='dashes'> —</span> is hideously toxic and broken; and usefully
  879.    reveals the kind of thinking that makes morally crippled leaders all across our system love this technology.</p>
  880.    <p>The road ahead looks bumpy from where I sit. And when the business community wakes up and realizes that replacing
  881.    people with shitty technology doesn’t show up as a positive on the financials after you factor in the consequences of customer
  882.    rage, that’s when the hot air gushes out of the bubble.</p>
  883.    <p>It might not take big chunks of InvestorWorld with it. But I’m betting it does.</p>
  884. </div></content></entry>
  885.  
  886. <entry>
  887. <title>Social Photos</title>
  888. <link href='https://www.tbray.org/ongoing/When/202x/2024/02/15/Social-Photos' />
  889. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/02/15/Social-Photos#comments' />
  890. <id>https://www.tbray.org/ongoing/When/202x/2024/02/15/Social-Photos</id>
  891. <published>2024-02-15T12:00:00-08:00</published>
  892. <updated>2024-02-20T12:21:16-08:00</updated>
  893. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Publishing' />
  894. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  895. <category scheme='https://www.tbray.org/ongoing/What/' term='Publishing' />
  896. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos' />
  897. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  898. <category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
  899. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I like taking pictures, and I like sharing pictures wherever I hang out online. A problem with this is     knowing that the pictures will very rarely look as good in other people’s browsers and apps as they do to me in Lightroom on a     big bright 4K screen. Thus this piece, a basic investigation of how photos are processed and transformed on Mastodon,     Bluesky, and Threads</div></summary>
  900. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  901.    <p>I like taking pictures, and I like sharing pictures wherever I hang out online. A problem with this is
  902.    knowing that the pictures will very rarely look as good in other people’s browsers and apps as they do to me in Lightroom on a
  903.    big bright 4K screen. Thus this piece, a basic investigation of how photos are processed and transformed on Mastodon,
  904.    Bluesky, and Threads.</p>
  905.    <p>I was never that much of an Instagram poster; Insta does a good job of taking your crappy phone pix and juicing them up with
  906.    filters so they look way better. That’s irrelevant to me, because not only do I like taking pictures, I like polishing them
  907.    with Lightroom and Silver Efex and so on. So with a few exceptions, everything I want to share gets pulled onto my Mac and
  908.    edited before I share it.  And once I’ve done that, why would I post pictures anywhere but where I have my normal
  909.    conversations?</p>
  910.    <h2 id='p-1'>The picture</h2>
  911.    <p>Here it is:</p>
  912.    <img src="https://www.tbray.org/ongoing/When/202x/2024/02/15/orig-full-size.png" alt="Montana from the air" />
  913.    <div class='caption'><p>Taken with a Pixel 7 out an airplane window somewhere just west of Havre, Montana.
  914.    It seems like there are two layers of clouds at the left of the picture but if you look closely, the lower one I think is the
  915.    Rocky Mountains in the distance.</p></div>
  916.    <p>That’s a <em>big</em> picture, both in its subject and raw size: The Pixel version, after editing, is 3814x2290. Also it has
  917.    a lot of fine detail, and rewards zooming in.   When I
  918.    post it, I’d like some sense of the bigness to come across, and when tapped to enlarge, I’d like it to wow people a little, especially
  919.    those fortunate enough to be looking at big screens. And I’d like it to be at least OK on your phone.</p>
  920.    <p>Normally, pictures here in the blog are limited to max 720x720 in the column of text, and the larger version you get by
  921.    clicking to 1440x960.  But in this case, if you click you get a 2558x1536 version, the objective being that that’ll be big
  922.    enough to fill almost any screen it gets viewed on.</p>
  923.    <h2 id='p-2'>Methodology and apology</h2>
  924.    <p>The question I want to investigate is, “which platforms are going to make my pictures look good?” But I haven’t really figured
  925.    out yet how to do that.  To start with, what kind of picture is going to do best as a metric to judge the processing
  926.    quality?</p>
  927.    <p>Anyhow, I picked this one and posted it to
  928.    <a href="https://cosocial.ca/@timbray/111944201090317720">Mastodon</a>,
  929.    <a href="https://bsky.app/profile/tbray.org/post/3kll7x662ot22">Bluesky</a>, and
  930.    <a href="https://www.threads.net/@twbray/post/C3bfS5Jp5nW">Threads</a>, and here gather data about the results.
  931.    But hey, why not tap those links on whatever device you’re using right now and see what you think about how the picture looks there?</p>
  932.    <p>The columns are:</p>
  933.    <ol>
  934.      <li><p><b>Bytes:</b> the size of the photo as downloaded.</p></li>
  935.      <li><p><b>WxH:</b> width and height, in pixels.</p></li>
  936.      <li><p><b>“Q”:</b> the JPG quality, as reported by Imagemagick’s <code>identify --verbose</code>. The quotes are there because
  937.      I’m not sure how to interpret, or even whether it’s any use at all.</p></li>
  938.    </ol>
  939.    <table>
  940.      <tr align="center"><td class="empty"></td><td class="empty"></td><th>Bytes</th><th>WxH</th><th>“Q”</th></tr>
  941.      <tr align="right"><td class="empty"></td><th>Original</th><td class="num">1671514</td><td class="num">2558 1536</td><td class="num">94</td></tr>
  942.      <tr align="right"><td class="empty"></td><th>Blog form</th><td class="num">624961</td><td class="num">1440  865</td><td class="num">94</td></tr>
  943.      <tr align="right"><th>Bluesky</th><th>Android FS</th><td class="num">302972</td><td class="num">864  663</td><td class="num"></td></tr>
  944.      <tr align="right"><th>Bluesky</th><th>Android mini</th><td class="num">42410</td><td class="num">345  345</td><td class="num"></td></tr>
  945.      <tr align="right"><th>Bluesky</th><th>Web FS</th><td class="num">536345</td><td class="num">2000 1201</td><td class="num">80</td></tr>
  946.      <tr align="right"><th>Bluesky</th><th>Web mini</th><td class="num">112335</td><td class="num">1000  601</td><td class="num">80</td></tr>
  947.      <tr align="right"><th>Mastodon</th><th>Web FS</th><td class="num">1555111</td><td class="num">2558 1536</td><td class="num">90</td></tr>
  948.      <tr align="right"><th>Mastodon</th><th>Web mini</th><td class="num">86374</td><td class="num">619  372</td><td class="num">90</td></tr>
  949.      <tr align="right"><th>Phanpy</th><th>Web FS</th><td class="num">1555111</td><td class="num">2558 1536</td><td class="num">90</td></tr>
  950.      <tr align="right"><th>Phanpy</th><th>Web mini</th><td class="num">86374</td><td class="num">619  372</td><td class="num">90</td></tr>
  951.      <tr align="right"><th>Threads</th><th>Web FS</th><td class="num">888067</td><td class="num">2160 1297</td><td class="num">90</td></tr>
  952.      <tr align="right"><th>Threads</th><th>Web mini</th><td class="num">888067</td><td class="num">2160 1297</td><td class="num">90</td></tr>
  953.    </table>
  954.    <p>Note that each of the posts included not one but two pictures, because I was also
  955.    interested in how the platforms allocated screen space. The platforms typically have two display modes, “mini”, as shown in the
  956.    feed, and “FS” for Full Size, what you get when you click on the picture.</p>
  957.    <h2 id='p-3'>Original/Blog form</h2>
  958.    <p>I think that ideally, I’d like each platform’s presentation of the picture, when you click on it, to have the same number of
  959.    pixels and for each pixel to have the same color value, as in my original.</p>
  960.    <h2 id='p-4'>Bluesky</h2>
  961.    <p>First of all are numbers from the Android app, but please don’t take them seriously. The process of extracting them from the
  962.    Pixel’s screen and getting them onto my Mac involved multiple irritating steps, each one of which may have damaged the
  963.    bits. So I didn’t repeat the exercise for the other platforms.
  964.    They are mostly here to encourage me, should I pursue this further, to find a good clean way to extract this
  965.    information.</p>
  966.    <p>I do note, however, that the “mini” form in the Bluesky Android feed really crushes those poor little pictures down and, for this
  967.    particular picture, offers no suggestion that it’s big.</p>
  968.    <p>The Web version of Bluesky does not preserve my pixels, but coerces the size down to 2K and 1K width in FS and mini
  969.    versions.</p>
  970.    <h2 id='p-5'>Mastodon and Phanpy</h2>
  971.    <p><a href="https://phanpy.social">Phanpy</a> is an alternate client for Mastodon; I think it’s very good and it’s my daily
  972.    driver. The table reveals that, in this case, the alternate client pulls in the same images as the official Web client, which is
  973.    good.</p>
  974.    <p>It also reveals that Mastodon preserves the picture’s dimensions, but obviously reprocesses it somehow, because the photos
  975.    grow (somewhat) smaller. I wish they didn’t do that. It’s open-source, I should peek in and see what they actually do.</p>
  976.    <p>Phanpy does a better job of actually showing the pictures in-feed than the official Mastodon client, and both are nicer than
  977.    Bluesky.</p>
  978.    <h2 id='p-6'>Threads</h2>
  979.    <p>I had difficulty, because the Threads Web client is a tangly JavaScript fever dream, so it’s really hard to get at the
  980.    underlying photos, but my efforts suggested that it uses the same picture for the “mini” and “FS” versions, just getting
  981.    the browser to scale them down.</p>
  982.    <p>Furthermore, Threads doesn’t want pictures to be more than 2160 pixels wide.</p>
  983.    <h2 id='p-7'>Maybe I’m wrong</h2>
  984.    <p>Because the experimental work was manual and thus highly prone to fumblefingers and brain farts.  If you
  985.    think that any of these numbers are wrong, you may be right; please yell at me.</p>
  986.    <p>I hesitate to offer a conclusion because this is, as noted at the top, the first steps in what could be a large
  987.    and interesting research project, one that I probably don’t have the expertise to conduct. But, here are a few anyhow.</p>
  988.    <p>First,
  989.    they all do a pretty good job. Second, none of them actually offer an opportunity to view my bits exactly as uploaded, which I
  990.    think they should.  Third, client designers should follow Phanpy’s lead in figuring out how to make better use of screen
  991.    real-estate to highlight images.</p>
  992.    <h2 id='p-23'>What Lewis Carroll Said</h2>
  993.    <p>And I quote: <i>“What is the use of a book,”</i> thought Alice, <i>“without pictures
  994.    or conversations?”</i></p>
  995.  
  996. </div></content></entry>
  997.  
  998. <entry>
  999. <title>Vision 1993</title>
  1000. <link href='https://www.tbray.org/ongoing/When/202x/2024/02/02/Vision-1993' />
  1001. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/02/02/Vision-1993#comments' />
  1002. <id>https://www.tbray.org/ongoing/When/202x/2024/02/02/Vision-1993</id>
  1003. <published>2024-02-02T12:00:00-08:00</published>
  1004. <updated>2024-02-02T12:00:00-08:00</updated>
  1005. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Augmented Reality' />
  1006. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1007. <category scheme='https://www.tbray.org/ongoing/What/' term='Augmented Reality' />
  1008. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I’ve plowed through the first wave of AVP (Apple Vision Pro) reviews, and it seems pretty obvious that, at the current price     and form factor, it’s not gonna be a best-seller.  But I remain a strong believer in Augmented Reality (the AVP is     VR not AR, for the moment). As I was diving into the reviews, a little voice in the back of my head kept saying “I once read about     what this is trying to be.”</div></summary>
  1009. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1010.    <p>I’ve plowed through the first wave of AVP (Apple Vision Pro) reviews, and it seems pretty obvious that, at the current price
  1011.    and form factor, it’s not gonna be a best-seller.  But I remain a strong believer in Augmented Reality (the AVP is
  1012.    VR not AR, for the moment). As I was diving into the reviews, a little voice in the back of my head kept saying “I once read about
  1013.    what this is trying to be.”</p>
  1014.    <img src="https://www.tbray.org/ongoing/When/202x/2024/02/02/original.png" alt="William Gibson’s Virtual Light" class="inline" />
  1015.    <p>What I was remembering was
  1016.    <a href="https://en.wikipedia.org/wiki/Virtual_Light">Virtual Light</a>, a 1993 novel by William Gibson, allegedly set in
  1017.    2006. It paints a clear picture of a future that includes AVP’s descendants. So I re-read it. Maybe looking back is the way to
  1018.    look forward.</p>
  1019.    <h2 id='p-1'>But first…</h2>
  1020.    <p>I wanted to say: It’s a terrific book! If you haven’t read it you might really like it. I hadn’t in years and I sure
  1021.    enjoyed the re-read. The people in it are charming, and it’s built around a fabulous physical artifact that drives the plot. No, I
  1022.    don’t mean AR goggles, I mean San Francisco’s Bay Bridge, which in <cite>Virtual Light</cite> and
  1023.    <a href="https://en.wikipedia.org/wiki/Bridge_trilogy">two subsequent novels</a>, has
  1024.    been wrecked by an earthquake and become a huge countercultural shantytown, one of the coolest venues Gibson has ever
  1025.    invented, and that’s a strong statement. Also, protagonists Chevette and Rydell are two of his best characters; another
  1026.    strong statement.</p>
  1027.    <img src="https://www.tbray.org/ongoing/When/202x/2024/02/02/pink-face.png" alt="William Gibson’s Virtual Light" class="inline"/>
  1028.    <p>Anyhow, I don’t think it’s much of a spoiler to say that the AR devices I’m writing about, despite being what the title
  1029.    refers to, are peripheral to the plot. It turns out that one such device contains information that’s secret enough to attract
  1030.    hired killers, skip tracers, and crooked Homicide cops to recover it when it gets stolen; plenty of plot fuel right there.</p>
  1031.    <h2 id='p-2'>Quoting</h2>
  1032.    <p>Here are a few out-takes from the book describing the titular technology.</p>
  1033.    <p>Quote:</p>
  1034.    <blockquote>
  1035.      <p>Nothing in it but a pair of sunglasses, expensive-looking but so dark she hadn’t even been able to see through them last
  1036.      night.</p>
  1037.    </blockquote>
  1038.    <p>Quote:</p>
  1039.    <blockquote>
  1040.      <p>…she took that case out.</p>
  1041.      <p>You couldn’t tell what it was made of, and that meant expensive. Something dark gray, like the lead in a pencil, thin as the
  1042.      shell of one of those eggs, but you could probably drive a truck over it… She’d figured out how you opened it the night
  1043.      before: finger here, thumb there. It opened. No catch or anything, no spring… Inside was like black suede, but it gave like
  1044.      foam under your finger.</p>
  1045.      <p>Those glasses, nested there. Big and black. Like that Orbison in the poster… She pulled them from the black suede… They
  1046.      bothered her … they weighed too much. Way too heavy for what they were, even with the big earpieces. The frames looked as
  1047.      though they’d been carved from slabs of graphite.</p>
  1048.      <p>She put them on. Black. Solid black.</p>
  1049.      <p>“Katharine Hepburn.” Skinner said.</p>
  1050.    </blockquote>
  1051.    <p>Quote:</p>
  1052.    <blockquote><p>Warbaby wore a black Stetson set dead level on his head, the brim turned up all the way around, and glasses with
  1053.    heavy black frames. Clear lenses, windowpane plain.</p></blockquote>
  1054.    <p>Quote:</p>
  1055.    <blockquote><p>“You date you some architects, some brain-surgeons, you’d know what those are… Those <em>VL</em> glasses. Virtual
  1056.    light.”</p>
  1057.    <p>“They expensive, Sammy Sal?”</p>
  1058.    <p>“Shit, yes. ’Bout as much as a Japanese car… Got these little EMP-drivers around the lenses, work your optic nerves
  1059.    direct. Friend of mine, he’d bring a pair home from the office where he worked. Landscape architects. Put ’em on, you go out
  1060.    walking, everything looks normal, but every plant you see, every tree, there’s this little label hanging there, what its name
  1061.    is. Latin under that…”</p></blockquote>
  1062.    <p>Quote (at a crime scene with Warbaby and Freddie):</p>
  1063.    <blockquote><p>Rydell noticed the weight as he slid them on. Pitch black. Then there was a stutter of soft fuzzy ball-lightning,
  1064.    like what you saw when you rubbed your eyes in the dark, and he was looking at Warbaby. Just behind Warbaby, hung on some
  1065.    invisible wall, were words, numbers, bright yellow. They came into focus as he looked at them, somehow losing Warbaby, and he
  1066.    saw that they were forensic stats.</p>
  1067.    <p>“Or,” Freddie said, “you can just be here <em>now</em> —”</p>
  1068.    <p>And the bed was back, sodden with blood, the man’s soft, heavy corpse splayed out like a frog. That thing beneath his chin,
  1069.    blue-black, bulbous.</p>
  1070.    <p>Rydell’s stomach heaved, bile rose in his throat, and then a naked woman rolled up from another bed, in a different room, her
  1071.    hair like silver in some impossible moonlight—</p>
  1072.    <p>Rydell yanked the glasses off…</p></blockquote>
  1073.    <p>Quote:</p>
  1074.    <blockquote><p>“Here. Check it out.” He put them on her.</p>
  1075.    <p>She was facing the city when he did it. Financial district… “Fuck a <em>duck</em>,” she said, those towers blooming there,
  1076.    buildings bigger than anything, a stone regular grid of them, marching in from the hills. Each one maybe four blocks at the
  1077.    base, rising straight and featureless to spreading screens likke the colander she used to steam vegetables. Then Chinese writing
  1078.    filled the sky.</p>
  1079.    </blockquote>
  1080.    <h2 id='p-3'>Hmmm…</h2>
  1081.    <p>What does Gibson’s 30-year-old vision teach us?</p>
  1082.    <ul>
  1083.      <li><p>The devices are still heavier than you’d like, but light enough to wear all the time out in the real world.</p></li>
  1084.      <li><p>Still expensive.</p></li>
  1085.      <li><p>They look super-cool.</p></li>
  1086.      <li><p>They are transparent while in use.</p></li>
  1087.      <li><p>You can use them to show pictures or share information the way you would today by handing over a phone or
  1088.      tablet.</p></li>
  1089.      <li><p>How you get information <em>into</em> them was as un-solved in 1993 as it is today.</p></li>
  1090.      <li><p>But the real core value is the “A” in “AR”<span class='dashes'> —</span> <em>augmenting</em> an aspect of the real
  1091.      world that you’re looking at. Even if only by hanging text labels on it.</p></li>
  1092.    </ul>
  1093.    <p>For me, that last point is at the center of everything. I want to be in a park at night and see fiery snakes climbing all the
  1094.    trees. I want to walk into a big-box store and have a huge glowing balloon appear over the Baking Supplies. I want floating
  1095.    labels to attach to all the different parts of the machine I’m trying to fix.</p>
  1096.    <p>Watching TV, by yourself, on a huge screen, is not the future. Augmenting reality is.</p>
  1097.    <p>The AVP? Some of its tech constitutes
  1098.    necessary but far from sufficient steps on the way from here to that 1993 vision.</p>    
  1099. </div></content></entry>
  1100.  
  1101. <entry>
  1102. <title>DC Again</title>
  1103. <link href='https://www.tbray.org/ongoing/When/202x/2024/01/30/DC-Again' />
  1104. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/01/30/DC-Again#comments' />
  1105. <id>https://www.tbray.org/ongoing/When/202x/2024/01/30/DC-Again</id>
  1106. <published>2024-01-30T12:00:00-08:00</published>
  1107. <updated>2024-02-02T11:22:19-08:00</updated>
  1108. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Washington DC' />
  1109. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1110. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  1111. <category scheme='https://www.tbray.org/ongoing/What/' term='Washington DC' />
  1112. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>For the second time this winter I’ve been to Washington and back. Herewith pictures and feelings. Everyone’s     seen plenty of photos of The Capital City Of The United States so I’ve tried for fresh views.     My feelings are more mainstream than my pictures, I’m pretty sure; the stories DC tells aren’t subtle</div></summary>
  1113. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1114.    <p>For the second time this winter I’ve been to Washington and back. Herewith pictures and feelings. Everyone’s
  1115.    seen plenty of photos of The Capital City Of The United States so I’ve tried for fresh views.
  1116.    My feelings are more mainstream than my pictures, I’m pretty sure; the stories DC tells aren’t subtle.</p>
  1117.    <h2 id='p-1'>Apologies</h2>
  1118.    <p>I know folks in the region and I have standing offers from people whose taste I trust to introduce me to others whose
  1119.    company they’re sure I’d enjoy. I ignored those people and offers. Sorry about that, and I have an excuse. This trip was another
  1120.    <a href="/ongoing/When/202x/2023/07/24/Workin-for-the-Man">workin’ for The Man</a> episode (the man being Uncle Sam).
  1121.    Specifically, I was there for a seven-hour deposition by attorneys representing Meta. I felt this to be a
  1122.    Performance, one that mattered and therefore worthy of my full attention.  So I needed to get centered, be in the zone.
  1123.    To walk and think.</p>
  1124.    <p>Don’t ask me how the deposition went, I dunno. When you’re speaking at a conference or rally or whatever, if the audience laughs at
  1125.    your jokes you know it’s probably going well. But you don’t throw jokes at defendants’ lawyers.</p>
  1126.    <p>That’s all I’m gonna say. Once again, I hope there’ll be lurid rear-view blog fodder once this is over.</p>
  1127.    <h2 id='p-2'>The Wharf</h2>
  1128.    <p>This trip, like
  1129.    <a href="/ongoing/When/202x/2023/12/20/Travel-Notes">the last</a>, took me to DC’s    
  1130.    <a href="https://en.wikipedia.org/wiki/Southwest_Waterfront">Southwest Waterfront</a>
  1131.    district. Only this time, I visited the waterfront.  Here’s the view looking out.</p>
  1132.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240126_231729153.png" alt="View from the DC’s Wharf district" />
  1133.    <p>Or, I should properly say,
  1134.    <a href="https://en.wikipedia.org/wiki/The_Wharf_(Washington,_D.C.)">The Wharf</a>, as reflected below.</p>
  1135.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240127_002517001.png" alt="DC’s Wharf waterfront" />
  1136.    <p>It’s a walkway along the Potomac, several blocks long, backed by a solid wall of restaurants and bars. The first evening I
  1137.    went down there, it was a
  1138.    freakishly-warm 24°C and this Canadian enjoyed the hell out of a restaurant-patio dinner.  An <em>extremely expensive</em>
  1139.    dinner. I shouldn’t complain, because I was also happy walking along the river’s edge, and I made two different stranger
  1140.    couples happy by offering to take pictures of them in front of one waterfront vista or another. Few smiles are cheaper.</p>
  1141.    <p>So, I recommend the Wharf. But, it’s really expensive. Which highlights a problem I’m starting to have with Washington
  1142.    DC. Like my hometown, there’s far, far too much money there.</p>
  1143.    <h2 id='p-4'>Bad vibe</h2>
  1144.    <p>After I flew in, pretty late one evening, I hit the hotel bar for pizza and beer. Pretty weird: Two big TVs, one Fox
  1145.    and one CNN. A certain class of American White Male Person, generally bulgy and prosperous, vibing more on the Fox side, talking
  1146.    (I eavesdropped)
  1147.    about football in Atlanta suburbs and being the agent for George Lazenby and how they’d had to grovel before a powerful woman
  1148.    named Barbara because they’d done something stupid and their career was over unless Barbara absolved them. They all had Good
  1149.    Relationships with Important People who could Make Things Happen. If they hadn’t wanted to be eavesdropped they wouldn’t have
  1150.    talked so loud.</p>
  1151.    <h2 id='p-9'>Museums</h2>
  1152.    <p>The day before the Big Event I decided to tourist<span class='dashes'> —</span> there are all those museums, plus I wanted to
  1153.    get physically tired so that I’d sleep well. I started at
  1154.    <a href="https://hirshhorn.si.edu">the Hirschhorn</a> because I love ambitious contemporary art showplaces. Granted,
  1155.    when I visit them, usually at least half the work seems weak or irrelevant or deranged. I don’t care, I admire the ambition, a
  1156.    contemporary artist has to try going somewhere nobody’s ever gone before and of course the failure rate is high.</p>
  1157.    <p>These places often have big rooms featuring artists trying
  1158.    to do big things, visually or intellectually or both. It’s just a special kind of space, and when I leave a big contemporary gallery,
  1159.    the outside world seems sepia-toned, free of sharp mental edges.</p>
  1160.    <p>None of the current exhibits really shook my grip on reality, which is what good contemporary art is supposed to do, but I
  1161.    enjoyed my visit; here are a couple of snaps.</p>
  1162.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_153018747.png" alt="Sculpture by Simone Leigh" />
  1163.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_154620991.png" alt="Art installation by Jessica Diamond" />
  1164.    <div class='caption'><p>Above: <cite>Cupboard</cite> by
  1165.    <a href="https://hirshhorn.si.edu/exhibitions/simone-leigh/">Simone Leigh</a>.<br/>
  1166.    Below: From <cite>Wheel of Life</cite> by
  1167.    <a href="https://hirshhorn.si.edu/exhibitions/jessica-diamond-wheel-of-life/">Jessica Diamond</a>.</p></div>
  1168.    <p>I hit the National Archive museum: Disappointing, unless you regard America’s founding documents as sacred texts. In and of
  1169.    themselves, they’re not much to look at.</p>
  1170.    <p>Finally, the Museum of the American Indian. I found the collection a little thin, albeit with a clear-eyed view of all the
  1171.    lies and thefts and betrayals.  But, that name…</p>
  1172.    <h2 id='p-6'>The city</h2>
  1173.    <p>Washington is obviously kind of a company town and these days, most Federal departments only ask people to show their faces
  1174.    one day a week, usually Tuesday. It also suffers from the urban-American sin of being car-optimized, shot through with
  1175.    broad rivers of asphalt. Which, except for Tuesdays, are now pretty well empty. You can cross one of these six-lane behemoths
  1176.    more or less anywhere, any time. I understand the Mayor is furiously lobbying the Feds to arm-twist the civil servants back into
  1177.    the offices but it doesn’t look like it’s working.</p>
  1178.    <h2 id='p-7'>The National Mall</h2>
  1179.    <p>It’s the big grass strip between the Capitol and the Washington Monument, dotted with Smithsonia and, on a chilly damp
  1180.    weekend day, hosting several flag-football games, well-organized and offering flashes of real talent. Heart-warming, I thought. Also
  1181.    a temporary
  1182.    white structure with music coming out of it and a sign saying “David’s Tent”. Hey, random free music is an opportunity and the door
  1183.    was open. It turned out to be a Christian worship joint and there was this frowning dude alone on stage strumming and
  1184.    singing: “holy, holy, holy” over and over. I only stayed inside for a minute or two and that was a lot of holy holies. There were
  1185.    two people in the front row of the front section, and as for the rest…</p>
  1186.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_160057395.png" alt="Inside David’s Tent" />
  1187.    <p>They need a better product manager.</p>
  1188.    <p>Eventually I ended up on the Capitol steps, the same ones the Trumpers stormed that January 6th. Lots and lots of those
  1189.    sectional fences that failed so badly were still queued up there. I hoisted an end of one with one arm, no strain. I’m not sure
  1190.    what they’re for, actually.</p>
  1191.    <p>Anyhow, here’s the view down the Mall from there. You might want to enlarge it.</p>
  1192.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_175015603-Edit.png" alt="The National Mall, from the Capitol end" />
  1193.    <div class='caption'><p>This picture started out sort of dreamy and abstract, then I bashed the hell out of it with Lightroom
  1194.    and Silver Efex. I claim it looks like what I saw, only more so.</p></div>
  1195.    <h2 id='p-8'>Wandering back</h2>
  1196.    <p>To my hotel I mean. The route went by an endless cavalcade of Congressional office buildings. Here’s one: check out the flag
  1197.    deployments, I guess we know where those particular congresspeople stand.</p>
  1198.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_181505087.png" alt="House office building featuring Israeli flags" />
  1199.    <p>By this time, I’d touristed for enough hours that my feet were pretty sore and I was finding the serried office-block ranks sort of
  1200.    oppressive. Also, I was damn hungry, and then my life was saved by
  1201.    <a href="https://myownpizza.com">My Own Pizza</a>, entirely unpretentious, selling good pies for a good price. All the customers
  1202.    were tourists with kids or local blue-collar workers, which in DC means Black. Way better vibe than my hotel bar.</p>
  1203.    <p>On the last trudge of the day, this:</p>
  1204.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/30/PXL_20240128_183546249.png" alt="Homeless person asleep on an HVAC vent outside a Congressional office building" />
  1205.    <div class='caption'><p>Asleep on a vent that I guess offers warm air. It’s raining.</p></div>
  1206.    <p>These buildings host the wealthiest organization that has ever existed on this planet.</p>  
  1207. </div></content></entry>
  1208.  
  1209. <entry>
  1210. <title>Lofree Flow</title>
  1211. <link href='https://www.tbray.org/ongoing/When/202x/2024/01/20/Lofree-Flow' />
  1212. <link rel='replies'        thr:count='5'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/01/20/Lofree-Flow#comments' />
  1213. <id>https://www.tbray.org/ongoing/When/202x/2024/01/20/Lofree-Flow</id>
  1214. <published>2024-01-20T12:00:00-08:00</published>
  1215. <updated>2024-01-20T12:00:00-08:00</updated>
  1216. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology/Mac OS X' />
  1217. <category scheme='https://www.tbray.org/ongoing/What/' term='Technology' />
  1218. <category scheme='https://www.tbray.org/ongoing/What/' term='Mac OS X' />
  1219. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Back in 2008, I     <a href='/ongoing/When/200x/2008/07/22/On-Keyboards'>complained here about Apple keyboards</a>. Apple still hasn’t addressed     my complaint (hard to believe, I know). So, 15 years later, as in late 2023, I picked up a     <a href='https://www.lofree.co/products/lofree-flow-the-smoothest-mechanical-keyboard'>Lofree “Flow”</a>, which I gather had a     Kickstarter and advertises itself as “The smoothest mechanical keyboard”. I’ve been using it     long enough to offer opinions</div></summary>
  1220. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1221.    <p>Back in 2008, I
  1222.    <a href="/ongoing/When/200x/2008/07/22/On-Keyboards">complained here about Apple keyboards</a>. Apple still hasn’t addressed
  1223.    my complaint (hard to believe, I know). So, 15 years later, as in late 2023, I picked up a
  1224.    <a href="https://www.lofree.co/products/lofree-flow-the-smoothest-mechanical-keyboard">Lofree “Flow”</a>, which I gather had a
  1225.    Kickstarter and advertises itself as “The smoothest mechanical keyboard”. I’ve been using it
  1226.    long enough to offer opinions.</p>
  1227.    <p>The problem with Apple keyboards is illustrated by the picture below; The Lofree is in the middle.</p>
  1228.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/20/PXL_20240120_000316073.png" alt="Three wireless keyboards, two from Apple one from Lofree" />
  1229.    <p>They’re all wireless. While the small Apple product at the bottom is <em>really</em> old, today’s equivalent has the same
  1230.    problems: There are no Home, End, PgUp, and PgDn keys, and the arrow keys are annoyingly small.
  1231.    The larger Apple at the top wastes space on the accountants’ number pad.</p>
  1232.    <p>The LoFree is small enough and has the keys I want.</p>
  1233.    <h2 id='p-1'>Why?</h2>
  1234.    <p>There are several places where I work regularly, and none of them feature a large desk, to the extent that if I have one or more
  1235.    of coffee, printed document, camera, or whatever else on the desk, things get crowded.  So small is good.</p>
  1236.    <p>Also, I use the navigation keys but never the number grid.</p>
  1237.    <p>Also, those last few years at AWS a few of the engineers near where I sat had fancy keyboards with multiple colors and would
  1238.    argue about key-feel options.</p>
  1239.    <p>Now, I generally like Apple keyboards and managed to avoid buying any of the infamous “butterfly” models. But there was this
  1240.    <a href="https://www.theverge.com/23965283/lofree-flow-low-profile-keyboard-review">rave review</a> in <cite>The Verge</cite>
  1241.    and I was trying to avoid some boring work that I was supposed to do, and there was a Black Friday sale, so here I am, my fingers
  1242.    now laying down a mellow rhythm section behind the creation of the prose melody you are now reading.</p>
  1243.    <h2 id='p-2'>What’s good</h2>
  1244.    <p>The feel and the sound. I got the tactile “Phantom” keys rather than the linear “Ghost” option, so I can’t report on the
  1245.    latter, but I don’t play twitchy games and the consensus seems to be that tactile is good for a fast touch typist. I’m not as
  1246.    blindingly fast as I used to be but I’m still north of 100wpm. It may be relevant that I have big fat farmer’s
  1247.    fingers and have always hit keyboards pretty hard.</p>
  1248.    <p>I’m struggling a bit for vocabulary to describe how this thing feels. I’ll settle for
  1249.    “eager”<span class='dashes'> —</span> the keys feel like they’re working with me to inject these blogwords into the
  1250.    noösphere.</p>
  1251.    <p>As for the sound, it’s just delicious; low but distinct, and to my ears, euphonious.</p>
  1252.    <h2 id='p-3'>Obvious problems</h2>
  1253.    <p>You might as well work with the thing plugged in, because the battery isn’t big enough and (perhaps to compensate) the
  1254.    Bluetooth goes to sleep quickly and (when unplugged) wakes up slowly.</p>
  1255.    <p>The backlighting is lousy; it illuminates the edges of the keys adequately, but the letterforms only weakly.  (Which for a
  1256.    touch typist is usually not a problem.) The “ambient” lighting is ridiculous; think of the flames on Wayne and Garth’s
  1257.    Mirthmobile. And if you have the lights turned up it runs the battery
  1258.    down even faster.</p>
  1259.    <p>I should mention that the enthusiast community is annoyed that they have trouble (on some systems) customizing the keyboard
  1260.    layout, and that the selection of key options is limited. My
  1261.    <a href="/ongoing/When/202x/2020/04/25/Mac-Migration#p-10">modestly-customized Mac keyboard layout</a> just worked.</p>
  1262.    <h2 id='p-4'>Mobility</h2>
  1263.    <p>My biggest problem is that switching back and forth between the Lofree and an Apple keyboards makes my fingers clumsy for
  1264.    enough minutes to
  1265.    be annoying.  Easy enough, just carry the Lofree around. It’s not big and despite the metal-not-plastic frame, is
  1266.    acceptably light.  Except for, there isn’t a carrying case on offer. Which feels like a real miss.</p>
  1267.    <h2 id='p-5'>Success?</h2>
  1268.    <p>Oh, definitely. Typing on it makes me happy. None of the problems interfere much given the way I use it. I guess the nav
  1269.    buttons are a little small but my fingers are starting to know where they are. Those big fat arrow keys are great. No, I’m not going
  1270.    to tumble over the edge onto the slippery slope of keyboard obsession. But this first step turned out fine.
  1271.    </p>
  1272. </div></content></entry>
  1273.  
  1274. <entry>
  1275. <title>Mourning Google</title>
  1276. <link href='https://www.tbray.org/ongoing/When/202x/2024/01/15/Google-2024' />
  1277. <link rel='replies'        thr:count='24'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/01/15/Google-2024#comments' />
  1278. <id>https://www.tbray.org/ongoing/When/202x/2024/01/15/Google-2024</id>
  1279. <published>2024-01-15T12:00:00-08:00</published>
  1280. <updated>2024-01-18T19:08:33-08:00</updated>
  1281. <category scheme='https://www.tbray.org/ongoing/What/' term='Business/Google' />
  1282. <category scheme='https://www.tbray.org/ongoing/What/' term='Business' />
  1283. <category scheme='https://www.tbray.org/ongoing/What/' term='Google' />
  1284. <category scheme='https://www.tbray.org/ongoing/What/' term='Technical/Google' />
  1285. <category scheme='https://www.tbray.org/ongoing/What/' term='Technical' />
  1286. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>On March 15, 2010, I     <a href='/ongoing/When/201x/2010/03/15/Joining-Google'>started a new job at Google</a>. The fourteen years since that day feel like     a century.     The title of my announcement     was <cite>Now A No-Evil Zone</cite> and, OK, I can hear the laughing from ten timezones away. I tried, then, to be restrained,     but there are hardly words to describe how happy and excited I was. I had escaped from the accretion disk the former Sun     Microsystems was forming around Oracle, that blackest of holes. And Google, in 2010, was the coolest place in the world to     work</div></summary>
  1287. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1288.    <p>On March 15, 2010, I
  1289.    <a href="/ongoing/When/201x/2010/03/15/Joining-Google">started a new job at Google</a>. The fourteen years since that day feel like
  1290.    a century.
  1291.    The title of my announcement
  1292.    was <cite>Now A No-Evil Zone</cite> and, OK, I can hear the laughing from ten timezones away. I tried, then, to be restrained,
  1293.    but there are hardly words to describe how happy and excited I was. I had escaped from the accretion disk the former Sun
  1294.    Microsystems was forming around Oracle, that blackest of holes. And Google, in 2010, was the coolest place in the world to
  1295.    work.</p>
  1296.    <p>Let me quote myself from a little bit further into that piece, on the subject of Google: “I’m sure that tendrils of stupidity
  1297.    and evil are even now finding interstitial breeding grounds whence they will emerge to cause grief.”  Well, yeah.</p>
  1298.    <p>This is in my mind these days as I’m on a retired-Googlers mailing list where the current round of layoffs is under
  1299.    discussion and, well, it really seems like the joy has well and truly departed the Googleplex.</p>
  1300.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/15/abc-xyz.png" alt="Alphabet Investor Relations" />
  1301.    <div class='caption'><p>But they did.<br/>(The Alphabet “Investor Relations” page<br/>is also its home page.)</p></div>
  1302.    <h2 id='p-4'>It’s not just Google</h2>
  1303.    <p>The last two decades of my career featured the arcing then crashing of popular regard for Big Tech. It’s
  1304.    hard to believe now, the years when those lovably nerdy Bay Area kids were leading humanity to a brighter,
  1305.    better-lit future; our leaders were lionized and when people found out you actually worked for Google, their eyes widened and you
  1306.    could feel the focus.</p>
  1307.    <p>These days, Big Tech features in hostile congressional hearings, mass layoffs, and messy antitrust litigation. It offers
  1308.    few experiences that can be uncritically enjoyed.</p>
  1309.    <p>While I was inside the Rooms Where It Happened, it was actually pretty hard to notice the public trust in our work auguring
  1310.    into the mountainside of alienation and cynicism.   It’s not that I think the companies are the problem, it’s the machineries
  1311.    and imperatives of Late Capitalism, which for a while we foolishly thought Internet companies could route around.</p>
  1312.    <h2 id='p-1'>“Ten blue links”</h2>
  1313.    <p>I remember the dismissive phase well: Ten blue links was boring, it was the past, it was not what people wanted.
  1314.    They want answers to their questions, complete and correct, so much more wholesome than an abbreviated sampling
  1315.    of the General Internet Uproar. And that was partly right: When I type in “-12C in F” or “population of vietnam” I just want a
  1316.    number.</p>
  1317.    <p>But those Ten Blue Links surfaced by the PageRank-that-was had a special magic. I found them intensely human, a
  1318.    reflection of the voices populating what remains of the Web, the only platform without a vendor. This was true when I was there
  1319.    and I said so, but was laughed at.</p>
  1320.    <p>And now, in Anno Domini 2024, Google has lost its edge in search. There are plenty of things it can’t find. There are
  1321.    compelling alternatives. To me this feels like a big inflection point, because around the stumbling feet of the Big Tech
  1322.    dinosaurs, the Web’s mammals, agile and flexible, still scurry. They exhibit creative energy and strongly-flavored voices, and
  1323.    those voices still sometimes find and reinforce each other without being sock puppets of shareholder-value-focused private
  1324.    empires.</p>
  1325.    <h2 id='p-3'>Psychopaths</h2>
  1326.    <p>For my money, that was the center of Google’s problem. Larry and Sergey were smart guys who recognized they didn’t know shit
  1327.    about corporateness and quickly got into a pattern of hiring and empowering psychotic pricks who were presumably “good at
  1328.    business”.  Not gonna talk about some of the things I saw because these
  1329.    people are wealthy and litigious.</p>
  1330.    <p>But I do have a question.</p>
  1331.    <h2 id='p-7'>What to use?</h2>
  1332.    <p>Among Google products, I mean.  These days, when I use Google Search or Chrome or Maps I just don’t feel like they’re on my
  1333.    side. And maybe that’s not unreasonable; after all, I’m not paying for them. Problem is, the best alternatives aren’t
  1334.    obvious.</p>
  1335.    <p>For now, here’s the direction I think I’m going: Use Chrome for Google stuff: Maps, Calendar, Docs, Translate. Safari and
  1336.    Firefox for non-Google stuff; they ain’t perfect but I think they’re better aligned with my interests.</p>
  1337.    <p>Our family company is still on Google Workspace or whatever it is they call Dasher these days: Mail, Contacts, Photos,
  1338.    Calendar, Meet. It’s OK. We pay for it and the price is sane. I don’t feel like it’s looking for ways to monetize each
  1339.    keystroke. I’d totally consider a less-scary alternative.</p>
  1340.    <p>I fear the combination of Google Maps and Reviews because it
  1341.    <a href="/ongoing/When/201x/2017/06/29/Fear-Google-Reviews">stinks of monopoly</a>. But I use Maps anyhow in my car via Android
  1342.    Auto because it’s nicely integrated with YouTube Music (which
  1343.    <a href="/ongoing/When/202x/2021/07/17/Music-Notes">I like</a>) and Google Calendar. For a while I used the Here.com maps
  1344.    and liked them a lot. I guess I could listen to YouTube over Bluetooth.</p>
  1345.    <p>Did I mention Android? I can’t stop using it, because I used to work in that building and because I decline to use iOS;
  1346.    If I wrote code for it I might not be able to give it away. And I carry Pixel phones, because I love the
  1347.    cameras.  Having said that, hearing Andy Rubin’s name still makes my
  1348.    gut clench. </p>
  1349.    <p>I love YouTube because I end most evenings, after everyone’s gone to bed, with a live musical performance by someone
  1350.    wonderful. But enshittification is creeping in at the edges.</p>
  1351.    <h2 id='p-6'>That cafe</h2>
  1352.    <p>In 2012 I moved from Android to Google’s Identity group. It happened to be in the same buildings as Google+, at
  1353.    a time when Google was definitely putting all its wood behind that arrow. Larry and Sergey’s offices were there too (not a
  1354.    coincidence). There was a major fringe benefit: Access to the Cloud Café.</p>
  1355.    <p>It was ethereal<span class='dashes'> —</span> OK, pretentious<span class='dashes'> —</span> almost beyond belief. Almost
  1356.    entirely vegetarian, rare plants hand-gathered by Zen monks and assembled into jewel-like little platelets-full that probably
  1357.    strengthened eleven different biochemical subsystems just by existing. And the desserts were beyond divine. Admittedly, sometimes
  1358.    when I left, my Norwegian-farmer metabolism grumbled a bit about not having had any <em>proper food</em>, but still.</p>
  1359.    <p>It was wonderful. It was absurd. And I got a $90K bonus that year because Google+ hit its numbers.</p>
  1360.    <p>It’s over, I think. It’s OK to miss it.</p>
  1361. </div></content></entry>
  1362.  
  1363. <entry>
  1364. <title>Five Electric-Jag Years</title>
  1365. <link href='https://www.tbray.org/ongoing/When/202x/2024/01/03/Five-Jaguar-Years' />
  1366. <link rel='replies'        thr:count='4'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/01/03/Five-Jaguar-Years#comments' />
  1367. <id>https://www.tbray.org/ongoing/When/202x/2024/01/03/Five-Jaguar-Years</id>
  1368. <published>2024-01-03T12:00:00-08:00</published>
  1369. <updated>2024-01-05T08:52:25-08:00</updated>
  1370. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Jaguar Diary' />
  1371. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1372. <category scheme='https://www.tbray.org/ongoing/What/' term='Jaguar Diary' />
  1373. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>I got a note from Jaguar advising that my free five-year “InControl Remote     and Protect” subscription was expiring and would be $99/year (Canadian) going forward. That’s right, this month is five years     since     <a href='/ongoing/When/201x/2019/01/13/My-I-Pace'>I picked up our 2019 Jaguar I-Pace</a> and joined the EV tribe. Thus this     (final?) visit to the <a href='/ongoing/What/The%20World/Jaguar%20Diary/'>Jaguar Diary</a> series</div></summary>
  1374. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1375.    <p>I got a note from Jaguar advising that my free five-year “InControl Remote
  1376.    and Protect” subscription was expiring and would be $99/year (Canadian) going forward. That’s right, this month is five years
  1377.    since
  1378.    <a href="/ongoing/When/201x/2019/01/13/My-I-Pace">I picked up our 2019 Jaguar I-Pace</a> and joined the EV tribe. Thus this
  1379.    (final?) visit to the <a href="/ongoing/What/The%20World/Jaguar%20Diary/">Jaguar Diary</a> series.</p>
  1380.    <h2 id='p-1'>$99, you say?!</h2>
  1381.    <p>Yeah. What you get is a mobile app (and Web site) that does useful things, including:</p>
  1382.    <ul>
  1383.      <li><p>Turn on the climate control to warm or chill the car while you’re having breakfast. This is a big deal in Canada.</p></li>
  1384.      <li><p>Make it honk so you can find it in a big parkade.</p></li>
  1385.      <li><p>Check whether you remembered to lock it, and do so if you didn’t.</p></li>
  1386.      <li><p>Keep a diary of all your trips, which is nice and I guess super-useful if you expense your driving.</p></li>
  1387.    </ul>
  1388.    <p>Since several of these require that Jaguar operate servers (hey,
  1389.    <a href="https://isitonaws.com/discover?name=incontrol.jaguar.com">on AWS in Dublin</a>) I guess I shouldn’t mind paying. Feels a
  1390.    little pricey but hey, I bought a Jag so I shouldn’t care? And I wouldn’t, except for they’re almost certainly harvesting
  1391.    data from the car like crazy and selling it. Which I call double-dipping.</p>
  1392.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/03/DSCF1325.png" alt="2019 Jaguar I-Pace" />
  1393.    <h2 id='p-2'>What about the car?</h2>
  1394.    <p>I have not regretted buying it for a single second of those five years. It’s comfy, faster than strictly necessary, reliable,
  1395.    practical, and cheap to run, even with that extra $99/year. Go read the other
  1396.    <a href="/ongoing/What/The%20World/Jaguar%20Diary/">diary entries</a> for that stuff. I guess the only thing to add is that,
  1397.    five years in, it still feels pretty well new. It’s fun to drive.  The battery seems to hold about the same number of
  1398.    kilometres.</p>
  1399.    <h2 id='p-3'>But
  1400.    <a href="https://mastodon.social/tags/waroncars">#WarOnCars</a>!</h2>
  1401.    <p>These days, my social-media feed contains many people who point out that Cars Are Bad and the spaces humans live in
  1402.    should be optimized for humans, and you Really Shouldn’t Like Cars.</p>
  1403.    <p>And I agree, mostly. I totally want to choke cars out of the spaces we live in, to create a fifteen-minute city. Simultaneously, I
  1404.    like cars for their own sake, for their engineering and aesthetics, for the joy of being able to go from my front door to
  1405.    <a href="/ongoing/When/202x/2021/08/05/Western-Electric">anywhere else on the continent</a> while
  1406.    seated comfortably, listening to good music.</p>
  1407.    <p>Yes, those viewpoints are in conflict but so what. People, statistically, also like alcohol and nicotine and speeding
  1408.    and adultery and Reality TV and junk food.  And can agree, abstractly, that indeed, those things are bad.
  1409.    It all comes down to
  1410.    <a href="/ongoing/When/202x/2022/11/28/On-Algorithms">protect me from what I want</a>.</p>
  1411.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/03/PXL_20240101_200154745.png" alt="2019 Jaguar I-Pace" />
  1412.    <p>There are two problems: First, the entire western edge of North America was built around sprawl and highways. Second, Late
  1413.    Capitalism’s egregious inequality has arranged that it’s hard for most people to afford to live near their jobs, or even where
  1414.    the public transit is good.</p>
  1415.    <p>So yeah, as we develop our cities, let’s exclude cars to the extent possible.
  1416.    And let’s do something about the economy too. I will vote for
  1417.    regulations that restrict my use of my car. And to the #WarOnCars troops: I’m on your side, but don’t tell me I shouldn’t like
  1418.    them.</p>
  1419.    <p>To start with, here’s a free idea: There should be a charge for occupying city space with your car, and it should depend
  1420.    heavily on the car’s size and weight.</p>
  1421.    <h2 id='p-5'>EV trends</h2>
  1422.    <p>I suspect that central
  1423.    Vancouver has one of North America’s highest EV densities. On our block, our side of the street, are a Nissan Leaf, a
  1424.    Tesla, a Hyundai Kona EV, and me. And there’s frequently a Rivian parked out front, don’t know where it lives. In fact I’m
  1425.    starting to see a lot of Rivians.  If you need a truck, the Rivian looks like a nice one, but I don’t think people in this
  1426.    neighborhood do.</p>
  1427.    <p>When I bought the Jag I was worried it was like buying a PC in the Nineties; wait six months and there’ll be
  1428.    something way better.  I got to test that hypothesis because a good friend just picked up a
  1429.    <a href="https://en.wikipedia.org/wiki/Hyundai_Ioniq_6">Hyundai Ioniq 6</a>, 2023 World Car of the Year. We
  1430.    went for a drive and yeah, the state of the art has improved.</p>
  1431.    <p>The Ioniq is, and feels, lighter than the
  1432.    Jag. It charges a lot faster. Its Android Auto implementation is nicer. The dashboard graphics are gracefully space-age. The
  1433.    shifter is clever and intuitive. No, it doesn’t have the Jag’s raw power or silky way through turns. But on balance, it is
  1434.    really a whole lot of car for the money. I’d buy one.</p>
  1435.    <p>The most important electric vehicles aren’t going to be personal automobiles. They’re going to be the buses and trains that
  1436.    eventually come to fill in the public-transit grid and turn cars into rarely-needed luxury options. They’re going to
  1437.    be the trucks that are currently a huge source of carbon loading.</p>
  1438.    <p>Cars will be with us for a while. But they should be lighter and smaller and fewer. And electric.</p>
  1439. </div></content></entry>
  1440.  
  1441. <entry>
  1442. <title>Happy New Year!</title>
  1443. <link href='https://www.tbray.org/ongoing/When/202x/2024/01/01/New-Years-Day' />
  1444. <link rel='replies'        thr:count='3'        type='application/xhtml+xml'        href='/ongoing/When/202x/2024/01/01/New-Years-Day#comments' />
  1445. <id>https://www.tbray.org/ongoing/When/202x/2024/01/01/New-Years-Day</id>
  1446. <published>2024-01-01T12:00:00-08:00</published>
  1447. <updated>2024-01-02T14:41:48-08:00</updated>
  1448. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Photos' />
  1449. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  1450. <category scheme='https://www.tbray.org/ongoing/What/' term='Photos' />
  1451. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Places/Vancouver' />
  1452. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1453. <category scheme='https://www.tbray.org/ongoing/What/' term='Places' />
  1454. <category scheme='https://www.tbray.org/ongoing/What/' term='Vancouver' />
  1455. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Customarily, on this day we go for a walk by the sea. This year “we” was just me, because Post-Covid. I     have pictures; subdued pictures, it was that sort of day. Herewith a few of those, and year-end     ramblings on optimism, AI/ML, cameras, and social media</div></summary>
  1456. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1457.    <p>Customarily, on this day we go for a walk by the sea. This year “we” was just me, because Post-Covid. I
  1458.    have pictures; subdued pictures, it was that sort of day. Herewith a few of those, and year-end
  1459.    ramblings on optimism, AI/ML, cameras, and social media.</p>
  1460.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/PXL_20240101_202023416.png" alt="Bare tree against grey sky, New Year’s Day, 2024, Vancouver" />
  1461.    <h2 id='p-1'>Optimism?</h2>
  1462.    <p>The climate catastrophe is gonna get worse before it starts getting better. But I see rays of light that might
  1463.    illuminate 2024. I really don’t think the Americans are going to elect That Guy again. I think unemployment will
  1464.    stay low and worker power will increase correspondingly.  I think there’s a significant chance we get a vaccine that actually
  1465.    stops Covid transmission, as opposed to today’s, which mostly just moderate its effects (still important of course). I think the
  1466.    health problems in my immediate family will improve a bit<span class='dashes'> —</span> Lauren is showing early signs of recovery from
  1467.    Post-Covid.</p>
  1468.    <p>Did I mention the climate catastrophe? I hope our political leaders come to their senses, get out from under
  1469.    the Carbon Hegemony, and do the necessary things that will necessarily bankrupt much of the Petroleum
  1470.    sector.  If they don’t, I think it near-inevitable that some of those defending the planet’s future will discard their
  1471.    commitment to non-violence. There is nothing people won’t do to protect their children.</p>
  1472.    <p>Weirdly, and assuming that our species’ self-inflicted climate-disaster injuries aren’t fatal, there is an upside. This
  1473.    situation falsifies  the central premise of Late Capitalism: That continued unending growth is essential, or even
  1474.    desirable. Particularly in the inevitable case where declining birthrates become pervasively global and there are
  1475.    fewer people each year needing goods and services.</p>
  1476.    <p>Put another way: Jeff Bezos can
  1477.    <a href="https://www.aboutamazon.com/news/company-news/2016-letter-to-shareholders">blow off “Day 2”</a> as much as he
  1478.    wants. But the Day-1 growth-at-all-costs dogma isn’t sustainable or even survivable. Day 2 is inevitable, and we need to learn
  1479.    how to make it good.</p>
  1480.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/DSCF1293.png" alt="Waterfront with ships and people, New Year’s day, 2024, Vancouver" />
  1481.    <h2 id='p-2'>AI/ML</h2>
  1482.    <p>I’ve spent my working life in software, and AI seems to be the only thing anyone wants to talk about. I’m not smart enough to
  1483.    know where this tech ends up fitting in. Also, I’m arrogant: I don’t think anyone else is smart enough
  1484.    either. It’s painfully obvious that we’re in the midst of a bubble; just watch the VC froth. A lot of that money is going to
  1485.    the same place as the billions they gave to the crypto-bros.</p>
  1486.    <p>I do have a recommendation: Assuming you’re busy and have a lot of input, don’t waste time reading “future of AI”
  1487.    predictions. Nobody knows.</p>
  1488.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/DSCF1312.png" alt="Duck in pond, New Year’s day, 2024, Vancouver" />
  1489.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/DSCF1314.png" alt="Duck in pond, New Year’s day, 2024, Vancouver" />
  1490.    <h2 id='p-3'>Photography</h2>
  1491.    <p>When I went down to the sea, I took a Fujifilm X-Cam with the
  1492.    <a href="/ongoing/When/201x/2018/01/20/Samyang-135mm-F2">Samyang 135mm/F2</a> bolted on, and of course my Pixel.  All but one of
  1493.    these pictures are Fuji/Samyang.  This is my chance to opine, once again, that the best way to use a camera that’s not
  1494.    a phone is to strap a difficult and opinionated lens on it then follow where it leads.</p>
  1495.    <p>I’m not that optimistic about the future of “real” cameras. When you watch the reviews from passionate camera-philes like
  1496.    <a href="https://www.youtube.com/@PetaPixel">Chris and Jordan over at Petapixel</a>, you realize that, to the extent that newer
  1497.    cameras are better, the improvement is at the margins; for example, shooting elite athletes at a distance. All modern cameras
  1498.    take great pictures, most times. This notably includes the one in your phone; but its lens is the opposite of difficult.</p>
  1499.    <p>2023 saw two real steps forward in camera technology:
  1500.    <a href="/ongoing/When/202x/2023/10/28/C2PA-Workflows">C2PA</a> and
  1501.    <a href="/ongoing/When/202x/2023/11/10/Global-Sensor">global shutter</a>. Global shutter is cool but of interest to only a few,
  1502.    and C2PA’s impact is strictly on the structure of belief; the technology itself is boring.  Neither will help you get a
  1503.    better cat picture.</p>
  1504.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/DSCF1289.png" alt="Polar-bear swimming, New Year’s day, 2024, Vancouver" />
  1505.    <img src="https://www.tbray.org/ongoing/When/202x/2024/01/01/DSCF1310.png" alt="Polar-bear swimming, New Year’s day, 2024, Vancouver" />
  1506.    <h2 id='p-4'>Social media</h2>
  1507.    <p>Most of my 2023 hours were filled by family health issues, my
  1508.    <a href="/ongoing/When/202x/2023/07/24/Workin-for-the-Man">expert-witness gig with Uncle Sam</a>, and what comes after Twitter.
  1509.    On the latter, I know only one thing for sure: That privately-owned centralized social media has not worked, will not work, can
  1510.    not work. Decentralized
  1511.    federation is the only sane path forward and we are right now making that up as we go along. Am I crazy to think that few things
  1512.    matter more than the forces that shape the broader human conversation?</p>
  1513.    <p>I know that if you’ve been reading me at all, you’ve heard this enough, but forgive me, it’s too late to stop now: I think the
  1514.    member-owned social-media co-op we’re building at
  1515.    <a href="https://cosocial.ca">CoSocial</a> offers a plausible glimpse of a resilient, fun, billionaire-proof social-media
  1516.    future.  I’m an old guy but I’m as excited as a kid about this path forward.</p>
  1517.    <h2 id='p-5'>This space</h2>
  1518.    <p>2024 will be this blog’s 21<sup>st</sup> year of operation. No month has had fewer than three pieces and my hope is
  1519.    to do as well or better going forward.  Not writing feels like not breathing.</p>
  1520.    <p>During the latter half of 2023, I produced two large
  1521.    legal submissions in connection with my Uncle-Sam gig, well over 400 pages in total. They are stuffed full of confidential
  1522.    information and will be read by only a small handful of people, then forgotten. That makes me sad, but producing them was still
  1523.    fun.</p>
  1524.    <p>Back in 2018, I wrote enough
  1525.    <a href="/ongoing/What/Song%20of%20the%20Day/">Song of the Day</a> pieces to fill a half-year’s days, and enjoyed it a lot. Most of
  1526.    the material was old; I was mining my own personal musical journey. Nothing wrong with that.</p>
  1527.    <p>But these last few years, I’ve been listening to lots of new music and, once Uncle Sam has settled down, I’ll play a
  1528.    variation: Music of the Day.  Most of it will be new-ish or at least new to me. And up front, I confess that most of that is
  1529.    driven by YouTube Music guessing what Tim might like.  So don’t let anyone tell you I’m against AI in the general case.</p>
  1530.    <h2 id='p-6'>Happy 2024, and good luck!</h2>
  1531.    <p>We’re going to need it.</p>
  1532. </div></content></entry>
  1533.  
  1534. <entry>
  1535. <title>Planes, Cameras, Capitals</title>
  1536. <link href='https://www.tbray.org/ongoing/When/202x/2023/12/20/Travel-Notes' />
  1537. <link rel='replies'        thr:count='1'        type='application/xhtml+xml'        href='/ongoing/When/202x/2023/12/20/Travel-Notes#comments' />
  1538. <id>https://www.tbray.org/ongoing/When/202x/2023/12/20/Travel-Notes</id>
  1539. <published>2023-12-20T12:00:00-08:00</published>
  1540. <updated>2023-12-22T15:44:10-08:00</updated>
  1541. <category scheme='https://www.tbray.org/ongoing/What/' term='The World/Travel' />
  1542. <category scheme='https://www.tbray.org/ongoing/What/' term='The World' />
  1543. <category scheme='https://www.tbray.org/ongoing/What/' term='Travel' />
  1544. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Since Covid started I haven’t traveled, except for a short hops to visit Mom in Saskatchewan.     But I spent Monday and Tuesday in Washington DC     <a href='/ongoing/When/202x/2023/07/24/Workin-for-the-Man'>workin’ for The Man</a> (the man being Uncle Sam) and came away with     notes on planes and hotels and cameras and people</div></summary>
  1545. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1546.    <p>Since Covid started I haven’t traveled, except for a short hops to visit Mom in Saskatchewan.
  1547.    But I spent Monday and Tuesday in Washington DC
  1548.    <a href="/ongoing/When/202x/2023/07/24/Workin-for-the-Man">workin’ for The Man</a> (the man being Uncle Sam) and came away with
  1549.    notes on planes and hotels and cameras and people.</p>
  1550.    <h2 id='p-8'>First, camera news</h2>
  1551.    <p>The rest of this piece is miscellaneous travel notes, aimed at people who are interested in Washington DC or the travel
  1552.    experience. But you might want to skim through it anyhow for the pictures. As usual, I traveled with a
  1553.    camera bag containing an excellent Fujifilm
  1554.    and a variety of lenses. I never broke it out.  The results from the
  1555.    <a href="/ongoing/When/202x/2023/06/09/Pixel-4-to-7">Pixel 7</a> are just unreasonably good.</p>
  1556.    <img src="https://www.tbray.org/ongoing/When/202x/2023/12/20/PXL_20231218_235826135.png" alt="A back alley in Southwest Washington, DC" />
  1557.    <div class='caption'><p>See the moon?
  1558.    This picture should hardly even be possible. It was dusk, the contrast was stark, the moon fetching but
  1559.    faint, and the sky very dark. It only took a little Lightrooming to prettify the sky and sharpen a bit.</p></div>
  1560.    <h2 id='p-5'>DC</h2>
  1561.    <p>I’ve always liked DC and this time I was in a new neighborhood,
  1562.    <a href="https://en.wikipedia.org/wiki/Southwest_Waterfront">Southwest Waterfront</a>, which is pretty nice even with too many
  1563.    large Federal agencies.</p>
  1564.    <img src="https://www.tbray.org/ongoing/When/202x/2023/12/20/PXL_20231218_235724078.png" alt="A residential street in Southwest Washington, DC." />
  1565.    <div class='caption'><p>A residential street in Southwest Waterfront, near the alley in the previous picture.  It has a bit of a
  1566.    fakey “HDR” look but that’s actually what it looked like, the traditional streetlights work well with the stone frontage.
  1567.    I posted these
  1568.    two pictures, and another nearby,
  1569.    <a href="https://cosocial.ca/@timbray/111604375436241665">on Mastodon as a quiz</a>,
  1570.    challenging people to identify the city. One frighteningly-smart person
  1571.    did.</p></div>
  1572.    <p>There are cities that feel unwelcoming, but DC isn’t one of them. On the way
  1573.    from the airport to my hotel via (excellent!) public transit I got lost twice, consulted a taxi dispatcher and random cop for
  1574.    help. I had a shopping mission where I needed guidance from big-store staff. I ate a couple of solo dinners, tucked into the corners of
  1575.    large-ish establishments at unpopular times to minimize plague risk.  Nobody made me feel like I was bothering them, everyone
  1576.    was happy to help, and in the empty-ish restaurants, staff dropped by to just shoot the shit a bit.</p>
  1577.    <p>100% of the people I’m talking about were Black. Just a coincidence?</p>
  1578.    <p>By the way, I heartily recommend
  1579.    <a href="https://www.waltersdc.com">Walter’s Sports Bar</a><span class='dashes'> —</span> I figured that since I was in the
  1580.    Nation’s Capital, the most American possible thing to have would be a burger in a sports bar. The place is comfy, the food
  1581.    is fine, and,  as noted, the people are nice.</p>
  1582.    <h2 id='p-3'>What happened?</h2>
  1583.    <p>On this sort of trip, I’d normally write up the payload<span class='dashes'> —</span> the meat of the meetings and the
  1584.    shape of the work.  But it is, as they say, “the subject of current litigation.” I promise, assuming I remain of sound mind
  1585.    after this is over, to share as much as I legally can. It should entertain.</p>
  1586.    <h2 id='p-4'>Plague protection</h2>
  1587.    <p>Given that each episode of Covid incurs a 5-10% chance of progress to some flavor of Long Covid, which my wife is already suffering
  1588.    from, and that the top medical recommendation for Long Covid sufferers is “Don’t get Covid again”, I was extra ultra paranoid
  1589.    about the possibility of infection. So I wore a KN95 in all public indoor spaces, to the extent possible, which means except
  1590.    when I was actually putting food or drink in my mouth. As I write this, I won’t know for a few more days whether or not it
  1591.    worked.</p>
  1592.    <p>Other people? not so much. The entire population has decided to “put Covid behind them” I guess. I can’t begin to understand
  1593.    how they see the trade-offs. I don’t think I’m crazy and it’d be ungenerous to think that everyone else is.</p>
  1594.    <h2 id='p-1'>Enviro-sinner</h2>
  1595.    <p>I can’t write about this without addressing the environmental issues. A handy
  1596.    <a href="https://flightfree.org/flight-emissions-calculator">online flight-emissions calculator</a> suggests this little jaunt
  1597.    worsened the global CO<sub>2</sub> problem by 1.4 metric tons. Ouch.</p>
  1598.    <p>I could point out that this level of sin is a tiny pale shadow of what I committed in my decades of jet-setting on
  1599.    behalf of one employer or another, or that my trip, in support of presumably-worthy high-stakes litigation, was of benefit to
  1600.    the species. Doesn’t really make it OK. I am now lobbying The Man to make future meetings virtual rather than physical.</p>
  1601.    <h2 id='p-2'>Planes</h2>
  1602.    <p>Meh. Like many things in life, the experience on offer has declined over the decades, as the “business
  1603.    class” experience has simultaneously improved; a symptom of our society’s current insanely-dysfunctional level of inequality.
  1604.    Since I have a vast
  1605.    inventory of points left over from my jet-set phase, I upgraded both ways. Shoot me. Or, shoot out the window.</p>
  1606.    <img src="https://www.tbray.org/ongoing/When/202x/2023/12/20/PXL_20231220_005328837.png" alt="Toronto from the air" />
  1607.    <img src="https://www.tbray.org/ongoing/When/202x/2023/12/20/PXL_20231220_005338130.png" alt="Toronto from the air" />
  1608.    <div class='caption'><p>These pictures are miraculous, shot through a not-terribly-clear airplane window with backing light trying to
  1609.    reflect off it. This is the first time the “computational photography” power of a Pixel has scared me a bit, because the picture
  1610.    actually looks quite a bit better than what my eyes saw. And that was before I juiced it up with Lightroom. Hmmm.</p></div>
  1611.    <p>I simultaneously miss travel and have enjoyed the past few years of not fighting airlines and airports; my long-held belief is
  1612.    that this is an
  1613.    <a href="/ongoing/When/200x/2007/03/30/Wrath-of-Heaven">industry that hates its customers</a>.  I have reserved a special level
  1614.    of hate for Toronto’s Terminal 1.</p>
  1615.    <p>Thus, you can imagine my surprise when my rollie busted a wheel in DC and I decided to check it through to Vancouver, and they just
  1616.    <em>checked it through</em>! No need to do the recover-and-recheck in Toronto. And also, you can come in from the US and go out
  1617.    again on domestic without passing through security. I guess I must tip my hat to my old enemy.</p>
  1618.    <p>Oh, and (noted reluctantly) more good news. The video system on one leg of the flight was Android-based (telltale boot
  1619.    screen) and wow, it was miles better than any previous in-flight entertainment experience. I knew about Android Auto, but I
  1620.    guess there’s now Android Airplane. So the pilots can say “OK Google, land on runway 23”? I hope it doesn’t need a reliable
  1621.    USB-C connection.</p>
  1622.    <img src="https://www.tbray.org/ongoing/When/202x/2023/12/20/PXL_20231218_013819145.png" alt="Postmodern hotel room" />
  1623.    <h2 id='p-7'>Postmodern hotel</h2>
  1624.    <p>How can a hotel be interesting?  This chain I’d never heard of that I’m not gonna name had rooms right across the street
  1625.    from work and the reviews were good and the price was good. I’m not naming them because I think their concept is sound
  1626.    but they haven’t nailed the execution yet.  The idea is that the rooms are teeny-tiny (like I’ve
  1627.    experienced in Japan) but on the ground level there’s this huge sprawling “Living Room” with lots of desks and sofas and tables
  1628.    and a big TV lounge and a bar with decent basic food. The decor is breathlessly hip everywhere.</p>
  1629.    <p>I watched Monday Night Football there, enjoying the company of a Mexican-American family who were crushed when Seattle pulled off that
  1630.    absurd last-minute win over Philadelphia; tears were shed on Jalen-Hurts-branded jerseys.</p>
  1631.    <p>Also, excellent breakfast.</p>
  1632.    <p>I think they might be onto something, except for I had a hard time sleeping because the duvet was too thick and the pillows
  1633.    were too thick, so I was cooking and my neck was hurting.</p>
  1634.    <p>I filled out the feedback form and got an email from a real person, so maybe it’ll get better. I mean, the core competence of
  1635.    a hotel has to be getting you a good night’s sleep, so this isn’t an excusable miss.  Anyhow, it’s years since I’ve stayed at a
  1636.    hotel that wasn’t a boring beige cookie-cutter.</p>
  1637.    <h2 id='p-9'>Travel!</h2>
  1638.    <p>It’s what humans do; go read
  1639.    <a href="https://en.wikipedia.org/wiki/The_Songlines">Bruce Chatwin</a>. I’ve missed it. But, to be enjoyed in moderation.</p>
  1640. </div></content></entry>
  1641.  
  1642. <entry>
  1643. <title>Recent Music Books</title>
  1644. <link href='https://www.tbray.org/ongoing/When/202x/2023/12/11/Recent-Music-Books' />
  1645. <link rel='replies'        thr:count='4'        type='application/xhtml+xml'        href='/ongoing/When/202x/2023/12/11/Recent-Music-Books#comments' />
  1646. <id>https://www.tbray.org/ongoing/When/202x/2023/12/11/Recent-Music-Books</id>
  1647. <published>2023-12-11T12:00:00-08:00</published>
  1648. <updated>2023-12-12T14:47:43-08:00</updated>
  1649. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Books' />
  1650. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts' />
  1651. <category scheme='https://www.tbray.org/ongoing/What/' term='Books' />
  1652. <category scheme='https://www.tbray.org/ongoing/What/' term='Arts/Music' />
  1653. <category scheme='https://www.tbray.org/ongoing/What/' term='Music' />
  1654. <summary type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>Seems that for the past few months most of the books I’ve read have been sci-fi (which I wrote up     <a href='/ongoing/When/202x/2023/12/10/Recent-Sci-Fi'>here</a>) or about music. Herewith notes on four of the     latter. The subjects are Philip Glass, John Cale, Cuba, and getting loaded</div></summary>
  1655. <content type='xhtml'><div xmlns='http://www.w3.org/1999/xhtml'>
  1656.    <p>Seems that for the past few months most of the books I’ve read have been sci-fi (which I wrote up
  1657.    <a href="/ongoing/When/202x/2023/12/10/Recent-Sci-Fi">here</a>) or about music. Herewith notes on four of the
  1658.    latter. The subjects are Philip Glass, John Cale, Cuba, and getting loaded.</p>
  1659.    <h2 id='p-1'>Glass</h2>
  1660.    <p><cite>Words Without Music</cite> is
  1661.    <a href="https://philipglass.com">Philip Glass’s</a> autobiography. I should start by saying that I’m a big fan,
  1662.    bought lots of albums back in the day. For anyone unfamiliar with the flavor, I recommend the following: Open up your favorite
  1663.    streaming service and say “Play <cite>Mishima</cite> by Philip Glass”. You’ll know pretty quick whether you like it.  If you
  1664.    do, you won’t be alone; I don’t have hard data but I think Phil is probably the best-selling practitioner of “New Music”,
  1665.    i.e. contemporary stuff that isn’t Pop music.</p>
  1666.    <p>I caught a live concert too, Phil and the Philip Glass Ensemble, in which he plays but doesn’t lead; (Early editions of the
  1667.    Ensemble included Steve Reich on keys.) They performed the
  1668.    <a href="https://en.wikipedia.org/wiki/Koyaanisqatsi">Koyaanisqatsi</a> sound-track while the movie played.
  1669.    What a sound!</p>
  1670.    <p>Any Glass fan is going to want to read this, I think.  But it’s not problem-free. First: He talks tons about his
  1671.    process and his high-level thinking about putting his music together, but zero about its music-theory basis.  By the way, one
  1672.    reason he’s so prolific is that he doesn’t have to write a Master Score as he composes: He just holds the music in his head and
  1673.    writes out the individual parts, one by one. I saw a documentary once which showed him writing musical lines at a comfortable
  1674.    handwriting speed, saying with an amused expression “This part, you see, this part goes pretty fast.”</p>
  1675.    <p>Second, it’s a
  1676.    depressing reminder of how deeply the Reagan-Thatcher dogma has savaged the fabric of our society. Glass was a bright kid in a
  1677.    middle-class family who
  1678.    went from an elite public school to an elite college with Nobel-Laureate teachers, then to an elite music school, then to
  1679.    Paris to study at the feet of Nadia Boulanger. The Paris section, by the way, is an astonishing read; Whatever
  1680.    you think of his music, the man studied his craft with heroic intensity.  Then he settled in New York and by,
  1681.    moving furniture and driving taxi, earned enough to rent a loft and compose furiously, turning the world of “New Music” inside
  1682.    out. Try to pull that off today. Everything’s been financialized and efficiency-maximized and there’s little space left
  1683.    for variant shoots of any art form to thrive then twist them sideways.</p>
  1684.    <p>Oh, another irritant: Most of the book is written in an extremely transparent flat-aspect style, which gets out of the way
  1685.    and I respect, and I was thinking “good solid prose, it’s a pity Phil doesn’t try to reach back and bring it a little bit, like
  1686.    he does in his music.” And then in the very last chapter, he does. Here’s a paragraph, relating his reaction when asked about
  1687.    what it felt like when composing one of his big pieces:</p>
  1688.    <blockquote><p>I don’t know … Because I’m not sure that I am there at that moment. The ordinary witness has been
  1689.    lost <span class='dashes'> —</span> the artist Philip has robbed the daily Philip of his ability to see himself. That’s very
  1690.    clearly what happens when people say “I wrote it in a dream,” or “I don’t know where the music came from. … All they’re really
  1691.    saying is “I don’t remember how I did it,” and they make up an outside source. But the real source is not any of those
  1692.    things. It’s a process that the artist has learned. He has tricked himself into gaining that extra attention that he needed to
  1693.    do the work.</p></blockquote>
  1694.    <p>I kinda wished that Phil had let loose some of that writing energy on more parts of the book. Whatever, it’s a valuable piece
  1695.    of the historical record.</p>
  1696.    <h2 id='p-2'>Cale</h2>
  1697.    <p><a href="https://john-cale.com">John Cale</a>, a Welshman, is a founding member of the Velvet Underground and one of life’s Really
  1698.    Interesting People. Disclosure: His album
  1699.    <a href="https://en.wikipedia.org/wiki/Sabotage/Live">Sabotage/Live</a> is central to the way I think of music: Live is
  1700.    better. Loud is better. Terrifying is best. I stage-managed one of the concerts on the tour that album showcases; that show
  1701.    went severely off the rails in a way that gives me a distant echo of PTSD all these decades later. I may write about it some
  1702.    year.</p>
  1703.    <p>Anyhow, I’m here to write about <cite>What’s Welsh For Zen</cite>, a sort of autobiography, in large format with plenty of
  1704.    photography and art splashed across all the pages. I wanted to read it and discovered that it’s only available used and for
  1705.    hundreds of dollars. So I took it out of the
  1706.    <a href="https://vpl.ca">public library</a> for free; isn’t it great to be a member of a civilization?</p>
  1707.    <p>Anyhow, Cale was a member of the same white-hot New York art scene that Phil Glass was, only with Lou Reed and Andy Warhol and
  1708.    lots of drugs. Boy, does John ever hate Lou. But he invests a lot of words in explaining what kind of a person Lou is and what it’s
  1709.    like to work with him. Or try to. Whatever, they produced some pretty fucking wonderful music together. Nobody ever said making
  1710.    art had to be fun.</p>
  1711.    <p>Cale’s portrayal of Warhol is way kinder. What I notice, looking back all these decades, is
  1712.    that everyone I’ve read writing about Warhol seems to be describing a different person.  Warhol managed the Underground for a
  1713.    while and it’s pretty clear that some of the ideas he brought to their oeuvre, in particular performance practices, have become
  1714.    integral to popular music at large.</p>
  1715.    <p>Anyhow, Cale plays a significant but not leading role in the story of how Rock music became what it is today. I’m glad that
  1716.    he put all this stuff on the record.</p>
  1717.    <h2 id='p-3'>Getting loaded</h2>
  1718.    <p>In Vancouver’s library system you go online, you find the book you want, you put it on hold, and after a while you get an
  1719.    email telling you it’s arrived at your local branch. Whenever I bike over there I go look at the featured-books shelves and
  1720.    occasionally pick one up.</p>
  1721.    <p>When I was picking up the Phil Glass book I noticed
  1722.    <a href="https://www.bloomsbury.com/ca/too-late-to-stop-now-9781448218257/">Too Late To Stop Now: More Rock’n’Roll War
  1723.    Stories</a> by Allan Jones, who spent decades in the pop-music journalism profession, back when you could make a decent living
  1724.    in journalism of many flavors.  This is, um, extremely lightweight, mostly tales of the author ingesting massive quantities of
  1725.    alcohol and cocaine and weed while hanging out with Rock Stars you might have heard of. Parts of it work well for an oldster
  1726.    like me because we remember the rage and excitement in the air when the New Wave swept away Prog Rock. Boy, does Mr Jones hate
  1727.    anything even remotely prog-related and, to be fair, those geezers kinda brought it on themselves.  Anyhow, what saves it is that he’s
  1728.    consistently funny.</p>
  1729.    <p>There’s a connection: One of the segments covers an extended conversation with John Cale, which re-iterates the awfulness of
  1730.    working with Lou Reed, but in this matter Cale comes off better through a third-party pen than his own.  Anyhow, if you
  1731.    were listening to music in the late Seventies this has a good chance of going deep on some artist you really cared about. And it
  1732.    might open your ears to something new; in my case, to the work of
  1733.    <a href="https://en.wikipedia.org/wiki/Roy_Harper_(singer)">Roy Harper</a>, whom I’d heard of but not actually heard, and now I
  1734.    have and am glad of it.</p>
  1735.    <h2 id='p-4'>Cuba</h2>
  1736.    <p>What happened was, I was watching a YouTube of a live concert by
  1737.    <a href="https://rhiannongiddens.com">Rhiannon Giddens</a>, which I recommend doing because she is by the way totally a
  1738.    goddess. She tends to chat at the audience a bit between songs, and in connection with something I totally forget, she
  1739.    recommended
  1740.    <a href="https://www.chicagoreviewpress.com/cuba-and-its-music-products-9781556526329.php">Cuba and Its Music: From the First
  1741.    Drums to the Mambo</a>, by
  1742.    <a href="https://en.wikipedia.org/wiki/Ned_Sublette">Ned Sublette</a>. I thought it sounded interesting. During the depths of
  1743.    Covid’s first wave, I took a few months of private Afro-Cuban music lessons via Zoom; bought a nice pair of Congas, even.  I
  1744.    recommend this for anyone who’s even a bit musically literate and interested in rhythm.  Just learning about
  1745.    the <a href="https://en.wikipedia.org/wiki/Clave_(rhythm)">Clave rhythm</a> and
  1746.    <a href="https://en.wikipedia.org/wiki/Bell_pattern">Bell pattern</a>, and a bit of <i>son</i> and <i>rumba</i> lore,  changed
  1747.    the way I think about rhythms. If you’re ever doing rhythm in a jam, throwing in a bit of clave feel will make everything
  1748.    magically funkier.</p>
  1749.    <p>So, I recommend this book, but… wow, it’s huge. It’s “only” 688 pages, the listing says (I read it in the Kindle app on my
  1750.    tablet) but it feels twice as long; took me weeks to finish.  It is monumentally thorough; by the time you’re finished, you will
  1751.    be damn erudite on the history and culture of Cuba from the Pre-Columbian era through to the Fifties.  It’s advertised as being
  1752.    “Part 1” but was published in 2004, so I’m not sure about Part 2.</p>
  1753.    <p>The Spanish organized-crime mob<span class='dashes'> —</span> I’m talking about Columbus and
  1754.    his successors<span class='dashes'> —</span> pretty well wiped out Cuba’s Indigenous population (although I learned in writing
  1755.    this that there are people who to this day claim to be
  1756.    <a href="https://en.wikipedia.org/wiki/Taíno">Taíno</a> and preserve that culture). Thus, there remain four input streams that
  1757.    intertwined to create Cuba’s remarkably-rich mix of language and religion and especially music:</p>
  1758.    <ul>
  1759.      <li><p>Spanish, which, given the dates, included strains of…</p></li>
  1760.      <li><p>Moorish, being the still-strong influence of
  1761.      <a href="https://en.wikipedia.org/wiki/Al-Andalus">Al-Andalus</a>.</p></li>
  1762.    </ul>
  1763.    <p>Then there were the enslaved Africans; they were not just
  1764.    one people, but from a variety of nations, and brought along with them two main currents of language and musical
  1765.    culture:</p>
  1766.    <ul>
  1767.      <li><p>The first, from West Africa’s southern coast<span class='dashes'> —</span> think of the range from Côte d'Ivoire to
  1768.      Benin, which was itself complex, including flavors from the coastline and then up into the Sahel, where once again there was
  1769.      a Muslim/Arabic influence, and last but definitely not least,</p></li>
  1770.      <li><p>The Congo, a general term here for southern Africa‘s eastern shore: Equatorial Guinea down to Angola.</p></li>
  1771.    </ul>
  1772.    <p>In Cuba, the Church was less efficient in its proselytizing than elsewhere in the New World, and thus the African religions,
  1773.    and even bits and pieces of the languages, survive and have a hefty influence on some of Cuba’s musics. Yes,
  1774.    that’s musics, plural; it’s not just one thing at all.</p>
  1775.    <p>Anyhow, to get the beginnings of a feel for the feel, type “Arsenio Rodriguez” or “Tito Puente” into your favorite music
  1776.    source and see what happens.</p>
  1777.    <p>Am I ever happy to have read this book, and if I don’t stop now, this blog piece will start to inherit its punishing length
  1778.    and complexity.  I’ve probably said enough for you to make a good guess whether it’s for you.</p>
  1779.    <h2 id='p-5'>Meta-music</h2>
  1780.    <p>I already have a couple of shelves of books on music, a high proportion being biographical, and reading these outings
  1781.    reminded me of why.  Books on music is a habit I recommend.</p>
  1782. </div></content></entry>
  1783.  
  1784. </feed>
  1785.  

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