Lapsed_Lurker comments on Wiki Spam - Less Wrong

8 Post author: dbaupp 12 November 2011 12:26AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (15)

You are viewing a single comment's thread. Show more comments above.

Comment author: Vladimir_Nesov 12 November 2011 01:39:37AM 1 point [-]

I'm not seeing how that would be any different.

Comment author: gwern 12 November 2011 03:44:54PM 0 points [-]

Count the clicks for rollback vs delete, remembering to remove the page contents from the deletion log.

Comment author: Lapsed_Lurker 12 November 2011 07:30:54PM *  0 points [-]

Count the clicks for rollback vs delete, remembering to remove the page contents from the deletion log.

Why not add a one-click 'remove spam page and all contents and remove and permablock the creator' button/script? (assuming this is possible and relativity easy)

Even if all it does is divert spammers into adding links to existing pages, that's still easier on me and Vladimir.

Encouraging spammers to mess with actual pages people want to read rather than advertising their presence with obvious spam as they currently do doesn't seem good.

Comment author: gwern 12 November 2011 07:36:50PM 0 points [-]

Why not add a one-click 'remove spam page and all contents and remove and permablock the creator' button/script? (assuming this is possible and relativity easy)

It's not built-in functionality, and so not easy.

Encouraging spammers to mess with actual pages people want to read rather than advertising their presence with obvious spam as they currently do doesn't seem good.

It may break their bots/scripts when they can't create pages as they obviously default to doing; and when spammers edit pages, they tend to not replace the contents but add to them. Since the wiki isn't heavily trafficked, it's a tradeoff I'm willing to make.

Comment author: wedrifid 12 November 2011 10:21:27PM 0 points [-]

Why not add a one-click 'remove spam page and all contents and remove and permablock the creator' button/script? (assuming this is possible and relativity easy)

It's not built-in functionality, and so not easy.

That isn't something that is terribly difficult to implement even as a completely external script using nothing but the web interface.