So indeed, the forum's image proxy is affected.
Yeah, now the imageproxy is under a DDoS. (You may still see some images due to caching in your browser.)
I'm
not going to try to fix this. It's really difficult to put a
proxy behind DDoS protection, because the attacker can always find and take down the outbound IP. Even if the outbound IP is different from the inbound IP, and even if the outbound IP drops all incoming connections from the general Internet, the outbound IP's networking can be entirely taken down through a sufficiently-large IP flood, which makes the proxy stop working. Maybe it could theoretically be fixed by having dozens of outbound IPs, or downloading images via Tor, but the former would be difficult to set up and maintain, and the latter would degrade performance. So my intention has always been that the imageproxy would just be expendable in the event of a DDoS. My plan is as follows:
First, I'm just going to wait a few days. Often DDoS attacks are temporary. I'm not really sure what motivates them, but it costs money to keep them up, so they rarely last all that long. (I have a bit of a conspiracy theory that these random DDoS attacks are done by DDoS protection companies to make the Internet impossible to use without being behind DDoS protection...)
If the attack is still going on in a few days, I'll consider measures like these:
- If there are any image hosts run by trustworthy companies where the privacy policy says that they don't keep logs, these could be exempted from the proxy. If you know of any, let me know.
- Maybe bitcointalk.org could pay TalkImg a monthly fee for a contractual guarantee that they won't keep logs. TalkImg could then be exempted from the proxy, and furthermore they would have more resources to function well.
- Bitcointalk.org could add support for uploading images directly.