Please log in. To create a new account, enter the name and password you want to use.
If you supplied an email address when you signed up or added a email later, you can have your password reset.
This user name doesn't exist. If you want to create a new account, just verify your password and log in.
This user name exists. If you want to create a new account, please choose a different name.
Enter the current email address you have registered in your profile. You'll get an email containing your new password.
You have no email address in your profile, so you can't have your password reset.
Password reset. Check your email in a few minutes
That account does not exist.
The email address specified is not registered with this account.
Delivery to this email address has failed.
In the middle of downloading a large Pool archive normally with Firefox 11 and not much else, I seem to have run into the limiting again (503 Service Temporarily Unavailable on the actual zip link), but if I triggered it myself by just downloading a single Pool while browsing the other Pools and the forums, something is wrong.
What I think is occurring is that you may be limiting CloudFlare IPs which are shared by all users. As soon as I bypassed CloudFlare, the problem went away, but I'll need to test more to see if that's temporary or not.
The only way I could see running into limiting, is the 10 requests a second, which seems extremely low for a site like this. Doing a test just now with CloudFlare bypassed, I was able to trigger this limit when just checking if images on a page existed on my HDD (I do this often so I don't waste bandwidth), without downloading anything, which I doubt was the intention.
Is there really a need to limit the requests at all? Why not just limit the total connections for original image downloads back to 4, like it was in the past? Though I suspect that would require you to figure out how to have different limiting for browsing, thumbnails, samples, zips, and original image downloads on your single server?
As far as the insane amount of bandwidth being using, assuming it's higher than before, I suspect at least part of it is only temporary and a result of changing all the image name prefixes from moe to yand.re. I remember a similar situation in the past when you changed to the image names from the MD5 to moe+tags, yet both the site and number of users were an order of magnitude smaller during that time.
Fortunately, unlike back then which required you to dump the entire DB so images could be renamed in bulk, I would hope people would be smart enough to figure out how to do a simple bulk rename of moe to yande.re, but maybe not. If this is the case, I'd suspect bandwidth would stabilize to something lower in a few months, once those users have re-grabbed the images they wanted.
Update: I've also been seeing intermittent problems where the site doesn't respond at all (usually on first visit). It gets stuck on 'Waiting for yande.re'.
Cyberbeing
What I think is occurring is that you may be limiting CloudFlare IPs which are shared by all users. As soon as I bypassed CloudFlare, the problem went away, but I'll need to test more to see if that's temporary or not.
The only way I could see running into limiting, is the 10 requests a second, which seems extremely low for a site like this. Doing a test just now with CloudFlare bypassed, I was able to trigger this limit when just checking if images on a page existed on my HDD (I do this often so I don't waste bandwidth), without downloading anything, which I doubt was the intention.
Is there really a need to limit the requests at all? Why not just limit the total connections for original image downloads back to 4, like it was in the past? Though I suspect that would require you to figure out how to have different limiting for browsing, thumbnails, samples, zips, and original image downloads on your single server?
As far as the insane amount of bandwidth being using, assuming it's higher than before, I suspect at least part of it is only temporary and a result of changing all the image name prefixes from moe to yand.re. I remember a similar situation in the past when you changed to the image names from the MD5 to moe+tags, yet both the site and number of users were an order of magnitude smaller during that time.
Fortunately, unlike back then which required you to dump the entire DB so images could be renamed in bulk, I would hope people would be smart enough to figure out how to do a simple bulk rename of moe to yande.re, but maybe not. If this is the case, I'd suspect bandwidth would stabilize to something lower in a few months, once those users have re-grabbed the images they wanted.
Update: I've also been seeing intermittent problems where the site doesn't respond at all (usually on first visit). It gets stuck on 'Waiting for yande.re'.