Being very much affiliated with the service, I will not comment at the suggestion, at least for now.
I strongly encourage everyone to read my blog post and spread the word about moving to the new engine. Changeswith the new URLs are also in the pipeline for NuGet 2/3 clients and related docs, but there we need some love from the maintainers.
The current SymbolSource website is integrated with the old engine, and in a very bad state indeed. I can only (once again) apologize for the situation. We are currently running SymbolSource as a side project and there is only a limited number of hours in a day (and night...).
There are a few areas holding us back at the moment: migrating private repositories to the new engine and finishing up some integrations, so that we don't loose any major features when migrating.