Wroom - we’re moving to Google App Engine
April 8th, 2008
We’ve been working quietly for a while to port Jaiku to Google infrastructure. Today we’re taking off our welding goggles to announce Jaiku will be one of the first apps to run on the new Google App Engine.
The Google App Engine enables applications to leverage powerful Google technologies and scale up to millions of users without infrastructure headaches.
Jaiku will be fully deployed on the Google App Engine in the near future. Andy & co. are working hard to ensure the port is a success and we will make a further announcement once the port has been completed.
Duncan Sample Says:
Congratulations! I hope it all goes smoothly. With the way some have reacted to recent down-times, I just hope this transition goes a little smoother for you :o)
Good luck!
April 8th, 2008 at 6:42 am
ARJW Says:
This is a good thing; at least from a development standpoint. I woul assume that the App engine will not just allow for the kind of scaling that Google can really take advantage of, but it would also present a simpler means to integrate Jaiku’s features into various services and vice-versa.
A piece of me sees Jaiku as a bit of a “tie that binds” users with aspects of Google’s services. A bit deeper than an ID, and more user tunable becaue of XML. Should be interesting.
I do hope that this app engine presents the means for more than just S60 devices to reap on the mobile side. Jaiku’s ability to work without a web connection for the presence setting could be just as powerful as other aspects of it.
April 8th, 2008 at 6:49 am
Brainjam » Jaiku flyttar till Google App Engine Says:
[…] Jaiku kommer vara en av de första applikationerna som kommer ta plats i Googles App Engine som kommer att vara en utvecklingsmiljlö. Det kommer säkert att innebära ytterligare nya applikationer. Vi kommer att se ett försök att bygga in utvecklare i Googles egen miljö. […]
April 8th, 2008 at 7:15 am
Jaiku flytter över till Google App Engine | Mikroblogg Says:
[…] Jaiku-gänget har haft fullt upp med att skriva om koden så att den lirar på Googles nya App Engine. Därmed blir Jaiku även den första koden som snurrar på App Engine. […]
April 8th, 2008 at 8:49 am
Martin Paljak Says:
This is very cool.
It is good and cool for Jaiku and to be honest, the Google infra thing looks awsome as well.
April 8th, 2008 at 10:10 am
Jaiku is moving (and opening!) | jaiku invites Says:
[…] The official announcement was made over on the Jaikido blog and the announcement of the Google App Engine was broadcast live by @Scobleizer via Qik and live blogged by @techcrunch on the TechCrunch blog. […]
April 8th, 2008 at 2:55 pm
Google App Engine | Utvbloggen Says:
[…] Ingen kan ju ha undgått att Google nu släpper en ny plattform där du kan köra din egen Python kod. Först ut att använda projektet blir Jaiku som köptes upp av Google förra året. […]
April 8th, 2008 at 5:54 pm
Two points about Google App Engine | Technovia Says:
[…] 2. I am very glad that Jaiku is moving to this platform. Now, suddenly, the effective radio silence that Jaiku has undergone makes a lot of sense. […]
April 8th, 2008 at 11:53 pm
Jacky Zhao Says:
good Done…
April 9th, 2008 at 5:34 am
bb5media Says:
good job for jaiku….
April 9th, 2008 at 12:45 pm
Jarkko Laine Says:
Does this mean Jaiku is being ported to Python as well, or are you using a yet-to-be-announced Java API for App Engine?
April 9th, 2008 at 3:17 pm
Google moving Jaiku to Google App Engine Says:
[…] Checkout: Wroom - we’re moving to Google App Engine […]
April 11th, 2008 at 11:37 am
BuiltByDave.co.uk » Google Application Engine vs Facebook f8., by David Stone Says:
[…] If the phone is your social network, what are companies doing? Well, the long and short of it is, not much. Sure, Facebook has possibly the best iPhone application in the market, and a mobile friendly version, however it’s not enough (and if you know of a mobile social network with traction please let me know). Contacts integration? Application platform? Oh, wait, yes, Android. I’ve not looked at Android, but I’m pretty sure it’ll allow contacts integration. Jaiku is moving to Google Application Engine, what about the mobile application? It’d make perfect sense to move it to Android as well. […]
April 13th, 2008 at 2:37 pm
Marcel Says:
I need a invitation please! my mail is umbrella.m@gmail.com
April 15th, 2008 at 3:52 am
Fábio Says:
Jaiku+orkut= brazilian happy!
April 19th, 2008 at 7:54 pm
Jyri Says:
Jarkko Laine: Jaiku is written mostly in Python
April 20th, 2008 at 8:12 pm
Mantas Vidutis Says:
Can we finally have a working US SMS system?
April 25th, 2008 at 4:34 am
Giselle Says:
Dear Jaiku/Google/Jaikusers,
Please, could you send me an invitation to Jaiku? I requested an account a while ago but no luck. My immersion in web 2.0, I feel, can’t progress until I get a Jaiku… :\
With sugar on top, make my week! giselleg@gmail.com
Thanks,
fellow web junkie and social networking geek,
Giselle
April 27th, 2008 at 9:03 pm
What’s been happening at JaikuInvites? | jaiku invites Says:
[…] Also one or two of you have asked what will happen to us when Jaiku opens, well I hope to keep bringing all the latest Jaiku news here and until the opening we will keep helping you to share those invites. I mite also have some new surprises for you too. […]
April 29th, 2008 at 6:12 am
Is Jaiku now a 20% time project? | jaiku invites Says:
[…] After a little further digging into it I discovered this thread on Jaiku in Finnish which is talking about the talk that @teemu gave in a Helsinki University. The basic gist of it is some of the students talking about what @teemu had said. He then comes on to clear a few things up (sorry about the rough translation see the original here. Please correct me if it’s wrong.) Let me correct some possible misunderstandings, Jaiku will continue its existence and Jaiku is being ported to the Google App Engine . Its porting will make the expansion of the user numbers possible in the future, so that joining without an invite will be possible. The Port is in part worked on full-time but we are also working in part on something new. […]
April 29th, 2008 at 6:07 pm
Behrang Says:
If I am not wrong Google’s policy only allows use of Java, Python, C, and JavaScript. So I guess your are moving the codebase to Python. Actually what is the current architecture of Jaiku?
May 2nd, 2008 at 6:53 pm
IDidntGetIn Says:
Hi! I have a few ideas for jaiku.
Would it be possible to have more benefits and features if the user has their jaiku’s visible to the public instead of their contacts only?
Another one would being able to choose an option on post your jaiku entrys either to the public, contact’s only, or to yourself.
So if hardcore privacy fans don’t like first idea then they can get around it by posting their entries to contacts only.
Last one would be if a user like this channel alot, there would be one more list feature to the right to tell what channel the user is subscribed to. There should be an option to display it or hide it.
May 12th, 2008 at 9:56 pm
spongefile Says:
Those of you looking for invites to Jaiku, go see www.jaikuinvites.com
May 18th, 2008 at 12:00 pm
rjones Says:
Too little. Too late.
Most everyone has already moved to Twitter.
May 24th, 2008 at 5:25 am
Notes for 4/13/2008 at MasterMaq’s Blog Says:
[…] There were two really big tech stories this week: the launch of Flickr Video, and the launch of Google’s App Engine. Haven’t had a chance to play with either of them yet. Flickr Video looks exciting based on what I’ve read so far. Google-owned Jaiku announced it is moving to App Engine. […]
May 29th, 2008 at 1:27 am
Google Dropped the Ball on Jaiku | sarahintampa Says:
[…] However, following the acquisition by Google, the silence was deafening. The usually highly responsive dev team didn’t post nearly as often. The API went missing in action a number of times. The normally rock solid service often either crawled to a halt or regularly reported 503 gateway errors (a database problem). The blog went quiet, although the developers raised their heads above the trenches in January of this year to proclaim “big things are coming” (‘We’ve joined Google. Now what?’). In April it was announced that Jaiku was being ported to the Google App Engine, which goes someway to explaining the lack of development. Unfortunately, the momentum was lost. Users started to slip back to Twitter. Developers just didn’t seem interested in taking advantage of the API so there no was no widespread developer ecosystem like the one that sprung up around Twitter. […]
May 29th, 2008 at 7:00 pm
Twitter vs. FriendFeed vs. Jaiku | Michael Koby (mkoby.com) Says:
[…] So to answer Mr. Scoble’s question, the reason that Jaiku is not discussed as a Twitter competitor is primarily due to its invite only status. About 6 months ago, when I first got into the micro-blogging, I used Jaiku exclusively and they had their own set of downtime issues. However, these might get resolved with Jaiku moving the Google App Engine. However, the larger issue is that people can’t really use service because they need an invite to be a part of the conversations that take place there. […]
June 2nd, 2008 at 3:43 pm
What About Jaiku? at BLAME SCOBLE Says:
[…] Back to Jaiku; I’m sure there is more in store for Jaiku in the future. It is being ported to Google’s App Engine, so that will almost certainly provoke a spike of interest when it’s complete. Jaiku is also still an “invite only” service at this point. When the door is opened up a little wider, I think we’ll see some more activity and buzz about Jaiku. […]
June 6th, 2008 at 12:48 am
Moved from Twitter to Jaiku | SYP Says:
[…] Or maybe it is not necessary. As of yesterday I am now updating my status on Jaiku (thanks to Glenn for giving me the invite). Currently you can’t sign up new account there but hopefully soon after they have moved to Google AppEngine. At least their IM bot works… […]
June 11th, 2008 at 5:16 am