What’s up with Pixelpost?
March 10, 2009
Every once in a while people ask us: “what’s up with Pixelpost?” The latest update was released at July 27, 2008 and they wonder about the current status.
Well, the truth is that the current release, 1.71, is pretty much rock solid and very stable (quite an accomplishment if you look at the code 
). Security wise this has been one of the best versions thus far. However, we have made some minor modifications to the code since the release, but mostly we cleaned up the abundance of old code. Perhaps we will release this as an intermediate version between 1.7x and 2.x.
The last couple of months we basically didn’t do much with the old 1.x code. We spend most of our time on the new version: Pixelpost 2.0. This is going to be a complete rewrite compared to the old 1.x code and as you probably know, this will take some time.
On the forums I compared it to building a house. Let’s assume your blog is a house. Everyone likes a different style: some will like brick buildings while others are looking for a simple wooden house. But every house needs a solid foundation. The foundation is the most important part of the whole building. A house can be expanded/modified to your own taste as long as the foundation is solid.
This is an analogy for where we at with Pixelpost at this time. The main focus is building a solid foundation on which everyone can build what they like. For instance: if you want people to comment on your photos you add the comment plugin. If you don’t want comments and correspondingly no SPAM, just don’t install the comment plugin. It is going to be that simple.
If you look at the current 1.x codebase there is no way to disable comments since they are an essential part of the system. Even if you don’t want users to comment on your images it is likely you do receive SPAM comments, because the code for the comments is an integral part of the system.
So hopefully the new version will address all those issues (and much more in the form of plugins/modules, like multiple users, openID, better EXIF support and the list goes on and on). To accomplish that we have to provide a nice, clean foundation build for speed.
