Category Archives: WordPress

The open source publishing platform I co-founded — development, releases, community, and the ecosystem.

Weeds in the Garden

Under the Iron has an old interview with Scott Johnson that is a good read. Now scroll down to the comments. Dozens and dozens of spam comments. I see this over and over again on MT and s9y sites. What’s terrible is these pages are just as dangerous as dedicated spam blogs. Think about it: I shouldn’t even be linking to it now.

Alex told me the other day about a new type of comment spam he’s been seeing: comments that link to normal blog entries. Well known blogs like Mozillazine. As advanced as tools like MT Blacklist have become, they’re pretty useless in cases like this. Are you going to blacklist Dave Sifry? Molly.com used to have spam comments on her site all the time. Even though she spent a lot of time and effort dealing with them (a daily chore) they only need to be there long enough for Googlebot to index them for the harm to be done. I’m not dogging on MT here, it’s just that there are tens of thousands of MT blogs out there who don’t have any protection and the spammers are targetting them mercilessly. Domain blacklists don’t scale (spammers can have thousands of domains easily and hijack innocent domains) and centralized registration hasn’t shown to be effective except against people who don’t like centralized registration, a group that doesn’t include spammers.

People used to say that WordPress doesn’t get spam comments because it’s not popular enough. I don’t think this argument holds water anymore. It’s true that MT has three to four times as many blogs as WordPress, but Serendipity has an order of magnitude fewer blogs than WP and is highly targetted by spammers. I think WordPress has, through design and luck, done a lot of things right with regards to comment management in general. First we respond to the problem in the core code quickly. Moderation and blacklisting has been in the core for half a year now. All of the WordPress developers are bloggers as well so we’re pretty sensitive to new techniques in use by the spammers. When early versions of WordPress 1.0 advertised moderation was on spammers instantly adapted to that and started searching for blogs that didn’t have the phrases we used, so in the next nightly build for testers I had changed how that worked so it couldn’t be targeted anymore. Then in 1.2 we expanded the already successful moderation to allow powerful regular expressions and target not just the content but things like number of links in a post. Let’s say that somehow two hundred spam comments did get on your blog, which would never happen in the first place because we’ve had throttling for over a year now, you can easily delete hundreds of spam comments at once in under five clicks. We’re not sitting still either, version 1.3 will have emergent registration based on code originally written by Kitten so there is a type of automatic whitelisting going on that spammers can’t duplicate because it uses email addresses like a secret key and WordPress never reveals your email address. (So Dave and Mark, stop leaving fake ones!) The code will be flexible enough to adapt for GPG signing for the ultra-geeky in the audience.

Any of these things by themself wouldn’t be very effective, and each method I’ve listed has its flaws and weaknesses and I know them. Which brings us to what I think the real reason WordPress, despite its explosion of popularity, still doesn’t get the level of spam other tools do: it’s more trouble than it’s worth. WordPress, to spammers, is an unpredictable and moving target. We’re not resting on our laurels, we have another exciting feature-filled release coming just a few months after the landmark version 1.2. The WordPress moderation system can be be toggled to manual mode, which is 100% effective at catching spam, or triggered only when something is suspicious. We’re committed to keeping the cost high and the reward uncertain for spammers which means you don’t have to wake up every morning to filth on your weblog as well as in your inbox. You can focus on what draws us all to this medium, writing and genuine interaction. Here’s a quote from Molly from a comment she left on Keith’s site:

I wanted open comments. In my situation, MT, despite the wonderful Jay Allen personallyhelping me on an almost daily basis to deal with comment spam, I was a major target. My ISP refused to continue dealing with me because the server molly.com resided on was brought to its knees twice due to spam floods. I was spending up to two hours PER DAY to undo the spam much less post.

Since switching to WP, I’ve had exactly five emails sent to me automagically for moderation. 3 of them were spam, 2 were just enthusiastic posts with multiple links from a reader.

Either way, I had instantaneous access to accept or delete those posts.

That’s the sort of thing that is incredibly rewarding about working on WordPress. Knowing that your work makes it easy for someone else to do what they love is one of the greatest feelings in the world. No amount of money or recognition can ever match that.

