Updated to 1.16.4

by AndrewMiller on April 18, 2011

in RichmondWiki,Site Updates

In an effort to nip the latest round of spam attacks in the bud, I upgraded the MediaWiki installation today to 1.16.4. It’s leaner, faster, and still a pain in the ass to install and configure.

But, thanks to a few updates and tightening of the captcha system, I expect to see less spam.

There are still a few bugs (mostly layout and CSS), but if you see anything amiss, please let me know.

Remaining to-do’s:

I’m sure I’m missing more, but this is still a big improvement in our anti-spam efforts and usability.

{ 2 comments }

Moving Forward

January 26, 2011

It’s been kind of quiet here on the blog and on the wiki. I’ve only had time to keep up with the spam on both, not contribute new content. Besides time, I’m trying to figure out how the wiki might fit into the local media/web/social scene. An aggregator? A focus on history and/or other static [...]

Read the full article →

How to Speed Up MediaWiki for SEO

June 12, 2010

Webmasters and wiki admins are rushing to improve their sites’ performance after Google’s official announcement that page load times are now considered in the ranking algorithms. Check out the performance gains we’ve achieved on RichmondWiki after a few updates in late May (from Google Webmasters, click to expand): Faster load times results in Googlebot crawling [...]

Read the full article →

DreamHost PHP5 Error in Unix Shell

May 21, 2010

I’m in the process of *finally* moving the wiki from Network Solutions to Dreamhost. Along the way, I encountered an unusual error while updating from MW 1.13.1 to 1.15.3 (yeah, so we were a little outdated but whatever): In my UNIX shell I typed in the following to run the update.php script: php update.php only [...]

Read the full article →

Discussion Page Spam

May 3, 2010

I’ve seen spammers post things on article Talk pages a few times now. Typically they resemble automated spammy link drops that are blindly targeting blog comments, forums and wikis. Today’s example:

Read the full article →