We did a significant update to Onaswarm this morning:

• Everywhere where we used to refer to "feeds" we now refer to "social networks". We believe this may be a little more clear
• We've simplified the "friend" relationship (which is really more like the Twitter "follows" idea, so we may be changing that more soon) so you don't choose to "aggregate into my account". Rather, you'll see to the right links for "Calendar", "Lifeblog" and "Lifestream"; next to those is a "+ friends" links, which you can click on to show what your friends are up to
• We've made a number of database improvements that should make things a little faster

We are upgrading to V11 this weekend. This may involve downtime, especially Sunday morning though we'll try to minimize disruptions. At times may be slow since we'll be effectively running two parallel BlogMatrix.coms for a while.

Update: we only got half way through the update and had some issues. We'll be picking up the second half ASAP.

We upgraded BlogMatrix.com this morning with the latest and greatest version of our software. The primary change is the new admin interface, which we'll be expanding and extending over the next few weeks.

The most notable bug fix is that draft mode now works if you have your own templates.

We upgraded the BlogMatrix software this morning; this mostly consisted of UI tweaks and minor bug fixes.

We're replacing the current stats system with something new in the very near future, probably tomorrow morning. The most noticible thing will be speed, followed by usability and looks. We'll probably roll in new features, such as hits over the last 24 hours and so forth over the next few weeks.

(Ignore the logo!)

We successfully upgraded the software to it's latest version this morning. This is mainly UI tweaks and performance enhancements -- if there's any issues, please contact us ASAP.

It's been a while since we've reported in. Things have been running relatively smooth since the last release. We've identified a number of improvements, mainly related to the database, and this seems to have solved 90% of our problems. We're looking to hit the last 10% with:

• reducing the size of log files (which are killing cache efficiency)
• having certain applications monitor system state and pausing during busy periods
• running "headless" (without front end apaches, which are causing the page cycle problem) 

Our attempt to upgrade this morning partially failed: we got all our software updates in, but the big "reorganization" of how our Apache servers work didn't take for some inexplicable reason. So we're going to try again tomorrow morning. Unfortunately, this means that getting the "wrong page" is still going to occur (though much less often than you were seeing 4 days ago).