Hung over and using Textmate, Imity user Rasmus built himself the until now missing Imity client for Nokia’s N73.
We will, of course integrate it into the official distribution. Until then, If you’re annoyed with the Generic Imity on your N73 (some of them seem to be fine, though), go ahead and try Rasmus’ build (look for ‘xImity’).
Works fine on my N73 ME V 3.0705, only missing detection of “fire button”, use Options > View instead.
Want to roll your own Imity, too?
[UPDATE: Hiya - yeah I know, the servers not liking itself so much this tuesday morning. I’m looking at it]
Some of you (OK - a lot of you) have been complaining about missed meetings because of failed saving to the server. People you know you met and know the imity client picked up did not end up in your journal. Over the weekend I discovered some bad configuration on the server and I just tested and updated an improvement of the server code.
This should remove a whole lot of these experiences.
Sidenote: Yes, various enhancements to the actual application - what you can do with Imity are also ready Real Soon Now.
I’ve updated the mobile app version as previously mentioned (and somewhat delayed) with a new version that does internet usage counting (visible in more|stats) and also provide some more helpful message screens during logins - so you can tell if it’s your password we don’t recognize of if you’re just not getting through to the server:
Next in the client: Econo-mode submission that will save on bandwidth by not updating the client with server information.
Next on the server: An overhaul of the events feature to get that ball rolling.
Ricki just put up a quick Build instruction for building your own Imity client for on Mac OS X. It looks easy.
As of today, our phone client is open source. New features, bug corrections, builds for new phones, it’s all open for your mad Java skills (or whatever you feel like porting to).
It’s a bit rough in the edges. Build instructions, final licenses, and a brand new release with a traffic counter are among the things that Claus will be adding to the project today and tomorrow. Meanwhile, make sure to visit the Imity client open source Wiki - it’s being updated as you read this.
Last night, Morten passed my on the street, riding his bike. I was walking in the opposite direction. The short encounter was long enough though, for Morten to get an alert on his Imity client that I was around.
Also today, I noticed a username I hadn’t seen before on the top 10 for the day.
I looked up the profile. Turns out we had past history - Yann was at Le Web when I was there and of course Nikolaj was there too.
It’s great to see Imity do exactly what we hoped for: Easy and effortless, direct and personal connections.
Good to meet you again, Yann!
We’ve had a couple of questions (and user reports) about how much data traffic Imity actually consumes, and there’s a couple of things I’d like to say about that.
First things first: I’m adding a traffic counter to the mobile application right now - and that will be available this week, so you can tell howmuch data we’re trying to send over the network.
Second: It’s a little bit tricky to “do the right thing” here: The whole purpose of the app is to save your life history to the web, which obviously consumes traffic, so it’s always going to have a traffic cost if you don’t have a flat data plan.
We haven’t in regular use had problems amoung the founder/developers in this regard - but we are no longer our heaviest users.
Third: There’s a conflict of interest here between the quality of the log and the cost of transmission. Some of the reports we get are from users unhappy with holes in their logs.
Fourth: A lot of the traffic issues are outside our control. I realize that stability at our end is an issue and very important. It’s clear from the blog that we could have hoped for more for the first couple of weeks. I’m working to make that as good as I can - but experience tells us that network stability is a huge issue with the mobile internet. It’s not even that we can recommend specific carriers. We have found connectivity to be very different as you move from cell to cell even and that’s across several carriers here in the Copenhagen area.
What I’m looking into now, along side metering, is a good solid way to save observations for later submission and I’m working to make it much more visible in the app how many networking problems we’ve been having for your phone/carrier/location combination and how much of your life history is stuck on your phone for later submission. Stay tuned for an update.
UPDATE: Sorry about the slight delay - I plan/hope to have a client out with a new econo-mode for long term in-pocket use tomorrow.
Sorry to say we’re having a spell of database trouble today (and last night). I’m trying to figure out why the server won’t stay available and will get back to you as soon as possible.
UPDATE:
Seems the server is in deeper trouble than that. I’m working on a fix.
UPDATE II:
Seems we’re back up again. I’m looking into the instability but I can’t really give you a timeline just yet.
Nikolaj was at DLD this week and as a nice consequence of that, this very nice blogpost on Imity and some of the perspectives on experiments like ours. We’re very open indeed to a lot of the perspectives Stephen points out.
Just to clear up any possible confusion: Stephen’s “only be open to registrations for a week or two” is a typo. We’re planning to be here and be as open as humanly possible for a very long time (recent server problems notwithstanding).
And just to be extra special clear: We like everything you say about us. Tell us what you think.
We’ve had a little server instability wednesday and today. I do apologize.
Point your 