Get your own customer support community
 

The BKite bridge to Twitter is misbehaving. Insight please.

Twitter and BKite connection lacking recent update; request some insight on my end.

I really want to utilize the BKite concept and hook to Twitter. Many of my friends do with much success. In reading your posts, I switched my settings from City to to all for Trusted Friends, Friends, Everyone and I still only see the City when checking-in. The include post is old and has no update.

(1) Can you tell me why when I allow Everyone else to see full information and I am set to Private, Twitter fails to get the $place correct?
(2) How far along are you with getting Twitter to be a trusted friend/friend?
(3) How come BKite fails to update Twitter (you have a few posts on this from a month ago, but no follow-up posts on what your research uncovered? I started seeing this situation this evening.

Appreciate your input. Until these matters are resolved, BKite will remain a limited access site for me, sadly.
 
sad I’m Frustrated and Concerned
Inappropriate?
1 person has this question

  • Inappropriate?
    Hi Bill,

    1) The reason that some check ins only have city info is partly due to some bugs on our end and partly due to some issues on Google's end. We pull all of our data from Google Maps and the street, city, state, country info that we send to Twitter depends on the info that we receive from GM and sometimes that info doesn't match up quite right or is missing altogether.

    For your most recent check in, it did send the place name to Twitter, but failed to send the $state and $country info.



    My best guess is that even though it has MN in the listing, we did not actually receive the state info from Google (and the country info is missing), which is why we couldn't send it to Twitter along with the place name.

    If you compare to my check in this morning:



    you'll see that there is a lot more info included in the listing for the Brightkite HQ (street, city, state, zip, country), which is why it sent all of the check in info to Twitter.

    2) Unfortunately we don't have an ETA on this just yet. It will take quite a bit of work on the back end to do this and we're currently tackling some bigger projects.

    3) These issues with Twitter are usually due to connection problems with their API. Even if the site is up, we may still have trouble connecting to the API. This could also be caused by users exceeding their hourly API limit, especially if you use other Twitter apps in addition to Brightkite. We've tried to make this as robust as possible on our end.

    If you can, try a few check ins throughout the day, at exact locations if possible, and see if the problem remains consistent for each check in. If so, we can check it out to see if there is anything weird going on on our end.
     
    happy
User_default_medium