Percentage of Splogs

Rant

I’ve been indicated a few places saying a third of blogs are spam. Someone came up with this by me saying we’ve axed around 800,000 splogs on WordPress.com, and looking at our number of blogs, which is 2.5m.

As for percentage of the total blogosphere, reported by Technorati as north of 100 million, which are splogs, I’d say the number is much higher – probably 80%. This isn’t as bad as it sounds, I just think spammers are very effective at creating hundreds of thousands to millions of blogs, they tend to stick around, and I feel like Technorati’s number doesn’t doesn’t adequately scrub these out.

While I’m making data-less estimates, I’d say there are about 25-30 million non-spam blogs, and about 8-14 million of those are active in terms of getting traffic or new posts. You could cover a meaningful portion of the blogosphere by just indexing 4 or 5 million blogs.

Splogs and blogger attrition are two problems no one really talks about, but that’s okay because I don’t think either is hindering anyone’s growth as measured by metrics that matter, like pageviews or uniques. (Though many of the services supporting so many splogs must have an inordinate amount of resources devoted to them.)

See also: Blog Ping and Spam Statistics, WordPress.com February wrap-up.

Scriblio for Libraries

WordPress, ,

Scriblio MATC Project Final Report. Scriblio is a system for helping libraries and is built on top of WordPress. The article describes some of the troubles with the close association with WordPress:

Shortly after the Mellon Foundation announced the award to the Scriblio project, the WordPress core developers reversed their longstanding position on tags and announced that the next release would include tag support. This is significant because metadata such as author or subject is functionally equivalent to tags in Scriblio, and much of the Scriblio code was devoted to managing those tags.

It also describes some of the benefits:

[T]he relationship between the open source WordPress community and commercial participants, including Automattic, the commercial entity that operates WordPress.com, has proven itself to deliver real benefits to all. […]

And the Scriblio project has enjoyed opportunities to contribute to the WordPress community as well. […] One recent example is Ticket #5649, where a change proposed by Scriblio was committed to the baseline code within an hour of its submission.

Overall, a good read on building a project on top of WordPress, helping an under-served community, and giving back by strengthening the underlying platform.

Wither Dreamweaver

Rant, , ,

I’ve done my coding in Dreamweaver for 5+ years now. I think I’m the only one who does so at Automattic, but it’s a good fit for me with the network/SFTP integration, decent PHP highlight, regex search/replace, and good project support. It was a natural transition for me from Homesite. I know there are a thousand other editors that I could use, and I know I shouldn’t be on Windows most of the time, but that’s not what this post is about. I’m utterly appalled by how bad Dreamweaver CS3 is. I paid hundreds of dollars to upgrade to something that consistently crashes when I edit certain parts of PHP files and CTRL + F no longer opens a search box unless I have a document open.

Dear Dreamweaver team, I’ve been putting up with these bugs for close to a year now. I will come down to San Jose and show you the bugs personally. Just please do something, or feign the appearance of movement. For now, I’m switching from CS3 to version 8, which is just sad.