On 5/17/06, Jeff Dik <s450r1@xxxxxxxxx> wrote:
Wow, Rannotate look great! I think people would love it. However I
fear that in order to use it on a highly visible ruby website, it
might need some kind of spam rollback features.
Implementing Bad Behaviour would go a long way to protecting the site:
http://www.ioerror.us/software/bad-behavior/
I recommend:
* bad behaviour
* logins
* email authentication
* captcha on the first 'x' edits (possibly unnecessary)
* regular expression banning. Each page-save checks against this regex.
* link banning (banning specific sites) via a spam blacklist list of some kind.
* IP/range/username banning
* page-locking, to make only administrators able to edit it.
* talk pages per article, so that discussion can get tucked away
somewhere else, especially when a page is locked.
I disagree with some things.
* I post more than once a minute, regularly. Sometimes I go back and
make one little change five seconds later.
* Captcha has plenty of workarounds and is annoying for regular
people. I hate it.
* Creating *yet another* user is annoying.. but most people will be ok
with it if they're serious. Is it possible to leverage something like
rubyforge logins?
* A lot of this feels just like a wiki. Why not just leverage a wiki?
(with a sane markup language and NoFiNgCamelCase)
--+
Right now I'm too involved with learning the programming to do much,
otherwise I'd be spending lots of time with documentation. I learn
through programming and reading code/examples.. programming
documentation is awful awful stuff.
My goal once I'm useful is to work on documentation systems and
human-readable documentation, so I'm interested in getting the ruby
documentation resources ready for me. ;)
|
