A high SEO ranking does not automatically indicate a reliable result.
When the WayBack Machine was down a while ago (it responded to traceroute UDP requests, but would not establish TCP connections on ports 80 and 443), the first Google hit for detecting down status (searching for [Archive.is] waybackmachine down – Google Search) failed miserably because it redirected web.archive.org (which fails) to http://www.archive.org (which succeeds):
IsIdDownRightNow failing to detect web.archive.org downtime
Luckily when asking around on Twitter:
others were experiencing the same problem, not just in The Netherlands, but also in other countries
VMware Server (formerly VMware GSX Server) is a discontinued free-of-charge virtualization-software server suite developed and supplied by VMware, Inc.
It means that nowadays there is a very small chance you will see mangled characters (what Japanese call mojibake) when you’re surfing the web.
Serving UTF8 does not mean no unicode problems.
Below are some issues that happened not too long ago and still happen. I have reported them to all parties involved through web-care, but no response whatsoever, and this is bad: Unicode support beyond basic ASCII for the below systems are still broken even for relatively simple non-ASCII characters based in diacritics decorating a standard ASCII character.
Yes, I know the realm of encoding and code pages is a mess, especially when handling data in multiple layers of an application stack. That’s why I wrote this post in the first place, and have a whole encoding category of blog posts plus a Mojibake subset.
David Cumps discovered that certain text files come up strange in Notepad. The reason is that Notepad has to edit files in a variety of encodings, and when its back against the wall, sometimes it’s forced to guess.
As a precursor to a post tomorrow showing that serving UTF8 does not mean organisations go without unicode problems, first some statistics.
The first Unicode ideas got drafted some 30 years ago in 1987. In 1991, more than 30 years ago, the Unicode Consortium saw the light. Nowadays more than 95% percent of the web-pages (close to 100% when you include plain ASCII) is served using the UTF-8 encoding.
It means that nowadays there is a very small chance you
will see mangled characters (what Japanese call mojibake) when you’re surfing the web.
Some nice graphs of unicode growth are at these locations are at these locations:
I think especially important are 2008 (when UTF-8 had outgrown all other individual encodings) and slightly after 2010, when UTF-8 alone covered more than 50% of the pages served. These exclude ASCII-only pages. Adding those would make the figures even larger.
Historical yearly trends in the usage statistics of character encodings for websites, June 2021
vSphere Integrated Containers Engine (VIC Engine) is a container runtime for vSphere, allowing developers familiar with Docker to develop in containers and deploy them alongside traditional VM-based workloads on vSphere clusters, and allowing for these workloads to be managed through the vSphere UI in a way familiar to existing vSphere admins.
Given my virtualisation infrastructure is ESXi based, I need to contemplate on this, as there are basically two choices for me:
Install a docker host as a VM on the ESXi host and go all the way docker (which needs a very good thought on how many resources to allocate to the docker host)
One of the most common upgrades for any Haswell (xx40) series ThinkPad is to replace the awful button-less touchpad (sometimes referred to as the ClunkPad) with a T450 touchpad that has the proper buttons for TrackPoint users. However, getting the buttons to work properly on xx40 hardware can be tricky – particularly if you are running Windows 10. In this video you will see how to get drivers installed that will allow you to use the TrackPoint as if this were a T450! As always thanks for watching! Some of the guides I used for this video:
I have edited the link so they show forum post titles, added way-back links, and added some crucial information:
PLEASE NOTE:
BEFORE YOU PUT IN THE NEW TOUCHPAD, INSTALL SOME EXTRA BUMPERS/RUBBERS ALONG THE TOP OF THE LID, LEFT AND RIGHT OF THE WEBCAM.
THESE SHOULD BE ABOUT TWICE AS THICK/HIGH AS THE SMALL BUMPERS THAT ARE THERE ALREADY.
Recommended size ~WxH: ~6 x 2 mm or ~1/4 x 5/64 inch.
PLACE THEM IMMEDIATELY LEFT AND RIGHT OF THE EXISTING BUMPERS.
FAILURE TO DO SO WILL RESULT IN SCRATCH MARKS ON THE SCREEN FROM THE NEW BUTTONS!