On Friday, February 21, 2014 9:40:56 AM UTC-5, kcrisman wrote: > > > > On Friday, February 21, 2014 9:11:33 AM UTC-5, Niles Johnson wrote: >> >> Now that I've spent a little time thinking about this, here are some >> comments: >> >> * I misread our version of askbot -- it's over 2 years old >> >> > True. > > > >> * recent versions of askbot (6 months ago or so) can put a captcha on >> users' first posts >> >> * some of the spam is posted as "Anonymous" -- but that still requires a >> login; I'd like to know which openID provider the spammer is using >> >> * there is a blockip branch on the askbot repository, but it's pretty old >> and looks like it didn't get finished >> https://github.com/ASKBOT/askbot-devel/pull/81 >> > > What do you suggest for right now? I can't find any setting that is > relevant, can't delete all posts with a certain tag or from a user (you can > block the user but the posts remain) - someone with access to the actual > machine will have to start looking at IPs or something... >
If we were evil, we could do DoS to the email and phone # in question. But we are, fortunately, not evil - perhaps unlike our mystery spammer. Does someone have access to the actual database? I suppose it could be done at that really low level too. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
