[twitter-dev] Re: Location Specific Public Timeline
Why not do a location-based Twitter search and then analyze the returned tweets? Or am I missing something in what you're trying to do? On Dec 11, 5:16 am, ArtJulian art.jul...@gmail.com wrote: Hi, I'm trying to build an application around trending topics based on a specific location through the public timeline, but would rather not filter the timeline on location afterwards. I did notice the Local Trends Methods, but I would like to set my own parameters and therefore depend on the public timeline to get the recent posts for the specific country. Is there a way to request thehttp://twitter.com/statuses/public_timeline.xml for specific countries and/or locations? I need the most recent status posts from a specific location, but I don't want to waste requests by deleting most of the data afterwards. Any help would be great! Arthur
[twitter-dev] Re: Location Specific Public Timeline
@Ed I think that ought to work as well. I did try doing something like that, however I hit a dead end because I kept getting cached results on querying search. (see topic: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/7a022ad241e44ab3#) Has anyone else had any success in getting location-based public timelines using search api ? Regards, Elroy On Dec 12, 1:20 pm, M. Edward (Ed) Borasky zzn...@gmail.com wrote: Why not do a location-based Twitter search and then analyze the returned tweets? Or am I missing something in what you're trying to do? On Dec 11, 5:16 am, ArtJulian art.jul...@gmail.com wrote: Hi, I'm trying to build an application around trending topics based on a specific location through the public timeline, but would rather not filter the timeline on location afterwards. I did notice the Local Trends Methods, but I would like to set my own parameters and therefore depend on the public timeline to get the recent posts for the specific country. Is there a way to request thehttp://twitter.com/statuses/public_timeline.xml for specific countries and/or locations? I need the most recent status posts from a specific location, but I don't want to waste requests by deleting most of the data afterwards. Any help would be great! Arthur- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: A New API For Browserless Apps?
On Fri, Dec 11, 2009 at 04:03:01AM -0800, Duane Roelands wrote: It seems clear to me from Raffi's comments on it that this third oauth flow is intended solely to enable Twitter use from embedded applications or in other environments in which it is not possible to use the existing oauth flows because there is no way to bring up a browser. And this will be enforced...how? The same way that oauth usage is enforced today: By attempting to educate users that they should not provide their login credentials to third-party websites. Developers who want the easier implementation and easier user experience will choose those methods, As noted in my earlier message, I dispute your assertion that type in name, remember password, type in password (even without an intermediate try to remember which password was for Twitter, enter a couple incorrect and/or typoed attempts, give up, go find the piece of paper where password is written down phase) is an easier user experience than click, click, click, done. Again, I grant that enter username and password is more familiar from long use, but it is not actually easier. In my experience (both as a developer and as a sysadmin), users prefer authentication methods which do not require them to remember or locate credentials. They often initially resist these alternative methods due to unfamiliarity, but, once they've done it enough times that they no longer have to think about how to carry out each step, they are highly resistant to going back to more traditional authentication methods which require them to do more work to log in. The fact that methods exist which remove this extra work while also being more secure is just gravy for those of us who are concerned with such things. Once users are accustomed to the ease of passwordless oauth login from one site, I fully expect them to want that same convenience on other sites. I further expect that this is already happening as users find that the existing web-based oauth flow is easier for them than basic auth. (The exception to these comments is in the case where oauth fails to work properly, which can be intensely frustrating for users. However, this is much less commmon now than it was even three months ago and, more importantly, by allowing Twitter to focus exclusively on oauth, I expect that replacing basic auth with this third oauth flow will lead to increased reliability of *all* oauth flows.) It in no way prevents or discourages use of the existing oauth flows in scenarios where a browser is available. Prevents? No. Discourages? Absolutely. It provides an incentive for poor security decisions by developers and users. Lazy developers will always take the easy way out, sure, and that's generally going to be less secure. But I'm still not seeing any coherent argument for how the planned third oauth flow will, in any way, be *worse* than the existing basic auth scheme. It may not be an absolutely perfect world in which absolutely nothing except Twitter itself is capable of accepting a Twitter password, but it's still a big improvement on what we have today. -- Dave Sherohman
[twitter-dev] Re: A New API For Browserless Apps?
Couldn't agree more. If this is true, it's time for me to say goodbye. On Dec 10, 11:40 pm, Duane Roelands duane.roela...@gmail.com wrote: Many of us in the developer community have been strongly pushing the point of view that third-party apps should never be asking for user credentials. We did so because we believed that Twitter was firmly committed to the security of the ecosystem and protecting the accounts of its users. It now appears that this belief was in error. This decision is going to actively hurt developers who chose the more secure implementation. Application A just lets me log in with my Twitter credentials, but Application B wants me to go through this harder process. Most users will choose option A, and the more-secure application B loses users. this decision punishes developers who chose the more secure model. It's disappointing, because a lot of developers have worked very hard to bring OAuth implementations to the community that were robust and secure and **didn't require a user to hand over their Twitter credentials**. There was a great opportunity here for Twitter to be a security leader in the social network space by saying We don't want our users giving their Twitter credentials to anyone except Twitter. It's a shame they didn't stick to their gun; the result is going to be a less- secure ecosystem.
Re: [twitter-dev] Invalid Signature Request when POST - ing
For the benefit of the list: I had an exchange with Mark off-list (because of OAuth credentials). One of the errors turned out to be in my app itself. The other is not confirmed/reproducible at this time. On Sat, Dec 12, 2009 at 11:40 AM, Mark McBride mmcbr...@twitter.com wrote: Could I get a complete dump of the HTTP conversation, including headers and body for the request and response? -- Harshad RJ http://hrj.wikidot.com
[twitter-dev] member_count lists issue
I SEEM to be getting a zero member count from a list where the only member is the owner of said list. Once I added another member to the list, the member count was 2. Anyone else notice this? Still trying to verify it's not on my end.
[twitter-dev] Re: 404 Errors on friends and followers using cursors
Another one: http://twitter.com/statuses/friends/giannetti.xml?cursor=1311765355356921547 On Dec 8, 10:32 am, Ammo Collector binhqtra...@gmail.com wrote: If you get the following URLs and continue to using the next_cursor, you receive incorrect 404s: http://twitter.com/statuses/friends/debra_bee.xml?cursor=130554434315...http://twitter.com/statuses/followers/fraying_ends.xml?cursor=-1http://twitter.com/statuses/followers/Sabrinita_Linda.xml?cursor=-1 Any ideas?
Re: [twitter-dev] Removing retweets from a user in your timeline
Submit a feature request: http://code.google.com/p/twitter-api/issues/entry?template=Feature%20Request On Thu, Dec 3, 2009 at 05:32, Rich rhyl...@gmail.com wrote: On Twitter.com there is the handy button to remove retweets from specific users from your timeline, by clicking on the green retweet icon. However I can't find a way to do this through the API? Is there a method or am I missing something? -- Abraham Williams | Awesome Lists | http://bit.ly/sprout608 Project | Intersect | http://intersect.labs.poseurtech.com Hacker | http://abrah.am | http://twitter.com/abraham This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] member_count lists issue
I have been noticing some quirky behavior with the Lists API today. So that might be causing your issue. Josh On Sat, Dec 12, 2009 at 9:56 AM, Matthew Terenzio mteren...@gmail.com wrote: I SEEM to be getting a zero member count from a list where the only member is the owner of said list. Once I added another member to the list, the member count was 2. Anyone else notice this? Still trying to verify it's not on my end.
[twitter-dev] WordPress implements a Twitter API root
fyi.. http://en.blog.wordpress.com/2009/12/12/twitter-api/ seems to only support xml from my limited initial testing. -chad
[twitter-dev] Twitter Api-Problem
Dear all, I have a problem using the Twitter-API with my own OAuth library. My own efforts to solve this problem led to nothing :-/. I successfully obtained an oauth_token and an oauth_token_secret via api-call. I was also possible to send signed GET requests (without parameters) and i was able to access protected statuses ( i.e. http://twitter.com/statuses/show/id.xml ). But I failed to send POST requests with additional api-parameters. My request looks like: --- POST /statuses/update.xml HTTP/1.1 Authorization: OAuth realm=http://twitter.com/statuses/ update.xml,oauth_consumer_key=faVMWtJvXP0IB3wsBaJTQ,oauth_nonce=3e3b26909fa40c2caac60614402a2214,oauth_signature_method=HMAC- SHA1,oauth_timestamp=1260449888,oauth_token=38161975-15hllTYOlXkOE4jM3wkEzfNkc1qJ0dFxpiXrwGXcB,oauth_version=1.0,oauth_signature=%2F3772JshuQJKDclbDyytiOZ5E3c %3D Host: twitter.com Content-Length: 16 Content-Type: application/x-www-form-urlencoded Content-ID: Date: Thu, 10 Dec 09 13:58:08 +0100 status=freutsich --- The signature was constructed from the following signature-base- string: POSThttp%3A%2F%2Ftwitter.com%2Fstatuses %2Fupdate.xmloauth_consumer_key%3DfaVMWtJvXP0IB3wsBaJTQ%26oauth_nonce %3D3e3b26909fa40c2caac60614402a2214%26oauth_signature_method%3DHMAC- SHA1%26oauth_timestamp%3D1260449888%26oauth_token %3D38161975-15hllTYOlXkOE4jM3wkEzfNkc1qJ0dFxpiXrwGXcB %26oauth_token_secret%3DREPLACEDREPLACEDREPLACED%26oauth_version %3D1.0%26status%3Dfreutsich I have no idea what i did wrong. I have a suspicion that my failure had something to do with the additional parameter (status=) and the way I add this parameter to the signature-base string ... Best regards Julius
[twitter-dev] What exactly does the follow parameter to friendships/create do?
Hi all, I'm sure this is a stupid question, but my Google kung fu is failing me. http://apiwiki.twitter.com/Twitter-REST-API-Method:-friendships%C2%A0create describes the parameter thus: * follow. Optional. Enable notifications for the target user in addition to becoming friends. What confuses me is: What are notifications for the target user? Thanks, Josh
[twitter-dev] Re: Regarding the search API based on Geo location
I've been trying to get search results with Geo but even if I do a query with a radius of 500mi around San Francisco, it returns me only tweets with geo=null. It seems that tweets with a geotag are not returned... Any idea why this is happening? Thank you, Jeremy
Re: [twitter-dev] What exactly does the follow parameter to friendships/create do?
This question gets asked every few weeks. Probably need to update the documentation. Right now it means subscribe with SMS to their updates. (In the twitter from a long long time ago, I believe this also controlled getting IM notifications). Zac Bowling
Re: [twitter-dev] What exactly does the follow parameter to friendships/create do?
Hey Josh, Notifications when enable will cause tweets from the followed user to be sent to the authenticated user's device. See http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-notifications%C2%A0follow for more details. Josh On Sat, Dec 12, 2009 at 7:37 PM, Josh Bleecher Snyder joshar...@gmail.com wrote: Hi all, I'm sure this is a stupid question, but my Google kung fu is failing me. http://apiwiki.twitter.com/Twitter-REST-API-Method:-friendships%C2%A0create describes the parameter thus: * follow. Optional. Enable notifications for the target user in addition to becoming friends. What confuses me is: What are notifications for the target user? Thanks, Josh
[twitter-dev] Rapid access of social graph method results in account being locked?
Hi there- I have an app that compares who you're following to your friends followers. To do this, I query ttp://twitter.com/friends/ids.json?user_id=X and compare that to my (saved) list of IDs. I noticed that if I make repeated (unauthenticated) queries to http://twitter.com/friends/ids.json?user_id=X (ie, I'm comparing my friends to friend A's friends, then to friend A's friend (B), then to friend B's friend (C)) that user_id X gets locked out (I get the We've temporarily locked your account after too many failed attempts to sign in. Please chillax for a few, then try again. when trying to login to the website (or from a Twitter client). I'm guessing that the rapid, multiple queries look like abuse. I did notice, however, then if I make authenticated queries to the same API method, the account locking does *not* happen. Is this an anti-abuse method? Is my only option to use authenticated calls? Sal
Re: [twitter-dev] Rapid access of social graph method results in account being locked?
I'll check with our abuse team, but this looks odd. On Sat, Dec 12, 2009 at 10:23 PM, Sal Conigliaro sco...@gmail.com wrote: Hi there- I have an app that compares who you're following to your friends followers. To do this, I query ttp://twitter.com/friends/ids.json?user_id=X and compare that to my (saved) list of IDs. I noticed that if I make repeated (unauthenticated) queries to http://twitter.com/friends/ids.json?user_id=X (ie, I'm comparing my friends to friend A's friends, then to friend A's friend (B), then to friend B's friend (C)) that user_id X gets locked out (I get the We've temporarily locked your account after too many failed attempts to sign in. Please chillax for a few, then try again. when trying to login to the website (or from a Twitter client). I'm guessing that the rapid, multiple queries look like abuse. I did notice, however, then if I make authenticated queries to the same API method, the account locking does *not* happen. Is this an anti-abuse method? Is my only option to use authenticated calls? Sal -- ---Mark http://twitter.com/mccv
