Oh, it was only the other day, we were wondering what happened to the data generated from Jaiku users naming cell towers. Although probably a lot of work to clean, it would be fun to get hold of :)
@lemonad Unfortunately a lot of it was thrown away as we did not keep full logs of presence (the client produces a lot of data) :-(.
We have bits of the logs, you could ask @termie (since I'm not at Google anymore I don't have access to any of that data).
Also, it's not clear whether users who have not always been public are ok with past data being published and we don't keept track of changes to visibility :-(
For all that, I think I'll have some exciting news within a couple of days.
Cool! At least I have some information on the subject now. Without per-change visibility status it would be tricky to release. It would definitely not be enough to check the private/public status of today.
Very much looking forward to hearing the news! Thanks for the reply! :)
It would be really cool if it could be released to specific users asking for it — although I realize it could potentially end up being a lot of work for @termie.
From this afternoon the Jaiku client uses the Google geolocation backend for positioning. From now on the 'city' and 'neighbourhood' in the client will be automatically filled based on the 'city' and 'street' and 'postal_code' from Google geolocation.
This works with the clients you already have installed.
(note that the location lookups are piggybacked on presence that is sent so it's not always up to date immediately when you move to new areas due to rate-limiting)
also, on a more general level, is there anyway to display this info outside the site? i see that the badges no longer work - has anyone used the appengine to take my status & location and display them like old "location" area did on (user).jaiku.com. would be nice to have that for display in facebook or on a site.
The turning of cellids to placenames for the Jaiku mobile client is done by specific permission from Google. That API is otherwise only available to Gears. The resulting location data and its storage in Jaiku are free to use.
All the calls that the Jaiku client uses (through it's front-end) are exposed via the JaikuEngine API. However, some of them are classed as private - that means that the API has no stability guarantees. See http://code.google.com/p/jaikuengine/source/browse/trunk/common/api.py#3521 - the relevant calls are presenceset and presenceget
19 comments so far
Oh, it was only the other day, we were wondering what happened to the data generated from Jaiku users naming cell towers. Although probably a lot of work to clean, it would be fun to get hold of :)
4 months ago by lemonad
@lemonad Unfortunately a lot of it was thrown away as we did not keep full logs of presence (the client produces a lot of data) :-(.
We have bits of the logs, you could ask @termie (since I'm not at Google anymore I don't have access to any of that data).
Also, it's not clear whether users who have not always been public are ok with past data being published and we don't keept track of changes to visibility :-(
For all that, I think I'll have some exciting news within a couple of days.
4 months ago by mikie
Cool! At least I have some information on the subject now. Without per-change visibility status it would be tricky to release. It would definitely not be enough to check the private/public status of today.
Very much looking forward to hearing the news! Thanks for the reply! :)
4 months ago by lemonad
So the location logs from the old S60 client is connected to respective user? Then I would really be interested in getting my own data somehow.
4 months ago by moonhouse
We only have parts of those logs. Talk to @termie.
4 months ago by mikie
@mikie: OK! Thanks, I will.
4 months ago by moonhouse
I'll ask @termie sometime when he's not too busy.
It would be really cool if it could be released to specific users asking for it — although I realize it could potentially end up being a lot of work for @termie.
4 months ago by lemonad
interesting... and curious about the news :)
4 months ago by cybette
The news is...
From this afternoon the Jaiku client uses the Google geolocation backend for positioning. From now on the 'city' and 'neighbourhood' in the client will be automatically filled based on the 'city' and 'street' and 'postal_code' from Google geolocation.
This works with the clients you already have installed.
(note that the location lookups are piggybacked on presence that is sent so it's not always up to date immediately when you move to new areas due to rate-limiting)
4 months ago by mikie
@mikie: That's awesome! Very cool! Do you have any idea when you would be able to release the new build to the public?
4 months ago by lemonad
I should be able to get it signed within 2 weeks.
4 months ago by mikie
woot!
4 months ago by termie
I wholeheartedly second @termie's woot!
4 months ago by lemonad
@mikie: fantastic!
also, on a more general level, is there anyway to display this info outside the site? i see that the badges no longer work - has anyone used the appengine to take my status & location and display them like old "location" area did on (user).jaiku.com. would be nice to have that for display in facebook or on a site.
4 months ago by dw
third the woot!
4 months ago by cybette
Will posts also be marked with their location?
4 months ago by ralphm
forth the woot!
4 months ago by ymb
will an android app be able to interact with this? or can apps like pingfm that now can use this info, be able to set the location?
4 months ago by BUGabundo
The turning of cellids to placenames for the Jaiku mobile client is done by specific permission from Google. That API is otherwise only available to Gears. The resulting location data and its storage in Jaiku are free to use.
All the calls that the Jaiku client uses (through it's front-end) are exposed via the JaikuEngine API. However, some of them are classed as private - that means that the API has no stability guarantees. See http://code.google.com/p/jaikuengine/source/browse/trunk/common/api.py#3521 - the relevant calls are presenceset and presenceget
4 months ago by mikie