Hey, it’s been months. What’s up?
Indeed, it’s been a few months of silence from me here. Let me fix this right now.
So, what’s cooking?
First, Listhings now has over 10,000 users. It happened rather quietly just a few days ago and Listhings now indeed has over ten thousand registerd users. Many donations have been made to support the development as well and I’m very thankful to all those who have done so. Have you donated already?
And second, a new version is in the works. I’ve been tinkering around with different frameworks and APIs such as Recess, CodeIgniter, Kohana and others. (These are web application development frameworks, for those who don’t know). A few months ago I settled on a decent one to base the new version of Listhings on. The new version will include a bunch of new features (one which I can shout out right now is rich text editing but there’ll be a lot more) and improvements on the stability and overall look and feel. I am pretty confident the new version will be released still within this year, 2010.
Now, speaking of stability… some of you might have noticed the frequent 3-5 minute downtimes Listhings has from time to time. I am doing all I can to avoid these but I can’t promise there will be no more such short downtimes until the release of the next version. Starting from the next version, there should be no more such short outages as I am planning to deploy the application into different set-up. On the scale of percentages by the way, the uptime of Listhings services has been around 97% over the last few weeks. This should significantly increase after the next release.
You might also want to ask “Why are these downtimes happening?” Well, it appears even though I am renting a virtual private server for Listhings, I still have to deal with something the hosting provider calls “extensive use”. They seem to have a mechanism in place that blocks the entire site for a few minutes in case it thinks the traffic gets too high (even though I stay within the limits of the virtual server) It’s pretty sad, I know, and I’ve optimized the site every possible way to avoid such blocks. Eventually the new version will be deployed into a completely different server set-up so such errors should be gone for good after the release.