Auto-Update VAC banned DB

[Jamyn]

I have a database of 1.5 million VAC banned accounts. I wouldn't mind walking the SR database to document the ~ 10k SR banned accounts. It may be beneficial to ship (and update w/the auto-updater) a list of SR and VAC banned accounts. That would save a huge amount of traffic to steamrep.org and still provide protectino for known-bad accounts. We'd just need an expiration date for our local cached records - say 4-12 hours.

Because some SR bans are (infrequently) reversed, I presume we can only cache that for a day or two. Still, one query per client every two days would reduce a lot of load. So maybe we can do something like:

// SR banlist // version: 1.2.3.4 // updated:

: : [...] ... that way we can re-query old (>24 hours) bans, but save a lot of traffic in general. And most of the traffic will be to our list, which we can serve up as a compressed text file. Low traffic, high speed, and we keep core traffic away from steamrep.org.

[ghost]

Not bad actually! Thats pretty cool. How'd you get a DB of it to begin with?

On Sat, Mar 23, 2013 at 3:14 AM, Jamyn notifications@github.com wrote:

I have a database of 1.5 million VAC banned accounts. I wouldn't mind walking the SR database to document the ~ 10k SR banned accounts. It may be beneficial to ship (and update w/the auto-updater) a list of SR and VAC banned accounts. That would save a huge amount of traffic for known-bad accounts.

Because some SR bans are (infrequently) reversed, I presume we can only cache that for a day or two. Still, one query per client every two days would reduce a lot of load. So maybe we can do something like: SR banlist version: 1.2.3.4 date:

: :

... that way we can re-query old (>24 hours) bans, but save a lot of traffic in general. And most of the traffic will be to our list, which we can serve up as a compressed text file. Low traffic, high speed, and we keep core traffic away from steamrep.org.

— Reply to this email directly or view it on GitHubhttps://github.com/waylaidwanderer/Mist/issues/19 .

[Jamyn]

I wrote a quick server/client pair of scripts to simplify the process. The server kept track of what was already checked, and offered small sets of randomized IDs (say, 10,000 at a time) to the client scripts. I then ran 4-5 client scripts from different machines that queried ~ 5-10 accounts at a time and then submitted the data back to the controller at the end of each batch.

I eventually found http://www.vacbanned.com/ and slurped in their data as well. I'm not currently running my client/server setup, but I could easily do so if we want the data.