Main Area and Open Discussion > Living Room

Anti-Necrospamming

<< < (5/12) > >>

ewemoa:
As an experiment, I put together a Greasemonkey script to change the color of the reply date string if it's been more than 180 days.

It currently only works w/ dates that contain YYYY-MM-DD portions, but if there's interest, may be it can be appropriately modified ;)

Anti-Necrospamming


--- Code: Javascript ---// ==UserScript==// @name          Nemse// @namespace     http://ewemoa.dcmembers.com/greasemonkey/// @description   Script to provide visual indication of posts older than some amount// @include       https://www.donationcoder.com/forum/*// @include       https://www.donationcoder.com/forum/*// ==/UserScript== var now, then, gap, age, dateRe, xpExp, snapResults, i, elm, text, m;now = new Date();age = 180;dateRe = /(\d{4})-(\d{2})-(\d{2})/;xpExp = "//div[contains(@id, 'subject')]/following-sibling::*";snapResults = document.evaluate(xpExp, document, null, XPathResult.UNORDERED_NODE_SNAPSHOT_TYPE, null);for (i = snapResults.snapshotLength - 1; i >= 0; i -= 1) {  elm = snapResults.snapshotItem(i);  text = elm.textContent;  m = dateRe.exec(text);  if (m === null) {    continue;  }  then = new Date(m[1], (m[2] - 1), m[3]);  gap = (now - then) / 1000 / 60 / 60 / 24;  if (gap > age) {    elm.setAttribute("style", "color: red;");  }}// XXX//alert("It is currently: " + now.getFullYear() + "-" + (now.getMonth() + 1) + "-" + now.getDate());

J-Mac:
Above post (I think) caused a "Page Exception" error - I couldn't even get this page to render without creating an exception certificate. How come?

Jim

gjehle:
other
1) i agree with justice, after a certain amount of time a thread is dead it could require a captcha to revive it
2) reviving threads could be limited to people who already contributed to DC, eg have more than 10 or 20 regular posts.
in the case where a spammer just signed up he wont be able to revive, and if they're spamming on new threads their accounts get deleted anyway.

app103:
I don't think a captcha to post would make a difference if it's a human spammer that already got past the captcha to make an account on the forum, in the first place.

I don't think we have an issue with spambots reviving old threads. If anything, it's human spammers that are quite capable of passing a captcha test, clicking extra buttons, etc., so adding more hoops for humans to jump through in order to stop spammers would be pointless, as they can jump through the same hoops anyone else can.

Restricting posting on older threads only to members after a certain number of posts is also not such a good idea, as this would deter posting to an older thread by someone that actually has something valid to add that may have just discovered the forum.

The best we can probably do with regards to human spammers posting on old threads is to delete it when we catch it and ban the spammer.

But it might be easier to spot if there was a visual indicator to readers, like I explained before.

Another thing to keep in mind is how I detect spam on the forum is usually with popup cody. If I see something that is obvious spam, I click through and take action, usually before anyone else gets a chance to see it. And I am not the only one that uses this method and is removing spam. (that's why you don't see that much spam around here) There is nothing in the popup to indicate when the last post in the thread was, so I don't know when I see it that an old thread was just revived. I do have an indicator of when the thread was started, but that really isn't anything to go by on this forum because there are many threads that have had a long beautiful life and still going strong. (the note-taking thread, for example)

If you do see something you suspect is spam, report it. I check all the reports that hit my inbox and delete any obvious spam, and if I am not sure about it, I leave it to another mod to check or bring it to mouser's attention and ask him what he thinks.

All in all, this forum has very little in the way of a spam problem. And it has been kept well under control. You can read the RSS feed from here without seeing a million spam posts, unlike another forum I am a member of, in which their feed is so loaded with spam (about 90%) that I can't find the valid posts any more. I had to unsubscribe and go back to visiting that forum directly, in order to avoid the spam. (google reader caches the posts in the RSS feed and shows older stuff that was removed, which includes all the spam) DC's RSS feed is still very clean in google reader, which means we are doing a great job getting rid of it very quickly.

We are not being over-run by spammers, so relax. This isn't an urgent issue that needs drastic action that would inconvenience normal members.

ewemoa:
Above post (I think) caused a "Page Exception" error - I couldn't even get this page to render without creating an exception certificate. How come?
-J-Mac (March 29, 2009, 01:01 PM)
--- End quote ---

I think it may have to do with my using SSL / https to access DC when creating the post -- perhaps uploading the attachment under those conditions caused the link(s) to the image / thumbnail to be made available only via SSL / https.

Navigation

[0] Message Index

[#] Next page

[*] Previous page