In the late nineties I had a laptop that supported SuperDisk¹ floppies that could store up to 120 MB. The disks were pretty expensive and the same laptop even had a CD-RW drive so I never got around to try it.
Funny enough it was accurate all while citing items that were not in the picture (not even cropped out), like tall buildings and signs in a specific language. I'm sure there will be refined versions that are scarily accurate. Another OSINT tool for better or worse.
I use US layout with Caps Lock mapped to toggle to my "native" layout. This way I can easily code without RSI-inducing combinations to get the frequently used {}[]\, and just tap caps when I'm writing emails without needing to retrain my muscle memory of where åäö are located.
On Windows there's also a setting to get each app to remember the selected keyboard layout (Set-WinLanguageBarOption -UseLegacySwitchMode) so I don't even need to switch most times.
Great writeup. For those interested in the subject there is also PumpkinOS (https://github.com/migueletto/PumpkinOS) with accompanying blog posts going in to details.
I seem to remember successfully upgrading a machine with IBM PC DOS 7 and Windows 3.1 to Windows 95. There were issues with a few DOS commands later as some had been upgraded and others remained the IBM version.
All sites on the .tel domain used to be rendered from DNS. It seems to have changed in 2017 but Wikipedia still says[1]:
"In contrast to other top-level domains, .tel information is stored directly within the Domain Name System (DNS) [...] as opposed to the DNS simply returning details (such as IP addresses)"
I like the concept - do you have any plans for a mobile client and how the UX would translate to smaller displays? In terms of essentials, version history would be on my list, perhaps using git as a backend so that you can access the notes with other tools as well.
You say shamelessly but it could also be "cluelessly" (which doesn't excuse the company in any way). When I interview candidates, one of the questions I ask is if they know anything about licenses and if they can describe differences between for instance MIT and GPL. In my experience a surprisingly large number have no clue of the implications on a product and use code/libraries without considering the license. Either way, it's prudent to have someone review projects for this kind of liabilities before shipping anything.