This seems to be working ok again, at least API wise. Tom
On Fri, Mar 12, 2010 at 12:02 PM, Andrew Badera <and...@badera.us> wrote: > Note some users also appear to have to clear cookies and sign back in, > in addition to unchecking the location option. > > --ab > > > > On Fri, Mar 12, 2010 at 6:56 AM, Andrew Badera <and...@badera.us> wrote: > > This is also preventing posting from web UI if user has location > > option checked in settings. > > > > ∞ Andy Badera > > ∞ +1 518-641-1280 Google Voice > > ∞ This email is: [ ] bloggable [x] ask first [ ] private > > ∞ Google me: http://www.google.com/search?q=andrew%20badera > > > > > > > > On Fri, Mar 12, 2010 at 6:49 AM, Thomas Woolway <tswool...@gmail.com> > wrote: > >> Yes, we're (TweetDeck) having the same issues, and it looks like Tweetie > is > >> as well - looks like something may have broken last night when rolling > out > >> the new geo features? > >> Tom > >> > >> On Fri, Mar 12, 2010 at 10:20 AM, Rich <rhyl...@gmail.com> wrote: > >>> > >>> I'm seeing this too, whenever I send a lat or long parameter I get a > >>> 502 error and can't post any geo location tweets > >>> > >>> On Mar 12, 8:59 am, janole <s...@mobileways.de> wrote: > >>> > Hi, > >>> > > >>> > I cannot send geotagged tweets via Gravity anymore. I'm always > getting > >>> > an HTTP 502 Bad Gateway error. > >>> > > >>> > Without attaching the lat/long vars, it's working. > >>> > > >>> > Strangely, I cannot send updates via the website either (twitter.com > ). > >>> > > >>> > @janole > >>> > > >>> > -- > >>> > Jan Ole Suhr / Gravity S60 Twitter Client > >>> > o...@mobileways.de > >> > >> > > >
