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

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