Not anymore...

Maybe he was mostly to determine how bad the spam problem was rather than part of the solution. Seeing as he was getting overwhelmed says he wasn't using SQL to do things quickly and powerfully in bulk. Really, a well done single line of SQL could deal with most of the spam using only usernames, that could be incorporated in the admin's pages that would prevent accidental deletion of the whole DB.

We'll have to see in a few hours when they get back online if they have a solution or not.

Wouldn't it be easier, if only accounts that bought at least one game were able to post?
I mean... this is a shop, right?

NORTH KOREANS ARE HERE.

Long live Dear Leader and the Eternal President!!

Well, as said before, there are people who want to inform theirselves about gog and the games on gog in the forums before they buy their first game.
It would be very unfriendly to those people to force them to buy a game before they can post here. Gog is all about being an open community, it`s not Steam which wants to milk every cent out of the people!

Kill, Krash And Destroy the spammers.

Warning: There's a legit thread amidst the spam in NWN too.
Same problem in TW2, be careful.

I`ve seen it.. ups! Well, de-marked it in the last second!!!

Be sure to check the thread and upvote the first post on the last page if it has been downvoted by the script.

I didn`t downvote it, I scratched the curve in the last second!

Minor script update, this is for "select individually":

http://pastebin.com/au9ii1na

This is for occasions where there are not enough spam threads for the "select all" script, but many threads by a single bot account (like this morning). Clicking the "B" (Bot) button will mark all threads by that user. Clicking the "U" (User) button will unmark all threads by this user. Rest of functions is the same.

Right now it's not that useful, because the "new account, new spam thread in every subforum" bots are the majority.

This misses, deliberately or not, part of what Ciris has been saying. It isn't just one blue text clearing threads for an hour or two; they have several programmers working on a long term fix. One that won't slap certain kinds of people in the face (like any one one posting something in Korean that is legit).

----------
Untargeted mini-rant:
GoG doesn't post feedback: people complain. GoG posts feedback: people complain. GoG isn't perfect: people complain.

----------
Edit: Sectioning off the mini-rant. The forum combined these two replies posts.

How? What kind of SQL fix is that fast and simple without inhibiting existing/potential customers.

Status: FO and NWN have slowly ongoing spam. NWN has a few old spam threads too - if someone would be so nice as to give them some treatment...

Well if we make assumptions based on the current DB, it will probably be...

[code]
DB games {
int gameID;
int userID;
}

DB user {
int userID;
char[] name;
char[] image;
int ranking;
DATE joined;
int state; //banned, locked, normal, Employee, etc
}

DB forumEntry {
int userID;
char[] title;
char[] message;
DATE date;
}
[/code]

That would be the basic structure that handles most of the data. There's probably a bit more to determine which ones you've read or what you've up/down voted, but that's not important.

If the username is unique, then we use that, if not we use the userID which is guaranteed to be unique. Depends on how they implemented it, regardless.. the SQL is probably incomplete/incorrect but this is off the top of my head.

//known spammer name
update USER u where u.name == "$spammerName" SET u.state = u.state | BANNED;

A few others could be added to work automatically, based on the date joining within 1 day, having an empty new topic, having the title include certain characters always used by the spammers, etc...

//bulk based on contents and date
update USER u where u.joined <= DATE(??,??,??) AND ForumEntry.title contains "[characters]" SET u.state = u.state | BANNED;

or with large numbers of entries being done very quickly....

//date set within 15 minutes say....
update USER u where u.joined <= DATE(??,??,??) AND count(ForumEntry.userID) > 10 SET u.state = u.state | BANNED;

Naturally to remove all entries by a known spammer....

UPDATE FourmEntry f where f.userID == "$spammerID" set STATE = HIDDEN; //hidden, spam, or whatever they are using.

If there's a topic owner setting somewhere and it equals the spammer's id, those are removed in place of or as well.

Just assert $spammerID isn't empty, perhaps using SELECT first as a test to see what it would remove/update first to ensure it doesn't randomly remove everything or an empty entry makes itself present. Adding in a "$spammerID" != "" would probably work as it's always 0 or 1, which works or doesn't...

They probably don't have SQL but store the threads in txt files...


;-)