If we have a wiki and want to prevent spam, I think the best solution is to assign long random individual passwords personally. Spammers actually will fill out captchas, research Python questions, actually will join groups and ask "what's the password?"; The gall I have seen from spammers of wiki is extraordinary.
Background: I hosted 20 wikis at a time once, and have been involved in many wiki. I've attended and helped conduct many wiki conferences. On Thu, May 2, 2013 at 7:51 AM, Chris Barker - NOAA Federal < [email protected]> wrote: > One nice thing about a wiki is that barrier to r try is really low for new > folks adding content. > > Of course, that's why they are so easy to spam, too. > > Is there really no system that works ok for spam. Management ? > - captcha > - answer a question any pythonista should know? > > It seems some people do manage to keep wikis up... > > But if all the content is generated but only a couple core folks anyway, > then no big deal. > > And we could be more pythonic and use Sphinx to generate the site. > > One other note: github does have a wiki, so we could use that for the > pages we want it to be particularly easy to update: proposed meeting > topics, that sort of thing. > > -CHB > > On May 1, 2013, at 9:38 PM, Mike Orr <[email protected]> wrote: > > The wiki is still down, partly because I forgot about it. The server > problems ceased when the wiki was turned off, so I'm not inclined to turn > it on again. I'll put up a static page with the next meeting info... as > soon as we decide on a next meeting. > > I like Kevin's idea of some kind of version-control based, github-ish > website to replace MoinMoin. We should have a Github account anyway to > encourage more SeaPIG projects. However, I don't know enough about Github > webhosting to know whether we want to commit our website to a third-party > service which may limit what we can effectively do with it. I'm also not > sure if I like its Markdown-based format. Markdown *is* becoming more and > more widely used (a commercial publisher has even standardized on it), and > I guess its syntax is the best of the wiki syntaxes and allows direct HTML > snippets. So maybe it would be OK. > > It's ironic because a version-controlled content with some kind of script > that converts it to a static HTML site is precisely what Linux Gazette > used. We resisted a CMS until the end (it was the early 2000s after all), > but now that several years have passed since its demise and newer paradigms > have flourished on the Web, several of LG's former editors think that if it > were (re)started now they'd go the CMS route. And I have been exploring > Kotti and it's got a lot of neat things, even if it's not fully polished > yet. But for the SeaPIG's site simple needs, I can see version-controlled > content with a static HTML converter as being sufficient. If it allowed > attachments, which we'd need for uploading slides and things. Maybe we can > talk about it at the next meeting. > > In the meantime, would somebody care to design a static home page with a > place for the next meeting info and a link to the mailing list? > > The Mailman list is running fine so it's not as urgent to replace, but it > will be an issue when I upgrade the OS. (Ubuntu 13.04 is not yet supported > on Linode, so it won't be right away.) I still like the idea of migrating > to Google Groups at some point. > > The $240 server bill has been paid so I'm still looking for donations to > help offset it. Not tax-deductibe, bla bla bla. > > -- > Mike Orr <[email protected]> > >
