This morning while changing Hugh V’s diaper, I said:” now we have to wipe that pee off so the skin doesn’t hurt later”. Hugh V says: “do we need ahh cream (diaper rash paste)?” To which I replied:”no, we need a little boy who puts his pee in the potty.” To which he replied:” well, I’m definitely a little boy.”
The time has come to update from wasta 16.04 to something newer.
The reasons I'm dissuaded are that things have been stable for almost 7 years.
xlingpaper - which is fine
I want to get rid of:
I'm thinking about following these instructions:
https://ubuntu.com/server/docs/upgrade-introduction
https://www.cyberciti.biz/faq/how-to-upgrade-ubuntu-16-04-to-18-04-lts-using-terminal/
Before I do that I need to bet a list of the various software I have installed:
Export list of installed programs and install them on another computer (Ubuntu)
https://www.cyberciti.biz/tips/linux-get-list-installed-software-reinstallation-restore.html
and follow: https://askubuntu.com/a/353004/1661518
https://phoenixnap.com/kb/upgrade-ubuntu-16-04-to-ubuntu-18-04
OK I did update on may 29th... it took 10 hours. Now I'm sorting out all the visual theme stuff I lost in the process something about unity vs gnome. Chromium updated fine, brave installs. I had to uninstall vivaldi, and signal Tom get the upgrade to work. Obsidian and slack now work. There is the question on if i should just move up the ladder to 22.04.
This is the opening screen in Lameta
I'm trying the newly available snap package for LaMeta... My first reaction upon hearing that Nathan Marti had ported the software to Linux was Great! Snap installed no problem and the software came alive. The challenge I see with the start up screen is that there is no Privacy Policy and no indication on what Personally Identifying Information will be collected by the application and who will have access to it, when they will have access to it, and for how long. Colorado, where the main developer lives has a Privacy Law, GDPR applies in the countries of some of the software's funders. However, more than legal compliance (which may include the information in the deposits), a policy which applies to the software users would be helpful... I just wanted to test out the software, not give my personal information to some unknown machine.
One of the frequent things I hear about OLAC is a critique of its Resource Type vocabulary. The OLAC application profile adds linguistics resource types in addition to DCMITypes and an unqualified DC type value. What I don't hear from these same cries for additional descriptive power is for a structured way to use any of the existing resource type vocabularies. Let me list a few:
It has been argued that the Dublin Core Type field is an example of a genre field. This may be true in some sense, but I have a tendency to think of it in terms of an interactivity type field; more of a modality field.
We newly acquired a Chevy Bolt EUV. It seems to present a very nice driving experience. One minor thing that I think the designers overlooked. When using Apple play, the fonts in the iPhone support a wide range of Unicode (as demonstrated by my phone's name in the first image). Apple play in the car's display unit also supports a similar range Unicode (second image). However, the screen of the drivers dash does not support the same set of characters (third image). It is quite common for fonts to replace the characters they don't contain with boxes. I encountered this issue with US based automobile manufacturers' media console displays in Nigeria when people were playing songs with titles in arabic script. 
Two other user experience issues:
https://github.com/Calamari-OCR/calamari
https://builtin.com/data-science/python-ocr
https://www.geeksforgeeks.org/python-reading-contents-of-pdf-using-ocr-optical-character-recognition/#
https://github.com/usnistgov/ocr-pipeline
We are entering that new era, where notes are beginning to appear.
There is a gap in the subject content of OLAC related to legal theory of artifact ownership. Maybe there is a LCSH tag for this...
From time to time we might wonder where archival materials might be located. There might be a way to discover these using OLAC and FOAF.