The new server hosting the indexing scripts seems to have a more strict memory usage, and the code base really needs an overhaul. Practically, this meant that the indexing failed because of running out of memory, causing the system to not index at all anymore. I have done some clean up, and Cb is back online.
Some of you noted and reported that Chemical blogspace has not seen any updates since March 4. I can confirm this problem, which is likely due to server movement on our ISP. My apologies for the inconvenience, and I hope to restore indexing on short notice, but given other priorities, I cannot give an ETA yet.
A bit more than four hands full of new blogs in the four months since New Blogs #11. Importantly, I have disabled the Accelrys blog in favor if the blogs of its individual contributors, Dana, George, Gerhard, Max, Nancy and Shikna. This is not to boost the number of blogs, but merely reflects that Cb focuses on personal (accountable) opinions and not corporate blog (which is often polluted with to much advertisement).
Would you object to seeing Google Adsense ads on the Cb website? The money it would bring up would be donated to a charity involved in promoting Open Science. Please let us know, either as comment on this blog item or by email.
Looking forward to hearing from you!
Not that the last two weeks has seen a boost on blog submissions to Chemical blogspace; just that I was not really finished with New Blogs #10.
Many new blogs have appeared in Chemical blogspace since New Blogs #9. I should really make these overviews more often (I left out the new blogs which have not blogged in 2009 yet):
Two weeks ago, I looked into why Cb was failing once more, as Cb was giving MySQL warnings, and the after that I cleaned up the list of active blogs. Several people reported that, for example, the Blue Obelisk RSS feed was down. Today, I found the cause of the lack of updates: the tags table had grown too much in size, and the Postgenomic.com software's SQL queries are not really optimised... So, our host (Dreamhost) renamed the table to fix the massive load on the MySQL server, causing the MySQL warnings, but also the lack of updates. I emptied the tags table, as the tags are not really crucial anyway, making the website show up nicely again, and hopefully making the update script not fail any more, either...
