I really could kill the developers over at Pixelpost. Hulk gets angry when he reads the forums. Hulk gets angry when he looks at the code. Hulk gets angry when things that should be in the upstream codebase aren’t. Hulk gets angry when he spends most of the day patching the new code (not that he minds that much, and not that it’s the worst way to spend a Saturday, but I really shouldn’t have to). hulk gets angry when he gets the impression that the developers just want everything to be made into an “addon” when “addons” won’t really get you very far for some feature requests. Things that Pixelpost really needs to focus on and put in their roadmap/milestones (if they have any which I would doubt):

internationaliziation
exif data in rss/atom feeds
thumb/full/no image in rss/atom feed
consistency in rss/atom feed content
rss/atom comment feeds
individual photo comment feeds
code formating/styling/standardization
code reuse/breaking into functions
out of the box anti-spam and captcha
header/footer in templates
<site_aboutlink>
prettier urls: simple: /photo/1 and more complex slugs: /2006/12/01/kids
database independent
remove “no intrusion”, 404 crap
standardize checking of possible x= parameters

And probably many more. It’s really not that bad of a product. And of course I use it, and I used it for Marc’s and Ben’s photoblogs, because when it comes down to it, it does its job, and it does it in a pretty short amount of code (because then it’s easy for me to hack on), but it really could use some polishing. I could probably easily get a dozen patches in to the development team, but I hesitate because if I did a whole lot of work to break all of my code updates into patches and then submit them to the developers, only to have them thumb their noses at me, well, I don’t want that to happen…

</pixelpost-rant>