Re: [twitter-dev] verify_credentials longevity?
It's also used for OAuth Echo, if I'm not mistaken? D On 08/31/10 01:21, Matt Harris wrote: Hey Jud, There are no plans to deprecate verify_credentials. It's use is still valid for OAuth as it allows you to check if the user token and secret you have are still good. Best, Matt On Mon, Aug 30, 2010 at 3:44 PM, Jud jvale...@gmail.com wrote: With the move to OAuth, are we going to see verify_credentials deprecate? http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0verify_credentials -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
Re: [twitter-dev] Re: How i can logout using oauth or rest api of twitter?
On 08/19/10 17:16, Ken wrote: Taylor, I don't need this as much as some other developers but I think I understand why they keep asking for this. Sure, our app is not logged in. But many apps make the user log in to Twitter in order to use the app. Then, when the user is done with the app, they can't just logout and leave, we have to tell them to go to Twitter.com and logout. This is embarrassing (unprofessional) and potentially risky. If they don't understand that they are still logged in with Twitter, they may make some mistake, such as tweeting from the wrong account, and there could be privacy/security concerns about subsequent actions a user may perform while unknowingly logged in to Twitter. So one way to handle this from your side would be to just forget the user's OAuth tokens. Your app will still appear authorized to the user in the connections screen, which would be confusing, but your application wouldn't be able to perform any operations on their behalf. It might be useful to have a destroy credentials endpoint though, to remove your app from the connections screen. D On Aug 19, 4:20 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: The REST API is (mostly) stateless. There is no logged in to log out. Are you wanting to ensure that the user has to enter their credentials in again when presented with the OAuth flow? If not, what would you be interested in doing this for? Taylor On Thu, Aug 19, 2010 at 6:50 AM, JTOne jthot...@gmail.com wrote: How i can logout using oauth or rest api of twitter?
Re: [twitter-dev] Re: Frequent errors when using OAuth, none when using basic
However, if oauth-proxy is indeed doing OAuth as badly as your list of faults implies, I may have a bit of a job on my hands to figure out what it's doing and fix it, or might try to find some other OAuth proxy or client. Pity, though, as oauth-proxy was about the only thing I'd found so far which lets me send tweets relatively easily from a shell script. (There was a curl-alike with OAuth support whose name I forget, which had so many dependencies (Ruby, I think) that I eventually gave up trying to get it to work.) I'm in the middle of tidying up a python-based oauth command-line client that I've written[1], to improve debugging output and remove a dependency. Would that be at all helpful? I aim to finish the tidyup in the next couple of hours (as it's mostly just a case of committing code). The only dependencies will be PyYAML[2] and httplib2[3], although the current version also depends on python-oauth2[4] which, despite its name, is an OAuth 1.0a client. I also plan to generate a setup script that will automagically fetch and install the required dependencies. Dave [1] http://github.com/dingram/pycloc [2] http://pypi.python.org/pypi/PyYAML [3] http://pypi.python.org/pypi/httplib2 [4] http://github.com/simplegeo/python-oauth2
Re: [twitter-dev] accented words
On 07/29/10 16:40, David Tavárez wrote: When I try to send an update containing accented words, the api throws an error: Incorrect signature. What can I do? It sounds like you're not encoding characters properly -- see http://groups.google.com/group/twitter-development-talk/msg/12d17a57566e2ad1?hl=en_US Dave
Re: [twitter-dev] Twitter Stream API - Location filtering limited to the Western Hemisphere?
On 07/21/10 15:13, James wrote: I'm attempting to stream Tweets from the UK as a whole(filtering further with tracking words), using Twitters stream API, however I'm having trouble with my bounding box. The LAT/LON pairs I'm using to define a bounding box of the whoe UK(Ire included) is as follows. -9.05, 48.77, 2.19, 58.88 However when I try to use this with the Twitter stream API, it states the following error message. Location track must be less than 1 degrees on a side: LocationTrack(48.77,-9.05,58.88,2.19) I can't imagine that Twitter do not allow you a specify a bounding box that covers an area that crosses between the negative/positive LAT. Am I missing something here, or would this mean that Twitter only allow you to stream if you are in the Wester hemishphere, effectively? If anyone has a suggest as to how I might be able to over-come this, I'd be very interested in hearing you out. Just a thought, but the error says that the bounding box must be at most one degree on each side... and that box is about 11x10. It does seem like a bit of a restriction, but still... D
