That plugin will give free licenses to Open Source projects (most plugins in the Atlassian ecosystem do)... As I've been doing a little dabbling with other Atlassian plugins, I'll look around for a page creation approval type of plugin.
We might want to reach out to codehaus, as I know they have quite a bit of spam in their wiki (https://docs.codehaus.org/) and it looks like they are not able to keep up with it. I think Apache might be someone else to reach out to. The cache generator layer might work too. With as fast as we remove the spam, you would think they would not have the incentive anymore, much like the recruiters on the mailing list have subsided once we started banning them. I think quite a bit of it is bot related. We have had lowered the number of spammers once we did the stopforumspam.com system, so it is better than it used to be. -- Larry On Mon, Nov 4, 2013 at 11:45 AM, Kohsuke Kawaguchi <[email protected]> wrote: > That plugin appears to be for pay and it doesn't look like it's about > hiding pages until edits are approved (which is what we need, but I'd > imagine tricky to do given how Confluence works.) I agree that selective > moderations would be ideal, but I'm more constrainted by my lack of > Confluence plugin development experience. > > Maybe we could do this in the static cache generator layer? If the page > appears a spam, the cache generator can generate a blank page, until we get > the author whitelisted (by adding him to a designated group in LDAP) It'd > still leave spam pages inside Confluence until they are manually cleaned > up, but if pages aren't visible, it'd hopefully reduce incentive for > spamming. > > I'm curious how other OSS communities deal with spams on WIki. > > > 2013/11/4 Larry Shatzer, Jr. <[email protected]> > > I've been wondering if we get something like >> https://marketplace.atlassian.com/plugins/com.comalatech.workflow to >> then have a larger group of people approve changes on the wiki, or at least >> new pages. To have them go through a review before being made public. (That >> might need a newer version of Confluence though). Another similar option is >> to somehow moderate the changes/page additions until they are deemed to be >> human, and then no moderation queue. >> >> There seems to be some "themes" to the spam pages, and to maybe collect >> those into a ban list for pages containing (I doubt any plugin or >> legitimate page would have information on Indonesian furniture, or pirated >> movies)... >> >> >> On Mon, Nov 4, 2013 at 9:03 AM, Kohsuke Kawaguchi <[email protected]> wrote: >> >>> Mainly to Larry, >>> >>> Over the weekend, I've noticed that there is a wave of ongoing spam >>> attack. I've deleted some pages and banned accounts, and I saw this morning >>> that you've deleted some pages too. Thank you very much for doing it. >>> >>> In fighting this wave, I've improved a bit on the tooling. If you >>> haven't been using it, check out >>> https://github.com/jenkinsci/backend-confluence-spam-remover and it'd >>> be great if you can also help us grow this tool. For example, once we >>> identify a spam, it'd make a lot of sense to delete all posts and pages >>> created by the user, and it'd be nice to roll back changes he made. >>> >>> I'm also trying to improve the account app to help us fight with spam >>> attacks. Some of the ideas include: >>> >>> * force some time between the registration to the activation to prevent >>> spammers from getting new accounts quickly. >>> * monitor IP addresses from which the sign-up is happening >>> >>> Any other suggestions welcome. >>> >>> -- >>> Kohsuke Kawaguchi >>> >> >> > > > -- > Kohsuke Kawaguchi > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
