Sounds like a plan to me. And I can do some spelunking around to see what (if any) plugins might be available for CS to combat this from the other end (unless someone else knows of one they can recommend that can save some googling).
Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Fri, Jul 8, 2011 at 11:44 AM, John Davidson <[email protected]> wrote: > We have spam in the body and also in the comments. Any plugin would be > welcomed if we can install it in our hosted environment. I will look this > weekend to see if we can set edit of a blog entry to the owner or admins > only. > > John Davidson > > > On Fri, Jul 8, 2011 at 11:36 AM, Stephen Bohlen <[email protected]> wrote: > >> Question for clarification: are we talking about spam that actually >> appears in the content of the wiki posting itself (which I honestly don't >> think I've seen much of) or are we talking about *comments* on blog posts >> (which in my experience seems to be the primary venue for the >> nhforge.orgspam I've seen thus far)? >> >> It does seem to me that wiki edit perms are probably orthogonal to the >> spam-in-comments issues that are the cause of most spam I've seen thus far. >> Sadly, spam-in-comments is something that bedevils all environments that >> permit comments :( I'll assume that there are spam-detector-plugins for >> Community Server just as there are for other CMSes that support commenting >> systems (WordPress, etc.). I'm not a CS expert myself -- does anyone >> perhaps know of any such things for CS that we might be able to plug in here >> in a way that wouldn't require onerous management effort on the part of the >> nhforge.org maintainers? >> >> >> Steve Bohlen >> [email protected] >> http://blog.unhandled-exceptions.com >> http://twitter.com/sbohlen >> >> >> On Fri, Jul 8, 2011 at 11:17 AM, John Davidson <[email protected]>wrote: >> >>> Community Server uses a Wiki which NHForge repurposes as a Blog. It is >>> open for any registered user to enter or revise data as any wiki is. We >>> could manage all requests for user accounts, but if you do, you can expect >>> that only the most determined of new users would every create a blog entry >>> in NHForge as the barrier for entry becomes too high. >>> >>> Also any registered user can create a comment on a Wiki entry. This is >>> where the majority of spam is. >>> >>> >>> Community Server can use a restricted list, but if we do then it will >>> become useless as a blog entry tool, as the user will need to be entered as >>> an editor by an administrator. >>> >>> So it is possible to control who becomes a registered user, or who >>> becomes an editor, but it is not very desirable to do so as it will require >>> multiple administrators to keep up with valid requests and it becomes >>> difficult to easily screen these anyway. >>> >>> John Davidson >>> >>> >>> On Fri, Jul 8, 2011 at 11:06 AM, Gabriel Schenker >>> <[email protected]>wrote: >>> >>>> I'd vote for restricting the group of users who can edit the wiki. Only >>>> on request a user is added to the group of editors. The moment such an >>>> editor abuses its rights he/she is banned >>>> >>>> >>>> On Fri, Jul 8, 2011 at 9:57 AM, Diego Mijelshon <[email protected] >>>> > wrote: >>>> >>>>> That's not correct. You can have a list of people allowed to edit the >>>>> wiki. >>>>> That is how all wikis work, including Wikipedia (even if that one >>>>> defaults to allowing everyone) >>>>> Now, if, the software we're using does not support that, it's a >>>>> different problem... >>>>> >>>>> Diego >>>>> >>>>> >>>>> >>>>> On Fri, Jul 8, 2011 at 11:47, Fabio Maulo <[email protected]>wrote: >>>>> >>>>>> On Fri, Jul 8, 2011 at 11:38 AM, Diego Mijelshon < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> A Wiki does not have to be editable for everyone... >>>>>>> >>>>>>> Diego >>>>>>> >>>>>>> >>>>>> That is a blogpost not a WIKI. >>>>>> >>>>>> -- >>>>>> Fabio Maulo >>>>>> >>>>>> >>>>> >>>> >>> >> >
