Skip to main content

Firefox 3.0, three out of eight million

Oh, the pangs of providing very popular software and challenging its users to download it as many times as possible.  Such is the situation with Mozilla and the rollout of its Firefox 3.0.

With the costs associated with bandwidth consumption being a consideration for sites that provide downloads, and especially so for those that provide popular content and software, it's amazing that such a challenge was even considered—let alone publicized.  Regardless, the point is moot since Mozilla seems unable to keep up with the demand spawned by the company's invitation anyway.

While I acknowledge and credit the organization with being able to keep up with the traffic it has by 11:00 AM EDT, my repeated attempts to download the browser have all ended in futility.  On some discussions I've read here and there users are reporting both success and failure.  Mine has been a case of repeated failure, as the closest I've come so far has been to fully load the main page at www.mozilla.com.

I'm going to keep trying, but it should serve as a lesson that challenges to download things will certainly be accepted.

About 2:15 PM EDT

Alas, I was able to successfully download and install Firefox 3.0 on both a Windows and Mac machine from work.  One more to go at home….

About 11:55 PM EDT

My download of Firefox 3.0 for Mac OS X was immediate and I had it on the system and running before midnight.  Now, after all that and despite all the hype, I doubt it will replace my hybrid Camino/Safari usage.  Just the same however, I can be counted as three of the eight million downloads in the first day!
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more