It's some time ago that there was any news regarding Spaaze. So I think it's about time to clarify the status and future of Spaaze and to summarize the state of the union.
In short: Spaaze will continue to be available online. There are no further updates planned in the foreseeable future. Spaaze will continue to receive security and bugfix updates as necessary.
Attention: Spaaze will be unavailable for some hours starting on Nov. 7th at 1 pm UTC.
Due to a server move we'll take down Spaaze on its current servers on the upcoming Thursday, and it could take some time (for the domain to update and point to the new servers) before it's reachable at its new home.
The last two days we did some maintenance work on Spaaze. That included infrastructure maintenance but mainly it's bugfixes that I experienced when using the iPad version. It's now possible again to install the bookmarklet on the iPad, and all the editing dialogs now behave much better. Especially when editing note items, there was a problem that made it impossible to scroll the note editor (besides a little trick of using the text selection mode to scroll). This is fixed now, and also all other inputs should react more quickly now. Another fixed thing regards using the bookmarklet on Youtube. Sometimes the bookmarklet did not detect that it was opened on a Youtube page, and only offered the Bookmark item to be added to Spaaze, but not the video item. This is now fixed as well.
We just got the info from our hosting provider that on December 13th there will be some maintenance work on our database server from 12am CST to 2am CST, which should be 7am to 9am CET. The word is, that this could lead to some 10 minute long outages. We are still considering how to deal with this. Either we turn of Spaaze entirely during this downtime, or we simply keep it running and live with the 10 minute outages during which it won't be able to sign in to Spaaze and it will not be possible to create, load or save changes to boards. However, we just wanted to warn you that there will be some kind of degraded service during this maintenance window.
It has been a little bit quiet around here for the last months, and I wanted to let you know what we are up to at the moment. As you may know, the company behind Spaaze (IRIAN Solutions) also provides other web services. A mind mapping service (Mind42) which was our start into web services, and a chat service (SimpleMeet.me). So after about five years of running Mind42 with a more or less unchanged design, we were working on a completely new Mind42 experience.
During the last two days some of you might experienced that Spaaze wasn't reachable and other sporadic errors. From our understanding these problems where caused by some network problems of our hosting provide Rackspace and they are working hard to resolve this recurring issues. For those interested, you can find their explanation of the last incident on their status page. We hope that this won't happen again and are monitoring the situation.
We've finally reached the end of the tunnel. Until now Spaaze was more or less still in Beta mode, meaning that everything was still for free while we gathered experience running this service. Now we are happy to announce that we ended the Beta phase. Spaaze grew up and became an adult.
Just a quick update on a problem some may recently experienced when using search. During the last days we had some problems with the stability of our full-text search service. We are currently tweaking the monitoring and automatic recovery mechanisms to hopefully increase the availability and reliability of this feature.
Just saw that there has been a problem with Spaaze on Sunday evening CST, respectively Monday morning UTC. Just wanted to let you know that this had nothing to do with our new servers, but rather was one of the rare problems of our hosting provider Rackspace. Seems like they had a network issue between 4:35 and 6:00 pm CST. Once their issues had been resolved Spaaze continued to work normally.
As described in the last blog post, we haven't been able to perform the actual server upgrade last Saturday. Now we've chosen to go a safer way. We prepare everything, and will simply point spaaze.com to the new server when ready. Since Spaaze isn't using a Load Balancer yet (I can only hope that there will be so many people in the future that we'll have to scale our infrastructure) I prefer to turn off the old one while the transition is in progress (to not mix up states between the two servers). This will be much less painful than what I had planned last Saturday, and need less time.