[Valid RSS] This is a valid RSS feed.


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


  1. <?xml version='1.0' encoding='UTF-8' ?>
  2. <rss version="2.0"
  3.    xmlns:atom=""
  4.    xmlns:dc=""
  5.    xmlns:sy="">
  7. <channel>
  8. <title>Greg's diary</title>
  9. <link></link>
  10. <atom:link href=""
  11. rel="self" type="application/rss+xml" />
  12. <description>Greg Lehey's online diary</description>
  13. <dc:creator />
  14. <dc:date>2024-04-22T13:19:39+10:00</dc:date>
  15. <dc:rights>Copyright 2015, 2016, 2017, 2018 Greg Lehey</dc:rights>
  16. <!-- for Emacs, this is a -*- mode: fundamental; coding: utf-8 -*- document -->
  17. <!-- temporary file, entries for last 7 days of previous month, used for RSS version -->
  19. <!-- topic G not selected
  20.      <p>
  21. It has now been <a href=";article=D-20240322-003739#D-20240322-003739">four days</a> since I had my cataract surgery.  Things are going completely according to
  22. plan, but it's still an interesting experience.  The bubble in my eye is gradually becoming
  23. smaller, and in the process the magnification effect is diminishing.  <a href=";subtitle=A%20new%20eye&amp;article=D-20240323-015848#D-20240323-015848">On Friday</a> it was about 10 dioptres, and now it can't be more than 1.5 dioptres.  And
  24. the real vision seems to be shifting in focus too.  Hopefully by the time the bubble is gone
  25. (tomorrow?  Wednesday?), the focus will be as intended.
  26.      </p>
  28.      <p>
  29. And apart from that, the floaters are interesting too.  Initially they looked like flies
  30. flying around, but now they're longer and joined.  Today I saw one, very thin and in L shape
  31. that covered about half the field of view and gradually moved into the bubble.  Presumably
  32. they'll all go away with the bubble.  But still it's irritating, and it's keeping me from
  33. doing anything useful.
  34.      </p>
  36. End deselected topic G (Eye recovery) -->
  39. <!-- topic pGo not selected
  40.      <p>
  41. When I visited <a href="">David Fabinyi</a> <a href=",%20second%20opinion&amp;article=D-20240201-014854#D-20240201-014854">in January</a>, I mentioned <a href="">depth of field</a>, and I got the impression that he hadn't heard the term before.  But
  42. it's important for my decision on what kind of vision aids I will need.  Of to search the
  43. web.  Yes, strangely the term doesn't seem to be in use for human optics.  What about
  44. <a href="">hyperfocal distance</a>?
  45. Also barely a mention.  It's not because the concepts don't apply—on the contrary, they're
  46. just as relevant.  So why?
  47.      </p>
  49.      <p>
  50. It seems that there's only one paper on the subject, “<a href="">The Depth of Field of the Human
  51. Eye</a>”, written by Fergus William Campbell in 1959, and only available for significant
  52. quantities of money.  Then there are discussions like <a href="">this one</a>, which refer to dead links and come out with claims like “Hyperfocal
  53. distance of human eye is 6 or 7 meters in indoor light”.  That would correspond to a depth
  54. of field of about 12 cm at 60 cm distance.  Could that be right?  Elsewhere I saw a similar
  55. claim, except that it was in feet.  So somehow I'm no closer to an answer.
  56.      </p>
  58. End deselected topic pGo (Depth of field?  Hyperfocal distance?) -->
  61. <item>
  62. <guid isPermaLink='true'></guid>
  63. <link></link>
  64. <category>technology</category>
  65. <category>photography</category>
  66. <category>opinion</category>
  67. <title>Where am I?</title>
  68.  <description>
  69.    <![CDATA[
  70.    <div align="justify">
  71.      <p>
  72. One of the recurring themes in film series that we watch is that somebody gets lost (in the
  73. Alps, for example).  They have mobile phone connection, but they don't know where they are.
  74.      </p>
  76.      <p>
  77. That's simple: all modern phones have a <a href="">GPS</a> module that can identify where they are to within a couple of metres.  And there
  78. are silly things like <a href="">Plus Codes</a> that convert the output into incomprehensible codes.
  79.      </p>
  81.      <p>
  82. That's nonsense, of course.  The phone should be able to send its location coordinates with
  83. every call, or on a call-by-call basis for the paranoid.  But its not available anywhere
  84. that I can see.  I've ranted about this numerous times, most recently <a href="!&amp;article=D-20220821-014415#D-20220821-014415">in August 2022</a>.
  85.      </p>
  87.      <p>
  88. But the matter of the <a href="">RAT</a> <a href=";article=D-20240320-212343#D-20240320-212343">last week</a> got me thinking.  Mobile phones always (as far as I can tell) embed the
  89. current GPS coordinates in every photo.  And with only a moderate amount of coaxing you can
  90. not only get the information, but pass it on to <a href="">Google Maps</a>!
  91.      </p>
  93.      <div align="left">
  94.  <a id="Photo-0" name="Photo-0"
  95.          href="diary-mar2024.php?dirdate=20240327&amp;imagesizes=2&amp;topics=c#Photo-0">
  96.          <img alt="This should be Android-image-fail-3.jpeg.  Is it missing?" border="0" id="Photo_0"
  97.               title="Photo Android-image-fail-3.jpeg.  Click to redisplay larger version of image."
  98.               src=""
  99.               width="300" height="225"
  100.           /></a>
  101.  <a id="Photo-1" name="Photo-1"
  102.          href="diary-mar2024.php?dirdate=20240327&amp;imagesizes=12&amp;topics=c#Photo-1">
  103.          <img alt="This should be Android-image-fail-6-detail.jpeg.  Is it missing?" border="0" id="Photo_1"
  104.               title="Photo Android-image-fail-6-detail.jpeg.  Click to redisplay larger version of image."
  105.               src=""
  106.               width="228" height="297"
  107.           /></a>
  108.  <a id="Photo-2" name="Photo-2"
  109.          href="diary-mar2024.php?dirdate=20240327&amp;imagesizes=112&amp;topics=c#Photo-2">
  110.          <img alt="This should be Android-image-fail-7.jpeg.  Is it missing?" border="0" id="Photo_2"
  111.               title="Photo Android-image-fail-7.jpeg.  Click to redisplay larger version of image."
  112.               src=""
  113.               width="177" height="384"
  114.           /></a>
  115.      </div>
  117.      <p>
  118. Isn't that nice? <i>Finally</i> something that works.
  119.      </p>
  121.      <p>
  122. Well, almost.  I suppose it's modern that Google Maps gets the address wrong (it relates to
  123. something at the top of the screen, under the coordinates).  But more to the point, it only
  124. works when you don't need it.  This is a photo taken on my own phone.  What about a photo
  125. sent with the messaging app?  Tried that with <a href="">Yvonne's</a> phone
  126. and got:
  127.      </p>
  129.        <a id="Photo-3" name="Photo-3"
  130.          href="diary-mar2024.php?dirdate=20240327&amp;imagesizes=1112&amp;topics=c#Photo-3">
  131.          <img alt="This should be Android-image-fail-8-detail.jpeg.  Is it missing?" border="0" id="Photo_3"
  132.               title="Photo Android-image-fail-8-detail.jpeg.  Click to redisplay larger version of image."
  133.               src=""
  134.               width="302" height="223"
  135.           /></a>
  137.      <p>
  138. No <a href="">Exif</a> data!  And look at the
  139. image sizes.  Yvonne's phone is effectively the same as mine, but the image has been reduced
  140. from 12 MP to 1.9 MP (a variable which it's too polite to mention).  About the only useful
  141. piece of information there is the path name, for which I had seaarched in vain with
  142. inadequate tools through the <a href="">Android</a> directory
  143. hierarchy.
  144.      </p>
  146.      <p>
  147. So: once again Android fail.  I can understand the paranoia of so many people who
  148. don't <i>want</i> their location to be known, but it should be easier than this, at least as
  149. an option.
  150.      </p>
  152.      <p>
  153. One day I'll find something really good about Android.  I'll be amazed.
  154.      </p>
  155.      </div>
  156.    ]]>
  157.  </description>
  158.  <dc:creator>Greg Lehey</dc:creator>
  159.  <dc:date>2024-03-27T01:35:53+00:00</dc:date>
  160. </item>
  163. <item>
  164. <guid isPermaLink='true'></guid>
  165. <link></link>
  166. <category>technology</category>
  167. <category>opinion</category>
  168. <title>Blacklist removal: success</title>
  169.  <description>
  170.    <![CDATA[
  171.    <div align="justify">
  172.      <p>
  173. Yesterday I received mail from Wendy Bartlett, whom I knew at <a href="">Tandem Computers</a>.  Replied, or at
  174. least I tried to:
  175.      </p>
  177.      <blockquote class="fullwidth">
  178. <div style="text-align:left">
  179.  <tt>
  180. &lt;;: host ff&#45;ip4&#45;mx&#45;[]
  181. <br />&nbsp;&nbsp; &nbsp;said: 553 5.3.0 flpd594 DNSBL:RBL 521&lt; &gt;_is_blocked.For
  182. <br />&nbsp;&nbsp; &nbsp;assistance forward this error to abuse_rbl@abuse&#45; (in reply to MAIL
  183. <br />&nbsp;&nbsp; &nbsp;FROM command)
  184.  </tt>
  185. </div>
  186. </blockquote>
  188.      <p>
  189. Damn, will this never end?  For the sake of completeness, sent a message
  190. to <tt></tt> to say that I was just an innocent bystander.
  191.      </p>
  193.      <p>
  194. Surprise, surprise:
  195.      </p>
  197.      <blockquote class="fullwidth">
  198. <div style="text-align:left">
  199.  <tt>
  200. Thank you for contacting the AT&amp;T Postmaster.
  201. <br />
  202. <br />The mail&#45;server IP address(es) associated with your request will be removed from the block list within 24&#45;48 hours from the date of this letter. AT&amp;T and its affiliates do NOT intentionally block legitimate mail in the course of our anti&#45;spam initiatives and regret any inconvenience this may have caused.
  203. <br />
  204.  </tt>
  205. </div>
  206. </blockquote>
  208.      <p>
  209. And yes, now it works!  I think this is the first time that I have been successful in such
  210. an appeal.
  211.      </p>
  212.      </div>
  213.    ]]>
  214.  </description>
  215.  <dc:creator>Greg Lehey</dc:creator>
  216.  <dc:date>2024-03-28T01:07:19+00:00</dc:date>
  217. </item>
  220. <!-- topic Go not selected
  221.      <p>
  222. My eye continues to improve.  The bubble is still there, but barely.  Hopefully it will soon
  223. be completely gone, and the new floaters with it.
  224.      </p>
  226.      <p>
  227. Today <a href="">Yvonne</a> went shopping and picked up some reading glasses
  228. for me.  We had carefully measured the distance from my head to monitor and established that
  229. it was about 60 to 62 cm.  That falls clearly between 67 cm (1.5 dioptres) and 57 cm (1.75
  230. dioptres).  I suggested getting one set of each power if we could return one.
  231.      </p>
  233.      <p>
  234. That didn't happen: nobody had 1.75 dioptre glasses on offer.  So she came back with a 1.5
  235. dioptre pair.  But that's not an issue: I couldn't focus to 67 cm with them, more like 40
  236. cm.  That corresponds to 2.5 dioptres!  And no, it's not the reading glasses.  They focus
  237. images from outside at exactly 67 cm.
  238.      </p>
  240.      <p>
  241. So it seems that currently, at any rate, my right eye is short-sighted by about 1 dioptre.
  242. Is that intentional?  Is that what <a href="">David
  243. Fabinyi</a> meant <a href=";subtitle=A%20new%20eye&amp;article=D-20240323-015848#D-20240323-015848">when he said</a> that “the lens focus is set to slightly shorter than infinity”?  1
  244. dioptre isn't “slightly shorter”, it's considerably short-sighted.  Hopefully things will
  245. improve.
  246.      </p>
  248.      <p>
  249.      </p>
  251. End deselected topic Go (Eye progress) -->
  254. <!-- topic Go not selected
  255.      <p>
  256. The bubble in my eye has been reducing in size, as advertised, but it was still there at
  257. 8:00 this morning.  I had hoped that it would have been gone by yesterday at the latest. But
  258. then I went back to bed for an hour or so, and at 9:00 it was gone.
  259.      </p>
  261.      <p>
  262. All OK now?  Not really.  The floaters are still there, probably as many as before, just
  263. longer strands now.  And I <i>still</i> can't see clearly when reading the monitor (with the
  264. reading glasses) or watching TV (without glasses in the right eye).  I can't make up my mind
  265. whether the focal length is increasing or not.  I can no longer see my outstretched hand
  266. clearly, so it could be, but it seems still to be less than the 3.5 m or so distance to the
  267. TV, indicating 0.3 <a href="">dioptres</a> or
  268. more.
  269.      </p>
  271.      <p>
  272. And then there's an unexpected additional issue.  Walking the dogs today, with only
  273. non-prescription sunglasses, I had difficulty aligning the view from each eye.  The image
  274. for the left eye was higher than for the right eye.  I had noticed this <a href=";subtitle=Seeing%20more%20clearly&amp;article=D-20240324-004100#vision-skew">on Saturday</a>, but attributed it to the glasses.  On the other hand, how could the
  275. operation cause this kind of issue?  Off-centre lens?
  276.      </p>
  278.      <p>
  279. Is this going to go away?  If not, I have two choices: have the lens replaced (and hope that
  280. it'll be better next time) or wear glasses all the time, one of the things that I had hoped
  281. to avoid.  But there's not much point in coming to any decisions now.  I certainly wouldn't
  282. have anything done until after the other eye has been done, and even that looks less likely
  283. to happen on the appointed date 11 April: <a href="">David Fabinyi</a> won't be available before then, and his locum is unlikely to be able to
  284. help.  Hopefully things will clear up before then.  I don't want the present situation to
  285. last too long.
  286.      </p>
  288.      <p>
  289. Received a card (credit card size) in the mail today, with no further comment.  It seems
  290. that I have a TECNIS™ Eyehance with TECNIS Simplicity™ Delivery System DI800.  What a lot of
  291. meainingless buzzwords!  About the only thing of interest is that the lens has a power
  292. of <b>+</b>21.5D, which doesn't really say very much about where the focus is set.
  293.      </p>
  295. End deselected topic Go (Bursting the bubble) -->
  298. <!-- topic ho not selected
  299.      <p>
  300. Petra Gietz helps us with the cleaning in the house.  She takes her job seriously:
  301.      </p>
  304.      <p>
  305.      </p>
  307. End deselected topic ho (I clean everything) -->
  310. <!-- topic aho not selected
  311.      <p>
  312. <a href="">Bruno</a> is the first cat we've had who
  313. isn't allowed outside.  It's clear that he doesn't like the restriction.
  314.      </p>
  316.      <p>
  317. For some time <a href="">Yvonne</a> has been suggesting that we cover over
  318. the dog pen behind her bedroom.  I've been reluctant because I couldn't see a way of really
  319. ensuring that Bruno can't get out of it.  But of course there are people who make cages for
  320. exactly that.  <a href="">Yvonne</a> came up with these:
  321.      </p>
  323.      <div>
  324. <a href="">The Cat Shack</a>      </div>
  326.      <div>
  327. <a href="">Pet Nets</a>      </div>
  329.      <p>
  330. Jesse Walsh is planning to build one for his own cats, and he's prepared to do the work for
  331. us too, so it sounds like a good idea to let him do his first.  Then we can take a look at
  332. it and get a better feeling for what needs to be done.
  333.      </p>
  335. End deselected topic aho (A cage for Bruno) -->
  338. <!-- topic k not selected
  339.      <p>
  340. I've had a somewhat strained relationship with <a href="">Sweet and sour fish</a>, but <a href="">Yvonne</a> had asked for it, so off to try things out again.
  341.      </p>
  343.      <p>
  344. <a href=";article=D-20231117-010606#D-20231117-010606">Last time</a> I had come to the conclusion that deep frying is the way to go, so that's
  345. what I did today.  I also added garlic for the first time.  I had always noted that there
  346. was no garlic, and I considered it a feature, but maybe it's a bug after all.  Certainly it
  347. tasted good with the garlic, to the point that Yvonne commented on how good it was this
  348. time.  As usual, I'm still not completely happy.  It wasn't until I updated the recipe
  349. afterwards that I discovered I had forgotten one detail: “reduce the quantity of sauce”.
  350.      </p>
  352. End deselected topic k (Sweet and sour fish, yet again) -->
  355. <!-- topic ko not selected
  356.      <p>
  357. While looking for something else, probably with <i>locate</i>, discovered a directory
  358. <a href="">/grog/recipes/alt.gourmand/recipes</a> that seems to have been on my
  359. system for ever.  It contains over 500 recipes and appears to be a snapshot of the
  360. <a href="">USENET Cookbook</a>.  Files
  361. had <a href="">troff</a> markup:
  362.      </p>
  364.      <blockquote class="fullwidth">
  365. <div style="text-align:left">
  366.  <tt>
  367. <code><font color="blue">=== grog@hydra (/dev/pts/28)</font> <font color="red">~/public_html/recipes/alt.gourmand/recipes</font> <font color="blue">56</font> &#45;&gt; <b><tt>grog gravlax</tt></b></code>
  368. <br />groff &#45;mm gravlax
  369. <br />
  370.  </tt>
  371. </div>
  372. </blockquote>
  374.      <p>
  375. Are they of any use?  None of the ones that I saw seemed very interesting.  And though the
  376. Wikipedia article considers it a pioneering attempt at <a href="">Electronic Publishing</a>, the
  377. dates of the recipes (1985 to 1989) overlap considerably with my own <a href="">COSIG</a> recipe collection.
  378.      </p>
  380. End deselected topic ko (Recipe treasure trove) -->
  383. <item>
  384. <guid isPermaLink='true'></guid>
  385. <link></link>
  386. <category>general</category>
  387. <category>technology</category>
  388. <category>opinion</category>
  389. <title>Open letter to the New York Times</title>
  390.  <description>
  391.    <![CDATA[
  392.    <div align="justify">
  394.      <p>
  395. To any human at the <a href="">New York
  396. Times</a>:
  397.      </p>
  399.      <p>
  400. TL;DR: I'm not receiving email, and I can't find any way to report it.  I don't consider a
  401. “Customer Care” only available in the middle of the night to be acceptable.  Please fix.
  402.      </p>
  404.      <p>
  405. In more detail: I've had a digital subscription to the <a href="">New York Times</a> for over 6 years, and
  406. I've found it a useful resource.  But today it occurred to me that I hadn't received any
  407. email from them for “a while”, How long?  Well, you keep bombarding my old email address
  408. with subscription offers that aren't as good as the one I have, but in the last week the
  409. only message I had to the real email address was an excruciatingly long survey.
  410.      </p>
  412.      <p>
  413. Looking back further, it seems that I haven't received anything for 9 days.  The last log
  414. entry (with modified recipient address) was:
  415.      </p>
  417.      <blockquote class="fullwidth">
  418. <div style="text-align:left">
  419.  <tt>
  420. Mar 21 16:44:19 lax postfix/qmgr[863]: 5C95728099: from=&lt;;, size=36475, nrcpt=1 (queue active)
  421. <br />Mar 21 16:44:20 lax postfix/smtp[47810]: 5C95728099: to=&lt;;,[]:25, delay=1.3, delays=0.03/0.01/0.55/0.75, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 1B41E2635C7)
  422.  </tt>
  423. </div>
  424. </blockquote>
  426.      <p>
  427. What's going on?  I still have access to the site, and I receive messages on my mobile
  428. phone.  Check my settings on the web site.  All OK, though I'm still subscribed to a
  429. discontinued newsletter.  OK, delete that and wait for the confirmation email.  It didn't
  430. even try.
  431.      </p>
  433.      <p>
  434. OK, try the help pages.  Nothing useful, no way to contact a human being.  With some
  435. difficulty I found <a href="">Contact information for international subscribers</a>, which gives me a free call number
  436. in Australia, 1800-170-145, available today from 22:00 to 6:00, exactly the time when I'm
  437. asleep.
  438.      </p>
  440.      <p>
  441. OK, the times make perfect sense in <a href="">New York</a> (where they're 9:00 to 17:00), but these are also the times for Australia.
  442. Clearly that doesn't work.
  443.      </p>
  445.      <p>
  446. So, New York Times, please:
  447.      </p>
  449.      <ul>
  450.        <li class="fullwidth">
  451.          <div class="listitemwidth">
  452.            Find a better way to report problems.  We have an Internet now, and people could enter
  453.            problem reports via the web.
  454.          </div>
  455.        </li>
  457.        <li class="fullwidth">
  458.          <div class="listitemwidth">
  459.            Ask yourselves why these delivery failures haven't been detected yet.  My guess is that
  460.            many people are affected, but even if not, this kind of problem should be logged and
  461.            reported.
  462.          </div>
  463.        </li>
  464.      </ul>
  466.      <p>
  467. You know my real email address.  Let me know when you have fixed it.
  468.      </p>
  469.      </div>
  470.    ]]>
  471.  </description>
  472.  <dc:creator>Greg Lehey</dc:creator>
  473.  <dc:date>2024-03-31T00:43:59+00:00</dc:date>
  474. </item>
  477. <!-- topic ga not selected
  478.      <p>
  479. Jesse Walsh along today to clean the windows  I spoke about his planned cat enclosure,
  480. but it looks as if he won't do it in a hurry.  On the other hand, he has a client for whom
  481. he has already built an enclosure, so maybe we can take a look at that.
  482.      </p>
  484. End deselected topic ga (Cleaning the windows) -->
  488. <item>
  489. <guid isPermaLink='true'></guid>
  490. <link></link>
  491. <category>technology</category>
  492. <category>opinion</category>
  493. <title>File system strangenesses</title>
  494.  <description>
  495.    <![CDATA[
  496.    <div align="justify">
  497.      <p>
  498. I've gradually been tidying up my old TV series archives.  One of the bigger jobs was
  499. <a href="">Um Himmels Willen</a>,
  500. where I reloaded some because the originals were truncated.  Finally got round to moving
  501. things around, but found something unexpected:
  502.      </p>
  504.      <blockquote class="fullwidth">
  505. <div style="text-align:left">
  506.  <tt>
  507. <code><font color="blue">=== grog@tiwi (/dev/pts/21)</font> <font color="red">/spool/Already/Series/Um&#45;Himmels&#45;Willen/D</font> <font color="blue">413</font> &#45;&gt; <b><tt>ls &#45;l 07&#45;01&#45;Am_seidenen_Faden.deu.vtt</tt></b></code>
  508. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;4 grog &nbsp;home &nbsp;58478 &nbsp;5 Mar 13:29 07&#45;01&#45;Am_seidenen_Faden.deu.vtt
  509. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/21)</font> <font color="red">/spool/Already/Series/Um&#45;Himmels&#45;Willen/D</font> <font color="blue">414</font> &#45;&gt; <b><tt>mv 07&#45;01&#45;Am_seidenen_Faden.deu.vtt ../07</tt></b></code>
  510. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/21)</font> <font color="red">/spool/Already/Series/Um&#45;Himmels&#45;Willen/D</font> <font color="blue">415</font> &#45;&gt; <b><tt>echo $?</tt></b></code>
  511. <br />0
  512. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/21)</font> <font color="red">/spool/Already/Series/Um&#45;Himmels&#45;Willen/D</font> <font color="blue">416</font> &#45;&gt; <b><tt>ls &#45;l 07&#45;01&#45;Am_seidenen_Faden.deu.vtt</tt></b></code>
  513. <br />&#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;4 grog &nbsp;home &nbsp;58478 &nbsp;5 Mar 13:29 07&#45;01&#45;Am_seidenen_Faden.deu.vtt
  514. <br />
  515.  </tt>
  516. </div>
  517. </blockquote>
  519.      <p>
  520. So I move a file to a different directory.  Move is successful.  And the file is still
  521. there!  How could that be?
  522.      </p>
  524.      <blockquote class="fullwidth">
  525. <div style="text-align:left">
  526.  <tt>
  527. <code><font color="blue">=== grog@tiwi (/dev/pts/21)</font> <font color="red">/spool/Already/Series/Um&#45;Himmels&#45;Willen/D</font> <font color="blue">437</font> &#45;&gt; <b><tt>ls &#45;il ../07/07&#45;01&#45;Am_seidenen_Faden.mp4 07&#45;01&#45;Am_seidenen_Faden.mp4</tt></b></code>
  528. <br />3196646 &#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;4 grog &nbsp;home &nbsp;1638402168 &nbsp;4 Mar 03:30 ../07/07&#45;01&#45;Am_seidenen_Faden.mp4
  529. <br />3196646 &#45;rw&#45;r&#45;&#45;r&#45;&#45; &nbsp;4 grog &nbsp;home &nbsp;1638402168 &nbsp;4 Mar 03:30 07&#45;01&#45;Am_seidenen_Faden.mp4
  530. <br />
  531.  </tt>
  532. </div>
  533. </blockquote>
  535.      <p>
  536. The very same file (same <a href="">inode</a> number) was already there, so the “move” was a success.  I still can't see whether it's a
  537. bug not to report it, or not to report the original.
  538.      </p>
  540.      <p>
  541. Another issue was more serious:
  542.      </p>
  544.      <blockquote class="fullwidth">
  545. <div style="text-align:left">
  546.  <tt>
  547. <code><font color="blue">=== grog@tiwi (/dev/pts/3)</font> <font color="red">/spool/Series/Watzmann&#45;ermittelt</font> <font color="blue">1766</font> &#45;&gt; <b><tt>rmdir 03/</tt></b></code>
  548. <br />ufs_rmdir: Bad link count 2 on parent inode 4228608 in file system /spool
  549. <br />rmdir: 03/: Invalid argument
  550. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/3)</font> <font color="red">/spool/Series/Watzmann&#45;ermittelt</font> <font color="blue">1767</font> &#45;&gt; <b><tt></tt></b></code>
  551. <br />
  552.  </tt>
  553. </div>
  554. </blockquote>
  556.      <p>
  557. What's that?
  558.      </p>
  560.      <blockquote class="fullwidth">
  561. <div style="text-align:left">
  562.  <tt>
  563. <code><font color="blue">=== grog@tiwi (/dev/pts/3)</font> <font color="red">/spool/Series/Watzmann&#45;ermittelt</font> <font color="blue">1768</font> &#45;&gt; <b><tt>l &#45;a</tt></b></code>
  564. <br />total 1
  565. <br />drwxr&#45;xr&#45;x &nbsp; 2 grog &nbsp;home &nbsp; &nbsp;512 14 Oct 21:14 .
  566. <br />drwxr&#45;xr&#45;x &nbsp;86 grog &nbsp;home &nbsp;2,560 30 Mar 18:43 ..
  567. <br />drwxr&#45;xr&#45;x &nbsp; 2 grog &nbsp;home &nbsp;3,584 30 Mar 17:59 03
  568. <br /><code><font color="blue">=== grog@tiwi (/dev/pts/3)</font> <font color="red">/spool/Series/Watzmann&#45;ermittelt</font> <font color="blue">1769</font> &#45;&gt;</code>
  569. <br />
  570.  </tt>
  571. </div>
  572. </blockquote>
  574.      <p>
  575. The directory <i>03</i> is there, but the parent directory only has two links.  A directory
  576. should have two links plus the number of subdirectories, here 1, so the link count should be
  577. 3.  What happened there?  Some kind of file system corruption,clearly, but how?  The
  578. modification time stamp (14 October 2023, 21:14) could give some indication, but I don't see
  579. anything in my diary.
  580.      </p>
  581.      </div>
  582.    ]]>
  583.  </description>
  584.  <dc:creator>Greg Lehey</dc:creator>
  585.  <dc:date>2024-03-31T01:27:40+00:00</dc:date>
  586. </item>
  589. <item>
  590. <guid isPermaLink='true'></guid>
  591. <link></link>
  592. <category>technology</category>
  593. <category>opinion</category>
  594. <title>More hydra completion</title>
  595.  <description>
  596.    <![CDATA[
  597.    <div align="justify">
  598.      <p>
  599. Apart from the various issues that I still need to think about, there's one thing
  600. about <i>hydra</i> that I've put on the back burner: the “beep” doesn't work.  But then I
  601. found this diary entry from <a href=",%20next%20step&amp;article=D-20140331-044038#D-20140331-044038">ten years ago</a>:
  602.      </p>
  604.      <blockquote class="fullwidth">
  605.        <div class="listitemwidth">
  606.   ... looked for the speaker connector, which I hadn't set up when I built the
  607.           machine. With good reason: this high-quality enclosure doesn't have a speaker! Not a big
  608.           issue, since they almost never fail, and I had dozens of old machines from which I could
  609.           cannibalize a speaker. But why didn't they include one?
  610.        </div>
  611.      </blockquote>
  613.      <p>
  614. I need to take a look, which could require shutting down the machine.  But if speakers are
  615. going out of fashion, which would make sense, isn't it time to find an alternative way to
  616. beep?  One that could be customized to say <i>who</i> beeped would be good.
  617.      </p>
  618.      </div>
  619.    ]]>
  620.  </description>
  621.  <dc:creator>Greg Lehey</dc:creator>
  622.  <dc:date>2024-03-31T01:42:15+00:00</dc:date>
  623. </item>
  626. <item>
  627. <guid isPermaLink='true'></guid>
  628. <link></link>
  629. <category>technology</category>
  630. <category>opinion</category>
  631. <title>Another Postfix tweak</title>
  632.  <description>
  633.    <![CDATA[
  634.    <div align="justify">
  635.      <p>
  636. Why does my mail from <i>hydra</i> come from, well, <tt></tt>,
  637. and not <tt></tt>, like from <i>eureka</i>?  I still don't know why,
  638. but Tom Ivar Helbekkmo, told me how to fix it.  Put this
  639. in <i>eureka</i>'s <i>/usr/local/etc/postfix/</i>:
  640.      </p>
  642.      <blockquote class="fullwidth">
  643. <div style="text-align:left">
  644.  <tt>
  645. masquerade_domains = $mydomain
  646.  </tt>
  647. </div>
  648. </blockquote>
  650.      <p>
  651. I've been using <a href="">Postfix</a> for well over 20 years, and I'm still learning.
  652.      </p>
  653.      </div>
  654.    ]]>
  655.  </description>
  656.  <dc:creator>Greg Lehey</dc:creator>
  657.  <dc:date>2024-03-31T01:42:20+00:00</dc:date>
  658. </item>
  661. <!-- topic ko not selected
  662.      <p>
  663. Roast ham for dinner tonight, which I chose to call „Das linke Osterschwein“ (“the crooked
  664. Easter swine”) as contrast to <a href="">BWV
  665. 158</a> „Das rechte Osterlamm“ (“the right Easter lamb”).  We've done this before, but
  666. there was room for improvement.
  667.      </p>
  669.      <p>
  670. First, as I had planned <a href=";article=D-20230911-015110#D-20230911-015110">last time</a>, cook it in the “bath tub” air fryer, which was at least big enough to take
  671. both the ham and the temperature probe.  But how high?  The stands made the choice for me:
  672.      </p>
  675.      <p>
  676. Based on prior experience, I baked at a setting of 190°, in contrast to the 170° in the hair
  677. dryer.  It took 54 minutes to bring the 560 g piece to 74° internal temperature:
  678.      </p>
  681.      <p>
  682. But it was still just as difficult to remove the net:
  683.      </p>
  685.      <div align="left">
  686.      </div>
  688.      <p>
  689. Nothing for it: we'll have to remove the net before roasting next time.
  690.      </p>
  692. End deselected topic ko (Das linke Osterschwein) -->
  695. <!-- topic Gpo not selected
  696.      <p>
  697. My eye continues to improve, and it's really conceivable that it will end up with normal
  698. infinity vision.  But this evening, looking at the garage lights, I saw streaks reminiscent
  699. of problems that I have had with camera lenses.  It's amazingly difficult to find an example
  700. of the effect, though in the past I've seen them seeing something like the streaks in
  701. <a href="">this image</a> (from <a href="">SIGGRAPH 2011 paper on
  702. Physically-Based Real-Time Lens Flare Rendering</a> via Wikipedia):
  703.      </p>
  705.      <a href="">
  706.      <img alt=""
  707.          title=".  Click to see in original size."
  708.          src=""
  709.          width="300"
  710.          /></a>
  711.      <p>
  712. The part I'm seeing are the spikes from the central source, not the reflections, and in my
  713. case they're irregular and mainly in a horizontal plane.  Will they go away?  Possibly not,
  714. but I could live with it.
  715.      </p>
  717.      <p>
  718. In passing, the <a href="">Wikipedia page</a> barely distinguishes between flare and streaks.  For me they're two very different
  719. things.
  720.      </p>
  722. End deselected topic Gpo (Eye: not there yet) -->
  725. <!-- topic klo not selected
  726.      <p>
  727. Today was <a href="">Easter Day</a>.  After
  728. <a href=";article=D-20240331-021538#D-20240331-021538">yesterday's</a> „linkes Osterschwein“ (“the crooked Easter swine”), it only seemed
  729. reasonable to follow <a href="">Bach's</a> <a href="">BWV
  730. 158</a> „Das rechte Osterlamm“ (“the right Easter lamb”).  But <a href="">Yvonne</a> doesn't like lamb any more, like so many other things.  How about <a href="">seekh kebab</a>?
  731.      </p>
  733.      <p>
  734. One reason is that I've always had trouble keeping the kebabs together.  But not-so-recently
  735. I bought a mixture that might make life easier:
  736.      </p>
  739.      <p>
  740. The package is interesting for a number of reasons, notably language.  It can't decide
  741. whether it's for Seekh Kabab or Shish Kebob.  The instructions are in English and German,
  742. where I can read „keine Preservative“ (“no condoms”), but some details are in French, and
  743. there are vestiges of Italian.  It promises recipes in French, Urdu, Hindi and Bangla inside
  744. the package, but I didn't find them.
  745.      </p>
  747.      <p>
  748. And of course it gives ingredients in archaic measures: <a href="">teaspoons and tablespoons</a>, whatever they may be for
  749. solids.  I find this the most frustrating part of trying a new recipe, trying to guess what
  750. they meant.
  751.      </p>
  753.      <p>
  754. And there more language hits me.  The ingredient list calls for butter, but the instructions
  755. mention oil.
  756.      </p>
  759.      <p>
  760. What is it?  My guess is that the butter is <a href="">ghee</a>, and in the original language (<a href="">Urdu</a>?) it can also be called oil.  That's
  761.        certainly the case in <a href="">Malay</a>, where ghee is called <i>minyak sapi</i>, and the word <i>minyak</i> means oil.  But by
  762.        the time the translation goes into German, things have changed completely: „Fügen Sie ½ - 1
  763.        Tasse Speiseöl hinzu“: “Add ½ to 1 cup cooking oil”.  Not only definitely oil, but also
  764.        almost certainly much more.  Assuming US American cups, that would be between 120 and 240 ml
  765.        of oil, compared to presumed 30 to 45 ml of butter.  I wonder how many people have messed up
  766.        their food like that.
  767.      </p>
  769.      <p>
  770. Things weren't much better for me.  My main concern was that the kebabs might fall apart,
  771. like they like to so much.  I didn't even entertain the idea of putting them on skewers.
  772. But make sausages out of them and fry them?
  773.      </p>
  776.      <p>
  777. The ones at the back didn't look too bad.  But they fell apart when I tried to put them into
  778. a serving dish:
  779.      </p>
  782.      <p>
  783. And while doing that, also made some roti <a href="">paratha</a>.  But the issues with the kebabs
  784. took me longer than I expected, and it showed:
  785.      </p>
  788.      <p>
  789. I decided to deep fry some frozen <a href="">pakoras</a> and <a href="">samosas</a> from
  790. <a href="">ALDI</a>.  How long?  2 minutes!  For
  791. both of them!  The pakoras were far larger, and it was fairly clear that they would need
  792. more than 2 minutes.  But after 4 they looked OK.  Only: they were still frozen in the
  793. middle!  Grr!
  794.      </p>
  796.      <p>
  797. All in all, definitely the wrong Easter lamb.
  798.      </p>
  800. End deselected topic klo (The wrong Easter lamb) -->
  802. <item>
  803. <guid isPermaLink='true'></guid>
  804. <link></link>
  805. <category>technology</category>
  806. <category>photography</category>
  807. <category>opinion</category>
  808. <title>distress: disaster?</title>
  809.  <description>
  810.    <![CDATA[
  811.    <div align="justify">
  812.      <p>
  813. Into the office first thing this morning and wanted to continue with yesterday's photo
  814. processing.  That involves waking <i></i>, the <a href="">ThinkCentre</a> running Microsoft, which is
  815. usually hibernated.  That goes via <a href="">rdesktop</a>, so I first hear the sound of the DVD drive seeking.
  816.      </p>
  818.      <p>
  819. But then nothing.  More problems with this bloody Microsoft?  No, the machine wasn't running
  820. at all.  Even the power light was off.
  821.      </p>
  823.      <p>
  824. More searching, and ultimately came to the conclusion that the box had some hardware
  825. failure.  Not to worry, I have a number of these boxen.  Took out the disk and put it in
  826. another one, same model.  And it came up happily with no repairs needed: after all, it had
  827. been hibernated.  Success!
  828.      </p>
  830.      <p>
  831. Well, not so fast.  When I started up <a href="">DxO
  832. PhotoLab</a>, it wanted me to enter the license key.  Why?  It's identically the same
  833. system that I have been using all along:
  834.      </p>
  836.        <a id="Photo-4" name="Photo-4"
  837.          href="diary-apr2024.php?dirdate=20240401&amp;imagesizes=11112&amp;topics=c#Photo-4">
  838.          <img alt="This should be DxO-1.png.  Is it missing?" border="0" id="Photo_4"
  839.               title="Photo DxO-1.png.  Click to redisplay larger version of image."
  840.               src=""
  841.               width="291" height="231"
  842.           /></a>
  844.      <p>
  845. Huh?  I have licensed the thing already.  OK, dig out the license key and painstakingly type
  846. it in, something that I have hated for decades.  And it worked, so clearly I didn't mistype.
  847.      </p>
  849.      <p>
  850. But things still weren't right.  My first task was to straighten this image:
  851.      </p>
  853.        <a id="Photo-5" name="Photo-5"
  854.          href="diary-apr2024.php?dirdate=20240331&amp;imagesizes=111112&amp;topics=c#Photo-5">
  855.          <img alt="This should be Wrong-Easter-Lamb-3-orig.jpeg.  Is it missing?" border="0" id="Photo_5"
  856.               title="Photo Wrong-Easter-Lamb-3-orig.jpeg.  Click to redisplay larger version of image."
  857.               src=""
  858.               width="300" height="225"
  859.           /></a>
  861.      <p>
  862. Yes, it's on its side, but it takes a single keystroke (<b>c-l</b>) to fix that.  The real
  863. issue, a little slower, is to get it exactly rectangular.  That's straightforward.  Select
  864. one of the almost descriptive symbols at the top of the window.  But they were gone!
  865.      </p>
  867.        <a id="Photo-6" name="Photo-6"
  868.          href="diary-apr2024.php?dirdate=20240401&amp;imagesizes=1111112&amp;topics=c#Photo-6">
  869.          <img alt="This should be DxO-2.png.  Is it missing?" border="0" id="Photo_6"
  870.               title="Photo DxO-2.png.  Click to redisplay larger version of image."
  871.               src=""
  872.               width="1181" height="57"
  873.           /></a>
  875.      <p>
  876. They should look like this:
  877.      </p>
  879.        <a id="Photo-7" name="Photo-7"
  880.          href="diary-apr2024.php?dirdate=20240401&amp;imagesizes=11111112&amp;topics=c#Photo-7">
  881.          <img alt="This should be DxO-4.png.  Is it missing?" border="0" id="Photo_7"
  882.               title="Photo DxO-4.png.  Click to redisplay larger version of image."
  883.               src=""
  884.               width="1135" height="59"
  885.           /></a>
  887.      <p>
  888. Why?  Something in the back of my head said <a href="">“ViewPoint”</a>.  Right, that could be it.  Back
  889. to my list of keys, searched the DxO menus, and luckily found a <b>Help</b> item “DxO
  890. ViewPoint → Activate DxO ViewPoint”.  And yes, that did it.  But what a pain!
  891.      </p>
  893.      <a name="Perfectly-Clear" id="Perfectly-Clear"></a>
  894.      <p>
  895. Still, <a href="">“Perfectly Clear“</a> didn't
  896. want to be outdone.  It, too, decided that I wasn't registered.
  897.      </p>
  899.        <a id="Photo-8" name="Photo-8"
  900.          href="diary-apr2024.php?dirdate=20240401&amp;imagesizes=111111112&amp;topics=c#Photo-8">
  901.          <img alt="This should be Perfectly-Clear-1.png.  Is it missing?" border="0" id="Photo_8"
  902.               title="Photo Perfectly-Clear-1.png.  Click to redisplay larger version of image."
  903.               src=""
  904.               width="368" height="183"
  905.           /></a>
  907.      <p>
  908. But unlike DxO, it didn't give me the option to register!  How do I register?  It didn't
  909. offer the possibility.  After some searching on the web, found a way: select the barely
  910. visible “About” towards the right at the bottom of the main window, which brings up this
  911. window:
  912.      </p>
  914.        <a id="Photo-9" name="Photo-9"
  915.          href="diary-apr2024.php?dirdate=20240402&amp;imagesizes=1111111112&amp;topics=c#Photo-9">
  916.          <img alt="This should be Perfectly-Clear-1.png.  Is it missing?" border="0" id="Photo_9"
  917.               title="Photo Perfectly-Clear-1.png.  Click to redisplay larger version of image."
  918.               src=""
  919.               width="300" height="226"
  920.           /></a>
  922.      <p>
  923. OK, click on Activate.  Yes, it comes up with another window that already knows the license
  924. key and email address:
  925.      </p>
  927.        <a id="Photo-10" name="Photo-10"
  928.          href="diary-apr2024.php?dirdate=20240402&amp;imagesizes=11111111112&amp;topics=c#Photo-10">
  929.          <img alt="This should be Perfectly-Clear-2.png.  Is it missing?" border="0" id="Photo_10"
  930.               title="Photo Perfectly-Clear-2.png.  Click to redisplay larger version of image."
  931.               src=""
  932.               width="347" height="194"
  933.           /></a>
  935.      <p>
  936. But the “ACTIVATE” button was greyed out, and nothing that I could do persuaded it to let me
  937. submit the data!  Off searching for answers, and finally found a way to send a message to
  938. their sales team (support has ended).  “Please prove that you are human and fill out this
  939. <a href="">CAPTCHA</a>”!  And yes, EyeQ, that's
  940. the correct information.  See if I care.  Clearly nobody can steal it.
  941.      </p>
  943.      <p>
  944. Damn you, EyeQ, and all those who insult people like that.  I won't fill out a CAPTCHA, ever
  945. again.  Sent off a rather stiff email to <tt></tt>
  946. and <tt></tt>, asking what to do and telling them what I thought of their
  947. attempts to insult their customers.  And <tt></tt> bounced.  Yes, my
  948. product has reached end of life (but should work for ever), but surely they have other
  949. customers.
  950.      </p>
  952.      <p>
  953. And that was only half of the pain.  What about <a href="">Yvonne</a>?  She
  954. has always had issues; clearly Microsoft likes her no more than she likes Microsoft.  But in
  955. fact things went relatively smoothly, once we persuaded the bloody thing to react at all.
  956. Trying from my system and a shell, I got
  957.      </p>
  959.      <blockquote class="fullwidth">
  960. <div style="text-align:left">
  961.  <tt>
  962. <code><font color="blue">=== grog@hydra (/dev/pts/26)</font> <font color="red">~/Mail</font> <font color="blue">79</font> &#45;&gt; <b><tt>rdesktop &#45;u yvonne distress</tt></b></code>
  963. <br />ATTENTION! Found a certificate stored for host 'distress', but it does not match the certificate
  964. <br />received from server.
  965. <br />Review the following certificate info before you trust it to be added as an exception.
  966. <br />If you do not trust the certificate the connection atempt will be aborted:
  967. <br />
  968. <br />&nbsp;&nbsp; &nbsp;Subject: CN=distress
  969. <br />&nbsp;&nbsp; &nbsp; Issuer: CN=distress
  970. <br />&nbsp;Valid From: Sat Mar 30 13:06:41 2024
  971. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; To: Sun Sep 29 12:06:41 2024
  972. <br />
  973. <br />&nbsp;&nbsp;Certificate fingerprints:
  974. <br />
  975. <br />&nbsp;&nbsp; &nbsp; &nbsp; sha1: e5821dd31e6a4e640b95ee93a1ec815430fa7304
  976. <br />&nbsp;&nbsp; &nbsp; sha256: edb83be75b8c33cb86e31fe2d40b1ce8fa95842e1f0e90216b024f5073407ebc
  977. <br />
  978. <br />Do you trust this certificate (yes/no)? yes
  979. <br />Connection established using SSL.
  980. <br />disconnect: Logout initiated by user.
  981. <br /><code><font color="blue">=== grog@hydra (/dev/pts/26)</font> <font color="red">~/Mail</font> <font color="blue">80</font> &#45;&gt; <b><tt>rdesktop &#45;u yvonne distress</tt></b></code>
  982. <br />Core(warning): Certificate received from server is NOT trusted by this system, an exception has been added by the user to trust this specific certificate.
  983. <br />Connection established using SSL.
  984. <br />Clipboard(error): xclip_handle_SelectionNotify(), unable to find a textual target to satisfy RDP clipboard text request
  985. <br />Protocol(warning): process_pdu_logon(), Unhandled login infotype 1
  986. <br />
  987.  </tt>
  988. </div>
  989. </blockquote>
  991.      <p>
  992. That must have something to do with the change in <i>something</i>, and by comparison it's
  993. acceptable.  After a bit of playing around, things worked, but only when I wasn't already
  994. logged in.  Previously it would produce a popup asking “shall I disconnect <tt>grog</tt>?”,
  995. but now it just silently fails.  And it seems that it no longer goes to sleep, so I have to
  996. explicitly put it to sleep (which, I discover, works with just a handful of mouse gestures).
  997.      </p>
  999.      <p>
  1000. So: things are almost working again, when there should have been no problems whatsoever.
  1001. But this is Microsoft.  And why did the programs want revalidation now?  It wasn't the disk;
  1002. it came up out of hibernation as if nothing had happened.  And it's barely the hardware.
  1003. The new machine has a PCI graphics card in addition to the on-board graphics (it was
  1004. once <i></i>), and it has only 16 GB of memory, and of course the <a href="">Ethernet</a> interface has a different
  1005. <a href="">MAC address</a>, requiring
  1006. updates to <i>/etc/ethers</i>:
  1007.      </p>
  1009.      <blockquote class="fullwidth">
  1010. <div style="text-align:left">
  1011.  <tt>
  1012. &#45;&#45;&#45; ethers 2023/02/18 00:33:55 1.10
  1013. <br />+++ ethers 2024/04/02 01:36:41
  1014. <br />@@ &#45;5,4 +5,4 @@
  1015. <br />&nbsp;6c:f0:49:09:7a:4d &nbsp;teevee
  1016. <br />&nbsp;00:21:86:21:ab:7e &nbsp;despair
  1017. <br />&nbsp;00:21:cc:d0:9e:0e &nbsp;euroa
  1018. <br />&#45;44:39:c4:90:52:20 &nbsp;distress
  1019. <br />+6c:0b:84:04:0a:5c &nbsp;distress
  1020. <br />
  1021.  </tt>
  1022. </div>
  1023. </blockquote>
  1025.      <p>
  1026. But clearly there's <i>something</i> about the hardware environment that triggers the
  1027. license check.  What is it?  And why?  It would make more sense to store the activation
  1028. information on the disk.  As it is, there's clearly a loophole: change the hardware once a
  1029. month and you can use DxO for free.
  1030.      </p>
  1032.      <p>
  1033. One thing's clear: I really need to migrate <i>distress</i> to a virtual machine, as I had
  1034. planned when I built <i>hydra</i>.  That way I'd save power, probably have more processing
  1035. power, and I could work around this kind of pain.
  1036.      </p>
  1037.      </div>
  1038.    ]]>
  1039.  </description>
  1040.  <dc:creator>Greg Lehey</dc:creator>
  1041.  <dc:date>2024-04-01T23:39:59+00:00</dc:date>
  1042. </item>
  1045. <!-- topic Phf not selected
  1046.      <p>
  1047. The news of the day: <a href="">Bibi</a> has been <a href="">castrated</a>!  It seems that it was just completing the job started <a href="">11 years ago</a>.  As the punchline of an unrelated joke goes, would you eat that pig all
  1048. at once?
  1049.      </p>
  1051.      <p>
  1052. Oh, and admire the delicacy of the reports.  They've changed “castration” to “hernia
  1053. operation”.
  1054.      </p>
  1056. End deselected topic Phf (Bibi castrated!) -->
  1059. <!-- topic hHgo not selected
  1061.      <p>
  1062. <a href="">Sixty years ago</a> I was preparing for the <a href="">GCE 'O' Level</a> exams.  One of the
  1063. set works for English Literature was the <a href="">Prologue</a> to
  1064. the <a href="">Canterbury Tales</a>,
  1065. and in a fit of misunderstanding I thought I could pass the exam by memorizing the entire
  1066. prologue (I failed).
  1067.      </p>
  1069.      <p>
  1070. But the weather today reminded me of the first two lines:
  1071.      </p>
  1073.      <blockquote class="fullwidth">
  1074.        <div class="listitemwidth">
  1075.  Whan that Aprille with his shoures sote
  1076.        </div>
  1078. <div class="listitemwidth">
  1080.  The droghte of Marche hath perced to the rote,
  1081. </div>
  1082.      </blockquote>
  1084.      <p>
  1085. In modern English: when April with its sweet showers has pierced the drought of March to the
  1086. root.
  1087.      </p>
  1089.      <p>
  1090. And somehow that seemed to fit.  Here a photo taken this morning:
  1091.      </p>
  1094.      <p>
  1095. According to the <a href="">Bureau of Meteorology</a>,
  1096. <a href="">0.8
  1097. mm</a> of rain over the whole month at <a href="">Ballarat Aerodrome</a>,
  1098. the closest measuring station to us.  By contrast, the average rainfall in March is 42 mm,
  1099. and in April 51.2 mm.
  1100.      </p>
  1102.      <p>
  1103. But now it's April, and as if to honour <a href="">Geoffrey Chaucer</a>, it rained
  1104.   heavily.  <a href="">The Bureau</a>   measured 46.8 mm, 58 times as much in the whole of March, or 1,755 times the March daily
  1105.   average.
  1106.      </p>
  1108.      <p>
  1109. That's their view, of course, and they told me so:
  1110.      </p>
  1113.      <p>
  1114. But despite their claims, that's the rainfall for <a href="">Ballarat</a>, not <a href="">Dereel</a>.  We measured only 28 mm, still a
  1115. welcome change and a refill for our water tanks.  On the other hand, I measured 5 mm of rain
  1116. last month.
  1117.      </p>
  1119. End deselected topic hHgo (Whan that Aprille with his shoures sote) -->
  1122. <item>
  1123. <guid isPermaLink='true'></guid>
  1124. <link></link>
  1125. <category>technology</category>
  1126. <category>photography</category>
  1127. <category>opinion</category>
  1128. <title>Another disaster</title>
  1129.  <description>
  1130.    <![CDATA[
  1131.    <div align="justify">
  1132.      <p>
  1133. Response from not one, but two people at <a href="">EyeQ</a> today, saying that the license details were correct, but because the product is no longer
  1134. supported, they can't do anything about it.  They did offer me a discounted upgrade to
  1135. <a href="">Radiant</a>, the new replacement, but that
  1136. would still cost money.
  1137.      </p>
  1139.      <p>
  1140. OK, one thing's for sure: changing hardware messes up licenses.  So let's do what I had been
  1141. planning all along and set up a virtual machine on <i>hydra</i>.  What shall I call it?
  1142. <a href="">Yvonne</a> was for <tt>discard</tt> or <tt>dismiss</tt>.  She
  1143. would have liked <tt>disgust</tt> too, but we've already had that one.  But by the time I
  1144. asked her, I had already started with the name <tt></tt>, so one of the
  1145. next ones will be Yvonne's choice.
  1146.      </p>
  1148.      <p>
  1149. First step, of course: make a copy of <i>distress'</i> disk.  Put it in <i>dereel</i>, which
  1150. I haven't used for months, and do a <i>dd</i>, which went at the reassuring speed of about
  1151. 103 MB/s, effectively wire speed.
  1152.      </p>
  1154.      <p>
  1155. Then create a new <a href="">VirtualBox</a> VM.  <a href=";subtitle=More%20VirtualBox%20setup&amp;article=D-20240318-005338#D-20240318-005338">Last time</a> I tried this, I ran into confusion between <i>hydra</i> and <i>eureka</i>.
  1156. But once I started the right version of <a href="">VirtualBox</a> (on <i>hydra</i>), and also
  1157. discovered how to include a native disk image (it <i>must</i> have a name ending
  1158. in <i>.hdd</i>), things went relatively smoothly, and soon I had it up and running.
  1159. Microsoft didn't like the change of IP address, but it didn't know why, just “Windows can't
  1160. find the problem”.  People, <a href="">“Windows”</a> <i>is</i> the
  1161. problem.  And everything I tried Just Worked—quite a success story.  Doubtless the devil is
  1162. in the detail, and I'll find other issues.
  1163.      </p>
  1164.      </div>
  1165.    ]]>
  1166.  </description>
  1167.  <dc:creator>Greg Lehey</dc:creator>
  1168.  <dc:date>2024-04-03T01:01:37+00:00</dc:date>
  1169. </item>
  1172. <item>
  1173. <guid isPermaLink='true'></guid>
  1174. <link></link>
  1175. <category>history</category>
  1176. <category>technology</category>
  1177. <category>opinion</category>
  1178. <title>50 years of microprocessors</title>
  1179.  <description>
  1180.    <![CDATA[
  1181.    <div align="justify">
  1182.      <p>
  1183. It has been well over 50 years since <a href="">Intel</a> introduced its first microprocessor, but for me the first one was the
  1184. <a href="">8008</a>.  Spent a while
  1185. comparing it with my most recent processor:
  1186.      </p>
  1188.      <table summary="Automatically generated table">
  1189.       <tr>
  1190.          <td valign="top" align="left">Feature</td>
  1191.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1192.          <td valign="top" align="right">I8008</td>
  1193.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1194.          <td valign="top" align="right">Ryzen 7950X</td>
  1195.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1196.          <td valign="top" align="right">factor</td>
  1197.       </tr>
  1199.       <tr>
  1200.          <td valign="top" align="left">Introduction</td>
  1201.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1202.          <td valign="top" align="right">April 1982</td>
  1203.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1204.          <td valign="top" align="right">September 2022</td>
  1205.       </tr>
  1207.       <tr>
  1208.          <td valign="top" align="left">Transistors</td>
  1209.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1210.          <td valign="top" align="right">3,500</td>
  1211.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1212.          <td valign="top" align="right">13,140,000</td>
  1213.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1214.          <td valign="top" align="right">3750</td>
  1215.       </tr>
  1217.       <tr>
  1218.          <td valign="top" align="left">CPUs</td>
  1219.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1220.          <td valign="top" align="right">1</td>
  1221.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1222.          <td valign="top" align="right">32</td>
  1223.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1224.          <td valign="top" align="right">32</td>
  1225.       </tr>
  1227.       <tr>
  1228.          <td valign="top" align="left">Clock speed</td>
  1229.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1230.          <td valign="top" align="right">0.0005 GHz</td>
  1231.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1232.          <td valign="top" align="right">4.5 GHz</td>
  1233.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1234.          <td valign="top" align="right">9000</td>
  1235.       </tr>
  1237.       <tr>
  1238.          <td valign="top" align="left">MIPS</td>
  1239.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1240.          <td valign="top" align="right">0.03</td>
  1241.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1242.          <td valign="top" align="right">220,000</td>
  1243.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1244.          <td valign="top" align="right">7333333</td>
  1245.       </tr>
  1247.       <tr>
  1248.          <td valign="top" align="left">Process size</td>
  1249.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1250.          <td valign="top" align="right">10 μm</td>
  1251.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1252.          <td valign="top" align="right">5 nm</td>
  1253.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1254.          <td valign="top" align="right">2000</td>
  1255.       </tr>
  1257.       <tr>
  1258.          <td valign="top" align="left">Die size</td>
  1259.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1260.          <td valign="top" align="right">16 mm²</td>
  1261.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1262.          <td valign="top" align="right">264 mm²</td>
  1263.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1264.          <td valign="top" align="right">16.5</td>
  1265.       </tr>
  1266.    </table>
  1268.      <p>
  1269. At first I was confused by the process size.  10 and 5?  Oh, different units.  The entire
  1270. I8008 processor could be
  1271.      </p>
  1273.      <p>
  1274. And in the course of my investigations, came across this <a href="">detailed
  1275. description of the chip layout</a>, which looks very interesting.  I should read it some
  1276. time.
  1277.      </p>
  1278.      </div>
  1279.    ]]>
  1280.  </description>
  1281.  <dc:creator>Greg Lehey</dc:creator>
  1282.  <dc:date>2024-04-03T03:43:50+00:00</dc:date>
  1283. </item>
  1286. <item>
  1287. <guid isPermaLink='true'></guid>
  1288. <link></link>
  1289. <category>general</category>
  1290. <category>technology</category>
  1291. <category>opinion</category>
  1292. <title>Where's my New York Times?</title>
  1293.  <description>
  1294.    <![CDATA[
  1295.    <div align="justify">
  1296.      <p>
  1297. No surprisingly, I got no response to my <a href=";article=D-20240331-004359#D-20240331-004359">open letter to the New York Times</a>.  During the week they relent and keep their 1-800
  1298. phone number manned beyond dawn until 10:00 (in the morning), so called up there, where a
  1299. grating artificial voice asked me for the 10 digit code.  Huh?  What's that?
  1300.      </p>
  1302.      <p>
  1303. Somehow worked past that and was connected to Robert, who told me that all was OK with my
  1304. subscription.  I explained (hopefully to his comprehension) that I wasn't getting any email.
  1305. He said that he would contact technical support (medium wait), after which he said that I
  1306. should now be receiving email.  Despite my requests, he didn't say whether they had found
  1307. any issue.  So now I just need to wait
  1308.      </p>
  1309.      </div>
  1310.    ]]>
  1311.  </description>
  1312.  <dc:creator>Greg Lehey</dc:creator>
  1313.  <dc:date>2024-04-04T05:38:50+00:00</dc:date>
  1314. </item>
  1317. <!-- topic Po not selected
  1318.      <p>
  1319. The world (or a any rate, USA, Canada, UK, Poland and Australia) are up in arms (no, that's
  1320. an inappropriate metaphor) about the killing of 6 aid workers.  Even <a href="">Anthony Albanese</a> got up on his
  1321. hind legs and condemned the killing of Lalzawmi "Zomi" Frankcom.  The Poles lamented the
  1322. death of Damian_Sobol.  The USA and Canada mournedJacob Flickinger.  Nobody mentioned
  1323. Saifeddin Issam Ayad Abutaha.
  1324.      </p>
  1326.      <p>
  1327. And for the first time ever, <a href="">Bibi</a> admitted a mistake.  They had killed non-Palestinian aid workers!  That can
  1328. happen in war, especially if three separate cars in a convoy at some distance from another
  1329. are targeted by precision missiles, but it should only happen to the Palestinians.
  1330.      </p>
  1332.      <p>
  1333. Bibi, does anybody outside Israel believe your drivel?  You're actively engaging in
  1334. genocide.  This strike succeeded in removing 200 tons of greatly needed food from Gaza.  To
  1335. quote from <a href=";utm_medium=email&amp;utm_campaign=wp_news_alert_revere&amp;location=alert">this article</a>      </p>
  1337.      <blockquote class="fullwidth">
  1338.        <div class="listitemwidth">
  1339.          “This is not an isolated incident,” said U.N. humanitarian coordinator James McGoldrick,
  1340.          citing the killing of at least 196 humanitarian workers in the occupied West Bank and Gaza
  1341.          since October. “This is nearly three times the death toll recorded in any single conflict
  1342.          in a year.” The 196 includes more than 175 U.N. staffers, U.N. Secretary General António
  1343.          Guterres said Tuesday.
  1344.        </div>
  1345.      </blockquote>
  1347.      <p>
  1348. When will people come to the recognition that Israel's barbarism is unacceptable and not
  1349. even useful to them.  No wonder <a href="">Hamas</a> attacked them.  Not a justification, of course, but you can't make people like you by
  1350. destroying them.
  1351.      </p>
  1353. End deselected topic Po (Netanyahu: Sorry, killed wrong aid workers) -->
  1356. <item>
  1357. <guid isPermaLink='true'></guid>
  1358. <link></link>
  1359. <category>technology</category>
  1360. <category>general</category>
  1361. <category>opinion</category>
  1362. <title>CJ off the air</title>
  1363.  <description>
  1364.    <![CDATA[
  1365.    <div align="justify">
  1366.      <p>
  1367. Mail from CJ Ellis today:
  1368.      </p>
  1370.      <blockquote class="fullwidth">
  1371. <div style="text-align:left">
  1372.  <tt>
  1373. Hi Greg It seems that I have had no phone signals since we last spoke &amp; you
  1374. <br />had been in touch with Broadband &nbsp;for me to be able to have message bank ..
  1375. <br />I thought it might have been the storm that has stop my phone , from having
  1376. <br />signals , but to even now there is nothing there .. Sorry to trouble you
  1377. <br />,but it has been a saga with broadband since we have changed to them with
  1378. <br />the phone service ..
  1379. <br />
  1380.  </tt>
  1381. </div>
  1382. </blockquote>
  1384.      <p>
  1385. What's wrong now?  Clearly the loss of <a href="">VoIP</a> has nothing to do with the bad weather.  Checked the status: both lines
  1386. registered.  Tried to call him.  Nothing.  After 2 minutes, the attempt timed out, but it
  1387. should have given some other indication before that.
  1388.      </p>
  1390.      <p>
  1391. Dammit, call <a href="">Aussie Broadband</a> support
  1392. again, and was connected to somebody who on asking admitted to the name Semanjit Kaur.  Once
  1393. again this incredible difficulty that all support personnel seem to have with handling calls
  1394. on behalf of another customer.  At least this time I'm on their list as an approved contact,
  1395. but she had trouble with the phone number.  I had a number ending in 3, from their web site
  1396. and also my own records.  She found the same number with a 2 in the last position.
  1397.      </p>
  1399.      <p>
  1400. More puzzling, then she decided that she had been looking in the wrong place and that the
  1401. number I had was correct.  For some reason she didn't try to call it.  Instead she wanted to
  1402. check the router configuration.  Can't access it.  Oh yes, I can.  I'll update the dial
  1403. plan.
  1404.      </p>
  1406.      <p>
  1407. I explained to her that the dial plan had nothing to do with incoming calls, but she thought
  1408. it would help anyway.  OK, but it meant getting CJ to power cycle the router, so that was
  1409. all we could do.  I sent a mail message to CJ explaining how to power cycle it, and that was
  1410. all that we could do for today.
  1411.      </p>
  1413.      <p>
  1414. Does this really have to be this difficult?
  1415.      </p>
  1416.      </div>
  1417.    ]]>
  1418.  </description>
  1419.  <dc:creator>Greg Lehey</dc:creator>
  1420.  <dc:date>2024-04-04T05:45:45+00:00</dc:date>
  1421. </item>
  1424. <item>
  1425. <guid isPermaLink='true'></guid>
  1426. <link></link>
  1427. <category>technology</category>
  1428. <category>opinion</category>
  1429. <title>Bigger disaster</title>
  1430.  <description>
  1431.    <![CDATA[
  1432.    <div align="justify">
  1434.      <p>
  1435. Carried on playing around with <i></i> today.  It was my intention to use
  1436. it seriously, and 1 CPU wouldn't cut it.  But <i>hydra</i> has 32 logical CPUs, so we could
  1437. easily allocate 8 to <i>disaster</i>.  Did that, and fired up <a href="">DxO PhotoLab</a>.  Please activate.  OK, we're
  1438. getting used to that.  But when I tried to activate <a href="">“ViewPoint”</a>, it told me “too many
  1439. activations”!  Three activations <i>on the same disk</i>!  Another support request, and all
  1440. I could do for today.
  1441.      </p>
  1443.      <p>
  1444. But I did try processing Saturday's photos.  140 images processed in 5 minutes! 28 images
  1445. per minute, where I previously only had about 5.  That's really worthwhile.  Only: for
  1446. reasons I haven't understood, it uses stupid amounts of CPU time when idle.
  1447. Here <i>disaster</i> and <i>eureso</i> (<a href="">FreeBSD</a>, reinstated to see if I could get it to work):
  1448.      </p>
  1450.      <blockquote class="fullwidth">
  1451. <div style="text-align:left">
  1452.  <tt>
  1453. PID USERNAME &nbsp; &nbsp;THR PRI NICE &nbsp; SIZE &nbsp; &nbsp;RES STATE &nbsp; &nbsp;C &nbsp; TIME &nbsp; &nbsp;WCPU COMMAND
  1454. <br />37150 grog &nbsp; &nbsp; &nbsp; &nbsp; 37 &nbsp;20 &nbsp; &nbsp;0 &nbsp; &nbsp;17G &nbsp; &nbsp;17G select &nbsp;28 493:14 241.39% VirtualBoxVM
  1455. <br />37024 grog &nbsp; &nbsp; &nbsp; &nbsp; 32 &nbsp;20 &nbsp; &nbsp;0 &nbsp;2501M &nbsp;2244M select &nbsp; 8 &nbsp; 2:53 &nbsp; 0.87% VirtualBoxVM
  1456. <br />
  1457.  </tt>
  1458. </div>
  1459. </blockquote>
  1461.      <p>
  1462. It wasn't like that all the time; it fluctuated wildly and dropped as low as 20%, still
  1463. unreasonably high.  But that's not <i>that</i> important: I can put it to sleep most of the
  1464. time.  Could it be something to do with GPU emulation?
  1465.      </p>
  1467.      <p>
  1468. During this time, the task manager showed something interesting:
  1469.      </p>
  1471.        <a id="Photo-11" name="Photo-11"
  1472.          href="diary-apr2024.php?dirdate=20240403&amp;imagesizes=111111111112&amp;topics=c#Photo-11">
  1473.          <img alt="This should be disaster-performance.png.  Is it missing?" border="0" id="Photo_11"
  1474.               title="Photo disaster-performance.png.  Click to redisplay larger version of image."
  1475.               src=""
  1476.               width="337" height="200"
  1477.           /></a>
  1479.      <p>
  1480.      </p>
  1482.        <a id="Photo-12" name="Photo-12"
  1483.          href="diary-apr2024.php?dirdate=20240403&amp;imagesizes=1111111111112&amp;topics=c#Photo-12">
  1484.          <img alt="This should be disaster-performance-detail.png.  Is it missing?" border="0" id="Photo_12"
  1485.               title="Photo disaster-performance-detail.png.  Click to redisplay larger version of image."
  1486.               src=""
  1487.               width="600" height="380.98159509202"
  1488.           /></a>
  1490.      <p>
  1491. The <i>top</i> output coincided with the 0% usage, but for non-obvious reasons it was using
  1492. up to 25% CPU, corresponding to 2 full CPUs.  Why?  Somehow this must have something to do
  1493. with virtual machines.
  1494.      </p>
  1495.      </div>
  1496.    ]]>
  1497.  </description>
  1498.  <dc:creator>Greg Lehey</dc:creator>
  1499.  <dc:date>2024-04-04T05:45:55+00:00</dc:date>
  1500. </item>
  1503. <item>
  1504. <guid isPermaLink='true'></guid>
  1505. <link></link>
  1506. <category>technology</category>
  1507. <category>opinion</category>
  1508. <title>More Aussie VoIP pain</title>
  1509.  <description>
  1510.    <![CDATA[
  1511.    <div align="justify">
  1512.      <p>
  1513. So why didn't CJ Ellis contact me about the success of power cycling his modem?  Checked the
  1514. status page.  Both phones not registered.  Did something go wrong with the router?  Is he
  1515. maybe completely off the net?
  1516.      </p>
  1518.      <p>
  1519. What a time!  I was in a hurry because of an appointment in <a href="">Geelong</a>, but called up Aussie support and
  1520. was told that there was a two minute wait—every two minutes for 8 minutes.  Finally I was
  1521. connected with Pranil, who asked all sorts of questions that I didn't know (CJ's mobile
  1522. phone number, for example, which for Aussie's purposes doesn't exist).  Finally I got
  1523. through to him that I just wanted to check whether CJ was on the net or not, but he kept
  1524. returning to VoIP configuration.  Finally he checked: yes, he was unable to establish
  1525. contact with CJ's router.  That probably means that it was off the air.  What are you going
  1526. to do about it?  It looks like a misconfiguration on Aussie's part.  Can somebody go on
  1527. site?  Sure, when do you want to go?  Oh, they expect <i>me</i> to drive the 55 km and do
  1528. the work!  To fix something that they had done!
  1529.      </p>
  1531.      <p>
  1532. Yet Another formal complaint, correcting his text that referred to VoIP rather than the
  1533. network link (“Internet”), with a request that this time they would send me the text of the
  1534. complaint.  And that would take up to ten days to resolve!  He said that he would put it on
  1535. priority, but that didn't help.  45 minutes on the phone for something that didn't even
  1536. concern me.
  1537.      </p>
  1538.      </div>
  1539.    ]]>
  1540.  </description>
  1541.  <dc:creator>Greg Lehey</dc:creator>
  1542.  <dc:date>2024-04-05T00:41:30+00:00</dc:date>
  1543. </item>
  1546. <!-- topic Go not selected
  1547.      <p>
  1548. Off to <a href="">Geelong</a> today for another
  1549. eye examination.  It was <i>much</i> slower than last time, and it took over half an hour
  1550. before Bridget, the <a href="">orthopist</a>, called me in.  Before she got a chance to do anything, I mentioned the apparently
  1551. incorrect focus of my right (“new”) eye.  She checked me and found that yes, I had an offset
  1552. of -0.5 dioptres spherically—almost exactly what I had guessed (well, -0.5 to -0.6).  But
  1553. she also found <a href="">astigmatism</a> of +1 dioptre at 100°.  That doesn't match any miscalculation in the infinity point, and
  1554. Bridget thought that it could be due to continuing inflammation of the eye.  It seems that
  1555. it takes 4 weeks for complete healing, thus presumably the timing of the drops.
  1556.      </p>
  1558.      <p>
  1559. It wasn't until we were done that I discovered that that was about all.  Presumably she was
  1560. there to measure my eye.  But I had thought that today's appointment was a precursor to next
  1561. week's operation on my left eye, when in fact they weren't interested in that at all.
  1562.      </p>
  1564.      <p>
  1565. Then, with the inevitable dilating drops, into see Shivesh Varma, <a href="">David Fabinyi's</a> <a href="">locum tenens</a>, the man with the
  1566. handshake of steel.  He put me through the usual tests, noted eye pressures of 12 mm Hg
  1567. (left) and 13 mm (right), apparently excellent values.  I mentioned the difference of focus,
  1568. and he checked through the lists and came up with a value of -0.45 dioptres.  I asked him to
  1569. ensure that this didn't get applied to my left eye, and he said that he would ask David to
  1570. call me before the procedure.
  1571.      </p>
  1573.      <p>
  1574. After we had left, got a phone call from him: in fact, my spherical correction is
  1575. effectively 0 dioptres, since the cylindrical correction is +1 dioptre, giving a focus range
  1576. from -0.5 to +0.5 dioptres.  That's an interesting consideration; maybe things will clear up
  1577. when the eye has finished healing.  In the meantime, of course, there's the question of
  1578. where the -0.45 dioptres comes from.  Still worth a talk with David, though I really don't
  1579. want to wait until the right eye has finished healing.
  1580.      </p>
  1582. End deselected topic Go (Cataract surgery follow-up) -->
  1585. <item>
  1586. <guid isPermaLink='true'></guid>
  1587. <link></link>
  1588. <category>technology</category>
  1589. <category>opinion</category>
  1590. <title>More Aussie pain</title>
  1591.  <description>
  1592.    <![CDATA[
  1593.    <div align="justify">
  1594.      <p>
  1595. Back home at 15:00 and tried to catch up with the day's work.  First this diary.  I was in
  1596. the middle of describing <a href=";article=D-20240404-054545#D-20240404-054545">yesterday's pain</a> with CJ's phone when the doorbell rang.  CJ, with a car full of
  1597. hardware.  It seems that he didn't just power cycle the router, he disconnected a number of
  1598. cables.  Did he put them back correctly?
  1599.      </p>
  1601.      <p>
  1602. Anyway, took the router in and connected it to <i>dereel</i>, which is seeing more use
  1603. lately.  All works, the phones register, as the Aussie status page shows.  And I still can't
  1604. call in!  So effectively we're where we were before I called Aussie the first time.
  1605.      </p>
  1607.      <p>
  1608. More investigations: I <i>can</i> make <i>some</i> outgoing calls.  I could call my mobile
  1609. phone, but not my “home phone” (also <a href="">VoIP</a> with <a href="">Aussie Broadband</a>).
  1610. So something is still wrong.  What do I do now?  Postpone.  Sorry, CJ, I know that you went
  1611. with Aussie on my recommendation (something that I will never do to anybody again), but I
  1612. don't have time.  Leave the hardware here and I'll look at it tomorrow.
  1613.      </p>
  1615.      <p>
  1616. But there are so many things that don't make sense here.  I need to add to this list as I
  1617. discover them:
  1618.      </p>
  1620.      <ul>
  1621.        <li class="fullwidth">
  1622.          <p class="listitemwidth">
  1623.            Clearly Aussie's support staff are incapable.  Why reconfigure a dial plan if the issue
  1624.            is with calling in?  Did Semanjit understand what she was doing?
  1625.          </p>
  1626.        </li>
  1628.        <li class="fullwidth">
  1629.          <p class="listitemwidth">
  1630.            What did CJ do?  He seems to be having comprehension issues.  He claimed that Aussie's
  1631.            voice menu didn't give him the choice of selecting “support”.  Tried it from his phone.
  1632.            Works as expected.  And what did he disconnect yesterday, and how did he reconnect it?
  1633.          </p>
  1634.        </li>
  1636.        <li class="fullwidth">
  1637.          <p class="listitemwidth">
  1638.    Looking at his call logs was strange.  There <i>must</i> be something wrong with this:
  1639.            Why does the usage log show calls from CJ to himself?
  1640.          </p>
  1642.  <table summary="Automatically generated table">
  1643.       <tr>
  1644.          <td valign="top" align="left">18-03-2024</td>
  1645.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1646.          <td valign="top" align="left">0395662250</td>
  1647.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1648.          <td valign="top" align="left">2m 14s</td>
  1649.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1650.          <td valign="top" align="left">$0.15</td>
  1651.       </tr>
  1653.       <tr>
  1654.          <td valign="top" align="left">01-04-2024</td>
  1655.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1656.          <td valign="top" align="left">0353182413</td>
  1657.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1658.          <td valign="top" align="left">4m 38s</td>
  1659.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1660.          <td valign="top" align="left">$0.00</td>
  1661.       </tr>
  1662.    </table>
  1664.  <p class="listitemwidth">
  1665.    That's a call from 0353182413 to 0353182413, the same number.  4½ minutes long!  How can
  1666.    that work?  On the same day, we have the same thing on the other line, 0353244269:
  1667.  </p>
  1669.  <table summary="Automatically generated table">
  1670.       <tr>
  1671.          <td valign="top" align="left">01-04-2024</td>
  1672.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1673.          <td valign="top" align="left">0353244269</td>
  1674.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1675.          <td valign="top" align="left">1m 44s</td>
  1676.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  1677.          <td valign="top" align="left">$0.00</td>
  1678.       </tr>
  1679.    </table>
  1681.  <p class="listitemwidth">
  1682.    They're too polite to give times (something that <a href="">MyNetFone</a> did much better), but what
  1683.    does it mean?  And of course there are no recent calls; for some reason it takes up to
  1684.    48 hours to update the call register, something that should happen in real time.
  1685.  </p>
  1686.        </li>
  1687.      </ul>
  1688.      </div>
  1689.    ]]>
  1690.  </description>
  1691.  <dc:creator>Greg Lehey</dc:creator>
  1692.  <dc:date>2024-04-05T01:29:44+00:00</dc:date>
  1693. </item>
  1696. <item>
  1697. <guid isPermaLink='true'></guid>
  1698. <link></link>
  1699. <category>technology</category>
  1700. <category>opinion</category>
  1701. <title>named death</title>
  1702.  <description>
  1703.    <![CDATA[
  1704.    <div align="justify">
  1705.      <p>
  1706. As if I didn't have enough to do, after CJ left I discovered that I hadn't received any
  1707. external mail for nearly 6 hours.  Local mail was still coming through, so checked things
  1708. on <i></i> (also <i></i>).  At first sight things looked OK.
  1709. Nothing queued bar the usual messages from <tt>MAILER_DAEMON</tt> to non-responsive spam
  1710. sites, <i>maillog</i> showed the usual rejections because of name lookup issues.  Sent a
  1711. message from <i></i>.  It didn't arrive!
  1712.      </p>
  1714.      <p>
  1715. A bit more searching and I discovered that <i>all</i> DNS lookups were failing: <i>named</i>
  1716. had stopped.  Why?  No idea, except that I added <i></i> to the
  1717. configuration yesterday.  <a href="">Nomen est omen</a>?  Restarted and things worked normally.  Another thing to check on
  1718. when I have time.
  1719.      </p>
  1720.      </div>
  1721.    ]]>
  1722.  </description>
  1723.  <dc:creator>Greg Lehey</dc:creator>
  1724.  <dc:date>2024-04-05T01:30:45+00:00</dc:date>
  1725. </item>
  1728. <item>
  1729. <guid isPermaLink='true'></guid>
  1730. <link></link>
  1731. <category>technology</category>
  1732. <category>opinion</category>
  1733. <title>Aussie: no support any more!</title>
  1734.  <description>
  1735.    <![CDATA[
  1736.    <div align="justify">
  1737.      <p>
  1738. So what's wrong with CJ's <a href="">VoIP</a> service?  The obvious thing to do would be to try it on my own <a href="">ATA</a> and see what
  1739. happened.  And indeed, it still didn't work.  The same symptoms: call in rang, but the
  1740. caller got a busy signal, and it stopped trying to call after a few seconds.  Clearly a
  1741. service configuration issue.
  1742.      </p>
  1744.      <p>
  1745. So I sent Aussie a summary of what has happened so far, and then called them at 14:20, and
  1746. was connected to a very quiet Mohammed after only 4 minutes.  The same old pain, at least 10
  1747. minutes of identification before we even got started.  But Mohammed couldn't find the
  1748. message I sent.  What address did I use?  <tt></tt>.  Ah, that's an
  1749. old, worn-out magic word.  Now I should send support requests
  1750. to <tt></tt>.  OK, did that, but where did the first message
  1751. go?
  1752.      </p>
  1754.      <p>
  1755. While waiting for the new message to arrive, asked why I hadn't had a confirmation of my
  1756. complaint.  It seems that they sent it to CJ, who is off the air!
  1757.      </p>
  1759.      <p>
  1760. Finally I got a response to my first support request:
  1761.      </p>
  1763.      <blockquote class="fullwidth">
  1764. <div style="text-align:left">
  1765.  <tt>
  1766. Date: Fri, &nbsp;5 Apr 2024 03:27:48 +0000 (UTC)
  1767. <br />&lt;;: host[] said: 550 5.1.1
  1768. <br />&nbsp;&nbsp; &nbsp;&lt;;: Recipient address rejected: User unknown in local
  1769. <br />&nbsp;&nbsp; &nbsp;recipient table (in reply to RCPT TO command)
  1770. <br />
  1771. <br />Return&#45;Path: &lt;;
  1772. <br />Received: from (121&#45;200&#45;11&#45; [])
  1773. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;by (Postfix) with ESMTP id 3B3A328088
  1774. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp;for &lt;;; Fri, &nbsp;5 Apr 2024 03:18:11 +0000 (UTC)
  1775. <br />
  1776.  </tt>
  1777. </div>
  1778. </blockquote>
  1780.      <p>
  1781. On the one hand, that's symptomatic of what has become of Aussie: no support any more.  But
  1782. look at the times!  It took over 9 minutes for their mail system to reject the message!
  1783.      </p>
  1785.      <p>
  1786. So he read the email and asked for CJ's email address, which is a little difficult for
  1787. non-native English speakers (though Mohammed spoke excellent English).  He decided to test
  1788. the connection on their “test bench”, whatever that may mean.  And it passed.  So it must be
  1789. the router.
  1790.      </p>
  1792.      <p>
  1793. What router?  This line was configured on my <a href="">ATA</a>.  I tried to make it
  1794. clear to him that if the problem moves with the service and not with the ATA, it must be a
  1795. configuration problem with the service, not the ATA.  But I failed.  He kept asking his
  1796. “level 2” people, who presumably have little more understanding than he.  And this despite
  1797. the request in my email:
  1798.      </p>
  1800.      <blockquote class="fullwidth">
  1801.        <div class="listitemwidth">
  1802.          Please forward this to your VoIP specialists.
  1803.        </div>
  1804.      </blockquote>
  1806.      <p>
  1807. He went through all sorts of rigmaroles, including another video view of the ATA
  1808. configuration screen.  I've seen this before, so I put the phone on a tripod, at which point
  1809. it obligingly rebooted.
  1810.      </p>
  1812.      <p>
  1813. More talking, and at some point he said that the service couldn't work at my address because
  1814. VoIP is tied to the Internet service.  That's nonsense of course, and I tried to explain to
  1815. him how VoIP works.  I don't think I succeeded.
  1816.      </p>
  1818.      <p>
  1819. Then he went back to the ATA configuration screen.  It has frozen, he said.  Clearly he had
  1820. never seen things on a tripod before.
  1821.      </p>
  1823.      <p>
  1824. After understanding that, he created a new service with the same number, so all I had to do
  1825. was type in the new password.  It ended in <b>l</b>, but he had read it as <b>1</b>.  And it
  1826. registered anyway, or at least the ATA claimed that it did.  Can I factory reset the ATA?
  1827. Emphatic <b><i>NO</i></b>!  Somehow I can't get it into their heads that the problem can't
  1828. be with the ATA, and think of the damage it would do.
  1829.      </p>
  1831.      <p>
  1832. In the end, we agreed that CJ would pick up the equipment and take it home with him, and
  1833. that they would mess with the configuration there—he <b><i>still</i></b> thinks that it's an
  1834. ATA configuration issue!.  But at least it gets it out of my hair.
  1835.      </p>
  1837.      <p>
  1838. Still, I could give CJ one of my spare VoIP lines to tide him over.  Took a look at his
  1839. router again.  Both lines registered!  Tried them out.  Yes, they work!  And so does the one
  1840. I have on my ATA.
  1841.      </p>
  1843.      <p>
  1844. How can that happen?  My best guess is that somebody at Aussie fixed things without telling
  1845. me.  Still, clearly good news.  CJ came and picked up his hardware and went home.  Called me
  1846. at 18:45.  Both lines down!  In addition, I checked my lines.  Now the one I had turned off
  1847. for the ATA test is showing the same symptoms: call in rings, but the caller gets busy
  1848. signal.  And call out works.
  1849.      </p>
  1851.      <p>
  1852. What does all this mean?  It could be that Mohammed was correct after all: the VoIP
  1853. configuration depends on the IP address, maybe a misguided attempt to lessen abuse.  That
  1854. would also explain why I was never able to configure Aussie VoIP on my mobile phone.  All of
  1855. this points to a configuration issue on the SIP server or proxy, which happen to be the same
  1856. machine.  Still, sufficient to the day is the evil thereof.  So far this week I must have
  1857. spent at least 8 hours fighting this problem, and all sorts of other things have had to wait
  1858. as a result.
  1859.      </p>
  1860.      </div>
  1861.    ]]>
  1862.  </description>
  1863.  <dc:creator>Greg Lehey</dc:creator>
  1864.  <dc:date>2024-04-05T02:35:44+00:00</dc:date>
  1865. </item>
  1868. <item>
  1869. <guid isPermaLink='true'></guid>
  1870. <link></link>
  1871. <category>photography</category>
  1872. <category>technology</category>
  1873. <title>disaster processing photos</title>
  1874.  <description>
  1875.    <![CDATA[
  1876.    <div align="justify">
  1877.      <p>
  1878. <i></i> seems to work well now, though I still need to confirm my software
  1879. licenses.  But one was a surprise:
  1880.      </p>
  1882.        <a id="Photo-13" name="Photo-13"
  1883.          href="diary-apr2024.php?dirdate=20240405&amp;imagesizes=11111111111112&amp;topics=c#Photo-13">
  1884.          <img alt="This should be PerfectlyClear-1.png.  Is it missing?" border="0" id="Photo_13"
  1885.               title="Photo PerfectlyClear-1.png.  Click to redisplay larger version of image."
  1886.               src=""
  1887.               width="356" height="189"
  1888.           /></a>
  1890.      <p>
  1891. <a href="">“Perfectly Clear“</a> has decided that
  1892. it's licensed after all!  I need to tread carefully now to ensure that it doesn't change
  1893. its mind.
  1894.      </p>
  1895.      </div>
  1896.    ]]>
  1897.  </description>
  1898.  <dc:creator>Greg Lehey</dc:creator>
  1899.  <dc:date>2024-04-06T04:32:33+00:00</dc:date>
  1900. </item>
  1903. <item>
  1904. <guid isPermaLink='true'></guid>
  1905. <link></link>
  1906. <category>technology</category>
  1907. <category>opinion</category>
  1908. <title>Aussie: You are not worthy</title>
  1909.  <description>
  1910.    <![CDATA[
  1911.    <div align="justify">
  1912.      <p>
  1913. <i>Another</i> day half wasted trying to get <a href="">Aussie Broadband</a> to fix their configuration problem.  Once again a message explaining
  1914. the situation and asking them to do something about it.
  1915.      </p>
  1917.      <p>
  1918. Then called up Aussie, and for a change I was connected to an Australian, Harrison.  He
  1919. wasn't the brightest: I gave him the details at the outset, but he wanted to hear my date of
  1920. birth no less than three times and CJ's address twice.  After a quarter of an hour he still
  1921. had not managed to identify me, and I asked to be connected to his supervisor.
  1922.      </p>
  1924.      <p>
  1925. After a few minutes I was connected to Paul, who also couldn't find the message I sent.  I
  1926. suggested that they had serious problems with their email system and he agreed, yes, the
  1927. system isn't logical.  But even after he found it, and asking my date of birth another 3
  1928. times and CJ's address at least once, he refused me access.  He wouldn't even admit that
  1929. they had a customer called CJ Ellis, and he couldn't give me any details—even not why he
  1930. didn't like my credentials.  The privacy laws prohibit that.  He would also not tell me
  1931. where I could turn to solve the problem at hand.  In the end, after 42 minutes, I hung up.
  1932. Aussie (represented by Paul, surname protected for privacy reasons) has refused support for
  1933. reasons that they don't want to divulge.
  1934.      </p>
  1936.      <p>
  1937. So what went wrong there?  Did something in their system raise a red flag?  Or, more likely,
  1938. is he completely incompetent and unable to find his way round Aussie's support
  1939. infrastructure?  I think I'd go for the second choice.  I thought of calling up again and
  1940. seeing if the next “consultant” could find his way round the system better.  But I couldn't
  1941. stand the pain.  Instead I sent CJ an email:
  1942.      </p>
  1944.      <blockquote class="fullwidth">
  1945. <p class="listitemwidth">
  1946.          I've spent another 1½ hours today trying to resolve your phone problems.  Unfortunately,
  1947.  today they have decided to refuse to let me work on your behalf.  I spent 45 minutes on
  1948.  the phone today and was brushed off by a supervisor who didn't like something about my
  1949.  credentials, but who was too polite to say what.
  1950. </p>
  1952. <p class="listitemwidth">
  1953.  So: I don't know where to go from here.  Your lines are still down, and Aussie is too
  1954.  proud to do anything about it.  The best you can do is send them an email and tell them
  1955.  what you think.
  1956. </p>
  1958. <p class="listitemwidth">
  1959.  Sorry that I recommended Aussie to you.  I won't do that to anybody again.  My only excuse
  1960.  is that they once used to be a good company, but they're doing everything they can to
  1961.  change that.  I'll look for an alternative VoIP service for you.
  1962. </p>
  1963.      </blockquote>
  1965.      <p>
  1966. What went wrong here?  As I said to CJ, once they were a good ISP.  Now they've become
  1967. inefficient bureaucrats who would make <a href="">Telstra</a> envious.  And of course the faults haven't been fixed.  But why did this
  1968. happen?  It happened to <a href="">Internode</a>, also once a bright star in the ISP sky.  As <a href="">Simon Hackett</a> put it, <a href="">How
  1969. to ignore a customer without even trying</a>.  Ironically, that experience drove him to
  1970. Aussie.  I wonder if he's still as happy with them now.  I note that the problems I have now
  1971. are similar to what I complained about <a href=";subtitle=Still%20more%20VoIP%20pain&amp;article=D-20230911-015000#D-20230911-015000">last September</a>, just worse.  And the solutions that I mention would still apply.  The
  1972. only thing that I would add is that support people seem to be set to believe that all
  1973. problems are misconfiguration of customer hardware, even when there's hard evidence to the
  1974. contrary.  Yes, it's difficult to find good support personnel, but that's what escalation
  1975. procedures are for.
  1976.      </p>
  1978.      <p>
  1979. So: what do I do now?  I should drop Aussie like a hot potato, but who knows if there's a
  1980. better ISP?  And how do I get my /24 routed?  But it does look like a good idea to look for
  1981. a better VoIP supplier.  Mañana.
  1982.      </p>
  1983.      </div>
  1984.    ]]>
  1985.  </description>
  1986.  <dc:creator>Greg Lehey</dc:creator>
  1987.  <dc:date>2024-04-07T00:32:00+00:00</dc:date>
  1988. </item>
  1991. <item>
  1992. <guid isPermaLink='true'></guid>
  1993. <link></link>
  1994. <category>technology</category>
  1995. <category>photography</category>
  1996. <category>opinion</category>
  1997. <title>disaster?  despise!</title>
  1998.  <description>
  1999.    <![CDATA[
  2000.    <div align="justify">
  2001.      <p>
  2002. <a href="">Yvonne</a> had some photos to process yesterday, and she did it
  2003. on<i>disaster</i>, which worked well.  I checked the processing times, and they seemed
  2004. significantly faster than her normal processing on <i>distress</i>, but I forgot to write
  2005. them down—something like one photo per minute, because all her photos are done with
  2006. <a href="">DxO PhotoLab's</a> <a href="">DeepPRIME</a> feature.  But that
  2007. increase in processing speed didn't seem as dramatic as I had noticed
  2008.      </p>
  2010.      <p>
  2011. But why limit myself to 8 CPUs?  <i>hydra</i> has 32 logical CPUs.  I could easily increase
  2012. the number on <i>distress</i> to 16.
  2013.      </p>
  2015.      <p>
  2016. And, probably, invalidate my license keys.  OK, how about cloning it?  And yes, that's easy.
  2017. Shut down the machine, right click on it, select <b>Clone</b> and follow the instructions.
  2018. And without much ado I had a new machine, which Yvonne decided to
  2019. call <i></i>.  But <a href="">DxO
  2020. PhotoLab</a> decided that my license key was invalid, and so did Microsoft.  I have DxO's
  2021. license key written down, and their support team was relatively responsive with the key for
  2022. <a href="">“ViewPoint”</a> (which I haven't
  2023. applied yet), so once I'm happy we could stick with <i>despise</i>.
  2024.      </p>
  2026.      <p>
  2027. And how did Yvonne go?  Worked out of the box modulo setting DxO in 30 day trial mode.  And
  2028. it was much faster.  The only issue was memory: it only had 16 GB of memory, and running 14
  2029. concurrent conversions (the maximum) it was hitting memory limits.  So I should probably add
  2030. another 8 GB of memory.
  2031.      </p>
  2033.      <p>
  2034. My own access to the machine was less satisfactory:
  2035.      </p>
  2037.      <blockquote class="fullwidth">
  2038. <div style="text-align:left">
  2039.  <tt>
  2040. <code><font color="blue">=== grog@hydra (/dev/pts/29)</font> <font color="red">~/Photos/20240405</font> <font color="blue">942</font> &#45;&gt; <b><tt>/home/local/bin/dordesktop despise 3790x2110+0 &amp;</tt></b></code>
  2041. <br />Connecting to despise
  2042. <br />
  2043. <br />ATTENTION! The server uses and invalid security certificate which can not be trusted for
  2044. <br />the following identified reasons(s);
  2045. <br />...
  2046. <br />
  2047. <br />Do you trust this certificate (yes/no)? Core(error): Failed to read response from stdin
  2048. <br />Segmentation fault (core dumped)
  2049. <br />Disconnected from despise, status 139
  2050. <br />
  2051.  </tt>
  2052. </div>
  2053. </blockquote>
  2055.      <p>
  2056. And that was repeatable.  <i>rdesktop</i> really dumped core for no obvious reason.  But
  2057. that, too, will find a solution.
  2058.      </p>
  2059.      </div>
  2060.    ]]>
  2061.  </description>
  2062.  <dc:creator>Greg Lehey</dc:creator>
  2063.  <dc:date>2024-04-07T01:44:20+00:00</dc:date>
  2064. </item>
  2067. <item>
  2068. <guid isPermaLink='true'></guid>
  2069. <link></link>
  2070. <category>general</category>
  2071. <category>photography</category>
  2072. <category>technology</category>
  2073. <category>opinion</category>
  2074. <title>DST ends</title>
  2075.  <description>
  2076.    <![CDATA[
  2077.    <div align="justify">
  2078.      <p>
  2079. <a href="">Daylight Saving Time</a> ended today.  Lots of clocks to change, including my cameras.
  2080.      </p>
  2082.      <p>
  2083. In days gone by I have used this horrible <a href="">OI.Share</a>, mobile phone app to set the
  2084. time on the OM-D cameras.  But it's <i>such</i> a pain.  It has the advantage of setting it
  2085. almost exactly correct (why do mobile phones, which use <a href="">NTP</a>, still have times that
  2086. vary by a couple of seconds?).  But is it that important?  <a href="">Yvonne's</a> <a href="">Olympus
  2087. OM-D E-M5 Mark III</a> proved to be 3 minutes fast.  That's 1 second per day since DST
  2088. started, but should I (or Yvonne) constantly reset it?  I'd be for resetting only when it
  2089. really makes sense, and then I can do it with programs after the event, like this case
  2090. <a href=";article=D17-10#D17-10">14 years ago</a>      </p>
  2092.        <a id="Photo-14" name="Photo-14"
  2093.          href="diary-apr2024.php?dirdate=20100417&amp;imagesizes=111111111111112&amp;topics=c#Photo-14">
  2094.          <img alt="This should be Evening-19.jpeg.  Is it missing?" border="0" id="Photo_14"
  2095.               title="Photo Evening-19.jpeg.  Click to redisplay larger version of image."
  2096.               src=""
  2097.               width="319" height="212"
  2098.           /></a>
  2099.        <a id="Photo-15" name="Photo-15"
  2100.          href="diary-apr2024.php?dirdate=20100417&amp;imagesizes=1111111111111112&amp;topics=c#Photo-15">
  2101.          <img alt="This should be Evening-7.jpeg.  Is it missing?" border="0" id="Photo_15"
  2102.               title="Photo Evening-7.jpeg.  Click to redisplay larger version of image."
  2103.               src=""
  2104.               width="225" height="300"
  2105.           /></a>
  2107.      <p>
  2108. Setting the time manually was so much faster, though several cameras managed to change 2
  2109. hours instead of one, presumably a key bounce issue.  What I did discover, however, was that
  2110. the date on the
  2111. <a href="">E-30</a> was wrong.  Some time last
  2112. month it seems that it decided that the month was December, as the <tt>mdir</tt> output shows:
  2113.      </p>
  2115.      <blockquote class="fullwidth">
  2116. <div style="text-align:left">
  2117.  <tt>
  2118. 53102888 ORF &nbsp;10993760 2024&#45;03&#45;10 &nbsp;13:25
  2119. <br />53102889 ORF &nbsp;13378519 2024&#45;03&#45;10 &nbsp;13:25
  2120. <br />53152890 ORF &nbsp;10993854 2024&#45;03&#45;15 &nbsp;13:25
  2121. <br />53152891 ORF &nbsp;13225868 2024&#45;03&#45;15 &nbsp;13:25
  2122. <br />53162892 ORF &nbsp;10993377 2024&#45;03&#45;16 &nbsp;13:25
  2123. <br />
  2124.  </tt>
  2125. </div>
  2126. </blockquote>
  2128.      <p>
  2129. Was it only the month?  The time shows 13:25 every time, <a href="">mean solar noon</a>, so it probably was.  I wonder
  2130. how that happened.  But the camera is now over 15 years old, so I'll just keep my eye on the
  2131. date when I turn it on.
  2132.      </p>
  2133.      </div>
  2134.    ]]>
  2135.  </description>
  2136.  <dc:creator>Greg Lehey</dc:creator>
  2137.  <dc:date>2024-04-08T02:29:32+00:00</dc:date>
  2138. </item>
  2141. <item>
  2142. <guid isPermaLink='true'></guid>
  2143. <link></link>
  2144. <category>technology</category>
  2145. <category>language</category>
  2146. <category>opinion</category>
  2147. <title>More fun with Aussie</title>
  2148.  <description>
  2149.    <![CDATA[
  2150.    <div align="justify">
  2151.      <p>
  2152. To my surprise, three messages from <a href="">Aussie
  2153. Broadband</a> <del>support</del> accounts today.  One was a boilerplate acknowledgement that I had
  2154. complained about not being allowed access to CJ's account <a href=";article=D-20240407-003200#D-20240407-003200">yesterday</a> with no
  2155. suggestion about what went wrong, just suggesting that CJ should authorize me, something that happened in July last year.  So I
  2156. sent a <a href="">reply</a> asking in particular:
  2157.      </p>
  2159.      <blockquote class="fullwidth">
  2160. <div style="text-align:left">
  2161.  <tt>
  2162. Please respond and tell me:
  2163. <br />
  2164. <br />1. &nbsp;What aspect of my identification does not meet your approval.
  2165. <br />2. &nbsp;Why your support staff have so far agreed that I am a
  2166. <br />&nbsp;&nbsp; &nbsp;representative.
  2167. <br />3. &nbsp;Where these privacy laws are stated.
  2168. <br />4. &nbsp;What makes you think that name, address and date of birth are any
  2169. <br />&nbsp;&nbsp; &nbsp;kind of evidence of the identity of the caller. &nbsp;All of this is
  2170. <br />&nbsp;&nbsp; &nbsp;available on the web.
  2171. <br />
  2172.  </tt>
  2173. </div>
  2174. </blockquote>
  2176.      <p>
  2177. I also noted that I would raise this matter with the <a href="">TIO</a>.
  2178.      </p>
  2180.      <p>
  2181. And then there was another message addressed to the same thread, but referring to the VoIP issue.
  2182. The final message was more to the point:
  2183.      </p>
  2185.      <blockquote class="fullwidth">
  2186. <div style="text-align:left">
  2187.  <tt>
  2188. Unfortunately we are unable to access the modem as our logs are show a
  2189. <br />connection to a dell devices at the moment.
  2190. <br />
  2191. <br />Are you able to confirm the Ethernet coming from the NBN box is connected to
  2192. <br />the WAN port on the modem.
  2193. <br />
  2194.  </tt>
  2195. </div>
  2196. </blockquote>
  2198.      <p>
  2199. This silly “modem” word again.  Clearly he's talking about the Netcomm router.  But that
  2200. does look strange.  CJ's machine is made by <a href="">Dell</a> (how did they identify it?  <a href="">MAC address</a>?).  Has he wired it up
  2201. wrong?  Sent him off a message:
  2202.      </p>
  2204.      <blockquote class="fullwidth">
  2205. <div style="text-align:left">
  2206.  <tt>
  2207. You'll have seen this message below, which I copied you on. &nbsp;I think
  2208. <br />they're still barking up the wrong tree, but one thing makes me
  2209. <br />wonder: they talk about seeing a Dell device. &nbsp;Your computer is Dell,
  2210. <br />right? &nbsp;Are you sure you connected the cables up correctly? &nbsp;As I said:
  2211. <br />
  2212. <br />&gt; 1. &nbsp;NTD connected to a Netcomm router (via Ethernet, of course).
  2213. <br />&gt; 2. &nbsp;Router connected to a Microsoft computer and two phones.
  2214. <br />
  2215. <br />In English: the box on the wall is connected to the red connector on
  2216. <br />the router. &nbsp;The computer is connected to one of the yellow connectors
  2217. <br />on the router. &nbsp;Is this what you have done? &nbsp;If not:
  2218. <br />
  2219. <br />1. &nbsp;Write down how you connected the cables, and tell me by email.
  2220. <br />2. &nbsp;Fix it.
  2221. <br />
  2222. <br />This should be done as quickly as possible.
  2223. <br />
  2224.  </tt>
  2225. </div>
  2226. </blockquote>
  2228.      <p>
  2229. And the response?  A total of three, all saying nothing and not answering what I thought
  2230. were clear instructions, except to say that he <i>had</i> connected the computer directly to
  2231. the NTD to get any connection at all, and that the phones (on the router) were <i>still</i>
  2232. not working.  By the end of the day we still had nothing.  I'm beginning to think that the
  2233. current issues are of CJ's making.
  2234.      </p>
  2236.      <p>
  2237. Later in the day, another message from Aussie:
  2238.      </p>
  2240.      <blockquote class="fullwidth">
  2241. <div style="text-align:left">
  2242.  <tt>
  2243. In a fixed wireless setup, the NBN box/NTD/Network terminal device, often gets
  2244. <br />called the modem.
  2245. <br />
  2246.  </tt>
  2247. </div>
  2248. </blockquote>
  2250.      <p>
  2251. I assume that this is  a response to my reply quoted above:
  2252.      </p>
  2254.      <blockquote class="fullwidth">
  2255. <div style="text-align:left">
  2256.  <tt>
  2257. &gt; There is no modem. &nbsp;I haven't checked personally, but what I
  2258. <br />&gt; understand is:
  2259. <br />&gt;
  2260. <br />&gt; 1. &nbsp;NTD connected to a Netcomm router (via Ethernet, of course).
  2261. <br />&gt; 2. &nbsp;Router connected to a Microsoft computer and two phones.
  2262. <br />
  2263.  </tt>
  2264. </div>
  2265. </blockquote>
  2267.      <p>
  2268. Clearly the second responder misunderstood.  The first called the router a “modem”.  The
  2269. second called the <a href="">NTD</a> a
  2270. “modem”.  What better example of why you shouldn't use <a href="">inappropriate terms</a>?
  2271.      </p>
  2272.      </div>
  2273.    ]]>
  2274.  </description>
  2275.  <dc:creator>Greg Lehey</dc:creator>
  2276.  <dc:date>2024-04-08T02:48:26+00:00</dc:date>
  2277. </item>
  2280. <!-- topic ko not selected
  2281.      <p>
  2282. Baked chicken thighs again today.  We did them <a href=";subtitle=%E2%80%9CAir%20fried%E2%80%9D%20chicken%20thighs&amp;article=D-20240202-012506#D-20240202-012506">two months ago</a> in the “hair dryer” air fryer, and they came out more or less as
  2283.        planned: meat temperature 78° after 21 minutes at 210°:
  2284.      </p>
  2287.      <p>
  2288. But they seemed to have required a higher meat temperature.  OK, as planned, this time 30
  2289. minutes to achieve 82°.
  2290.      </p>
  2292.      <p>
  2293. That took 13 minutes, and the thighs didn't look as brown as they could.  Clearly I had
  2294. placed the temperature probe in the wrong place.  Turned off the thermometer and went by
  2295. eye, stopping when they seemed OK:
  2296.      </p>
  2299.      <p>
  2300. That was after about 18 minutes!  And certainly they were cooked enough.  The thermometer
  2301. showed a temperature round 95°.  They tasted fine, but I'm still dissatisfied.  Why the
  2302. difference?  These thighs were smaller, but that wouldn't significantly affect the time it
  2303. took to brown them.  Maybe the start temperature (21°)?  I didn't note it last time.
  2304.      </p>
  2306. End deselected topic ko (Baked chicken thighs again) -->
  2309. <item>
  2310. <guid isPermaLink='true'></guid>
  2311. <link></link>
  2312. <category>technology</category>
  2313. <category>opinion</category>
  2314. <title>VoIP problems: resolved!</title>
  2315.  <description>
  2316.    <![CDATA[
  2317.    <div align="justify">
  2318.      <p>
  2319. Mail from CJ Ellis this morning:
  2320.      </p>
  2322.      <blockquote class="fullwidth">
  2323. <div style="text-align:left">
  2324.  <tt>
  2325. Good morning Greg .good news , the phone is working It seems that their
  2326. <br />message bank is now working properly for me , but I am 26 in the que , I am
  2327. <br />hope to get a message bank on the phone as it was as I wanted in the first
  2328. <br />place with themm .. Sore y for all you troubles with them ... It was good
  2329. <br />to get to the computer to find all the lights working on the router &amp; the
  2330. <br />phone working ..
  2331. <br />
  2332.  </tt>
  2333. </div>
  2334. </blockquote>
  2336.      <p>
  2337. What does that mean?  It's certainly not an answer to my questions.  My best guess is that
  2338. he finally plugged the thing in, and it worked.
  2339.      </p>
  2341.      <p>
  2342. CJ, I've spent the best part of a week trying to work around <a href="">Aussie Broadband</a> to solve the problems.  The last
  2343. two days, including the extreme annoyance of not being able to authenticate myself, were
  2344. only due to you not following instructions.  Sorry, my good will is exhausted.  Next time
  2345. find somebody else to solve your perceived issues.
  2346.      </p>
  2348.      <p>
  2349. That still leaves a question open: my second phone line (the one listed in the phone book)
  2350. no longer works, showing the same symptoms that CJ's did (can call out, incoming calls ring
  2351. but return a busy signal to the caller).  At first I thought that it was directly related to
  2352. reconfiguring the <a href="">ATA</a>, but quite possibly it's been like that for a long time.  I only have the phone
  2353. to collect voice messages, and for that Aussie is particularly useless: there's no way to
  2354. find if you have voice mail except by calling the voice mail number.  So an alternative
  2355. might be a less painful way to fix it.
  2356.      </p>
  2357.      </div>
  2358.    ]]>
  2359.  </description>
  2360.  <dc:creator>Greg Lehey</dc:creator>
  2361.  <dc:date>2024-04-09T03:04:08+00:00</dc:date>
  2362. </item>
  2365. <item>
  2366. <guid isPermaLink='true'></guid>
  2367. <link></link>
  2368. <category>technology</category>
  2369. <category>opinion</category>
  2370. <title>More Aussie Broadband pain</title>
  2371.  <description>
  2372.    <![CDATA[
  2373.    <div align="justify">
  2374.      <p>
  2375. Response from <a href="">Aussie Broadband</a> <del>support</del> accounts to my <a href="">authentication questions</a> yesterday.  No attempt to address my issues, just
  2376.      </p>
  2378.      <blockquote class="fullwidth">
  2379. <div style="text-align:left">
  2380.  <tt>
  2381. I strongly suggest you contact our team on 1300 880 905 with CJ so we can
  2382. <br />arrange a solution to this issue.
  2383.  </tt>
  2384. </div>
  2385. </blockquote>
  2387.      <p>
  2388. And I explained why that won't work 2 days ago.  OK, up a notch:
  2389.      </p>
  2391.      <blockquote class="fullwidth">
  2392. <div style="text-align:left">
  2393.  <tt>
  2394. Please note the TIO deadline tomorrow and forward this matter to your
  2395. <br />complaints team. &nbsp;I expect to see a complaint number with details (not
  2396. <br />just asterisks) by this evening.
  2397. <br />
  2398.  </tt>
  2399. </div>
  2400. </blockquote>
  2402.      <p>
  2403. And I got a complaint number **16941085**, with no text.  <i>Sigh</i>.
  2404.      </p>
  2405.      </div>
  2406.    ]]>
  2407.  </description>
  2408.  <dc:creator>Greg Lehey</dc:creator>
  2409.  <dc:date>2024-04-09T03:04:26+00:00</dc:date>
  2410. </item>
  2413. <!-- topic k not selected
  2414.      <p>
  2415. We've had our coffee machine for <a href=";article=D-20191109-224636#D-20191109-224636">over 4 years now</a>, and modulo routine annoyance with “descaling” (not needed for
  2416. rainwater), it works well.  But in the last couple of days the water tank looks like this:
  2417.      </p>
  2420.      <p>
  2421. What causes that?  Is it indicative of something in our water tanks?
  2422.      </p>
  2424. End deselected topic k (Green coffee water tank) -->
  2427. <item>
  2428. <guid isPermaLink='true'></guid>
  2429. <link></link>
  2430. <category>technology</category>
  2431. <category>opinion</category>
  2432. <title>despise performance comparison</title>
  2433.  <description>
  2434.    <![CDATA[
  2435.    <div align="justify">
  2436.      <p>
  2437. Comparison of photo processing times using <a href="">DxO PhotoLab</a> <a href="">DeepPRIME</a>:
  2438.      </p>
  2440.      <table summary="Automatically generated table">
  2441.       <tr>
  2442.          <td valign="top" align="left">Machine</td>
  2443.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2444.          <td valign="top" align="right">Number</td>
  2445.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2446.          <td valign="top" align="right">Time</td>
  2447.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2448.          <td valign="top" align="right">Time/photo</td>
  2449.       </tr>
  2451.       <tr>
  2452.          <td valign="top" align="left">despise</td>
  2453.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2454.          <td valign="top" align="right">133</td>
  2455.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2456.          <td valign="top" align="right">41:20</td>
  2457.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2458.          <td valign="top" align="right">19..5 s</td>
  2459.       </tr>
  2461.       <tr>
  2462.          <td valign="top" align="left">distress</td>
  2463.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2464.          <td valign="top" align="right">29</td>
  2465.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2466.          <td valign="top" align="right">33:32</td>
  2467.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2468.          <td valign="top" align="right">70.0 s</td>
  2469.       </tr>
  2471.       <tr>
  2472.          <td valign="top" align="left">distress</td>
  2473.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2474.          <td valign="top" align="right">34</td>
  2475.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2476.          <td valign="top" align="right">37:26</td>
  2477.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2478.          <td valign="top" align="right">66.1 s</td>
  2479.       </tr>
  2481.       <tr>
  2482.          <td valign="top" align="left"></td>
  2483.       </tr>
  2484.    </table>
  2486.      <p>
  2487. I think we can accept that that's considerably faster.  And I was able to activate both
  2488. <a href="">DxO PhotoLab</a> and <a href="">“ViewPoint”</a>.  That just leaves <a href="">“Windows” </a> itself, and for that I need to find what I have done
  2489. with the license key.
  2490.      </p>
  2492.      <p>
  2493. All perfect?  Not quite.  Why does this system use so much CPU time when idle?
  2494.      </p>
  2496.      <blockquote class="fullwidth">
  2497. <div style="text-align:left">
  2498.  <tt>
  2499. &nbsp;&nbsp;PID USERNAME &nbsp; &nbsp;THR PRI NICE &nbsp; SIZE &nbsp; &nbsp;RES STATE &nbsp; &nbsp;C &nbsp; TIME &nbsp; &nbsp;WCPU COMMAND
  2500. <br />56239 grog &nbsp; &nbsp; &nbsp; &nbsp; 45 &nbsp;20 &nbsp; &nbsp;0 &nbsp; &nbsp;25G &nbsp; &nbsp;25G select &nbsp; 9 &nbsp;69.5H 254.78% VirtualBoxVM
  2501. <br />
  2502.  </tt>
  2503. </div>
  2504. </blockquote>
  2506.      <p>
  2507. Is this maybe typical of Microsoft?  It's not a big deal, since I can put it to sleep when I
  2508. don't need it, but it would be interesting to understand.
  2509.      </p>
  2510.      </div>
  2511.    ]]>
  2512.  </description>
  2513.  <dc:creator>Greg Lehey</dc:creator>
  2514.  <dc:date>2024-04-09T03:20:35+00:00</dc:date>
  2515. </item>
  2518. <!-- topic h not selected
  2519.      <p>
  2520. After cleaning my teeth last night, put my toothbrush on its charger.  The charge light
  2521. didn't go on.  <i>Another</i> dead toothbrush?  Took it into <a href="">Yvonne's</a> bathroom and tried it on the charger there.  Still no light.  Replaced
  2522. Yvonne's toothbrush.  No light.
  2523.      </p>
  2525.      <p>
  2526. Oh.  Into the garage and to the switchboard.  Circuit breaker tripped.  Turned it on and
  2527. heard a <i>beep</i> not far away.  What's that?  But yes, now both toothbrushes charged.
  2528.      </p>
  2530.      <p>
  2531. But this morning it had failed again, and this time it stayed failed.  OK, what's on this
  2532. circuit?  Guest bedroom, laundry (including a freezer, the source of the <i>beep</i>), and
  2533. outside, of course, the sewage pump and the bore water pump.  The latter two seem the most
  2534. likely cause, particularly given the borderline waterproof connections used for external
  2535. power points in Australia.  Disconnected them and turned the breaker on again.  It stayed
  2536. on.
  2537.      </p>
  2539.      <p>
  2540. So one of the exterior pumps is involved.  Which?  It's a borderline issue, so I left them
  2541. disconnected all day, and we had no further issues.  Tomorrow I can start reconnecting.
  2542.      </p>
  2544. End deselected topic h (More power problems) -->
  2547. <item>
  2548. <guid isPermaLink='true'></guid>
  2549. <link></link>
  2550. <category>technology</category>
  2551. <category>general</category>
  2552. <category>opinion</category>
  2553. <title>Aussie complaints make contact</title>
  2554.  <description>
  2555.    <![CDATA[
  2556.    <div align="justify">
  2557.      <p>
  2558. Mail from <a href="">Aussie Broadband</a> about my
  2559. complaint.  In summary:
  2560.      </p>
  2562.      <blockquote class="fullwidth">
  2563. <div style="text-align:left">
  2564.  <tt>
  2565. Thank you for bringing your concerns to our attention regarding the difficulties you've encountered
  2566. <br />with unauthorized access to the account. We understand the importance of addressing this matter
  2567. <br />promptly and appreciate your patience as we work to find a resolution.
  2568. <br />
  2569. <br />As per the guidelines outlined by the Australian Communications and Media Authority (ACMA), our
  2570. <br />company is required to adhere to strict customer identity authentication rules to safeguard the
  2571. <br />privacy and security of our customers' information. This includes verifying all points of
  2572. <br />identification to ensure compliance with privacy laws.
  2573. <br />
  2574. <br />For more information on ACMA's customer identity authentication rules, please visit the following
  2575. <br />link: [;identity&#45;authentication&#45;rules]
  2576. <br />
  2577. <br />At this stage, we have marked your complaint as resolved, as we are following the prescribed rules
  2578. <br />and procedures for customer privacy and safety. We appreciate your understanding of our position on
  2579. <br />this matter.
  2580. <br />
  2581.  </tt>
  2582. </div>
  2583. </blockquote>
  2585.      <p>
  2586. Is there <i>anything</i> in there that suggests that they have even read the complaint?
  2587. Despite multiple requests they certainly haven't sent me the text, and they have addressed
  2588. none of the issues.  Is Aussie staffed by morons?
  2589.      </p>
  2591.      <p>
  2592. About the only thing of interest is the link <a href=""></a>.  I followed it
  2593. and found <i>nothing</i> to support their actions or claims.  It was interesting, though: it
  2594. refers to “high-risk customer transactions”, which include:
  2595.      </p>
  2597.      <blockquote class="fullwidth">
  2598.        <ul>
  2599.  <li class="listitemwidth">
  2600.    SIM swaps
  2601.  </li>
  2603.  <li class="listitemwidth">
  2604.    transfers from a post-paid to a pre-paid service
  2605.  </li>
  2607.  <li class="listitemwidth">
  2608.    transfers of title (also known as change of ownership)
  2609.  </li>
  2611.  <li class="listitemwidth">
  2612.    adding additional phone service/s to an account
  2613.  </li>
  2615.  <li class="listitemwidth">
  2616.    activating a service for an overseas customer
  2617.  </li>
  2619.  <li class="listitemwidth">
  2620.    buying an additional mobile phone
  2621.  </li>
  2623.  <li class="list2width">
  2624.    blocking an International Mobile Equipment Identity or a Permanent Equipment Identifier.
  2625.  </li>
  2626. </ul>
  2628. <p class="listitemwidth">
  2629.  Depending on the services you provide, you may identify more high-risk transactions than
  2630.  just those listed above.
  2631. </p>
  2632.      </blockquote>
  2634.      <p>
  2635. Clearly this is a different category of transaction from reporting a fault.  But Aussie
  2636. demands this authentication before even knowing what the matter is.  And what about this
  2637. stupid “give me your name, address and date of birth”?  The rules, <b>only for high-risk
  2638. customer transactions</b>, are:
  2639.      </p>
  2641.      <blockquote class="fullwidth">
  2642. <p class="listitemwidth">
  2643.  <strong>3. Implement MFA for high-risk customer transactions</strong>. An example of MFA
  2644.  where a requesting person initiates a high-risk customer transaction is:
  2645. </p>
  2647. <ol>
  2648.  <li class="list2width">
  2649.    an account username and password, <strong>and</strong>
  2650.  </li>
  2652.  <li class="list2width">
  2653.    a unique verification code or secure link, sent to the customer’s mobile number or
  2654.    validated mobile application.
  2655.  </li>
  2656. </ol>
  2657.      </blockquote>
  2659.      <p>
  2660. No mention of date of birth.  User name and password.  And under the circumstances they
  2661. mention, <a href="">multi-factor authentication</a> is acceptable.
  2662.      </p>
  2664.      <p>
  2665. So: Aussie doesn't have a leg to stand on.  I sent them a corresponding answer, reminding
  2666. them of this evening's <a href="">TIO</a> deadline.
  2667.      </p>
  2669.      <p>
  2670. And I got another reply, talking about how their support people had done everything
  2671. correctly.  Huh?  What does that have to do with authentication?  Replied accordingly,
  2672. reminding them that I still hadn't seen the text of the complaint.  It wasn't until later
  2673. that I discovered that this was a response to the other complaint that I had initiated on
  2674. <a href=";article=D-20240405-004130#D-20240405-004130">Thursday</a>.  Once again I think they got the wrong end of the stick, but without the
  2675. text of the complaint it's hard to say who is to blame.
  2676.      </p>
  2678.      <h4>
  2679. Preparing the TIO complaint
  2680.      </h4>
  2682.      <p>
  2683. So what do I say to the TIO?  Clearly this needs preparation.  What I see is:
  2684.      </p>
  2686.      <ul>
  2687.        <li class="fullwidth">
  2688.          <div class="listitemwidth">
  2689.            Aussie relies on antiquated authentication methods like address and date of birth,
  2690.            things that many people can know.  I have all the information needed to “authenticate”
  2691.            myself as CJ, for example.  And the <a href="">ACMA</a> rules specifically mention user names and passwords, which are obvious choices.
  2692.          </div>
  2693.        </li>
  2695.        <li class="fullwidth">
  2696.          <div class="listitemwidth">
  2697.            Aussie applies extreme authentication rules even when not necessary.  I can almost
  2698.            accept this one; what happens if things change in mid-discussion?
  2699.          </div>
  2700.        </li>
  2702.        <li class="fullwidth">
  2703.          <div class="listitemwidth">
  2704.            Aussie refused to authenticate me <a href=";article=D-20240407-003200#D-20240407-003200">on Saturday</a>, and they won't say why.
  2705.          </div>
  2706.        </li>
  2708.        <li class="fullwidth">
  2709.          <div class="listitemwidth">
  2710.            Aussie doesn't even seem to have read my complaint, closing it without any action.
  2711.          </div>
  2712.        </li>
  2713.      </ul>
  2715.      <p>
  2716. Is there more?  To be considered.
  2717.      </p>
  2719.            </div>
  2720.    ]]>
  2721.  </description>
  2722.  <dc:creator>Greg Lehey</dc:creator>
  2723.  <dc:date>2024-04-10T01:33:01+00:00</dc:date>
  2724. </item>
  2727. <!-- topic G not selected
  2728.      <p>
  2729. Call from <a href="">David Fabinyi</a> today about
  2730. the <a href="">intraocular lens</a> for my left eye.  It seems that when combined with a <a href="">vitrectomy</a>, some residual <a href="">astigmatism</a> can remain, and the
  2731. accuracy of focus can vary depending on the results of the operation.  Makes perfect sense,
  2732. but it's not quite what I heard <a href=",%20second%20opinion&amp;article=D-20240201-014854#D-20240201-014854">on our first appointment</a>.
  2733.      </p>
  2735.      <p>
  2736. Based on what they've seen, I probably have some corneal astigmatism, and for the left eye
  2737. he has chosen a <a href="">Toric IOL</a> with
  2738. focus at infinity.  That all sounds very good, and it confirms the validity of my decision
  2739. to have my right (non-dominant) eye first.  So the procedure can continue on Thursday as
  2740. planned.
  2741.      </p>
  2743.      <p>
  2744. In passing, it seems that they have a whole stock of IOLs, and the can return what they
  2745. don't need.  David had a choice of two for me, and we'll discuss it before the procedure on
  2746. Thursday.  He mentioned the purchase prices that they pay are in the order of $400 to $800,
  2747. but he estimates that the manufacturing cost is much lower.
  2748.      </p>
  2750. End deselected topic G (Cataracts: next step) -->
  2753. <item>
  2754. <guid isPermaLink='true'></guid>
  2755. <link></link>
  2756. <category>technology</category>
  2757. <category>general</category>
  2758. <category>opinion</category>
  2759. <title>18 years of blog!</title>
  2760.  <description>
  2761.    <![CDATA[
  2762.    <div align="justify">
  2763.      <p>
  2764. Mail from <a href="">LiveJournal</a> today,
  2765. enclosing (if that's the word) a “virtual gift” for <a href="">being with them</a> for 18 years.  That was a
  2766. reaction to people calling my diary a “blog”, and it was very short-lived, round 2 days.  I
  2767. seem to have <a href="">barely mentioned</a> it in
  2768. my diary.
  2769.      </p>
  2770.      </div>
  2771.    ]]>
  2772.  </description>
  2773.  <dc:creator>Greg Lehey</dc:creator>
  2774.  <dc:date>2024-04-10T02:20:57+00:00</dc:date>
  2775. </item>
  2778. <item>
  2779. <guid isPermaLink='true'></guid>
  2780. <link></link>
  2781. <category>technology</category>
  2782. <category>opinion</category>
  2783. <title>Aussie Broadband: Go away</title>
  2784.  <description>
  2785.    <![CDATA[
  2786.    <div align="justify">
  2787.      <p>
  2788. Another message from <a href="">Aussie Broadband</a> complaints today.  It seems that they have completely misunderstood the complaint, something
  2789. that could only have happened if they had read neither the complaint nor my messages.  But
  2790. the content is amazing:
  2791.      </p>
  2793.      <blockquote class="fullwidth">
  2794. <div style="text-align:left">
  2795.  <tt>
  2796. I understand your concern at this point in time. However, what you are
  2797. <br />requesting is not something we can accommodate. I have reached out to our
  2798. <br />compliance team for further input.
  2799.  </tt>
  2800. </div>
  2801. </blockquote>
  2803.      <p>
  2804. He understands my concern?  There's no evidence whatsoever of that.  And why can't he
  2805. “accommodate” what “I am requesting”?  My guess is because he has so little understanding of
  2806. the issue that he can't do anything.
  2807.      </p>
  2809.      <blockquote class="fullwidth">
  2810. <div style="text-align:left">
  2811.  <tt>
  2812. As per our ACMA complaint guidelines, we may take up to 10 days for further
  2813. <br />response. If this complaint goes to the TIO, it is still within the ideal time
  2814. <br />frame.
  2815.  </tt>
  2816. </div>
  2817. </blockquote>
  2819.      <p>
  2820. “We are fully bureaucracy compliant”.
  2821.      </p>
  2823.      <blockquote class="fullwidth">
  2824. <div style="text-align:left">
  2825.  <tt>
  2826. Alternatively, if you are not happy with our policy, and since you are not in
  2827. <br />a lock&#45;in contract, you may look for an ISP which suits your needs in regards
  2828. <br />to your privacy.
  2829. <br />
  2830.  </tt>
  2831. </div>
  2832. </blockquote>
  2834.      <p>
  2835. “We won't fix the problem.  Go away”.  But the interesting thing is “your needs in regards
  2836. to your privacy”.  Clearly he has understood <i>nothing</i>.
  2837.      </p>
  2839.      <p>
  2840. How do you complain about a complaints person who doesn't do his job?
  2841.      </p>
  2842.      </div>
  2843.    ]]>
  2844.  </description>
  2845.  <dc:creator>Greg Lehey</dc:creator>
  2846.  <dc:date>2024-04-11T03:53:21+00:00</dc:date>
  2847. </item>
  2850. <item>
  2851. <guid isPermaLink='true'></guid>
  2852. <link></link>
  2853. <category>technology</category>
  2854. <category>general</category>
  2855. <category>opinion</category>
  2856. <title>Authenticating calls</title>
  2857.  <description>
  2858.    <![CDATA[
  2859.    <div align="justify">
  2860.      <p>
  2861. Returning to the issue of authentication, I have had contact with three different health
  2862. service providers this week: <a href="">Specsavers</a>, <a href="">St John of God</a> in
  2863. <a href="">Geelong</a> and <a href="">Health First</a>.  All accepted my call without
  2864. identification, at least once: on calling back to Health First, I was asked for the
  2865. inevitable date of birth.
  2866.      </p>
  2868.      <p>
  2869. Why not the others?  Because they recognized my phone number.  Health First did that once
  2870. too, but they “up”graded their booking software.  Specsavers knew all my data without having
  2871. to ask.  And the things that they were doing were more “high risk” than anything I do with
  2872. Aussie.  And Aussie of all people should be able to identify the phone, since it's with
  2873. them.
  2874.      </p>
  2876.      <p>
  2877. On the other hand, I read an <a href="">article</a> today about a person scammed out of $10,000 with a related exploit, one of
  2878. the high risk transactions explicitly mentioned in the <a href="">ACMA</a> guidelines: a <a href="">SIM</a> swap.  I
  2879. haven't finished analysing the somewhat confused article, but it seems that the victim made
  2880. two mistakes:
  2881.      </p>
  2883.      <ul>
  2884.        <li class="fullwidth">
  2885.          <p class="listitemwidth">
  2886.            Storing access details for his bank accounts on his mobile phone.
  2887.          </p>
  2888.        </li>
  2890.        <li class="fullwidth">
  2891.          <p class="listitemwidth">
  2892.            Having an account with <a href="">Optus</a>.
  2893.            They sent him a message to his mobile phone (much use if it had been stolen) and timed
  2894.            out.  So rather than refusing the transaction, they allowed it!  This image from the
  2895.            article:
  2896.          </p>
  2898.    <a id="Photo-16" name="Photo-16"
  2899.          href="diary-apr2024.php?dirdate=20240410&amp;imagesizes=11111111111111112&amp;topics=c#Photo-16">
  2900.          <img alt="This should be Optus-security.png.  Is it missing?" border="0" id="Photo_16"
  2901.               title="Photo Optus-security.png.  Click to redisplay larger version of image."
  2902.               src=""
  2903.               width="258" height="262"
  2904.           /></a>
  2905.        </li>
  2906.      </ul>
  2908.      <p>
  2909. But clearly that's another issue altogether.  And even if they had received a positive
  2910. reply, what does that mean?  As the article states,
  2911.      </p>
  2913.      <blockquote class="fullwidth">
  2914.        <p class="listitemwidth">
  2915.          ETEL said it sent a unique verification code via SMS to ensure the customer seeking to
  2916.  port their phone number was <b> in possession of the device</b> (my emphasis).
  2917.        </p>
  2918.      </blockquote>
  2920.      <p>
  2921. And how does that help identify the customer?  To me, it does suggest a lot of caution in
  2922. choosing a new <a href="">RSP</a>, however (not that Optus would have come close to being a choice).
  2923.      </p>
  2924.      </div>
  2925.    ]]>
  2926.  </description>
  2927.  <dc:creator>Greg Lehey</dc:creator>
  2928.  <dc:date>2024-04-11T04:06:01+00:00</dc:date>
  2929. </item>
  2932. <!-- topic Go not selected
  2933.      <p>
  2934. So it seems that I have some corneal <a href="">astigmatism</a>, something that nobody told
  2935. me about until I found out last week.  But 1 <a href="">dioptre</a>?  That seems a little unusual.  Off
  2936. looking for my prescriptions, and came up with this one from <a href=";article=D-20210128-024301#D-20210128-024301">January 2021</a>:
  2937.      </p>
  2939.      <table summary="Automatically generated table">
  2940.       <tr>
  2941.          <td valign="top" align="left">Eye</td>
  2942.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2943.          <td valign="top" align="left">Spherical </td>
  2944.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2945.          <td valign="top" align="left">Cylindrical </td>
  2946.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2947.          <td valign="top" align="left">Axis </td>
  2948.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2949.          <td valign="top" align="left">Near-add</td>
  2950.       </tr>
  2952.       <tr>
  2953.          <td valign="top" align="left">R </td>
  2954.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2955.          <td valign="top" align="left">+2.25 </td>
  2956.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2957.          <td valign="top" align="left">-1.25 </td>
  2958.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2959.          <td valign="top" align="left">115° </td>
  2960.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2961.          <td valign="top" align="left">+2.50</td>
  2962.       </tr>
  2964.       <tr>
  2965.          <td valign="top" align="left">L </td>
  2966.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2967.          <td valign="top" align="left">+2.00 </td>
  2968.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2969.          <td valign="top" align="left">-0.50 </td>
  2970.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2971.          <td valign="top" align="left">105° </td>
  2972.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  2973.          <td valign="top" align="left">+2.50</td>
  2974.       </tr>
  2976.       <tr>
  2977.          <td valign="top" align="left"></td>
  2978.       </tr>
  2979.    </table>
  2981.      <p>
  2982. Now it's 1 D at 100°.  And the left eye has less.  But that was total astigmatism, not just
  2983. corneal astigmatism.  And in passing, is there any difference between +2 spherical and -0.5
  2984. cylindrical on the one hand and +1.5 spherical and +0.5 cylindrical on the other hand?  Or
  2985. is it just the way things get measured?
  2986.      </p>
  2988. End deselected topic Go (More thoughts on astigmatism) -->
  2991. <!-- topic Go not selected
  2992.      <p>
  2993. Off to <a href="">Geelong</a> this morning,
  2994. once again very early, to have my other (left) eye rebuilt.  To my surprise, a large number
  2995. of the people involved recognized me.  The first was Roxy, who took this photo of my dilated
  2996. left pupil:
  2997.      </p>
  3000.      <p>
  3001. What a good example of mobile phone photography!  Two other nurses also recognized me.  I'm
  3002. impressed.
  3003.      </p>
  3005.      <p>
  3006. It would be easy to say that “everything went the same way as last time”, but that's not
  3007. quite correct.  Somehow it took a lot longer today, not during the procedure, but
  3008. beforehand.  The result was that I was there for 3½ hours, while <a href=";article=D-20240322-003739#D-20240322-003739">last time</a> it was only 2 hours, 20 minutes.  But I didn't notice that until I compared
  3009. my times.
  3010.      </p>
  3012.      <p>
  3013. The procedure was as before, except that this time I was fitted with a <a href="">Toric IOL</a>.  As I had discovered, part of the
  3014. procedure involves marking the orientation of the eyeball while the patient is sitting up,
  3015. since it may rotate when lying down.  But I wasn't expecting <a href="">David Fabinyi</a> to poke me in the eye with what
  3016. looked like a felt-tipped pen.  Of course the anaesthetics did their job, so it wasn't that
  3017. painful.
  3018.      </p>
  3020.      <p>
  3021. He also gave me more details of the <a href="">IOL</a>: -0.06 <a href="">dioptre</a> spherical, 1
  3022. dioptre cylindrical.  I forgot to ask about the axis, but that's quite strong compared to
  3023. the prescription I got <a href=";article=D-20210128-024301#D-20210128-024301">in 2021</a>.  But that's the difference between the <a href="">cornea</a> and the complete eye, maybe.
  3024.      </p>
  3026.      <p>
  3027. And why -0.06 dioptres cylindrical?  The target would have been -0.25 dioptres (4 m, a good
  3028. <a href="">hyperfocal distance</a>,
  3029. but they only come in steps of 0.25 dioptres, so the next one would have been 0.31 dioptres.
  3030. Assuming the hyperfocal distance of 4 m (± 0.25 dioptres <a href="">depth of focus</a>), that would give me
  3031. a maximum sharp distance of about 16 m.  As it is, I will have a close distance of 3.2 m.
  3032. And the other eye is more myopic, so it's not a big deal.
  3033.      </p>
  3035.      <p>
  3036. The procedure itself was different, too.  First Liam Broad, the anaesthetist, decided to put
  3037. the <a href="">cannula</a> in my elbow, since
  3038. it had been so painful last time.  And this time there was much more light, though once
  3039. again I didn't notice being moved into the operating theatre.  And the visual effects were
  3040. very different: instead of random geometric shapes, I saw four pillars arranged in a square.
  3041. They moved and changed shape, but the arrangement was still the same.  David says that this
  3042. might be a reaction to the anaesthetic, which this time seemed to be stronger than last
  3043. time.
  3044.      </p>
  3046.      <p>
  3047. Then back home, and this time I read the instructions: remove the eye cover at 18:00.  Here
  3048. before and after:
  3049.      </p>
  3052.      <p>
  3053. And things looked <i>very</i> strange.  A bubble in my field of view, of course, this time
  3054. mercifully smaller.  But I had forgotten how obtrusive it was.  And everything looked so
  3055. bright!  I could barely stand looking at the TV.  The image must have been equivalent to 2
  3056. to 3 <a href="">EV</a> more than the
  3057. right eye.  Also not very sharp, and with a pronounced magenta cast, and the images was
  3058. considerably lower than the image from the right eye, and I couldn't correct it.  But that's
  3059. early days, and presumably it will improve.
  3060.      </p>
  3062. End deselected topic Go (The other eye) -->
  3065. <!-- topic ho not selected
  3066.      <p>
  3067. Surprising spam today:
  3068.      </p>
  3070.      <blockquote class="fullwidth">
  3071. <div style="text-align:left">
  3072.  <tt>
  3073. Subject: M07956723
  3074. <br />Message&#45;ID: &lt;;
  3075. <br />
  3076. <br />Good Afternoon,
  3077. <br />
  3078. <br />Please be advised we have provided our assessment report and quote to substantiate &nbsp;our demands &nbsp;that was a result of
  3079. <br />
  3080. <br />Of an accident that you are liable for. Our costs were &nbsp;assessed and Approved by a licensed professional motor vehicle assessor.
  3081. <br />
  3082. <br />Find attached our final letter of demand and advise your intentions within 7 days.
  3083. <br />
  3084.  </tt>
  3085. </div>
  3086. </blockquote>
  3088.      <p>
  3089. Somebody who had read my entries on the <a href="">AAMI</a> matter <a href="!&amp;article=D-20230413-024617#D-20230413-024617">last year</a> and wanted to cash in?  Checked the headers.  No, this abortion of a
  3090. message really came from AAMI.  And once again they have not responded to my questions, nor
  3091. provided any proof (including the claimed assessment report).  Instead they once again
  3092. provided irrelevant photos, and also a screen shot of my <a href="!&amp;article=D-20230413-024617#D-20230413-024617">article</a> on the subject at the time, which pretty much disproves their claims.  But
  3093. why now?  Is the “final” letter of demand a glimmer of hope that they will then let the
  3094. matter rest?  I have little hope.
  3095.      </p>
  3097. End deselected topic ho (AAMI never gives up) -->
  3100. <item>
  3101. <guid isPermaLink='true'></guid>
  3102. <link></link>
  3103. <category>technology</category>
  3104. <category>opinion</category>
  3105. <title>Bloody Microsoft again!</title>
  3106.  <description>
  3107.    <![CDATA[
  3108.    <div align="justify">
  3109.      <p>
  3110. Now that it doesn't use any significant power, I have taken the easy way out and
  3111. let <i></i> (Microsoft <a href="">“Windows”</a> 10)
  3112. carry on running.  <b><i>Bad</i></b> idea.  Microsoft did its usual update without asking
  3113. me, and after that <a href="">“Perfectly Clear“</a> didn't want to know about registration.  Back to where I was <a href=";article=D-20240401-233959#Perfectly-Clear">at the beginning of the month</a>.
  3114.      </p>
  3116.      <p>
  3117. <b><i>Grrr!</i></b>  But <i>despise</i> is a virtual machine, and I do backups religiously.
  3118. Can I revert to the state of yesterday evening?  No, it seems.  Restoring the backup was
  3119. trivial, but every attempt to restart it failed with <tt>VERR_ACCESS_DENIED</tt>.  But not
  3120. only
  3121. <i>despise</i>: <i>all</i> VMs.  More searching, and found what I've seen before <a href=";article=D-20240317-013629#D-20240317-013629">less than a month ago</a>: I need to be in the <tt><tt>voxusers</tt></tt> group.
  3122.      </p>
  3124.      <p>
  3125. But aren't I?  <a href="ödinger's_cat">Schrödinger's
  3126. cat</a>: yes, I'm in the <i>/etc/group</i> entry, but the shell I was running was started
  3127. longer ago (4 January).  So I had to start an <i>xterm</i> from a fresh login, and then it
  3128. worked.  And yes, Perfectly Clear was still enabled at that time.  So: keep snapshots.  If
  3129. things go wrong, just revert to them.
  3130.      </p>
  3132.      <p>
  3133. Who needs Microsoft updates anyway?
  3134.      </p>
  3135.      </div>
  3136.    ]]>
  3137.  </description>
  3138.  <dc:creator>Greg Lehey</dc:creator>
  3139.  <dc:date>2024-04-12T03:29:48+00:00</dc:date>
  3140. </item>
  3143. <!-- topic H not selected
  3144.      <p>
  3145. It's been 100 years since the birth of my mother, Audrey Lehey née Herbert.  And, of course,
  3146.        <a href=";article=D-20190216-034819#D-20190216-034819">five years since she died</a>.  Once again: how time flies!  And how the world has
  3147.        changed since her birth.
  3148.      </p>
  3150. End deselected topic H (Audrey Herbert turns 100 years old) -->
  3153. <!-- topic G not selected
  3154.      <p>
  3155. Into <a href="">Geelong</a> again this morning
  3156. to have my eye operation checked.  Since yesterday my vision has improved considerably,
  3157. though it's still not as good as the right eye.  But now I have something to compare, and
  3158. it's good to see the gradual improvement.
  3159.      </p>
  3161.      <p>
  3162. And the strangeness yesterday evening, the magenta colour cast and excessive brightness?
  3163. Probably a reaction to the anaesthetic, which can take up to 12 hours to dissipate.
  3164.      </p>
  3166.      <p>
  3167. Then back home in time for breakfast.  An hour's drive to Geelong, 10 minutes wait, 5
  3168. minutes consultation, and an hour back again.
  3169.      </p>
  3171. End deselected topic G (Eye checkup) -->
  3174. <item>
  3175. <guid isPermaLink='true'></guid>
  3176. <link></link>
  3177. <category>photography</category>
  3178. <category>technology</category>
  3179. <category>opinion</category>
  3180. <title>Reprocessing old photos</title>
  3181.  <description>
  3182.    <![CDATA[
  3183.    <div align="justify">
  3184.      <p>
  3185. <a href=";article=D12-10#D12-10">Fifteen years
  3186. ago</a> I spent a lot of time comparing photo processing.  A lot has changed since then.
  3187. In particular, I was concerned with gradation, and I took a lot of photos with different
  3188. camera settings.  I made a comparison between “muted” and “vivid” profiles, which showed no
  3189. obvious difference.  I thought that I had not understood that “muted” and “vivid”, like many
  3190. of the settings, only applied to the in-camera <a href="">JPEG</a> images.  But that's not the case:
  3191. these <i>were</i> JPEGs (which I took alongside the raw images), and there was really almost
  3192. no difference:
  3193.      </p>
  3195.        <a id="Photo-17" name="Photo-17"
  3196.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=111111111111111112&amp;topics=c#Photo-17">
  3197.          <img alt="This should be soft-thumbnail.jpeg.  Is it missing?" border="0" id="Photo_17"
  3198.               title="Photo soft-thumbnail.jpeg.  Click to redisplay larger version of image."
  3199.               src=""
  3200.               width="300" height="225"
  3201.           /></a>
  3202.        <a id="Photo-18" name="Photo-18"
  3203.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=1111111111111111112&amp;topics=c#Photo-18">
  3204.          <img alt="This should be vivid-thumbnail.jpeg.  Is it missing?" border="0" id="Photo_18"
  3205.               title="Photo vivid-thumbnail.jpeg.  Click to redisplay larger version of image."
  3206.               src=""
  3207.               width="300" height="225"
  3208.           /></a>
  3210.      <p>
  3211. There's really almost no differencd.  What does the <a href="">Exif</a> data say?  Here the relevant difference
  3212. between “muted” (-) and “vivid” (+):
  3213.      </p>
  3215.      <blockquote class="fullwidth">
  3216. <div style="text-align:left">
  3217.  <tt>
  3218. &#45;Custom Saturation &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 0 (min &#45;5, max 5)
  3219. <br />+Custom Saturation &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 1 (min &#45;5, max 5)
  3220. <br />&#45;Contrast Setting &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: &#45;1 (min &#45;5, max 5)
  3221. <br />&#45;Sharpness Setting &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : &#45;2 (min &#45;5, max 5)
  3222. <br />+Contrast Setting &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: 0 (min &#45;5, max 5)
  3223. <br />+Sharpness Setting &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : 0 (min &#45;5, max 5)
  3224. <br />&#45;Picture Mode &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Muted
  3225. <br />+Picture Mode &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Vivid
  3226. <br />&#45;Contrast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Low
  3227. <br />&#45;Saturation &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal
  3228. <br />&#45;Sharpness &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Soft
  3229. <br />+Contrast &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Normal
  3230. <br />+Saturation &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: High
  3231. <br />+Sharpness &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : Normal
  3232. <br />
  3233.  </tt>
  3234. </div>
  3235. </blockquote>
  3237.      <p>
  3238. I wonder if it's still that bad.
  3239.      </p>
  3241.      <p>
  3242. Still, that's not the sort of thing I do any more.  Here's a more typical image, which I
  3243. chose because it showed the worst gradation at the time.  Here the best I made then.  First
  3244. a conversion with <a href="">UFRaw</a>, then an
  3245. unspecified “optimization”, probably <a href="">Ashampoo</a> photo optimizer, that seems only to have made things worse, then a conversion with
  3246. Olympus “Master”, which at least corrected the geometry and made it marginally
  3247. better:
  3248.      </p>
  3250.        <a id="Photo-19" name="Photo-19"
  3251.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=11111111111111111112&amp;topics=c#Photo-19">
  3252.          <img alt="This should be Pattern-ufraw-default-settings.jpeg.  Is it missing?" border="0" id="Photo_19"
  3253.               title="Photo Pattern-ufraw-default-settings.jpeg.  Click to redisplay larger version of image."
  3254.               src=""
  3255.               width="299" height="225"
  3256.           /></a>
  3257.        <a id="Photo-20" name="Photo-20"
  3258.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=111111111111111111112&amp;topics=c#Photo-20">
  3259.          <img alt="This should be Optimized-Pattern-ufraw-default-settings.jpeg.  Is it missing?" border="0" id="Photo_20"
  3260.               title="Photo Optimized-Pattern-ufraw-default-settings.jpeg.  Click to redisplay larger version of image."
  3261.               src=""
  3262.               width="299" height="225"
  3263.           /></a>
  3264.        <a id="Photo-21" name="Photo-21"
  3265.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=1111111111111111111112&amp;topics=c#Photo-21">
  3266.          <img alt="This should be Pattern-olympus-converted.jpeg.  Is it missing?" border="0" id="Photo_21"
  3267.               title="Photo Pattern-olympus-converted.jpeg.  Click to redisplay larger version of image."
  3268.               src=""
  3269.               width="300" height="225"
  3270.           /></a>
  3272.      <p>
  3273. I've progressed since then.  Here the best I made then (the Olympus “Master" image), then as
  3274. processed with my standard “Myset” profile with <a href="">DxO PhotoLab</a>, then that image further enhanced
  3275. by <a href="">“Perfectly Clear“</a>:
  3276.      </p>
  3278.        <a id="Photo-22" name="Photo-22"
  3279.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=11111111111111111111112&amp;topics=c#Photo-22">
  3280.          <img alt="This should be Pattern-olympus-converted.jpeg.  Is it missing?" border="0" id="Photo_22"
  3281.               title="Photo Pattern-olympus-converted.jpeg.  Click to redisplay larger version of image."
  3282.               src=""
  3283.               width="300" height="225"
  3284.           /></a>
  3285.        <a id="Photo-23" name="Photo-23"
  3286.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=111111111111111111111112&amp;topics=c#Photo-23">
  3287.          <img alt="This should be Pattern-DxO-Myset.jpeg.  Is it missing?" border="0" id="Photo_23"
  3288.               title="Photo Pattern-DxO-Myset.jpeg.  Click to redisplay larger version of image."
  3289.               src=""
  3290.               width="300" height="225"
  3291.           /></a>
  3292.        <a id="Photo-24" name="Photo-24"
  3293.          href="diary-apr2024.php?dirdate=20090412&amp;imagesizes=1111111111111111111111112&amp;topics=c#Photo-24">
  3294.          <img alt="This should be Pattern-DxO-Myset-PC.jpeg.  Is it missing?" border="0" id="Photo_24"
  3295.               title="Photo Pattern-DxO-Myset-PC.jpeg.  Click to redisplay larger version of image."
  3296.               src=""
  3297.               width="300" height="225"
  3298.           /></a>
  3300.      <p>
  3301. This is pretty much my standard processing.  If I cared enough, I might be able to improve
  3302. the image further.  But it does partially explain why it took me so long to raw images.
  3303.      </p>
  3304.      </div>
  3305.    ]]>
  3306.  </description>
  3307.  <dc:creator>Greg Lehey</dc:creator>
  3308.  <dc:date>2024-04-13T00:55:01+00:00</dc:date>
  3309. </item>
  3313. <item>
  3314. <guid isPermaLink='true'></guid>
  3315. <link></link>
  3316. <category>technology</category>
  3317. <title>Finding rwhod</title>
  3318.  <description>
  3319.    <![CDATA[
  3320.    <div align="justify">
  3321.      <p>
  3322. <i></i> is now running as well as you can expect of a Microsoft system, but
  3323. I'm still running into this irritating loss of <i>rwhod</i> on reboot.  <a href=";article=D-20240317-020847#D-20240317-020847">Last time</a> I noted issues, but not how to fix it.  What I need to do is:
  3324.      </p>
  3326.      <ol>
  3327.        <li class="fullwidth">
  3328.          <div class="listitemwidth">
  3329.            Start <i>CMD.EXE</i> as <tt>administrator</tt> with <b>c-s-mouse1</b>.
  3330.          </div>
  3331.        </li>
  3333.        <li class="fullwidth">
  3334.          <div class="listitemwidth">
  3335.            <i>cd</i> to <i>\Program&nbsp;Files—(x86)/rwho</i>.
  3336.          </div>
  3337.        </li>
  3339.        <li class="fullwidth">
  3340.          <div class="listitemwidth">
  3341.            Try running <i>rwhod</i>.
  3342.          </div>
  3343.        </li>
  3345.        <li class="fullwidth">
  3346.          <div class="listitemwidth">
  3347.            If this fails, find <i>RWHODINSTALLER.EXE</i>, which is somewhere else, location not
  3348.            divulged.  This time I didn't need it.
  3349.          </div>
  3350.        </li>
  3352.        <li class="fullwidth">
  3353.          <div class="listitemwidth">
  3354.            From past experience, <i>RWHODINSTALLER.EXE</i> can fail with permissions issues.
  3355.            Rename the old <i>\Program&nbsp;Files—(x86)/rwho/rwhod</i> to something expressing your
  3356.            opinion of Microsoft and try again.
  3357.          </div>
  3358.        </li>
  3359.      </ol>
  3361.      <p>
  3362. In passing, discovered Yet Another strangeness in Microsoft:
  3363. as <tt>administrator</tt>, <i>NET USE</i> claims that there are no network “shares”.  As
  3364. normal user all works well.
  3365.      </p>
  3366.      </div>
  3367.    ]]>
  3368.  </description>
  3369.  <dc:creator>Greg Lehey</dc:creator>
  3370.  <dc:date>2024-04-13T00:55:33+00:00</dc:date>
  3371. </item>
  3375. <!-- topic Gh not selected
  3376.      <p>
  3377. Tried to pour myself a glass of wine this evening.  Not for the first time, it didn't quite work:
  3378.      </p>
  3381.      <p>
  3382. This, too, will pass.
  3383.      </p>
  3385. End deselected topic Gh (The dangers of one-eyedness) -->
  3388. <!-- topic G not selected
  3389.      <p>
  3390. One of the first things that I noticed when I opened my eye after the <a href=";article=D-20240323-015848#D-20240323-015848">rebuild of my right eye</a> was the surprising number of floaters.  And with <a href=";article=D-20240412-023546#D-20240412-023546">the left eye</a> there were none.
  3391.      </p>
  3393.      <p>
  3394. But that has changed.  Like with the <a href=";article=D-20240326-012453#D-20240326-012453">right eye</a>, they have changed in shape, tending towards strands.  That's clearly
  3395. transient: I can't notice any floaters in my right eye any more, so these will almost
  3396. certainly go away too.
  3397.      </p>
  3399. End deselected topic G (Floaters again) -->
  3402. <!-- topic ha not selected
  3403.      <p>
  3404. Jesse Walsh gave us the contact details of Cassie Clarke in <a href="">Corindhap</a>, who has a an
  3405. external cat cage.  Off this afternoon to take a look.        </p>
  3407.      <p>
  3408. I was mainly interested in the details, to the point that I forgot to take a photo of the
  3409. entire cage.  How cat-proof is it?  I think it will be sufficient:
  3410.      </p>
  3413.            <p>
  3414.      </p>
  3416. End deselected topic ha (A cat cage) -->
  3419. <!-- topic h not selected
  3420.      <p>
  3421. On the way home, drove down Swamp Road to see what the bushfire had done.  A lot of burning,
  3422. of course, but it seems that none of the trees had been burnt down.:
  3423.      </p>
  3426.      <p>
  3427. Somehow it's all to close to “home”.  Here a corner of a walk we used to take with the dogs:
  3428.      </p>
  3431.      <p>
  3432. And this tree, I think, shows the remains of the <a href="">Amyema pendula</a> that is on the
  3433. Wikipedia page (here my original), and what I think are the remains of the same bush today:
  3434.      </p>
  3437.      <p>
  3438. And here a sign where I cut open my finger trying to hold back <a href="">Nikolai</a> <a href=";subtitle=Kangaroo-related%20injury&amp;article=D-20150115-231918#D-20150115-231918">nine years ago</a>.  It's not damaged, but it's good for orientation.  Here in 2015 and
  3439. now:
  3440.      </p>
  3443.      <p>
  3444.      </p>
  3446. End deselected topic h (Dereel bushfire aftermath) -->
  3449. <item>
  3450. <guid isPermaLink='true'></guid>
  3451. <link></link>
  3452. <category>photography</category>
  3453. <category>technology</category>
  3454. <category>opinion</category>
  3455. <title>despise photo processing times</title>
  3456.  <description>
  3457.    <![CDATA[
  3458.    <div align="justify">
  3459.      <p>
  3460. <a href="">House photo</a> day today, a total of 111
  3461. images to convert.  And <i>despise</i> did it in 3 minutes, 50 seconds, an average speed of
  3462. 2.07 s per photo.  That's far better than I have ever seen.
  3463.      </p>
  3465.      <p>
  3466. But then I converted another 17 images from the afternoon.  1 minute, 30 seconds, or 5.3
  3467. seconds per image.  Why?  My guess is that there's some amazing inefficiency in <a href="">DxO PhotoLab</a> that applies at the start of every
  3468. processing batch.  Even the values given are inaccurate: it can take up to 15 seconds after
  3469. pressing <a href="">“export”</a> before it even starts.
  3470. Still, a great improvement over the other machines.
  3471.      </p>
  3472.      </div>
  3473.    ]]>
  3474.  </description>
  3475.  <dc:creator>Greg Lehey</dc:creator>
  3476.  <dc:date>2024-04-14T00:48:10+00:00</dc:date>
  3477. </item>
  3480. <item>
  3481. <guid isPermaLink='true'></guid>
  3482. <link></link>
  3483. <category>technology</category>
  3484. <title>Manipulating data in the Microsoft space</title>
  3485.  <description>
  3486.    <![CDATA[
  3487.    <div align="justify">
  3488.      <p>
  3489. I've been running <a href="">autocutsel</a> for a while now, and it works, up to a point.  If I copy something on Microsoft, it
  3490. automatically updates the clipboard on the machine that runs the <a href="">rdesktop</a>.  If I mark text on an <a href="">xterm</a>, it also appears in the clipboard.  But
  3491. it doesn't change the cutbuffer in any way, and that's not what I understand from the
  3492. documentation:
  3493.      </p>
  3495.      <blockquote class="fullwidth">
  3496.        <div class="listitemwidth">
  3497.          When the clipboard is changed, it updates the cutbuffer.  When the cutbuffer is changed,
  3498.  it owns the clipboard selection.  The cutbuffer and clipboard selection are always
  3499.  synchronized.
  3500.        </div>
  3501.      </blockquote>
  3503.      <p>
  3504. There's this word “own” that I don't understand.  But I do understand “always synchronized”,
  3505. and that's not what I see.  Is this a bug, a misdocumentation, or what?
  3506.      </p>
  3507.      </div>
  3508.    ]]>
  3509.  </description>
  3510.  <dc:creator>Greg Lehey</dc:creator>
  3511.  <dc:date>2024-04-15T01:42:00+00:00</dc:date>
  3512. </item>
  3516. <item>
  3517. <guid isPermaLink='true'></guid>
  3518. <link></link>
  3519. <category>technology</category>
  3520. <title>How to save an SMS</title>
  3521.  <description>
  3522.    <![CDATA[
  3523.    <div align="justify">
  3524.      <p>
  3525. I've been trying for years to find a way to save or copy an <a href="">SMS</a>.  Based on my almost complete lack of
  3526. success, you'd think that somebody wanted to avoid it.  Even the mobile phone apps that
  3527. promise to save or forward them don't work for me.
  3528.      </p>
  3530.      <p>
  3531. But finally I've found a way to at least save the text, if not the metadata:
  3532.      </p>
  3534.      <ol>
  3535.        <li class="fullwidth">
  3536.          <div class="listitemwidth">
  3537.    Start Microsoft “PhoneLink” and display the message.
  3538.          </div>
  3539.        </li>
  3541.        <li class="fullwidth">
  3542.          <div class="listitemwidth">
  3543.             Select text.  This only works with the text itself, not the rest of the display.
  3544.          </div>
  3545.        </li>
  3547.        <li class="fullwidth">
  3548.          <div class="listitemwidth">
  3549.            Copy to clipboard with <b>c-c</b>.
  3550.          </div>
  3551.        </li>
  3553.        <li class="fullwidth">
  3554.          <div class="listitemwidth">
  3555.             Mark text in <i>xclipboard</i> on the host machine.
  3556.          </div>
  3557.        </li>
  3559.        <li class="fullwidth">
  3560.          <div class="listitemwidth">
  3561.            Save!
  3562.          </div>
  3563.        </li>
  3564.      </ol>
  3566.      <p>
  3567. Simple, isn't it.  You have to love Microsoft.
  3568.      </p>
  3569.      </div>
  3570.    ]]>
  3571.  </description>
  3572.  <dc:creator>Greg Lehey</dc:creator>
  3573.  <dc:date>2024-04-15T01:47:05+00:00</dc:date>
  3574. </item>
  3577. <item>
  3578. <guid isPermaLink='true'></guid>
  3579. <link></link>
  3580. <category>photography</category>
  3581. <category>technology</category>
  3582. <category>opinion</category>
  3583. <title>Understanding depth of focus</title>
  3584.  <description>
  3585.    <![CDATA[
  3586.    <div align="justify">
  3587.      <p>
  3588. One of the things I learnt as part of my <a href="">cataract</a> operation was the term <a href="">depth of focus</a>.  I know that, right?
  3589. No, what I know and use is <a href="">depth of field</a>.  And while they're closely related, there's a subtle difference:
  3590. depth of field is measured in distances, the closest and furthest distance in acceptable
  3591. focus <i>when you focus on a specific point</i>.  I've known this for ever, at least since I
  3592. started using cameras <a href="">60 years ago</a>.
  3593. The lenses had a depth-of-field scale on the lens, here a <a href="">Diaxette</a> that looks
  3594. just like the one I had at the time:
  3595.      </p>
  3597.        <a id="Photo-25" name="Photo-25"
  3598.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=11111111111111111111111112&amp;topics=c#Photo-25">
  3599.          <img alt="This should be Diaxette-Cassar-lens.jpeg.  Is it missing?" border="0" id="Photo_25"
  3600.               title="Photo Diaxette-Cassar-lens.jpeg.  Click to redisplay larger version of image."
  3601.               src=""
  3602.               width="318" height="213"
  3603.           /></a>
  3604.        <a id="Photo-26" name="Photo-26"
  3605.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=111111111111111111111111112&amp;topics=c#Photo-26">
  3606.          <img alt="This should be Diaxette-Cassar-lens-detail.jpeg.  Is it missing?" border="0" id="Photo_26"
  3607.               title="Photo Diaxette-Cassar-lens-detail.jpeg.  Click to redisplay larger version of image."
  3608.               src=""
  3609.               width="491" height="138"
  3610.           /></a>
  3612.      <p>
  3613. The top (black) scale is distance, in feet, and the lower (red) scale is depth of field.
  3614. Here the focus is set to 30 ft (10 m), and the scale shows a depth of field from a little
  3615. over 20 ft to a little below 60 ft at f/2.8, or 14 ft to beyond ∞ at f/8.
  3616.      </p>
  3618.      <p>
  3619. The devil's in the detail, of course, and <a href=";article=D5-11#D5-11">14 years ago</a> I found the contradictions enough that I wrote <a href="">my own program</a> to calculate depth of field.
  3620.      </p>
  3622.      <p>
  3623. The problem with depth of field is that it depends on the distance.  Depth of focus is
  3624. measured in <a href="">dioptres</a>, the
  3625. correction needed to move the edges of acceptable focus to the prime focus.  And that makes
  3626. sense: it's independent of the distance.
  3627.      </p>
  3629.      <p>
  3630. Or is that the definition?  The <a href="">Wikipedia page</a> is currently very vague:
  3631.      </p>
  3633.      <blockquote class="fullwidth">
  3634.        <div class="listitemwidth">
  3635.          Depth of focus can have two slightly different meanings. The first is the distance over
  3636.          which the image plane can be displaced while a single object plane remains in acceptably
  3637.          sharp focus; the second is the image-side conjugate of depth of field.  With the first
  3638.          meaning, the depth of focus is symmetrical about the image plane; with the second, the
  3639.          depth of focus is slightly greater on the far side of the image plane.
  3640.        </div>
  3641.      </blockquote>
  3643.      <p>
  3644. The first definition looks like the inverse of depth of field: instead of measuring the
  3645. subject distance, it measures the object distance.  And clearly the claim that the depth of
  3646. focus is symmetrical is just plain false.  At 1:1 magnification the values are the same.
  3647. And the “second definition” seems to be the same thing.  Without formulae the whole thing is
  3648. too fuzzy to understand.  But the formulae presented are just plain wrong: they're formulae
  3649. for depth of field.  The page also stated:
  3650.      </p>
  3652.      <blockquote class="fullwidth">
  3653.        <div class="listitemwidth">
  3654.  While depth of field is generally measured in macroscopic units such as meters and feet,
  3655.  depth of focus is typically measured in microscopic units such as fractions of a
  3656.  millimeter or thousandths of an inch.
  3657.        </div>
  3658.      </blockquote>
  3660.      <p>
  3662. That's clearly only part of the statement, of course.  In <a href="">optometry</a> depth of focus is usually
  3663. measured in dioptres, so I said so.
  3664.      </p>
  3666.      <p>
  3667. So: clearly the Wikipedia page is almost useless.  What else is there?  The first hit on
  3668. Google tells me:
  3669.      </p>
  3671.      <blockquote class="fullwidth">
  3672.        <div class="listitemwidth">
  3673.          In optometry depth of focus is usually measured in dioptres.
  3674.        </div>
  3675.      </blockquote>
  3677.      <p>
  3678. That's quite impressive.  It's a reference to what I wrote in Wikipedia only a few hours
  3679. earlier.  And clearly it's useless for confirming my claims.  How about <a href="">Gemini</a>?
  3680.      </p>
  3682.      <blockquote class="fullwidth">
  3683.        <div class="listitemwidth">
  3684.          <b>Q</b>: How do I calculate depth of focus in dioptres?
  3685.        </div>
  3687. <div class="listitemwidth">
  3688.  <b>A</b>: Depth of focus (DOF) isn't directly calculated in diopters. DOF is typically
  3689.  measured in linear units like millimeters or feet
  3691. </div>
  3692.      </blockquote>
  3694.      <p>
  3695. That's a quote from an older version of the Wikipedia page!  And it uses the term “DOF”,
  3696. which I always took to mean depth of field.  But there are others who disagree.  <a href="">This article</a>, from the US
  3697. <a href="">National
  3698. Institutes of Health</a>, writes:
  3699.      </p>
  3701.      <blockquote class="fullwidth">
  3702.        <div class="listitemwidth">
  3703.          In theory, only one plane or surface of world can be in focus at one time. However, the
  3704.          eye exhibits a certain tolerance to out-of-focus images, a feature that is known as
  3705.          depth-of-focus (DOF). The corresponding distance range in which the objects are seen
  3706.          “clearly” is known as depth-of-field (DOFi).
  3707.        </div>
  3708.      </blockquote>
  3710.      <p>
  3711. Somehow the term <a href="">NIH</a> sounds appropriate.
  3712.      </p>
  3714.      <p>
  3715. And there's more.  <a href="">This paper</a> goes into some detail, and maybe it contains all that I need to know.  It refers to human
  3716. eyes, and interestingly (on page 830) it comes up with a depth of focus of 0.1 dioptre for
  3717. adult humans.  I just need to read it more carefully.
  3718.      </p>
  3720.      <p>
  3721. In summary, I'm just as confused as I was at the beginning.  I need to check my maths, but
  3722. it seems that the concepts are poorly understood, and measuring depth of focus in dioptres
  3723. is really independent of the subject (or object) distance.  That's why depth of field scaled
  3724. work.  But measuring the depth of focus by distances from the sensor is <i>not</i> distance
  3725. independent.  Eyes are a special case because the sensor is always at the same distance from
  3726. the entrance pupil.  But even there, the linear depth of focus should not be symmetrical,
  3727. which should be particularly apparent when using strong auxiliary lenses (say +20 dioptres,
  3728. bring focus to 5 cm).
  3729.      </p>
  3730.      </div>
  3731.    ]]>
  3732.  </description>
  3733.  <dc:creator>Greg Lehey</dc:creator>
  3734.  <dc:date>2024-04-15T01:56:47+00:00</dc:date>
  3735. </item>
  3738. <item>
  3739. <guid isPermaLink='true'></guid>
  3740. <link></link>
  3741. <category>technology</category>
  3742. <category>opinion</category>
  3743. <title>Off the net again!</title>
  3744.  <description>
  3745.    <![CDATA[
  3746.    <div align="justify">
  3747.      <p>
  3748. Idly checking <a href=""><i>ping</i></a> times today brought a failure: I couldn't ping <i></i>
  3749. from <i></i>.  Nor anywhere else, for that matter.
  3750.      </p>
  3752.      <p>
  3753. Firewall problem?  No, a <i>traceroute</i> stopped much earlier than that.  Is there
  3754. something wrong?  The block has been routed here for nearly a year, and <a href=";subtitle=Opening%20the%20flood%20gates&amp;article=D-20230508-022452#D-20230508-022452">in May last year</a> I confirmed:
  3755.      </p>
  3757.      <blockquote class="fullwidth">
  3758. <div style="text-align:left">
  3759.  <tt>
  3760. <code><font color="blue">=== grog@eureka (/dev/pts/24)</font> <font color="red">~</font> <font color="blue">33</font> &#45;&gt; <b><tt>whois &#45;h " &#45;v"</tt></b></code>
  3761. <br />AS &nbsp; &nbsp; &nbsp;| IP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | BGP Prefix &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| CC | Registry | Allocated &nbsp;| AS Name
  3762. <br />NA &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;| NA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| AU | ripencc &nbsp;| 1991&#45;05&#45;01 | NA
  3763. <br />4764 &nbsp; &nbsp;| &nbsp; &nbsp;| &nbsp; &nbsp;| AU | ripencc &nbsp;| 1991&#45;05&#45;01 | WIDEBAND&#45;AS&#45;AP Aussie Broadband, AU
  3764. <br />
  3765.  </tt>
  3766. </div>
  3767. </blockquote>
  3769.      <p>
  3770. And what do I have now?
  3771.      </p>
  3773.      <blockquote class="fullwidth">
  3774. <div style="text-align:left">
  3775.  <tt>
  3776. <code><font color="blue">=== root@lax (/dev/pts/7)</font> <font color="red">~</font> <font color="blue">90</font> &#45;&gt; <b><tt>whois &#45;h " &#45;v"</tt></b></code>
  3777. <br />AS &nbsp; &nbsp; &nbsp;| IP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | BGP Prefix &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| CC | Registry | Allocated &nbsp;| AS Name
  3778. <br />NA &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;| NA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| AU | ripencc &nbsp;| 1991&#45;05&#45;01 | NA
  3779. <br />
  3780.  </tt>
  3781. </div>
  3782. </blockquote>
  3784.      <p>
  3785. Gone!  An easy enough bug to fix, I suppose.  But it means dealing with <a href="">Aussie Broadband</a> “support” again.  The first part
  3786. (after authenticating myself) will be to explain to the first level support person what I'm
  3787. talking about.  The horror!
  3788.      </p>
  3789.      </div>
  3790.    ]]>
  3791.  </description>
  3792.  <dc:creator>Greg Lehey</dc:creator>
  3793.  <dc:date>2024-04-15T03:18:22+00:00</dc:date>
  3794. </item>
  3797. <!-- topic p not selected
  3798.      <p>
  3799. One of the important parameters of a digital camera is the pixel depth, which determines the
  3800. dynamic range of the sensor.  <a href=";article=D14-14#D14-14">Fifteen years ago</a> I
  3801. wrote “I gather that my Olympus <i>[<a href="">E-510</a>]</i> has only 10 bit pixels”.
  3802.      </p>
  3804.      <p>
  3805. Is that correct?  Today I went searching and came up with a blank.  The best specs page I
  3806. could find is <a href="">this page</a>, but it, too, is too polite to say.  Why are people not interested?  It has
  3807. much more of a bearing on the image quality than the <i>number</i> of pixels.
  3808.      </p>
  3810. End deselected topic p (Pixel depth of digital cameras) -->
  3813. <item>
  3814. <guid isPermaLink='true'></guid>
  3815. <link></link>
  3816. <category>technology</category>
  3817. <category>opinion</category>
  3818. <title>How to copy SMS, again</title>
  3819.  <description>
  3820.    <![CDATA[
  3821.    <div align="justify">
  3822.      <p>
  3823. Callum Gibson read my article on <a href=";article=D-20240415-014705#D-20240415-014705">how to save an SMS</a>.  He has a simpler method: <a href="">Google messages</a>.  That way you don't need Microsoft,
  3824. just a web browser.
  3825.      </p>
  3827.      <p>
  3828. OK, sounds interesting.  Off to take a look, but instead of <a href=""></a> I was redirected to <a href=""></a>.  Funny, says Callum, “it works for
  3829. me”.  Still, the page is clearly related, full of advertisements and content unrelated to
  3830. what I'm looking for, like “With Google Messages, you can customize your experience, ensure
  3831. private conversations, and enjoy the latest AI features.”.  Dammit, all I want to do is to
  3832. save an SMS with its metadata, like you can do with any sane <a href="">MUA</a> with a single click!
  3833.      </p>
  3835.      <p>
  3836. First, of course, I have to install Google Messages on my phone.  Good news: it's compatible
  3837. with all my “devices” (which in this context I think means “phones”).  OK, install.  I was
  3838. given a <i>single line</i> choice of which “device”:
  3839.      </p>
  3841.        <a id="Photo-27" name="Photo-27"
  3842.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=1111111111111111111111111112&amp;topics=c#Photo-27">
  3843.          <img alt="This should be Google-messages-1.png.  Is it missing?" border="0" id="Photo_27"
  3844.               title="Photo Google-messages-1.png.  Click to redisplay larger version of image."
  3845.               src=""
  3846.               width="353" height="192"
  3847.           /></a>
  3849.      <p>
  3850. Damn, that's my old phone, the one I just use for experiments.  Ah, but single line windows
  3851. are <i>modern</i>.  Click and you get:
  3852.      </p>
  3854.        <a id="Photo-28" name="Photo-28"
  3855.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=11111111111111111111111111112&amp;topics=c#Photo-28">
  3856.          <img alt="This should be Google-messages-2.png.  Is it missing?" border="0" id="Photo_28"
  3857.               title="Photo Google-messages-2.png.  Click to redisplay larger version of image."
  3858.               src=""
  3859.               width="357" height="189"
  3860.           /></a>
  3862.      <p>
  3863. Sometimes I despair.  OK, click on the second one, and receive the information that the app
  3864. will soon be installed.  Wait a while.  Nothing.  While I was looking, discovered this
  3865. comment about the app:
  3866.      </p>
  3868.      <blockquote class="fullwidth">
  3869.        <div class="listitemwidth">
  3870.          December 30, 2019
  3871.        </div>
  3873. <div class="listitemwidth">
  3874.  I still don't know what good this app is, but I can never find answers to the noises that
  3875.  are bugging me.
  3876. </div>
  3877.      </blockquote>
  3879.      <p>
  3880. And that was what <i>I</i> wrote <a href=";article=D-20200101-010424#D-20200101-010424">on the following day</a>.  Further investigation shows that it was already installed on
  3881. the phone, and it's the standard messages app that I use.  Why didn't Google say so?
  3882. They're supposed to keep track.
  3883.      </p>
  3885.      <p>
  3886. So: what next?  I couldn't find anything to tell me what to do.  Finally, though, found my
  3887. way through the maze.  You have to be logged in to Google to even get the correct link!
  3888. And that told me the way through the maze of menus on my phone: click on the image of
  3889. myself (currently) at top right and select <b>Device pairing</b>, which tells me to go to
  3890. <a href=""></a>.  And there I get a <a href="">QR Code</a> and instructions:
  3891.      </p>
  3893.        <a id="Photo-29" name="Photo-29"
  3894.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=111111111111111111111111111112&amp;topics=c#Photo-29">
  3895.          <img alt="This should be Google-messages-3.png.  Is it missing?" border="0" id="Photo_29"
  3896.               title="Photo Google-messages-3.png.  Click to redisplay larger version of image."
  3897.               src=""
  3898.               width="319" height="212"
  3899.           /></a>
  3901.      <p>
  3902. Problem: there is no <b>QR code scanner</b> on the phone:
  3903.      </p>
  3905.        <a id="Photo-30" name="Photo-30"
  3906.          href="diary-apr2024.php?dirdate=20240415&amp;imagesizes=1111111111111111111111111111112&amp;topics=c#Photo-30">
  3907.          <img alt="This should be Google-messages-4.jpeg.  Is it missing?" border="0" id="Photo_30"
  3908.               title="Photo Google-messages-4.jpeg.  Click to redisplay larger version of image."
  3909.               src=""
  3910.               width="177" height="384"
  3911.           /></a>
  3913.      <p>
  3914. I couldn't find a way to use the code.  But I did have the option of signing in, and
  3915. suddenly that worked,
  3916.      </p>
  3918.      <p>
  3919. And the results?  It looks surprisingly like Microsoft's PhoneLink.  But it does have the
  3920. advantage that I don't have to fire up a Microsoft machine to access it.
  3921.      </p>
  3923.      <p>
  3924. So, next step: save the messages.  Why would you want to do that?, says Callum.  But yes,
  3925. you can back them up—to <a href="">Google
  3926. Drive</a>, the storage medium that has caused me so much pain in the past.  And doubtless
  3927. the format would be unwieldy.
  3928.      </p>
  3930.      <p>
  3931. And at the end, I also understood the comment I made <a href=";article=D-20200101-010424#D-20200101-010424">five years ago</a>: the thing keeps dinging at me, the noise it makes when a notification
  3932. arrives.  But all I find is information that my phone is linked to a web browser.
  3933.      </p>
  3935.      <p>
  3936. So what's wrong here?  Clearly the ability to save messages to Google Drive could be useful
  3937. to some people.  But why can't I save them on the current machine?  Once again other people
  3938. are making decisions for me, not the ones I want.  It would be so simple just to save the
  3939. messages, metadata and all, but modern web and mobile phone software seems to ignore the
  3940. obvious and want to run before it can walk.
  3941.      </p>
  3943.      <p>
  3944. So, a comparison of the methods:
  3945.      </p>
  3947.      <table summary="Automatically generated table">
  3948.       <tr>
  3949.          <td valign="top" align="left"></td>
  3950.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3951.          <td valign="top" align="left">Microsoft PhoneLink</td>
  3952.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3953.          <td valign="top" align="left">Google Messages</td>
  3954.       </tr>
  3956.       <tr>
  3957.          <td valign="top" align="left">1</td>
  3958.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3959.          <td valign="top" align="left">Start Microsoft “PhoneLink” and display the message.</td>
  3960.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3961.          <td valign="top" align="left">Pair phone with <i></i></td>
  3962.       </tr>
  3964.       <tr>
  3965.          <td valign="top" align="left">2</td>
  3966.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3967.          <td valign="top" align="left">Select text.</td>
  3968.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3969.          <td valign="top" align="left">Go to <i></i> and display message</td>
  3970.       </tr>
  3972.       <tr>
  3973.          <td valign="top" align="left">3</td>
  3974.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3975.          <td valign="top" align="left">Copy to clipboard with <b>c-c</b>.</td>
  3976.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3977.          <td valign="top" align="left">Select text.</td>
  3978.       </tr>
  3980.       <tr>
  3981.          <td valign="top" align="left">4</td>
  3982.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3983.          <td valign="top" align="left">Mark text in <i>xclipboard</i> on the host machine.</td>
  3984.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3985.          <td valign="top" align="left">Mark text in <i>xclipboard</i>.</td>
  3986.       </tr>
  3988.       <tr>
  3989.          <td valign="top" align="left">5</td>
  3990.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3991.          <td valign="top" align="left">Save!</td>
  3992.          <td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td>
  3993.          <td valign="top" align="left">Save!</td>
  3994.       </tr>
  3996.       <tr>
  3997.          <td valign="top" align="left"></td>
  3998.       </tr>
  3999.    </table>
  4001.      <p>
  4002. So yes, it could be easier if it weren't for the fact that I have to explicitly pair and
  4003. unpair.  But the noise it keeps making means that I have to unpair when I'm not using it.
  4004. Why can't they have a button to turn the noise off?
  4005.      </p>
  4007.      <p>
  4008. In passing, Callum mentioned another app, SMG Backup and Restore.  It still just copies to
  4009. Google Drive.
  4010.      </p>
  4011.      </div>
  4012.    ]]>
  4013.  </description>
  4014.  <dc:creator>Greg Lehey</dc:creator>
  4015.  <dc:date>2024-04-16T00:04:41+00:00</dc:date>
  4016. </item>
  4019. <!-- topic G not selected
  4020.      <p>
  4021. The bubble in my eye is gradually getting smaller, not as fast as I had hoped.  This
  4022. evening, though, I had two after the evening eyedrops!  One was the normal bubble, and the
  4023. other one was a tiny bubble about 5% of the size of the main one.  It hung around for an
  4024. hour or two before disappearing again.
  4025.      </p>
  4027.      <p>
  4028. How did that happen?  My guess is that one of the floaters kept it from joining the main
  4029. bubble.
  4030.      </p>
  4032. End deselected topic G (Double bubble) -->
  4035. <item>
  4036. <guid isPermaLink='true'></guid>
  4037. <link></link>
  4038. <category>technology</category>
  4039. <category>opinion</category>
  4040. <title>Solving the routing issue</title>
  4041.  <description>
  4042.    <![CDATA[
  4043.    <div align="justify">
  4044.      <p>
  4045. I should have called <a href="">Aussie Broadband</a> yesterday about the <a href="!&amp;article=D-20240415-031822#D-20240415-031822">routing problems</a> that I discovered on Sunday.  But I dreaded the encounter, so I put
  4046. it off.
  4047.      </p>
  4049.      <p>
  4050. But it had to be done, and today I called up and was connected relatively quickly to Ashika,
  4051. who of course didn't understand.  What kind of router do I have installed?  She could only
  4052. see one IP address.  I tried to explain, and she decided to escalate to “level 2” after only
  4053. 3 minutes.  And after a total of 5 minutes, the call was done: she would send me an email,
  4054. to which I should reply with the problem details.
  4055.      </p>
  4057.      <p>
  4058. That's actually quite reasonable, and quite a difference from recent encounters.  But how do
  4059. I explain in a manner that will get the problem involved?  Ask an expert, Philip Paeps.
  4060.      </p>
  4062.      <p>
  4063. First question: what tools do I use?  So far I have been using the rather strange invocation
  4064.      </p>
  4066.      <blockquote class="fullwidth">
  4067. <div style="text-align:left">
  4068.  <tt>
  4069. <code><font color="blue">=== root@lax (/dev/pts/7)</font> <font color="red">~</font> <font color="blue">90</font> &#45;&gt; <b><tt>whois &#45;h " &#45;v"</tt></b></code>
  4070. <br />AS &nbsp; &nbsp; &nbsp;| IP &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; | BGP Prefix &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| CC | Registry | Allocated &nbsp;| AS Name
  4071. <br />NA &nbsp; &nbsp; &nbsp;| &nbsp; &nbsp;| NA &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| AU | ripencc &nbsp;| 1991&#45;05&#45;01 | NA
  4072.  </tt>
  4073. </div>
  4074. </blockquote>
  4076.      <p>
  4077. And I don't even understand the syntax.  I know the basic syntax for <a href="">whois</a>, but it doesn't describe
  4078. the <tt>-v</tt> parameter.  I'm still not 100% clear what it is, but it seems that it's
  4079. passed to a special version of <i>whois</i> at <a href=""></a>, which also proves to have a web interface that doesn't really say any more.
  4080.      </p>
  4082.      <p>
  4083. So: in the course of the discussion, Philip came up with the following tools:
  4084.      </p>
  4086.      <ul>
  4087.        <li class="fullwidth">
  4088.          <p class="listitemwidth">
  4089.            <a href=""></a>, which is particularly unreliable.  While I
  4090.    got it to work with <a href="">Google
  4091.    Chrome</a>, I wasn't able to get it to work with <a href=""><i>firefox</i></a>:
  4092.          </p>
  4094.  <blockquote class="fullwidth">
  4095. <div style="text-align:left">
  4096.  <tt>
  4097. Sorry, We appear to be broken.
  4098. <br />While the issue has been logged on our side,
  4099. <br />it might help to send this following message to the admin (
  4100.  </tt>
  4101. </div>
  4102. </blockquote>
  4104.  <p class="listitemwidth">
  4105.    It does seem to have some interesting information when it's prepared to divulge it.
  4106.  </p>
  4107.        </li>
  4109.        <li class="fullwidth">
  4110.          <p class="listitemwidth">
  4111.    <i></i>, accessible by <i><a href="">telnet</a></i>.  It's particularly verbose:
  4112.          </p>
  4113.  <blockquote class="fullwidth">
  4114. <div style="text-align:left">
  4115.  <tt>
  4116. <code><font color="blue">=== root@hydra (/dev/pts/34)</font> <font color="red">~</font> <font color="blue">20</font> &#45;&gt; <b><tt>telnet route&#45;</tt></b></code>
  4117. <br />Hello, this is FRRouting (version 9.0.1).
  4118. <br />Copyright 1996&#45;2005 Kunihiro Ishiguro, et al.
  4119. <br />
  4120. <br />route&#45;> &nbsp;show bgp ipv4 unicast
  4121. <br />BGP routing table entry for, version 8922913
  4122. <br />Paths: (21 available, best #21, table default)
  4123. <br />&nbsp;&nbsp;Not advertised to any peer
  4124. <br />&nbsp;&nbsp;22296 6140 1299 4764
  4125. <br />&nbsp;&nbsp; &nbsp; from (
  4126. <br />&nbsp;&nbsp; &nbsp; &nbsp;Origin IGP, valid, external, rpki validation&#45;state: not found
  4127. <br />&nbsp;&nbsp; &nbsp; &nbsp;Community: 1299:35000 22296:10004
  4128. <br />&nbsp;&nbsp; &nbsp; &nbsp;Last update: Tue Apr 16 14:46:43 2024
  4129. <br />
  4130.  </tt>
  4131. </div>
  4132. </blockquote>
  4134.  <p class="listitemwidth">
  4135.    This repeats many times, about 200 lines, and I haven't been able to decipher it yet.
  4136.    In addition, though there's a <tt>help</tt> command, it doesn't say anything useful, in
  4137.    particular not what other commands are available.
  4138.  </p>
  4140.  <p class="listitemwidth">
  4141.    <a href="">Routeviews</a> also has a web interface that I
  4142.    haven't been able to decipher yet.
  4143.  </p>
  4144.        </li>
  4146.        <li class="fullwidth">
  4147.          <p class="listitemwidth">
  4148.            <a href=""></a>.  Philip gave
  4149.            me a <a href="">URL for my net block</a>.
  4150.          </p>
  4151.        </li>
  4152.      </ul>
  4154.      <p>
  4155. In the process, Philip identified a nick “cyrusone”, also known as Mark Price, who helped me
  4156. through the maze <a href=";article=D-20230428-003822#D-20230428-003822">a year ago</a>.  He is “a prince among men” and Philip's upstream.
  4157.      </p>
  4159.      <p>
  4160. In the background, it seems that Philip contacted people whom he knows at Aussie:
  4161.      </p>
  4163.      <blockquote class="fullwidth">
  4164. <div style="text-align:left">
  4165.  <tt>
  4166. *trouble* A look is being taken by an aussiebb person with a clue &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [13:08]
  4167. <br />*trouble* do you have your WAN IP? &nbsp;They're trying to find where your route should go
  4168. <br />&lt;Groogle&gt; xl0: flags=8943&lt;UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST&gt; metric 0 mtu 1500
  4169. <br />*trouble* my transit friend found an edge friend who is now looking around :) &nbsp; &nbsp; [13:14]
  4170. <br />&lt;Groogle&gt; This looks like it might happen faster than the typical support call to the [13:15]
  4171. <br />&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;support people.
  4172.  </tt>
  4173. </div>
  4174. </blockquote>
  4177.      <p>
  4178. So the whole thing took 16 minutes.  On occasion I've taken longer to authenticate with
  4179. Aussie “support”.  And yes, it works.
  4180.      </p>
  4182.      <p>
  4183. Some of the tools show interesting graphic representations.  The <a href="">RIPE
  4184. page</a> shows:
  4185.      </p>
  4187.        <a id="Photo-31" name="Photo-31"
  4188.          href="diary-apr2024.php?dirdate=20240416&amp;imagesizes=11111111111111111111111111111112&amp;topics=c#Photo-31">
  4189.          <img alt="This should be RIPE-view.png.  Is it missing?" border="0" id="Photo_31"
  4190.               title="Photo RIPE-view.png.  Click to redisplay larger version of image."
  4191.               src=""
  4192.               width="489" height="391.2"
  4193.           /></a>
  4195.      <p>
  4196. And when I can get it to work, <i></i> shows:
  4197.      </p>
  4199.        <a id="Photo-32" name="Photo-32"
  4200.          href="diary-apr2024.php?dirdate=20240416&amp;imagesizes=111111111111111111111111111111112&amp;topics=c#Photo-32">
  4201.          <img alt="This should be  Is it missing?" border="0" id="Photo_32"
  4202.               title="Photo  Click to redisplay larger version of image."
  4203.               src=""
  4204.               width="489" height="504.28125"
  4205.           /></a>
  4207.      <p>
  4208. In summary: it helps to have friends.  And it shows how big a difference there is between
  4209. Aussie's front line mail configurer “support” and the people behind the scenes
  4210.      </p>
  4211.      </div>
  4212.    ]]>
  4213.  </description>
  4214.  <dc:creator>Greg Lehey</dc:creator>
  4215.  <dc:date>2024-04-17T00:39:17+00:00</dc:date>
  4216. </item>
  4219. <!-- topic G not selected
  4220.      <p>
  4221. I had hoped that the bubble in my eye would be gone by now, but no such luck.  It's getting
  4222. smaller, and on a couple of occasions I got a smaller one that then went away again.  But by
  4223. evening it was still not gone.
  4224.      </p>
  4226. End deselected topic G (Eye progress) -->
  4229. <!-- topic kH not selected
  4230.      <p>
  4231. It's been <a href=";article=D17-11#D17-11">fifteen years</a> since I started cooking with <a href="">sourdough</a>.  In that time I have tried
  4232. various sources, including making my own from <a href="">kimchi</a> juice, but in <a href=";subtitle=New%20sourdough%20starter&amp;article=D-20171019-222849#D-20171019-222849">October 2017</a> I bought one on <a href="">eBay</a>, and
  4233. I've been using that ever since.
  4234.      </p>
  4236.      <p>
  4237. But somehow things are changing.  I now have something like the 50th generation of the
  4238. starters, and starters that would happily keep for months are becoming dark and mouldy
  4239. within the 2 months that I need them to last for.  And looking back to October 2017, it
  4240. seems that they're also less active.  How did that happen?  I can replace them, of course,
  4241. but it irritates me.
  4242.      </p>
  4244. End deselected topic kH (Sourdough lifetime?) -->
  4247. <!-- topic Go not selected
  4248.      <p>
  4249. The bubble in my left eye has been shrinking continuously, but somehow not as fast as the
  4250. one in my right eye three weeks ago.  That bubble was much larger, and it took 163 hours,
  4251. almost exactly a week to disappear.  This one started at about the size that the right
  4252. bubble had after two days, but it still took 155 hours.  But this evening, <i>finally</i>,
  4253. it was gone.  All done bar the floaters.
  4254.      </p>
  4256.      <p>
  4257. So, for the first time in decades, I can see clearly in the distance.  Really?  <a href=";subtitle=A%20new%20eye&amp;article=D-20240323-015848#D-20240323-015848">After the first operation</a> I had the distinct impression that my focus was too close
  4258. by 0.5 <a href="">dioptres</a>, which was maybe
  4259. confirmed by the follow-up examination <a href=";subtitle=Cataract%20surgery%20follow-up&amp;article=D-20240405-011513#D-20240405-011513">two weeks later</a>.  But now I can see clearly, read email on TV better than I have been
  4260. able to for months, and I can read text on my computer monitors at the 67 cm distance that
  4261. you'd expect from 1.5 dioptre glasses.
  4262.      </p>
  4264.      <p>
  4265. But sometimes I get the impression that my focus shifts in relatively short periods of time,
  4266. and that distant things are not as sharp as they could be.  From time to time the vision is
  4267. also smudged, maybe something to do with the eye drops.  In addition, the view of each eye
  4268. doesn't quite correspond; hold a hand in front of one eye and then the other, and the view
  4269. changes both in shape and position.  Take the hand away and I have perfect stereoscopic
  4270. vision.  Clearly it's a good idea to wait for things to settle.
  4271.      </p>
  4273. End deselected topic Go (I can see clearly now) -->
  4276. <!-- topic h not selected
  4277.      <p>
  4278. I don't know why, but the last few weeks have been particularly active, as this diary shows.
  4279. Clearly the eye operations were one aspect, but only one.  Finally, though, it seems as if
  4280. things are getting quieter.  I'm not complaining.
  4281.      </p>
  4283. End deselected topic h (Peace?) -->
  4286. <!-- topic Gp not selected
  4287.      <p>
  4288. It only became clear in the course of the day: now that my left eye has “normal” distance
  4289. vision, I no longer need optical corrections in my cameras, and I could use the viewfinders
  4290. in my older film cameras.  I could do that before with my right eye, of course, but that's
  4291. not my dominant eye.  It really takes time to get used to the idea.
  4292.      </p>
  4294. End deselected topic Gp (More eye improvements) -->
  4297. <!-- topic ao not selected
  4298.      <p>
  4299. <a href="">Yvonne</a> has decided that <a href="">Bruno</a> is lonely, and that we could do with another
  4300. cat.  Maybe she's right; I had thought of the same thing myself.
  4301.      </p>
  4303.      <p>
  4304. And what kind of cat?  It seems that <a href="">ragdolls</a> are the flavour of the year, to the point that they keep cropping up
  4305. unrelated search results.  But I chose Bruno, who was exactly what I was looking for.  This
  4306. time it's Yvonne's choice.  And she wants a brown <a href="">Burmese</a> female.  But the only one she
  4307. could find was 3 years old, a little older than I had expected.
  4308.      </p>
  4310.      <p>
  4311. Burmese are popular cats, right?  And brown is the standard base colour.  How difficult can
  4312. it be to find a kitten?  Off to look at <a href="">Gumtree</a>, which seems to think that I'm in <a href="">Queensland</a>.  Checking through the listings, there were only 6 hits, 3 of them
  4313. Ragdoll.  Another was only adult chocolates, and the last two were the same advertisement: 4
  4314. chocolates, 1 lilac, and one brown—male, and sold.  So there's really nothing!  Am I looking
  4315. in the wrong place?  It seems that brown Burmese are no longer in fashion.
  4316.      </p>
  4318.      <p>
  4319. In passing, these kittens are marked (apparently by Gumtree) as being available from 2
  4320. April, though the date of birth was 2 February!  What responsible breeder gives away kittens
  4321. at 2 months of age?  Not even this one, as it happens—he wants to wait until 27 April, by
  4322. which time they will be 12 weeks old, the bare minimum.  I would expect them to keep them
  4323. with their mother until they're 16 weeks old, which would be 24 May.  But that's academic
  4324. when they don't have anything that interests us.
  4325.      </p>
  4327. End deselected topic ao (Another new cat?) -->
  4330. <!-- topic g not selected
  4331.      <p>
  4332. Paul Donaghy along today to mow the lawn.  He was finished much faster than in the past, as
  4333. he noted.  So the new mower saves money too.
  4334.      </p>
  4336. End deselected topic g (Mowing the lawn again) -->
  4339. <!-- topic gho not selected
  4340.      <p>
  4341. Michael, a colleague of Warrick Pitcher, along today to remove the blackwood (<a href="">Acacia melanoxylon</a>) that has
  4342.        sprung up too close to the house in the last 5 years.  Most of his time seems to have been
  4343.        spent loading and unloading his machine and driving it to the site of the tree.
  4344.      </p>
  4347.      <p>
  4348. And then he pulled it out almost without effort:
  4349.      </p>
  4352.      <p>
  4353. The whole thing, including moving the remains of the tree to the west of the property, took
  4354. 40 minutes.  Michael estimates that 100 years ago it would have taken 5 men half a day.
  4355.      </p>
  4357.      <p>
  4358. And now the dogs are confused:
  4359.      </p>
  4362.      <p>
  4363.      </p>
  4365. End deselected topic gho (Removing the blackwood) -->
  4368. <!-- topic h not selected
  4369.      <p>
  4370. Into town today to have my hair cut.  The first time I drove a car in how long?  It proved
  4371. to be <a href=";article=D-20240214-013023#D-20240214-013023">13 February</a>, coincidentally also to have my hair cut.  And my car had been so lonely
  4372. that it didn't want to start, so I had to take <a href="">Yvonne's</a> car.
  4373.      </p>
  4375.      <p>
  4376. And what's it like driving again?  A little different from what I expected.  Clearly I
  4377. didn't need glasses any more, and that made itself noticeable at the corner of Grassy Gully
  4378. Road and Ballarat-Colac Road: there's a 135° junction, and I need to look over my shoulder
  4379. to see oncoming traffic.  In the past the frame of the glasses got in the way.  No more!
  4380. But I'm still not sure whether my stereoscopic vision is working properly.  Presumably that
  4381. will improve over the weeks.
  4382.      </p>
  4384. End deselected topic h (Another haircut) -->
  4387. <item>
  4388. <guid isPermaLink='true'></guid>
  4389. <link></link>
  4390. <category>animals</category>
  4391. <category>technology</category>
  4392. <category>photography</category>
  4393. <category>opinion</category>
  4394. <title>Still more cats</title>
  4395.  <description>
  4396.    <![CDATA[
  4397.    <div align="justify">
  4398.      <p>
  4399. <a href="">Yvonne</a> is really dead set on getting a brown <a href="">Burmese cat</a>.  No other colour will do.
  4400. We could have found a (small) number of chocolates, but no, it must be a brown.
  4401.      </p>
  4403.      <p>
  4404. So she asked the seller for photos.  And they came by mobile phone, of course.  But what I
  4405. didn't expect was that she couldn't download them.  First she had to turn on mobile data and
  4406. download them slowly and expensively!  Only later did I find suggestions:
  4407.      </p>
  4409.        <a id="Photo-33" name="Photo-33"
  4410.          href="diary-apr2024.php?dirdate=20240419&amp;imagesizes=1111111111111111111111111111111112&amp;topics=c#Photo-33">
  4411.          <img alt="This should be Android-notworking-1.jpeg.  Is it missing?" border="0" id="Photo_33"
  4412.               title="Photo Android-notworking-1.jpeg.  Click to redisplay larger version of image."
  4413.               src=""
  4414.               width="177" height="384"
  4415.           /></a>
  4416.        <a id="Photo-34" name="Photo-34"
  4417.          href="diary-apr2024.php?dirdate=20240419&amp;imagesizes=11111111111111111111111111111111112&amp;topics=c#Photo-34">
  4418.          <img alt="This should be Android-notworking-1-detail.jpeg.  Is it missing?" border="0" id="Photo_34"
  4419.               title="Photo Android-notworking-1-detail.jpeg.  Click to redisplay larger version of image."
  4420.               src=""
  4421.               width="434" height="155"
  4422.           /></a>
  4424.      <p>
  4425. More searching in the settings pages brought me to this:
  4426.      </p>
  4428.        <a id="Photo-35" name="Photo-35"
  4429.          href="diary-apr2024.php?dirdate=20240419&amp;imagesizes=111111111111111111111111111111111112&amp;topics=c#Photo-35">
  4430.          <img alt="This should be Android-notworking-3-detail.jpeg.  Is it missing?" border="0" id="Photo_35"
  4431.               title="Photo Android-notworking-3-detail.jpeg.  Click to redisplay larger version of image."
  4432.               src=""
  4433.               width="281" height="240"
  4434.           /></a>
  4436.      <p>
  4437. People, we've had machines with multiple interfaces for 40 years!  The routing issues have
  4438. been resolved.  Why should it be necessary to choose things manually?  And if so, why is the
  4439. default the slower and more expensive network?  My guess is that Internet and phone network
  4440. still haven't come to terms with each other.
  4441.      </p>
  4443.      <p>
  4444. But that was on <a href="">Yvonne's</a> phone.  On mine I don't even get the
  4445. choice.
  4446.      </p>
  4448.      <p>
  4449. And what do the photos look like?  The cat looks more chocolate than brown, at least in some
  4450. of the photos.  Where are they?  How do I know?  Hidden somewhere in the innards of
  4451. <a href="">Android</a>.  I
  4452. still haven't been able to get them out onto a sane medium.
  4453.      </p>
  4455.      <p>
  4456. How I hate Android!
  4457.      </p>
  4458.      </div>
  4459.    ]]>
  4460.  </description>
  4461.  <dc:creator>Greg Lehey</dc:creator>
  4462.  <dc:date>2024-04-20T00:52:55+00:00</dc:date>
  4463. </item>
  4466. <item>
  4467. <guid isPermaLink='true'></guid>
  4468. <link></link>
  4469. <category>general</category>
  4470. <category>technology</category>
  4471. <category>opinion</category>
  4472. <title>Power fail?</title>
  4473.  <description>
  4474.    <![CDATA[
  4475.    <div align="justify">
  4476.      <p>
  4477. While cooking breakfast today, the lights over the cooktops went out.  More investigation
  4478. showed that <i>another</i> circuit breaker had tripped.  Why?  There's nothing outside that
  4479. could have done so, but the water kettle thermostat had just turned it off.  Is it on its
  4480. way out?  No idea, but it did demonstrate to us where circuit 5 (from the row of breakers)
  4481. is: “kitchen”, pantry, lounge room and dining room.  So <i>tiwi</i> failed too.  Fortunately
  4482. it came back without too much trouble, but I hate it when computers go down.
  4483.      </p>
  4484.      </div>
  4485.    ]]>
  4486.  </description>
  4487.  <dc:creator>Greg Lehey</dc:creator>
  4488.  <dc:date>2024-04-21T03:01:11+00:00</dc:date>
  4489. </item>
  4492. <!-- topic ao not selected
  4493.      <p>
  4494. Off to <a href="">Keilor Downs</a> today,
  4495. a journey of 135 km, to see Helen Weir and her cat Pixie, the one that <a href="">Yvonne</a> wanted to buy.  She's definitely brown and not chocolate:
  4496.      </p>
  4498.      <p>
  4499. But that was after we had found her: she had hidden, apparently when she heard us coming.
  4500. She's a little timid, but Yvonne likes her, so we took her.  Her kennel name is Stacemoh
  4501. Pixie Lee, but Yvonne decided to call her <a href="">Mona</a>.
  4502.      </p>
  4504.      <p>
  4505. Helen has a number of other cats, and like us 35 years ago, she is interested in red cats.
  4506. Her current litter has two males:
  4507.      </p>
  4509.      <div align="left">
  4510.      </div>
  4512.      <p>
  4513. They're both male, but they're clearly of different colours.  The father is lilac, the
  4514. mother tortie, but her pedigree shows that she carries chocolate and blue, so it's
  4515. reasonable to assume that the lighter one is cream, not the most common colour.  Of course,
  4516. it's <i>very</i> difficult to reproduce the colours correctly in a photo, but the difference
  4517. is obvious.
  4518.      </p>
  4520.      <p>
  4521. Back home, picked up a crate from Julie Donaghy and first put her in the bathroom.  She
  4522. wandered around, into Yvonne's office, but then returned to the box, where he stayed for
  4523. several hours.
  4524.      </p>
  4527.      <p>
  4528. In the evening, I finally pulled her out of the box, and she came with little resistance,
  4529. and walked around the lounge room.  As good as no contact with <a href="">Bruno</a>.  She's clearly suffering from the change,
  4530. so we put her in the laundry to spend the night.
  4531.      </p>
  4533. End deselected topic ao (Hello Mona) -->
  4536. <item>
  4537. <guid isPermaLink='true'></guid>
  4538. <link></link>
  4539. <category>technology</category>
  4540. <category>general</category>
  4541. <category>opinion</category>
  4542. <title>Google maps: the curate's egg</title>
  4543.  <description>
  4544.    <![CDATA[
  4545.    <div align="justify">
  4546.      <p>
  4547. I've been using <a href="">Google Maps</a> for navigation even when I don't need it, but clearly today's journey to <a href="">Keilor Park</a> was a case where I did need
  4548. it.  It got us there with no problems at all, once again taking a short cut round the
  4549. university which proved to be about 2 minutes shorter than going through <a href="">Ballarat</a>.
  4550.      </p>
  4552.      <p>
  4553. But the user interface!  Even by <a href="">Android</a> standards it's
  4554. appalling.  Today I had:
  4555.      </p>
  4557.      <ul>
  4558.        <li class="fullwidth">
  4559.  <p class="listitemwidth">
  4560.    Send the route to my phone.  I would have liked to send it to <a href="">Yvonne's</a> phone, but it's too secure for that.  And I know from past experience
  4561.      that it will forget a route at the drop of a hat.  OK, there's this “Pin” button.  Press
  4562.      that.  Your route is pinned!  But how do I get it back again?  I couldn't find a way.
  4563.      Pressing the button again just “unpins”.  An obvious place would be <b>Directions</b>,
  4564.      but that only gave me places like <a href="">Geesthacht</a>, <a href="">Frankfurt</a> (am Main), <a href="">Brussels</a> and similar.  Nothing to do
  4565.      with Keilor Park.  Doubtless there's a way to recall it, but I didn't find it, and this
  4566.      interface is supposed to be <a href="">intuitive</a>.
  4567.  </p>
  4569.          <p class="listitemwidth">
  4570.    Part of the problem here is clearly that “there can only be one”.  No matter where I
  4571.    look at Google Maps, it remembers it into one single group of places.  And even then
  4572.    there are places that I don't recall even looking at, like <a href="">Kuala Lumpur
  4573.    International Airport</a>.
  4574.          </p>
  4575.        </li>
  4577.        <li class="fullwidth">
  4578.          <p class="listitemwidth">
  4579.            We thought that we wouldn't have enough cash to pay for <a href="">Mona</a>, so I went looking for an <a href="">ATM</a>.  Google Maps
  4580.            offers all sorts of things to “Explore” round the destination.  Restaurants, hotels,
  4581.            petrol stations, “car places”, whatever that might be, and “More”, which proves to be
  4582.            banks, “coffee”, post offices, bars, groceries and hospitals.  Still no ATMs.  And
  4583.            banks?  All closed, of course: today was Saturday.  But without drawing attention to
  4584.            itself, any choice offers an input field.  And there I could enter “ATM”.  But why so
  4585.            complicated?  And this was on a real computer.  I don't dare think what it would have
  4586.            been like on a mobile phone.
  4587.          </p>
  4588.        </li>
  4590.        <li class="fullwidth">
  4591.          <p class="listitemwidth">
  4592.            If I want to get rid of a route and change it for another, what do I do?  <a href=";article=D-20240323-020612#D-20240323-020612">Last month</a> I established that I should answer “Yes” to the question “Exit
  4593.            Navigation?” to continue navigating.  But today I had a complete failure.  I had loaded
  4594.            the route from Helen's place to the next ATM, but I didn't really want to go there, just
  4595.            establish where it was.  OK, Google, take me home.  Exit Navigation?  Yes!  But it
  4596.            didn't work.  And I was already at the freeway, so I turned on it anyway.  Only later
  4597.            did I realize that I was on the wrong freeway, the one to <a href="">Bendigo</a>.  OK, Google, take me home.
  4598.            Nice map of the local area, but no directions.  I had to stop in the emergency lane,
  4599.            stop and restart the app, and then <i>finally</i> it worked, taking me across a
  4600.            cross-country route that in fact didn't seem any worse than the way we came over the
  4601.            freeway.
  4602.          </p>
  4603.        </li>
  4604.      </ul>
  4606.      <p>
  4607. Then there are silly things like lack of preferences.  Do I get directions in kilometres or
  4608. miles?  Google Maps decides, based on the location, and if I don't like it, I can fix it.
  4609. Why can't I tell it “forget archaic measurements”?
  4610.      </p>
  4612.      <p>
  4613. So on the way home I saw Google Maps from its worst and its best sides.  I had to fight to
  4614. get it to take me home, but when I did, it found a good route that I would probably not have
  4615. found by myself.  All it needs is an interface overhaul.
  4616.      </p>
  4617.      </div>
  4618.    ]]>
  4619.  </description>
  4620.  <dc:creator>Greg Lehey</dc:creator>
  4621.  <dc:date>2024-04-21T03:14:00+00:00</dc:date>
  4622. </item>
  4625. <item>
  4626. <guid isPermaLink='true'></guid>
  4627. <link></link>
  4628. <category>technology</category>
  4629. <category>photography</category>
  4630. <category>opinion</category>
  4631. <title>hydra crash!</title>
  4632.  <description>
  4633.    <![CDATA[
  4634.    <div align="justify">
  4635.      <p>
  4636. Back home, I had plenty of photos to process.  A good thing that I have <i>despise</i>,
  4637. which gets through them really quickly.
  4638.      </p>
  4640.      <p>
  4641. But then things froze up.  Somehow the <i>rdesktop</i> window had focus and wouldn't let go.
  4642. And <i>vtys</i> hung.  Gradually it became clear: I had lost network connectivity.  Nothing
  4643. for it but the Big Red Button.  Two crashes in one day!
  4644.      </p>
  4646.      <p>
  4647. Not only that, of course.  I've been holding off updating the <a href="">X</a> configuration on <i>hydra</i> until my eyes are OK again.
  4648. And there's so much piled up: the <a href="">window managers</a> are a real mess.
  4649. Managed to get the thing up and stumbling, but of course there was no time left for photo
  4650. processing.  And why did the system freeze?  Defective network card?  It might be a good
  4651. time to install the driver for the on-board interface, which might be of better quality.
  4652. Still more work.
  4653.      </p>
  4654.      </div>
  4655.    ]]>
  4656.  </description>
  4657.  <dc:creator>Greg Lehey</dc:creator>
  4658.  <dc:date>2024-04-21T04:55:30+00:00</dc:date>
  4659. </item>
  4662. <!-- topic ah not selected
  4663.      <p>
  4664. Up first thing this morning to see how <a href="">Mona</a> was getting on.  But I didn't need to open the door to the laundry: it was already open!
  4665. Clearly we have a door-opener.  By contrast, <a href="">Bruno</a> can't even open the door when it's ajar.  Of Mona herself there was nothing to
  4666. be seen.
  4667.      </p>
  4669.      <p>
  4670. Waited a while, but still no Mona.  <a href="">Yvonne</a> spent some time
  4671. looking under armchairs, and finally found something under the sofa that moved from one
  4672. position to another the next time she looked.  Mona?  A little later we heard a sound that
  4673. could have been a cat.  Where was she?  Nothing to be seen under the sofa, so we turned it
  4674. on its back and took a look:
  4675.      </p>
  4678.      <p>
  4679. About the only thing we saw, apart from lots of dirt, was this:
  4680.      </p>
  4683.      <p>
  4684. That's a cable for the recliner at the left.  Somebody must have put it under part of the
  4685. frame.  And it didn't work, but that was only because the cable had been disconnected from
  4686. the power supply.
  4687.      </p>
  4689.      <p>
  4690. And there seems to be no way to get further inside the sofa without destroying something.
  4691. Yvonne was concerned that Mona might have got into a place where she couldn't get out again.
  4692. But that seemed unlikely given that she had been able to move around before, so we left it.
  4693. Our biggest concern was that she doesn't seem to have eaten anything since she arrived here.
  4694.      </p>
  4696.      <p>
  4697. A few hours later I saw her on the windowsill in the dining room.  Looked timid, but she let
  4698. me approach her and stroke her, purred and seemed relatively happy.  But then she was off
  4699. again, and a too-enthusiastic greeting from the dogs did nothing to make her more confident.
  4700. And for the first time we heard <a href="">Bruno</a> hiss.
  4701.      </p>
  4703.      <p>
  4704. More gone Mona, until the evening, when she came out again.  Let me stroke her, but walked
  4705. on, and a bit later she was gone again.  Clearly this is going to be a long process.  Left
  4706. her in the lounge room (I think) for the night, with the door to laundry (litter tray and
  4707. food) open.
  4708.      </p>
  4710.      <p>
  4711. And her door-opening?  That's a serious issue.  This stupid house door latch can't be
  4712. effectively locked from the inside.  It can be locked, of course, but you just need to push
  4713. on the handle to unlock it, and any cat can do that.  So we're going to have to replace it.
  4714. In the meantime Yvonne came up with this mechanism:
  4715.      </p>
  4718.      <p>
  4719. But that proved to be less than convenient, and I'm concerned that she could disable it by
  4720. pushing sideways on the rod.  So we put in something more difficult to move:
  4721.      </p>
  4724.      <p>
  4725.      </p>
  4727. End deselected topic ah (Where's Mona?) -->
  4730. <item>
  4731. <guid isPermaLink='true'></guid>
  4732. <link></link>
  4733. <category>technology</category>
  4734. <category>opinion</category>
  4735. <title>hydra: the other shoe</title>
  4736.  <description>
  4737.    <![CDATA[
  4738.    <div align="justify">
  4739.      <p>
  4740. Continued with the photo processing so rudely interrupted by the <a href="!&amp;article=D-20240421-045530#D-20240421-045530">crash</a> yesterday.  And it happened again!  In each case it happened while I was
  4741. processing photos on <i></i>, a virtual machine running on <i>hydra</i>.
  4742.      </p>
  4744.      <p>
  4745. What caused it?  Yesterday I had guessed a network adapter hang, based on the fact that
  4746. everything else seemed to work, but I couldn't <i>ping</i> the machine, and any attempt to
  4747. start a program hung, presumably because the <tt>PATH</tt> includes directories on other
  4748. machines.  But for some reason <a href="">ARP</a> seemed to work.  Is
  4749. that a counterindication?  Other possibilities might include overheating, but I didn't have
  4750. the issue when processing my <a href="">house photos</a>, which also maxes out 32 cores.  And <i>despise</i> processes 32 images simultaneously,
  4751. accessing <i>eureka:/Photos</i> via <a href="">Samba</a>, so it places quite a load
  4752. on the network.
  4753.      </p>
  4755.      <p>
  4756. For the time being I'll assume that it's the network adapter.  I'll install the driver for
  4757. the other interface Real Soon Now, and in the meantime there's just despair
  4758. (<i></i>).  And that works, though significantly slower.
  4759.      </p>
  4760.      </div>
  4761.    ]]>
  4762.  </description>
  4763.  <dc:creator>Greg Lehey</dc:creator>
  4764.  <dc:date>2024-04-22T02:30:21+00:00</dc:date>
  4765. </item>
  4768. <item>
  4769. <guid isPermaLink='true'></guid>
  4770. <link></link>
  4771. <category>technology</category>
  4772. <category>opinion</category>
  4773. <title>The daily Android pain</title>
  4774.  <description>
  4775.    <![CDATA[
  4776.    <div align="justify">
  4777.      <p>
  4778. For some reason I found myself using <i></i>, <a href="">Yvonne's</a> phone, today.  I wanted to access my <a href="">local index</a>, <a href=";header=no">simplified for mobile
  4779. telephones</a>.  But it wasn't there.  How do I enter it?  The URL isn't designed even for
  4780. keyboards, let alone toy glass keyboards.
  4781.      </p>
  4783.      <p>
  4784. But there was nothing for it.  Try to
  4785. type <tt>;grog/index-local.php?page=talipon&amp;header=no</tt> into
  4786. the thing.  Yes, says Google, you
  4787. mean <tt>;header=no</tt>, right?
  4788.      </p>
  4790.      <p>
  4791. No, you
  4792. idiot, <tt>;grog/index-local.php?page=talipon&amp;header=no</tt>.
  4793. Don't try to outguess me.  But I couldn't find a way to enter the URL.
  4794.      </p>
  4796.      <p>
  4797. OK, install <a href=""><i>firefox</i></a>, which for
  4798. some reason wasn't on the phone.  Ah, you mean Firefox Fast <b>&amp;</b> Private Browser?
  4799.      </p>
  4801.      <p>
  4802. No, I mean <i>firefox</i>.  But I couldn't find it.  OK, install the Fast <b>&amp;</b>
  4803. Private Browser, with a tasteful dark blue background.  And yes, it works.  Is this a
  4804. different product, or just modern terminology for the old <i>firefox</i> that I know and
  4805. hate?  At least today it showed one advantage over <a href="">Google Chrome</a>.
  4806.      </p>
  4807.      </div>
  4808.    ]]>
  4809.  </description>
  4810.  <dc:creator>Greg Lehey</dc:creator>
  4811.  <dc:date>2024-04-22T02:38:51+00:00</dc:date>
  4812. </item>
  4814.      </channel>
  4815. </rss>

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 RSS" 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:

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