Wednesday, August 27, 2008

We’re back, and invitations are now unlimited

As many of you know, we’ve been offline for the last few days, working to address an issue with a server. We’re back, and we’re sorry for the inconvenience.

We’ve now moved Jaiku to a Google data center. This is something that we’d planned to do anyway, as part of our future transition to Google App Engine. Now that we’ve moved, we’ll need to ask you to review and accept a new terms of service and privacy policy. Head here to do that.

As a special thank you for your patience, we’d like to throw a little nest-warming party and open unlimited invitations for Jaiku.

We appreciate your support!

Monday, August 18, 2008

From the Dev Corner: An Under-The-Hood Preview of Our New Engine

It’s been a while since we’ve given an update on the progress of the porting of Jaiku to Google App Engine, and many of you have been keen to know how work is progressing.

It’s as if we were retrofitting a locomotive with a powerful new engine. Everything under the classic body gets upgraded.

Just like on the inside the locomotive is composed of a drive train, transmission, and so on, Jaiku is composed of services for features like fetching Web feeds, receiving and sending SMS, the IM bot, and Jaiku Mobile. We’re reimplementing them all so that they work well with the App Engine. In some cases we’re expanding the App Engine platform itself. We’re taking the opportunity to learn from porting Jaiku to benefit both our users and make App Engine better.

The port to App Engine will also benefit third-party developers who are writing cool applications for Jaiku. In the process of rewriting Jaiku’s Web site on Django, we’re improving the way the site is written so 3rd party developers will have greater control over the system and can write applications that provide richer features to their users.

Those who’ve payed attention know how excited we are about open Web standards like OAuth, Microformats, and OpenID. The port to AppEngine is an opportunity to add more support for them to the Jaiku platform and contribute back to the community by implementing support for the standards we love. For example, the new Jaiku API will support OAuth.

The biggest benefit for the Jaiku community is that we’ll be able to grow and support many more users. Where before we used MySQL, now we’re using the more scalable App Engine data store and an improved data model. We’ll be moving existing users’ data to the new architecture to make sure Jaiku scales up for you and all your friends.

So, where are we now? We’re putting the finishing touches on the entire system. As any developer knows, sometimes there are surprises, so we’ll periodically let you know how things are progressing.

We appreciate your patience and can’t wait to open up Jaiku to everyone!

Web server outage

Update: All services are now up and running again. According to our data center provider, the power failure that affected Jaiku this Sunday was caused by the meltdown of a mains switch and disrupted the servers of over 8,000 customers.

A power failure at about 9am PST (7pm EET) today at the data center provider where Jaiku’s servers are located caused an outage on We are back up and running, but it will take some more time before all services are fully operational. We apologize for the service break and are working to get all functions back to normal as soon as possible. Thanks for your patience!