Quote from: MisterWil on March 08, 2014, 08:36:12 PM

Quote from: GalacticMiningCorp on March 08, 2014, 07:35:57 PM

Quote from: ClemsonBTC on March 08, 2014, 07:17:30 PM

Eh.. How does that work? My one IP refreshing every couple of minutes enables DDoS protection? Wouldn't miners trip it too everytime they sent/received data, they have to be sending connections far more often than this stats thing?

I'm not sure what PW's back end infrastructure is like but MrWil is aggregating data through PW's web endpoint. If, for example, MrWil's processes are hitting PW's API for 1,000 users, ranging from 1 min to 5 mins each, that's several thousand requests a minute at least to that endpoint. This could definitely look like a DDOS attack to monitoring software.

The mining data is most likely set up a different way. This is an educated guess at best.

Ideally, PW would be setting up rate limiting for the API for general use, and maybe white-listed IP addresses for more intensive services like MrWil's with some kind of rev-share or other agreement in place for the service.

You got it, I think. It's actually closer to ~4000 people every 1-5 minutes. The connections from my servers are being ended immediately and not just timing out like stale DNS records. I'm also personally seeing intermittent data points pop up. I'm almost positive that it's due to the new DDOS protection that's in place. I sent poolwaffle the IP's of the two servers that will be connecting to the API in the hopes that he can white-list them.

Whitelisted, Ideally within the hour, everything should be going through fine from the stats pages