BlogMatrix
 

Site Updated

edit David P. Janes 2007-04-07 10:40 UTC add comment  ·  ·

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.

Nasty crash on blogmatrix.com

edit David P. Janes 2006-08-24 20:39 UTC 2 comments  ·  ·
We had a nasty crash on blogmatrix.com today; we've fully recovered the system as far as we can tell. If there's any issues please contact us ASAP.

This is a good as time as any -- and perhaps better than most! -- to tell everyone that we're migrating servers to a better and more reliable hosting environment running the V10 look and feel (i.e. what you're seeing here right now). If you have an active account on blogmatrix.com; try "userid.semantic.blogmatrix.com"; that's mostly what your account is going to look like.

We'll try to make the transition as smooth as possible though some elements, such as custom sidebar markup may not be transfered. All your podcasts, videocasts and blog entries will be transfered; in fact, they mostly are already.

We'll make the old (i.e. the current) blogmatrix.com available under a different DNS in case there's anything else to be transfered.

 

Rogers/Shaw, iTunes and BlogMatrix

edit David P. Janes 2005-11-21 11:09 UTC add comment  ·  ·

If you’ve been having problems downloading in the Toronto area, this may be the problemBoing Boing). We have no solution at this point, except to suggest only downloading one item at a time.

Server Upgrades

edit David P. Janes 2005-10-11 13:20 UTC add comment  ·  ·

Many of you have been seeing very low download speeds. We apologize for the problem and are working on fixing the issue. We will be adding additional hardware on an independent network by the end of the month to speed up the service seen by our paying customers.

Brutal performance problems

edit David P. Janes 2005-08-28 23:03 UTC add comment  ·

Sorry – we were having some brutal problems with performance this evening which required some emergency work on our primary HTTPD server. The good news: we think we have the probem licked—we were routing too much data through a HTTP proxy. We’re now directly serving media files from our main HTTPD server rather than hiding them through a chain of indirection.