maemo.org - Talk - [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

maemo.org - Talk (https://talk.maemo.org/index.php)

- Applications (https://talk.maemo.org/forumdisplay.php?f=41)

Re: *ZapLoc* - Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;) - testers wanted

Quote:

Originally Posted by jpala16 (Post 1009513)

Same here. It says authenticated. I haven't tried if it works (Facebook Places) yet as I'm not willing to post where I have been on Facebook, as I don't want to let half the people there know where I have been. Is that what it does, I'm right?

If searching for places via FB works you are authorized correctly.
If not delete facebook.dat from /home/user/.zaploc and reauthenticate using MicroB.

But why using this app with FB if you don´t want to check in to places???

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

Quote:

Originally Posted by petur (Post 1009502)

Right now, the daemon is going mad.... the gps icon goes on/off with a rate of 1/sec. And I don't mean it is blinking, it is actually enabling/disabling location services, as the drop-down statusmenu constantly redraws itself to show/hide the location icon.

edit: log attached:

Code:

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

Starting GPS...

2011-05-18 23:02:43: Got loc data 51.034139,3.713658 (acc 96.017000) 

alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0

Updates within 100 meters - not sending

2011-05-18 23:02:43: General location update 51.034139,3.713658 (acc 

96.017000)

Searching for closest spot:

Sleeping GPS for approx. 0 minutes

^CTraceback (most recent call last):

  File "/opt/zaploc/app/zdaemon.py", line 295, in restart_gpsd

KeyboardInterrupt

2011-05-18 23:02:44: Got loc data 51.034139,3.713658 (acc 96.017000) 

alt nan (32767.500000), head nan, speed nan, Mode 2, Try 0

Updates within 100 meters - not sending

2011-05-18 23:02:44: General location update 51.034139,3.713658 (acc 

96.017000)

Searching for closest spot:

Sleeping GPS for approx. 0 minutes

2011-05-18 23:02:45: Got loc data 51.034139,3.713658 (acc 96.017000) 

alt nan (32767.500000), head nan, speed nan, Mode 0, Try 0

^CTraceback (most recent call last):

  File "/opt/zaploc/zaploc-daemon.py", line 8, in <module>

    if __name__ == '__main__': app.zdaemon.main(sys.argv[1:])

  File "/opt/zaploc/app/zdaemon.py", line 470, in main

  File "/opt/zaploc/app/zdaemon.py", line 337, in init

KeyboardInterrupt

Hmm, somehow you've managed to configure the time to 0 minutes? Or have you tried the new command line options?

You can do

Code:

python /opt/zaploc/zaploc-daemon.py -i 5 --cell

...for example. Clearly somehow you've gotten your update time set to 0 minutes.... not sure how you did that. :)

EDIT: Ok I undersand what you did: You tried the "udpate only when cell tower changes" mode? That is NOT WORKING yet. It will actually, indeed, set the update rate to 0. DON'T USE THAT YET!!

Old text you can forget:
I'd go into the setup in ZapLoc and change the value, then restart the daemon in -v mode to see what it says it's delay is.... if that doesn't work, I'd kill /home/user/.zaploc/config.dat and see if that helps.

/Z

Re: *ZapLoc* - Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;) - testers wanted

Quote:

Originally Posted by Reflektorfalke (Post 1009490)

yap. I set Opera as default browser using browser switchboard. It opened and said "Authenticated, you may close this window now..."

Okay, that's interesting. This means the callback got to the app properly... but maybe the auth-token didn't. I don't think I do much testing if the auth-token is really there and working before I pop you over to the "you may close this window" page. Hmm.

Quote:

After closing the progress bar in Zaploc seemed to go on forever, but after closing and restarting Zaploc showed FB as authenticated, but obviously it was not...

This is a sign of something crashing after it has received the callback, so I'm guesstimating it's hung up on trying to extract a nonexisting auth token... or somesuch.

I'll try to reproduce, and see what I can do. For now... well.... avoid Opera Mini for auth? :)

/Z

Re: *ZapLoc* - Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;) - testers wanted

Quote:

Originally Posted by Reflektorfalke (Post 1009541)

I realize there is a possibility for a misunderstanding here that I hadn't thought about: When you choose the "Facebook" or "Twitter" checkboxes when checking in, it's not really ZapLoc that is tweeting nor facebooking (with the exception of explicitly using Facebook Places), it is the service itself. So checkin e.g. "Twitter" in a Gowalla spot, it is actually Gowalla that is told to tweet.

So if you are not using FB Places, you don't need to authenticate with Facebook at all, if you don't want to. It may still be interesting to LOOK at FB places, even if you don't plan to check in to them.

/Z

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

wow, awesome, will give it a try.

Re: *ZapLoc* - Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;) - testers wanted

Quote:

Originally Posted by Reflektorfalke (Post 1009541)

I'm learning what those things are. I'm searching for information at this time. Didn't get that Facebook Places is different than posting your current location to Facebook.

I use this app for Google Latitude. It works fantasticly. But now I want to know what the other features are, what do they imply for my privacy and all that stuff.

Thanks again for your work MasterZap. Keep it up! :)

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

Quote:

Originally Posted by MasterZap (Post 1009692)

EDIT: Ok I undersand what you did: You tried the "udpate only when cell tower changes" mode? That is NOT WORKING yet. It will actually, indeed, set the update rate to 0. DON'T USE THAT YET!!

bingo.....

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

Quote:

For now... well.... avoid Opera Mini for auth

Btw, this seems to be a "known" issue with not using microB for authorisation? Atleast there are other apps which explicitly state this:
http://talk.maemo.org/showthread.php...ghlight=microb

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

Just wanted to let you know that so far everything seems to be working well with the newest version, and the command line options are amazingly useful :)

Keep up the good work!

Re: [Announce] ZapLoc - a Gowalla/Foursquare/Facebook places/Latitude aggregator - "All your location based services are belong to us" ;)

I just had ZapLoc stop updating Latitude again - it is set to check every 5 minutes and update at least once per hour. Current latitude data was 2 hours old, so I decided to start de daemon in the terminal to check, and it told me it detected and killed the running version.

So the daemon isn't crashing, but why is it stopping the updates?

How to go about to debug?