> I've followed some of the emails of the thread Google Wiki Usefulness. . .. > One big point was: How to protect against spammers? > ============= =======================================================
Actually, I found a really good reference on this today: * http://www.wikia.com/wiki/Help:Spam It echoes a lot of what you said. They combine blacklists, captchas, and simple iq tests to help block edits that are most likely to contain spam. It seems like a pretty good strategy to me if you're going to let anonymous users contribute to your wiki. > Vim community driven "own" system ? > ============= ======================================================= > Has anyone elaborated the pro cons of > a) using a dedicated server* and our own or adjusted system, funded by > vim community (* or something like that) Yes, and it wasn't well-received. > b) a free hosting like Google Wiki Problems with this wiki are the reason that we're looking for other possible solutions. > c) extend the already existing vim.org to support wiki like features? This hasn't gained much traction. > Do we already know what we really want/ need? > ============= ======================================================= > a) > I've read about some people fearing loosing initial authorship of tips > causing those authors to not mantain their tips any longer? I don't think that this will be a problem. > b) > On the other hand we need some pages gathering all the important nice > peaces of code shaping a a kind of cookbook having headlines... > ... > All I want to say is: I think there can be more benefits than copying > tips. Does my imagination match yours? I'm all in favor of refactoring the tips some day if we find a better design that the Vim community prefers. But in the mean time, let's move the stuff over and strive to achieve 100% data fidelity in the process.
