Chris's dashboard

Jud started following the question "Fire Eagle integration" in Loopt.

Chris replied on October 05, 2008 07:55 to the question "Fire Eagle and changes in the way lat/long placemarks are defined" in Brightkite:

On another probably related note, I checked in a while ago at <http://brightkite.com/places/b3581dcb...>, and Fire Eagle wasn't updated at all.

RAD Moose replied on October 04, 2008 05:19 to the question "Will more invites be available soon?" in Brightkite:

DOH! (I use FireEagle too!)

Awesome.. Thanks! =)

Chris replied on October 04, 2008 04:19 to the question "Will more invites be available soon?" in Brightkite:

You can get one by going to http://fireeagle.yahoo.net/gallery and clicking on the Brightkite link.

Chris replied on October 04, 2008 04:17 to the question "Fire Eagle and changes in the way lat/long placemarks are defined" in Brightkite:

On a (probably) related note, if I check in at a U.S. airport by searching for the airport code, Brightkite will update my Fire Eagle location to "USA," rather than the actual location of the airport. For example, I just tried checking in at DFW, and when I went to Fire Eagle, they had my location as "somewhere in the USA."

Chris asked a question in Brightkite on October 04, 2008 04:10:

Fire Eagle and changes in the way lat/long placemarks are defined

I've defined some locations for hotels outside the U.S. where I frequently stay, using lat/long coordinates. Here's one:

http://brightkite.com/places/3af038ec...

And here's another that I defined a number of weeks later:

http://brightkite.com/places/9788c228...

Note that in the first case, the location shows the name I defined, along with the lat/long coordinates in parentheses. The second shows the name I defined, but in parentheses it shows only the country code of the location (PH). The latter behavior (country code only) seems to occur with all the new locations I've created this way.

One problem is that when Brightkite updates Fire Eagle with one of these new locations, it updates the location not with the lat/long coordinates but with the country only, as if I'd gone to Fire Eagle and simply typed in "Philippines" as my location. This puts me at a considerable distance from my actual location.

Is this a bug, or is something else happening that I don't understand?

Dan F. started following the question "Fire Eagle integration" in Loopt.

A comment on the problem "Rate limiting on non-authenticated requests" in Twitter:

Afaik, requesting to be whitelisted is the only way to work around the API limit. Kindly see Joel's reply above yours for more info. – mdy, on September 22, 2008 00:34

Chris replied on September 21, 2008 20:03 to the problem "Rate limiting on non-authenticated requests" in Twitter:

So it appears that I can't write an application on Google App Engine that accesses the Twitter API. The very first request I made put me over the limit, so presumably other people on Google App Engine and the same IP address are also making Twitter API requests. Is there a way around this?

Todd Jones replied on September 21, 2008 19:05 to the idea "Location Support" in Ping.fm:

Would love to see the recent posts show recent locations, or maybe a separate tab for that

A comment on the idea "Location Support" in Ping.fm:

Done! – Sean, on September 21, 2008 18:37

A comment on the idea "Location Support" in Ping.fm:

It would be great if this was extend to Jaiku! – blueheron, on September 21, 2008 17:38

A comment on the question "Did location naming break?" in Brightkite:

You're right, though as it's documented in this thread there's no whitespace either. And I've created them without using whitespace before. In any case, it works with the whitespace, so I'll do it that way. Thanks. – Chris, on September 21, 2008 13:52

Carnager replied on September 21, 2008 13:47 to the question "Did location naming break?" in Brightkite:

I don't see a whitespace between the geographic location and the opening bracket ([)

eg.
You post:
25.033215,121.559365[The Tavern, Taipei]

How about:
25.033215,121.559365 [The Tavern, Taipei]

Chris asked a question in Brightkite on September 21, 2008 12:47:

Did location naming break?

I wanted to create a named location, so I did a search for "25.033215,121.559365[The Tavern, Taipei]." I've done this before with the expected result, but this time the bracketed name seems to have been ignored. Did something change, or am I spacing out and doing something wrong?

Andrew Shuttleworth replied on September 20, 2008 06:42 to the idea "Location Support" in Ping.fm:

ping.fm now has location updating features: http://ping.fm/blog/a-great-day-for-n...

I added a new idea for a trigger for location updates: http://getsatisfaction.com/pingfm/top...

Sean replied on September 18, 2008 00:40 to the idea "Location Support" in Ping.fm:

Oh, it's coming!

John359 replied on September 13, 2008 20:02 to the question "WAY off" in Loki:

Its happening again. It says that I am out side the coverage area! I am in side it.

Ryan Sarver replied on September 04, 2008 14:51 to the problem "Firefox 3 does not allow the toolbar to be installed because "it does not offer secure updates"" in Loki:

Hey guys, just posted a new update that supports PowerPC users. You have to grab it off the Mozilla Addons site:

https://addons.mozilla.org/en-US/fire...

A comment on the problem "Firefox 3 does not allow the toolbar to be installed because "it does not offer secure updates"" in Loki:

This may happen if you're not logged into the Firefox Add-ons site; try creating an account and logging in, the downloading the extension. – Chris Lawrence, on September 01, 2008 06:16