OpenMoko wiki needs to be set to read-only due to spam

Troy Benjegerdes hozer at hozed.org
Sun Nov 11 21:17:33 CET 2012


On Sun, Nov 11, 2012 at 08:16:03AM +0800, Paul Wise wrote:
> On Sat, 2012-11-10 at 18:57 -0500, Harry Prevor wrote:
> 
> > Sorry for bringing this somewhat old topic up, but why did this have
> > to be done? I can understand restricting editing to registered users
> > only or adding CAPTCHAs to prevent spam, but isn't making the (still
> > very important) wiki entirely read only very exccessive? I've found a
> > few pages with errors but I'm now unable to edit them, seemingly
> > forever. Please reconsider this.
> 
> The only sysadmin (Harald) doesn't yet have time to setup some anti-spam
> mechanisms. I've volunteered as a second sysadmin but Harald hasn't had
> time to do some things that are needed before he can add me to the team.
> Making the wiki read-only is a stop-gap measure until some anti-spam
> stuff can be setup and all the spam pages removed by myself or Harald.
> 

How can I get a database dump of the wiki so I can clone it? What I'd 
really like to be able to do is run a read-write fork/clone of the 
mirror, and have the backend database be files in mercurial or git,
and then we can have an editable version that I can experiment with 
OpenID auth with, and possibly have an easy way to merge 'patches'
back to the read-only main site. This probably requires more patching
to the mediawiki software than I want to think about.

I'd also like to be able to put the contents of the OpenMoko wiki on
a Wikireader, and having the DB would make this a bit easier.



More information about the community mailing list