gwibber-bugs team mailing list archive

[Teester <803149@xxxxxxxxxxxxxxxxxx>]

I am working on this but I was unaware of this particular bug report
until yesterday.

Foursquare's changes seem to be two fold. Firstly, they're moving
everything to use oauth and getting rid of the password method of
authenticating. Secondly, they're moving from API version 1 to version
2.

I've been struggling to figure out how their implementation of oauth
works for what feels like 6 months.  Fortunately, in the past couple of
days, I've had a breakthrough.  At this point, I can authenticate with
foursquare, so part 1 is done, but I have not yet transitioned the api
parts from version 1 to version 2.  Hopefully, if I get time in the next
day or so, that should be done too, at which point, I'll attach a branch
for consideration.

** Changed in: gwibber
       Status: New => In Progress

-- 
You received this bug notification because you are a member of Gwibber
Bug Heros, which is subscribed to Gwibber.
https://bugs.launchpad.net/bugs/803149

Title:
  Your foursquare client is out of date

Status in Gwibber:
  In Progress

Bug description:
  Today I started getting status updates from "Jimmy Foursquare" that
  "Your foursquare client is out of date! If you don't upgrade before
  August 1st it will stop working."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwibber/+bug/803149/+subscriptions