Why the hell is it so hard to use the BOSS Placefinder API?
So, we were using the old (now deprecated without warning) PlaceFinder API, which worked great. So now we're trying to figure out how to use OAuth with PlaceFinder. Is anyone else here confused as hell on how to do this? There are no clear examples (this: http://developer.yahoo.com/boss/search/boss_api_guide/codeexamples.html does not work for me), and the step-by-step OAuth instructions (http://developer.yahoo.com/oauth/guide/oauth-auth-flow.html) don't make any sense if all I want to do is a simple geolocation call.
Simply put, there are no clear instructions/examples on how to use the PlaceFinder API call. I've tried using the get_token_request to get a token secret, but that always gives me an 'signature_invalid' error. (I've tried both PLAINTEXT and HMAC-SHA1 signature methods.) I've also tried using an empty string for a token secret, but of course to no avail.
This is really terrible...I can't imagine that anyone at Yahoo actually tried to set up a PlaceFinder API call from scratch. Why the hell do I need to use OAuth to get some simple damn coordinates? Why the hell can't they just make the API call through HTTPS? Why are there no simple instructions? Why is there no simple Yahoo BOSS client library for Python, Ruby, etc.? Why the hell haven't I heard anyone complaining about this? Am I just stupid, or is making this API call needlessly complicated?