jaiku invites

So after five days and six hours of down time Jaiku is back! At about 11pm BST (GMT+1) or 3PM PDT (PST+1) we had re-ignition! Woooo!

So what has changed? Well it is not on the Google App Engine yet! While the error page was on the Google App Engine the DNS has been updated yet again and Jaiku has moved to some ordinary servers inside the Google network and data centers. If you are still having issues getting to Jaiku now, you will need to flush your local DNS cache and S60 blogger handily provided a link on how to do that. If that doesn’t work then you will have to wait till your ISP does it, normally every 24 hours or try using OpenDNS. As you can see from the below headers it is being served by a nginx sever which is a modified version of apache that is for general use at Google.

Response Headers - http://jaiku.com/

Server: nginx/0.7.11
Date: Thu, 28 Aug 2008 00:32:08 GMT
Content-Type: text/html; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
Vary: Host
X-Powered-By: PHP/5.1.6
Cache-Control: no-cache, private
Content-Encoding: gzip

200 OK

The second thing is we now have UNLIMITED INVITES. Yes that’s right much as I suspected, Jaiku has followed the Gmail model and gone for staying closed but with unlimited invites. So if you have some time to spare please share a few a we have quite a back log to get through here at JaikuInvites and to those that are already sending invites out a big thank you!

Other notice able changes are everything is quite speedy and all the badges seam to working great again even some of the flash based ones that were giving trouble before like the map on the home page.

As always stay here with JaikuInvites for all your latest Jaiku News!

The long awaited move for Jaiku has finally begun. Last night they took down the home page and took all services off-line and replaced them with this message …

Folks, we’re offline for the weekend for server maintenance. Now’s a good time to talk to someone you love.

Now I can confirm that they have moved to the Google App Engine and will be hosted there when they come back up. As they say picture paints a thousand words, so for proof take a look at this.

For those of you not familiar with trace routes the last few lines there show that the domain Jaiku.com is now on the Google network. The IP address that it finishes at is also one belonging to several blocks used by GAE. Up until this, Jaiku.com had remained on the same Finnish server it was on when google bought it, trying to survive on just 1GB of RAM.

So what can we expect to see now that Jaiku has moved? Well the number one thing we can expect is near 100% reliable service, no more down time for the API or the IM bot and the last of the 502 Bird. The next thing is open registrations for all, whether that will come in the form of a Google account or Jaiku account remains to be seen yet but I would safely say that we will see Jaiku and Google accounts merged into one in the near future. And finally we will hopefully see the launch of some new features and maybe even the public release of the current updated beta S60 client, I’ve also heard that a lesser featured iPhone client may on the horizon too.

As always we’ll have more news as soon as we get it here on JaikuInvites so be sure to drop by.

Update: I have just been in contact with the Jaiku team and while they can’t comment on anything right now they are “working hard to bring Jaiku back online soon.” I guess we’ll just have to wait and see what’s in store.

Update 2: More proof that Jaiku is moving/has moved, the response headers for Jaiku.com are now returning that they are being served by the “Google Frontend” server. See the full output below:

Response Headers - http://www.jaiku.com/blog/

Content-Type: text/html; charset=utf-8
Cache-Control: public
Expires: Sun, 24 Aug 2008 20:46:09 GMT
Content-Encoding: gzip
Date: Sun, 24 Aug 2008 15:59:09 GMT
Server: Google Frontend
Content-Length: 632

200 OK

The Google Frontend server, is the server type that is used by all Google App Engine Apps.

Update 3: Jaiku have confirmed the move! They have updated the status message on their homepage to read:

Setting up our nest in a new datacenter, after finding an issue with a server on Friday. Sorry for the inconvenience. We’re working to get back online soon.

Update 4: Google have issued a second statement to the Eweek Google Watch blog.

“We’ve been working on the Jaiku service over the weekend after finding an issue with one of our servers on Friday. As part of the solution, we’re moving the service to a Google data center. Users can expect Jaiku to be back up soon.”

Nothing new there, but it’s still only 3:00pm in San Francisco where the whole Jaiku team is based this week. Even Teemu Kurppa (@teemu) the normally London based developer is in San Francisco this week, we expect to help with port. One of his last updates on Jaiku before the downtime being (from the Google cache):

“Firealarm sent us out to windy street and I forgot my hoodie. But I saw Guido! “
By teemu Friday, 22 August 2008 in Google, San Francisco, CA, USA. Add Comment

“Server-side fixing”
By teemu Thursday, 21 August 2008 in San Francisco, CA, USA