Search suddenly takes forever

[chaostastic]

For whatever reason searches never get to a result page and keeps spinning forever. This happened suddenly for no apparent reason and stays. Searches work fine at piratebay clone sites.

I have no problems otherwise, going to a member page works as does loading torrent pages form there and magnet files works as usual. I can of course use google with the "site:" limiter, but what could be going on here?

It's the same in any of my browsers.

[KatSucks]

I haven't seen an issue recently. Are you using some sort of proxy or other method of viewing the site or is it a direct connection?

[Average Joe]

I haven't seen an issue recently. Are you using some sort of proxy or other method of viewing the site or is it a direct connection?

That, or an external or third party software might be interferring with the connecting, or weakening it. (Tor, Antiviruses, Firewalls); it varies, but it's not always the case.

It could also be (if not a proxy), but your direct connection that could be causing it.
But as they say, the more information; the more that people can help you.

[chaostastic]

I haven't seen an issue recently. Are you using some sort of proxy or other method of viewing the site or is it a direct connection?

Proxy. Fast enough to watch full bandwidth netcasts without interruptions or breakup. Seriously, I don't even notice when I'm using the proxy. There's no performance difference. Other sites, as I mentioned, works as fast as expected. Only thepiratebay.se times out.

I do have javascript turned off for thepiratebay.se. This has not been an issue in the past.

---

I do have javascript turned off for thepiratebay.se. This has not been an issue in the past.

It was javascript. So I'll turn it on and hack it so it loads the page and then stops whatever it's doing. Obviously that is something I don't want done.

A suggestion is to not make javascript a requirement. It's just stupid.

---

It seems the issue is more complicated than javascript on or not, as I still have issues in Google Chrome, but not in Chromium. I'll see what I can find.