coolasacuke

Folks may have noticed that the site has been slow for logged-out users over the last while. This is partly because we separate traffic by logged-in, "logged out but have visited the site before", and "logged out, never visited the site before" and assign the fewest resources to the last category (because we're pretty confident the overwhelming majority of it is bot and scraper traffic, even if it's often impossible to say for sure). The flood of garbage traffic is a plague and a scourge the entire internet is dealing with, and it's hitting small sites the hardest as operators get better and better at cloaking their requests to look like real, authentic use. We long ago hit the point where adding more resources is a possible solution (because they just eat them up as soon as we do), and splitting traffic lets us keep the site usable for our actual users without wasting too much server power on garbage.

We've now, lucky us, reached the point where the "logged out, have never visited the site before" path is just flooded all the time, and the "logged out but have visited the site before" path is suffering some of the overflow. We've made some changes to the routing to try to improve things for logged out users who have visited the site before and keep it at "it may be a little bit slow, but at least it works" instead of "it keeps timing out", and we've seen some improvements, but if you're accustomed to browsing the site while logged out, I'm really sorry but it may continue to be a little miserable.

You will get the fastest page loads and the best performance by browsing the site logged in. If you are having trouble loading the front page to log in, bookmark the direct login page. We can't route the front page to the "more power" server pool, because it's a common target for garbage traffic, but we've switched /login over to "more power" and we'll try to keep it there as long as we can unless it starts getting slammed, too.