Apply location updates to THAT post

I've notticed that when using the @l feature ping.fm updates your location AFTER updating your status. This doesn't make much sense. If I'm updating my location I'm probably already there. Is there anyway this could be fixed?

I’m annoyed

Inappropriate?

Reply to this idea

3 people like this idea

I like this idea! Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.

The company implemented this idea.

Create a customer community for your own organization

Plans starting at $19/month

EMPLOYEE

Remove Inappropriate?
Delete or Edit

Adam, Official Rep, replied on October 16, 2008 04:51

This has been a problem for a while. We do check in the location first.

http://getsatisfaction.com/pingfm/top...

I will try adding a delay between the checkin and message to see if that helps.

I’m delayed

this is one of the best points

1 Comment Add a comment This is one of the best points Mark as a company good point
Remove
Aaron Goodwin commented on October 16, 2008 04:56

Thanks Adam! I hope that does the trick.
Remove Inappropriate?
Delete or Edit

Jonathan M. Lane replied on February 26, 2009 16:10

I sent a "Update content... @l location" string to the Ping.FM XMPP bot, which processed the request (Recent Post on the web interface showed it a few moments later).

However, Brightkite posted my note with the location caption being "about location..." instead of the usual "@ location...", and there was no check-in before the post. I waited a few minutes and refreshed, but saw no update, so manually checked-in on Brightkite myself. See here: http://brightkite.com/people/jmlane

Is this the expected behaviour? If so, do I have to update Ping.FM with something like "@bk @l location..." to force a Brightkite check-in ONLY (no note) through Ping.FM?

I’m undecided

this is one of the best points

Add a comment This is one of the best points
EMPLOYEE

Remove Inappropriate?
Delete or Edit

Adam, Official Rep, replied on February 26, 2009 20:35

@l location should check you in first, then make your message about the location. I was able to test and reproduce your problem. This appears to be a problem or change on brightkite's side. I reported it to them so hopefully we can work it out soon. Thanks for reporting!

I’m bright

this is one of the best points

2 Comments Add a comment This is one of the best points Mark as a company good point
Remove
Jonathan M. Lane commented on February 26, 2009 20:38

My pleasure. Thanks for having a great product.

Did you report the bug via getsatisfaction? If so, a link to the new issue might be nice to keep an eye on this one.
Remove
Adam, (Official Rep), commented on February 26, 2009 21:15

I used their developer forum since it was an API related problem: http://groups.google.com/group/bright...
EMPLOYEE

Remove Inappropriate?
Delete or Edit

Adam, Official Rep, replied on March 03, 2009 22:03

Should be fixed now. let me know if it gives you any more problems.

I’m checking in

this is one of the best points

1 Comment Add a comment This is one of the best points Mark as a company good point
Remove
Jonathan M. Lane commented on March 04, 2009 17:42

Thanks a lot. I will report any issues I run into.