Second Class Citizen

Occasionally someone will pipe up and make you realise the sad truth amongst web developers, or for that matter, programmers. We are second class citizens in the eyes of many.

Gone are the days where making a computer do something different is cool, No, Now its a job, anyone can do it, you’ve just got to learn to code..  heck, some people are purely programmers for a day job, with no outside interest in it.

There Are No Famous Programmers – Zed A. Shaw (
Let me tell you about this cool new web server. I figured out how to merge the ZeroMQ event polling system with the libtask coroutine library so that you can use libtask to handle tons of TCP/UDP and ZeroMQ sockets in a single thread. I then took this very cool hack, and started building a web server using my Mongrel HTTP parser, but I modified the parser so that the same server on the same port can handle HTTP or Flash XMLSockets transparently. The next step is to get this server to route HTTP and XMLSocket JSON messages to arbitrary ZeroMQ backends. I was inspired by this so much that I registered and may try to bring it back. Not sure how or when though.

Sounds cool right? Totally doesn’t matter one bit. I could hack on projects like this and nobody would care at all because I’m a famous programmer, and there is no such thing as famous programmers. I don’t exist. I’m an enigma.

And he’s right, Name a “sucessful” startup who you can think of the name of the current CEO, I’m sure you can think of one, Did they write the product you’re associated with them however? In most cases, No. They’re just the ones with the vision, The one with money, The one with the guts to say “This could work!”. Being a programmer isnt enough anymore, you need a masters degree in marketing, A bucket load of cash, and a face to put forward – and face it, you’re not it.

Gone are the days when a single person can be a superstar, without the help from others, you’ll never reach gold; and if you do, be sure your programming days are long gone..

Introducing: “TwentyTen: Remove Max Editor Width”

(Download Link)

The new TwentyTen WordPress theme is a pretty awesome theme if you ask me. Written by decent people who know what they’re doing (Unlike many other themes out there — Which whilst shiny on the outside, can be a rabbits nest underneath).

The theme only has one problem to me — and as i’ve noticed, to some other people as well. Infact, Its annoying me right now, just writing this post.

So, What is it?

Its the limitation of limiting your TinyMCE (Thats your visual text editor on the New Post screen) window to 640px. It does have some uses, but for someone like me, just writing text, and not caring about the benefits; can be downright annoying.

Oh, I nearly forgot, It also applies to fullscreen mode. So for people with a 1200px wide monitor.. well.. you get the idea (If you dont, it means, your post will be using the left most 53% of the screen). This is actually a limitation of TinyMCE not being able to distinguish between inline and fullscreen edit modes to be fair, but is still a PITA all the same.

Do try and use it yourself however, I quite like it for aligning images, but not for general purpose posts..

So, Whats the benefit exactly?

Floating images. When was the last time you were writing a blog post, and tried to insert an image, then hit preview, and found it was in a completely different place than you were expecting? And that the text was flowing badly around it? Well, this allows you to have a preview of how the actual post WILL look right in the WordPress new Post administration panel. Pretty cool in general, a downright pain to others.

So, What can i do about it?

I’ve written this short (Seriously, Theres more comments than code in this plugin) plugin which allows your editor to regain its innermost full content width.

You can download the plugin from the repository Here. But since the plugin isn’t actually live yet (awaiting creation) you may download it HERE instead.

Revision Control 2.0 Beta

The time has come for a Beta release of Revision Control 2.0. Would also like to announce that I’ve Cracked the 20k downloads on a plugin! currently its standing at 412,320.

Download 2.0-beta Now. Download POT file for Translations

Things to note of this release:

  • Fully rewritten from scratch
  • Better support for multiple post types
  • 100% api usage, less chance of breaking something
  • Revisioning of Categories and Tags (Well, Any taxonomy really!) – One limitation, It doesn’t restore this, thats for the next Revision :)
  • WordPress 2.9+ only.

Compatibility with older releases: I’ve not 100% tested backwards compatibility, That will come this next week, For new users, you’ll have no problems, for existing users, you should be warned that your settings may not be remembered, more testing needs to happen to verify that it works in 100% of cases.

If you’d like to submit a Translation of this plugin, or encounter a bug just send it along to

Thank you to all,

EDIT: Release Date: 24th Jan 2010 – approximately.
EDIT2: Updated the POT and .zip locations, There were a few translation issues.

Nearly there… Revision Control 2.0

Revision Control 2.0 is nearly here.

A quick list of changes:

  • Fully rewritten from scratch, Will require WordPress 2.9+
  • Better support for custom post types (Will make much more sense with 3.0!)
  • Support for Revisioning of Taxonomy data ( Doesnt restore at present, Mearly revisions it)
  • Many small bugs removed from previous versions

Features in the pipeline (2.1?)

  • Restoring of Taxonomy Revision Data
  • Support for Metadata revisioning (Custom fields, Post thumbnail, etc)
  • Delete all revisions from Admin UI (Or potentially, cleanup so theres only 5 revisions for each post for example)

This seems like a small list, but for a small plugin, its actually a rather large ammount of work to get through.. If you feel like testing it out, Please do, You can download it from here:

Some of those 2.1 features may be in 2.0, It depends on how much time i have amongst other things in life, and how much testing is required.

Translators: Sorry, But i dont have a list of your email addresses to contact you directly.. I’ll be setting up a GlotPress installation for this sort of thing i think :) Feel free to take the langs provided and update them.. I may remove the old ones entirely shortly..

To those of you using some of my other plugins which have been lacking in updates, Most will be recieving a rewrite this year, hopefully in the coming months – But i do not have the time to give any definites here, Some will not be touched. Add From Server is the next on the list however!

A Call to Arms

WordPress 2.9 was just released, And several users have run into a bug. Surprising? Not really. Theres one simple reason for this, While thousands of people Test each and every WordPress release, These users are not You.

I’d like to use this as an example to all here, Why WordPress needs your help. No, I’m not talking about Coding help specifically, I’m talking about Testing. WordPress requires that users test the product throughout the development period.

WordPress is an open source application written by hundreds of contributors. While those hundreds probably use the Development version of WordPress every day, They do not use the same webhost as you, nor do they have the same theme, nor do they have the same requirements, They use different functions of WordPress than you.

During The beta and RC stages, thousands of people download and test, These testers are end users like you, In order to prevent these bugs getting into a released product, It requires that users actually take part in the developement of WordPress and report the bugs encountered.

Testing WordPress is not just something that Developers should do. If you use WordPress and enjoy using it, Please take some time once every few months to test WordPress, Its announced on the Dev blog when Beta’s are available, On a default install of WordPress, The Dashboard should have a RSS feed mentioning the releases too.

So please, For 3.0, When a Beta is released (Theres generally ~2-3 weeks of beta, with 2-3 beta’s from my quick recolection) Install it on your website, It doesnt have to be your main one, it can be in a subdirectory (ie. your usual one at and the test at, and test that things works ok for you, and your plugins, This does take an hour out of your time, and i realise not everyone can afford it, But it may spare you 2-3 hours of your time, when after a release, a bug that affects you is found, that a Developer had not noticed.

WordPress requires your input, Whilst I agree there are some downfalls in reporting bugs sometimes (Please do not flame me with related messages here, I’m not after that, This is mearly a request for more contributions) overall, your contributions would be greatly appreciated by all.

In order to make it easier to test Beta’s and nightly versions, Westi wrote this great plugin It allows you to use the inbuilt upgrader to upgrade to a beta, to make it easier for you, to be involved with the project you love using.