Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Jacobo221]

aMule's Wiki will be down for some days for maintenance.

The recent continous spam attacks it's been suffering has forced the current situation were a software update has become of great urge.

Anyone looking for the info that could be found in the wiki will have to use either Google's cache feature or check through http://archive.org (though archive.org's copies are more than a year old, so in most cases, not very useful). Of course, you can ask someone in the aMule Team (contact through e-mail or through IRC at #amule in irc.freenode.net) to mail you the document/article/info you were looking for.

Before you ask, the date when the wiki will be back up again is undeterminated. Obviosuly, it will be as soon as possible. But we are very busy these days and it won't be up until we can assure the situation we've been suffering these past moths will not happen again.

WE ARE VERY SORRY FOR THE INCONVENIENCE.

Public request: Help/Recommendations/Guidelines from anyone who has had experience fighting against wiki spammers will be very much apreciated.

[lionel77]

What if we made registering mandatory for posting to the wiki? Wouldn't that elimate most of the spamming?
We already don't allow unregistered posting here on the forum, so why not handle the wiki in the same way?

[Kry]

Because it kinnda, hum, kills the wiki's feling.

[Vollstrecker]

How about something like a quarantine box. Registered users post and all is fine. Unregistered users post, and the post comes to a separate Area, where someone can commit or reject it. This can be admins, separate mods, or just anyone that is registerred. Of course should the commiter be, too, and in case commiting spam or incorrect posts you can talk to this person or in worst case forbid him to commit.
This could be done with one additional field in posts and user database. Something like post.commited_by and user.allowed_to_commit.

[Kry]

Again kills the whole wiki feeling.

[Jacobo221]

lionel77:

allowing only registered users to edit won't work. The last spam attack was done by two registered users and lots of non-registered ips. One of those two registered users spammed ~500 articles in 20 minutes.

[Jacobo221]

vollstrecker:

actually, what I see is that that would requiere a lot of admin time spent in maintaining the wiki. Specially when some registered user modified an article which an unregistered user had modified before and hadn't been yet accepted.

Anyway, back with what I said to lionel77: the las spam attack, which took over the whole wiki (all of it's articles, talk pages and special pages), was done by two registered users (and some unregistered IPs too. bu the registered users did more than half the job).

[lionel77]

OK, then nevermind my suggestion -- all I ever saw was unregistered spamming and since the wiki was already down I wasn't able to look at the more recent spam attacks.

Looking forward to the new wiki software.

[kreegee]

just require a captcha ( http://en.wikipedia.org/wiki/Captcha ) when posting an edit should do the  job. i'm shure there's a captcha-plugin for almost any wiki-system...


imho that doesn't kill the wiki-feeling, everybody can still change the wiki at runtime...

[phoenix]

Hum, good idea, a captcha looks promising...

[Jacobo221]

Thanks kreegee!

that's what MrFaber and I have been talking about this afternoon:

[19:51] There are so many wiki sites out there, there should be another option
[19:51] Very good would be a registration through numbers and chars on images so bots wouldn't work but this is more a job of wikimedia than of yours/ours
[...]
[20:03] like I said before and kreegee in forum http://en.wikipedia.org/wiki/Captcha would do the job, but I don't know if there is a plugin
[20:04] best would be everytime a catcha for edit from anoymous and only one time on registration
[20:05] i've seen wikis where you must do the "write down here the numbers on the image by the right to verify you are not a spammer" to be able to submit an edit
[20:05] that would be th best imho, but i don'ty think we have to time and even maybe the knowledge to do it
[...]
[20:06] ah, ye, a captcha. i didn't knwo that was the name
[20:07] yes. best would be: registered users do the captcah only on register. non-registered users, on every edit
[20:07] Jacobo221, I didn't know the name too that's why I tried to describe

let's see what deltahf has to say about it

[wuischke]

Sounds promising and should prevent things like 500 Edits in 20 Minutes...
I'm looking forward to it, even if I didn't write much in the wiki until now...

[kreegee]

Originally posted by Jacobo221
Thanks kreegee!

you're welcome

i'm shure theres some kind of implementation of this in mediawiki, other people MUST have done this before...

[Truzzone]

For MediaWiki I found this and this  

Best regards,

Truzzone  

[Jacobo221]

Hey Truzzone! The second link ( http://www.fxparlant.net/Category:Mediawiki#Captcha ) looks great (I hope it doesnt requiere to have wordpress or drupal installed though). The first one is good but doesn't block all edits, just some and what's worst, is confident on registered users. The second one looks like a better anti-TuringTest solution

I had actually seen that page when searching for captchas but didn't take much time reading it. Now that you linked to it, i took a closer look and looks quite good. Thanks alot for that link!!! It needs some changes IMHO, such as SysOps shouldn't have the catcha img and box (ok, it's not veryfied if you are a sysop, but it's better if it even isn't there ). But looks really good. It even is XHTML compliant hehe.

Thanks a lot really for that link