On Wed, Mar 12, 2008 at 08:31:02PM +0100, Paul de Weerd wrote: > On Wed, Mar 12, 2008 at 10:50:35AM -0700, Unix Fan wrote: > | If you port it, or someone else does... don't make the same mistake > | as the current firefox 2 port... add recursive/async DNS resolution to > | the port instead of all those damn current DNS locks. > > That's not a problem in firefox.
But it becomes one when you remove SafeBrowsing... I'll explain: 1) you notice that firefox has a permanent HTTPS connection to google 2) you discover that google SafeBrowsing is bundled with firefox 3) you search how to deactivate it in firefox config UI... 4) you look what fucking config variables can be tweaked in about:config. browser.safebrowsing.enabled seams to be what you search for 5) your javascript console starts to be polluted with SafeBrowsing errors 6) you recompile firefox with ./configure --disable-safe-browsing 7) and now... when you type an invalid URL, you have to wait ~60seconds before any URL resolves...
