> Also, I think it's a little ridiculous to have this be a closed thing (I can't simply register to the wiki). Shouldn't the barrier to entry be _lowered_?
It is necessary to guard against spambots that auto-register themselves and then destroy the value of the wiki.
Regards,
Malcolm
_______________________________________________
Haskell-Cafe mailing list
To (un)subscribe, modify options or view archives go to:
http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe
Only members subscribed via the mailman list are allowed to post.
As currently stands, too little people can even edit the wiki know,
those are humans! you know? :-D . Now in all seriousness, how do other
wikis handle this issue? I know wikipedia filter blocks of IP & records
who-did-who to see bad behaving actors, maybe this is too much for our
case? what does for example the archwiki in this regard? (I will ask
them)
-- Ruben
Manual work.
Such as manually checking Registration requests.
Talking from experience with my own blog, I can say that antispam
software catches 99.9% of spam but I still need to react to the
remaining 0.05% false positives and 0.05% false negatives. I need to do
that promptly, else the real comments will take too much time to appear,
frustrating the authors.
My workload is "once per month or less", but that's likely because my
blog is virtually unknown.
O the site I co-developed (software craftsmanship community site with 1500+ users) everybody can register themselves (with OpenID / OAuth providers), and to edit the wiki, one needs to be logged in. So people have instant access if they want, and we did not have a single spambot case so far.
Cheers,
Nicole