When upgrading to the new WinCustomize 2007, a lot of the underlying code changed, resulting in much faster connection speeds for most users. We optimized a lot of things, and the result was traffic took a very significant jump. To this end, the site upgrade was incredibly successful. However, that spike in traffic caused an increased load on our servers and exposed performance issues that simply didn't exist when we were getting less traffic. The WC Browser/SDC site connection issues are not trivial and are requiring a fair bit of development research and implementation time. A fix is coming, but we can't give any sort of timeline at the moment.
We were faced with two options:
1. Deactivate the browser hooks to WinCustomize
2. Let WC Browser/SDC users bring the entire site to a crawl
We chose the option that would leave the site available to everyone. Even if you prefer the browser, the content is still readily available to you via the web. If we had not deactivated the browser hooks, no one, not even WC browser users, would have been able to access the libraries.
This is a consequence of higher traffic and was not something we could guess at or adequately simulate. Mark it up to growing pains.