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. Kev
On 1/19/06, Justin Forder <[EMAIL PROTECTED]> wrote: > Justin Forder wrote: > > > I've modified the Watir-based > > solution to work from the Recently Revised list, back to the time I last > > ran it... running it earlier today found 40 newly-spammed pages (and > > they are starting to impersonate my spam-eater - or maybe they just copy > > the previous updater's name) > > > > While the pages were flashing by on Watir I saw some spam that didn't > > match the patterns I'd picked up, so I am pressing on with something I > > had on my to do list - counting the URLs in each page. I'll use this to > > look for new signatures. (Just got those results into a spreadsheet.) > > A new signature from yesterday: > > <u style="display:none;"> > ... > </u> > > sometimes with no semicolon after 'none' > > 37 pages affected. > > > > > One spammer is still operating from 82.131.14.155 (34 changes yesterday). > > He's back on line right now. My last run will have removed some of his > changes. > > regards > > Justin > _______________________________________________ > Rails-core mailing list > [email protected] > http://lists.rubyonrails.org/mailman/listinfo/rails-core > _______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
