Insoshi Ruby on Rails blog

This week’s version of Insoshi fixes a significant annoyance, the creation of accounts with duplicate email addresses due to a limitation in the Active Record validates_uniqueness_of validation. You can check out the diffs at GitHub if you’re really motivated, but I’ll be making a blog post about it next week, so interested readers might want to wait for that.

The focus of Insoshi development has sharpened in the past several weeks, reflected in the updated roadmap and new milestones.  Now that the validates_uniqueness_of issue has been fixed, there are only four outstanding tickets to be resolved to solidify the Insoshi foundations. (Briefly, there are a couple of speed bottlenecks to clear, a necessary improvement to messaging, and a change from Ferret to Sphinx for search. Note: this last change will break compatibility with SQLite.) We also have a slew of mostly minor bits of polish to apply. Finally, a surprise contributor has made some significant improvements to the user experience (UX), so expect a significant site upgrade once we merge in his branch. We expect these three milestones to be met by the end of July.

We’re quite busy these days answering email on the Google group and tending to the developer site, as well as gearing up to talk to investors.  So, given the multitude of our non-development obligations, we’re going to turn down the heat on ourselves a bit by forgoing weekly updates* and only making new Insoshi posts when there are important changes to note. In concert with this reduced Insoshi-blogging schedule, we’ll be ramping up our Ruby on Rails blogging, with occasional illuminating Rails posts starting next week. Watch this space.  :-)

*Previous updates were posted to the Google group (and my internal Insoshi blog) rather than to this blog.