On Market Share

Nick says Feed Demon defaults to checking once every three hours, so depending on how you look at stats it may appear 1/3 of readers that poll every hour, skewing its market share numbers. Something similar may effect WordPress’ numbers with installations and blogs. If the average MT user has two or three blogs per installation (like their survey indicated) then the actual number of installations would be half or a third of what the blog survey numbers indicate, putting it much closer to WP’s numbers. Of course I know of no good way to track this, so it’s just a random musing.

Color Schemes Contest

I’m very interested in seeing some alternative color schemes for the WordPress admin, so I thought I’d sponsor a mini-contest here. You don’t have to be a WordPress user or even have it installed to participate. The colors don’t have to match the logo or anything like that, I’m just interested in seeing easy-on-the-eyes color schemes people would enjoy looking at. For people who aren’t running a nightly build or not running WP at all I’ve put up two screenshots that you can use to get an idea of where the colors will go. You don’t have to be a designer to play, just play around with the colors in those images until you find some that you like and then post the results. Winners (I’ll probably pick a couple) will get prominent mention on this site and wordpress.org, a free unlimited-user copy of WordPress, and a small monetary prize via Paypal. So fame and fortune, what more could you ask for?

So to recap the important bits:

What?
Playing with interesting color variations for the WordPress admin sections.
Materials?
Screenshot one, screenshot two, and a HTML dummy page.
How do I enter?
Leave a comment with some way to represent your color scheme, whether it is a screenshot, CSS code, linked post, hex values, whatever you’re comfortable with. You can enter as many times as you want and win multiple times. If you don’t have time to enter, link to this entry and let other people know about it.
Any guidelines?
Be creative! Don’t modify the layout, just the colors.
Deadline?
Friday night, my time. This is a low-impact project, all you need is a color picker and about ten minutes. Submit your entry as soon as possible so no uses your colors before you do. Enter as many times as you want.
Prizes?
Fame, fortune, and that warm fuzzy feeling you get from contributing to open source and having your work in front of thousands of people.

When all is said and done I’ll roll this into a plugin or something so people can enjoy it. You don’t have to be a designer to enter, just put together something you like.

Update: There are a few clarifications and tips in the comments, so you might want to look over those. The big news, however, is that Aaron Epstein has donated a copy of his excellent Color Schemer Studio product to be awarded to the top winner. Downloading a 15-day trial would be a great way to put together a great entry and get a taste of what you might win.

This hasn’t been forgotten, I’m just can’t write the plugin for the winners until 1.3 is finished. Thanks for your patience.

Staticize 2.5

Version 2.5 of the Staticize Reloaded plugin is now available for download. Installation instructions are included in the archive. What does Staticize Reloaded do? It is a highly advanced caching engine that dynamically and automatically caches pages on your site that need to be cached, when they need to be cached. It also allows for some parts of a page to be cached and others not to be, so for example your menu could always be dynamically included from a single file while your main blog content was cached. With Staticize Reloaded you don’t have to worry about rebuilding, stale caches, slow posting times, or any of that. It works silently, efficiently, and trasparently to both the end user and the author.

This version adds the ability to have dynamic functions on a page in addition to dynamic includes. It also adds full support for etags and last modified headers, though you must turn it on in the plugin file. My one tip is that when you redesign or tweak your template temporarily deactivate the plugin. Staticize Reloaded is well-suited for sites on older servers or that receive more than twenty thousand visitors per day. WordPress is so fast anyway I find it’s not worth caching on lower-traffic sites.

Update: The zip archive had a slightly older version of the plugin than the final 2.5 release. Please re-download to get the latest and greatest and fastest.

NetNewsWire Subscription Favelet

NetNewsWire Subscription Favelet that uses Mark’s excellent feed finder. Seems like a good hybrid solution. I have been less than impressed with NNW’s autodiscovery performance. In a perfect world I could take my OPML file (which only contains site URIs, not feed URIs) and it would import and autodiscover every feed. Also there seems to be no WordPress setting for weblogs. I’m new to all this, so some of this may be things I’m missing.