Kevin Clark wrote:
If we're getting such persistance from this ip can we just ban it? If
the wiki is using the i2 code, I'd be happy to code up a patch to
allow it.
Blocking IP addresses should be straightforward at the Web server level.
AFAIK the Wiki *is* running on i2 - can you tell me where to find the
code? The "i2" link on the pages just points to the Instiki site.
If you want to look at a patch for i2, I suggest the following:
When a page change is submitted, look at the diff between this and the
previous version (if this is a create, just looks at the submitted
content). Focus on what has been added, and count the number of URLs to
external sites. If this is over some configurable number, reject the change.
The pages that have large numbers of legitimate links accumulate them
slowly, so wouldn't be hit by this.
Doing the diff is important - otherwise a spammer could replace the
content of (e.g.) the RealWorldUsage page with a similar number of spam
links without being blocked.
This wouldn't protect against other kinds of malicious change, but would
bring the frequency of changes down to a point where people could deal
with it.
One further suggestion - the Recently Revised list should include the IP
address of the originator of the change.
regards
Justin
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core
