Originally posted on digitaltrends.
According to ZDNet, as both browsers prepare to launch the 100th version of their desktop browsers, it could create a situation where most websites fail to load on the new versions. That’s all due to an upcoming Y2K-type coding issue.
For younger readers, Y2K was a software problem in the late 1990s. Most computer programs at the time couldn’t properly read four-digit year dates, and the transition to the year 2000 caused some of these programs to work improperly.
This quirk of software development quickly gained traction in conspiracy circles, which proclaimed that the bug would create a global catastrophe. Fortunately, that didn’t happen. While some countries certainly had issues, most began preparing years in advance.
The issue with the 100th version of browsers comes down to something called a “user-agent,” a string of code that tells servers what browser is being used. Most website programs can only read double-digit UAs. Late in the first decade of this century, websites ran into a similar issue when the first double-digit UAs were introduced. That resulted in a lot of sites not loading properly, or at all.
Google and Firefox are working ahead to make sure most sites don’t encounter any issues. However, there are simply too many websites for Google and Firefox to handle the problem on their own.
Google is already offering instructions on how to make your site read three-digit UA strings. If you run a website, you may want to put in the legwork now to ensure your site is compatible with the newest version of Chrome.
Firefox and Chrome are the two most popular desktop browsers, and as of now this issue is limited to them. Other browsers are a long ways off from version 100, so they should run fine for the foreseeable future. That includes DuckDuckGo’s upcoming privacy browser.
It shouldn’t be anything world-ending, but being prepared in advance for issues like this will keep your site up and running while others run into problems.