[Amps]

The Bantionary needs to go.

It's become a spampocalypse. The database is currently 1.48GB of pure unrelenting glorious spam, to put that in perspective, our forum with all it's accumulated posts is still a mere 30mb, and it's reached the stage where it would be quicker to recreate it than fix it.

I propose we post the pages you think are worth saving here, in code tags, and rebuild that fizzbitch.

[Hamwise]

I agree with this. I knew there was something funny about our database sizes when I was browsing our server's directories.

A Wiki is too insecure, and too big, for us to patrol meaningfully. We need an alternative.

How about a CMS (content management system)? Sitellite was a company favourite when I worked for that web development firm. It is a lean, powerful and open-source CMS tool, with a good admin panel.

http://www.sitellite.org/

[Starky]

Is it not possible to disable the discussion pages?

[Amps]

Disabling them won't remove the massive amount of spam, or the automatic version changelogs, or the plethora of orphaned attachements looking desperately for a home etc. It's simpler to remove.

As for that CMS Hamwise, it's worth a try.

[smr]

I think we could just lock down the whole thing, only allowing user edits but really what needs to be done first is that the entire database needs scrubbed. It's full of junk. Once you get rid of that I think there's no problem just restarting it with MediaWiki and tighter permissions. The appeal of having a wiki is that people can edit dynamic pages, whereas the appeal of a CMS is to streamline the process of putting the content up in the first place.

I wonder if /office may fill a gap here - we want to let people collaboratively edit pages and it's spam free.

Little Bobby Tables, your time has come.

[Amps]

Speaking of which, can you create an office account for me? I've yet to test that baby out. As opposed to the many other babies which I've tested to exhaustion. Yes, I went there.

Edit:

I think we could just lock down the whole thing, only allowing user edits but really what needs to be done first is that the entire database needs scrubbed. It's full of junk. Once you get rid of that I think there's no problem just restarting it with MediaWiki and tighter permissions. The appeal of having a wiki is that people can edit dynamic pages, whereas the appeal of a CMS is to streamline the process of putting the content up in the first place.

That's a hell of a task though, just view the recent changes page to see exactly how frequently it's being spammed. A clean start would be much more beneficial, perhaps creating an archive page from there and storing all the good nonsensical articles of old in there. I've locked the database for now.