Digitprop's dashboard

A comment on the question "Fire eagle updates are they bi-directional?" in Brightkite:

Well, checked again and saw that the infinite loop still occurs with exactly identical locations. This was due to a bug in the code that tested for identical solutions. Fixed that, so it should work better now. I would still recommend against activating updates in both directions. – Digitprop, on September 09, 2009 20:15

A comment on the question "Fire eagle updates are they bi-directional?" in Brightkite:

Yes, sorry for the flood - I got the same when I activated updates in both directions for testing purposes. The problem is that due to the privacy filters - which can adjust the level of detail on both sides - the location stored in FE and the one stored in BK may actually be DIFFERENT. Then, when BK updates FE, the bridge will see a new location (although close to the previous one, of course) and so on. – Digitprop, on September 09, 2009 19:25

Digitprop replied on September 06, 2009 12:22 to the question "Placemark privacy settings not respected when checking in through Fireeagle/API?" in Brightkite:

Hi,

I have now looked into this in more detail. It seems that unfortunately the FireEagle API does not provide information on which application last updated a location (although this information is shown on your personal FE page when you sign in). Therefore, it is impossible for me to distinguish between BK and non-BK updates.

The only solution for the time being is to turn off BK -> FE updates, like you did, Balaji Dutt. I will add a warning to the BK/FE bridge site.

Digitprop replied on September 03, 2009 12:47 to the question "Placemark privacy settings not respected when checking in through Fireeagle/API?" in Brightkite:

Sorry - I think Lesley is spot on. Actually I hadn't accounted for a bidirectional link where FE would be updated from Brightkite. Therefore, there is a constant loop of updating between the two, and it might well be that this is the cause of your problem.

I will look into this and try to find a way to filter Brightkite updates from the FireEagle locations. Let's see.

I would assume that yes, if you don't allow BK to update FE, then the problem should not occur (neither the looping nor the privacy problem).

As for the privacy issue, I believe it must be related to the looping. Other than that, I cannot see where the FE/BK bridge would come into play. It retrieves the FE location with whatever accuracy you allowed, then sets it in BK. BK should then take care of the privacy level.

The bottom line is that making the updates monodirectional, from FE to BK, should solve the problem; and I will look into whether I can filter FE location updates that came from BK.

Cheers,
Markus

A comment on the idea "Please make BrightKite ROCK!" in Brightkite:

Cadill: I know what you mean. However, this is a small web app I cobbled together in a day, and is by no means intended to interfere with BK's own plans. As soon as BK has its own mechanism for pulling in information from FE, I will be happy to take it down. And BK can, too, if they feel it's a problem (I don't think they do, as it adds value to BK). After all, the app had to be registered in order to access the API. In any case, this is just a temporary workaround. – Digitprop, on August 25, 2009 07:40

Digitprop replied on August 24, 2009 14:31 to the idea "Please make BrightKite ROCK!" in Brightkite:

It just so happens that I've tapped into FireEagle's and BrightKite's respective APIs, and I have create a Fire Eagle / BrightKite bridge which pulls your location from FE and sets it in BK. Here's the URL:

http://geo.digitprop.com/aggregator/

This is of course not really scalable, as it polls the FE location for each registered user every 5 minutes, but for the time being it works.

Digitprop replied on August 24, 2009 14:31 to the idea "Why isn't brightkite retrieving my location from Fire Eagle?" in Brightkite:

It just so happens that I've tapped into FireEagle's and BrightKite's respective APIs, and I have create a Fire Eagle / BrightKite bridge which pulls your location from FE and sets it in BK. Here's the URL:

http://geo.digitprop.com/aggregator/

This is of course not really scalable, as it polls the FE location for each registered user every 5 minutes, but for the time being it works.

Digitprop replied on August 24, 2009 14:30 to the question "Fire eagle updates are they bi-directional?" in Brightkite:

It just so happens that I've tapped into FireEagle's and BrightKite's respective APIs, and I have create a Fire Eagle / BrightKite bridge which pulls your location from FE and sets it in BK. Here's the URL:

http://geo.digitprop.com/aggregator/

This is of course not really scalable, as it polls the FE location for each registered user every 5 minutes, but for the time being it works.

Digitprop replied on August 11, 2009 14:43 to the problem "No more similar faces?" in Polar Rose:

Same with me. After having tagged about 800 photos, I get single photos with no similars, although some of them are actually even duplicates, i.e. identical bitmaps.

This happens while Flickr Uploadr is adding about 2000 photos to a set. Maybe this is a timing issue / race condition where the matching algorithm takes in the newly added photos and doesn't detect matches while that's happening.

Or the algorithm cannot catch up with my tagging pace ;-)

Digitprop started following the problem "No more similar faces?" in Polar Rose.

Digitprop started following the problem "No more similar faces?" in Polar Rose.

Digitprop started following the problem "No more similar faces?" in Polar Rose.

Digitprop started following the question "GPS to update Brightkite?" in Brightkite.

Digitprop started following the idea "Please make BrightKite ROCK!" in Brightkite.

Digitprop shared an idea in Brightkite on July 23, 2009 14:44:

Why isn't brightkite retrieving my location from Fire Eagle?

I have set up my GPS-enabled phone to update my location in FireEagle daily. Looking at the FE API, it shouldn't be difficult to update brightkite with that information. Would be much more convenient than typing it in etc.

After all, that's the whole idea behind FireEagle - update once, get location information in a number of apps.