[twitter-dev] Http 502 Over Capacity with include_entities
Hi all I'm seeing an increase in http 502 responses including the fail whale HTML being returned when calling home_timeline with a since_id and around 200 messages being returned. Calling the same URL will then work the next time when called almost immediately after Im seeing an increase in this behaviour but if I turn off include_entities I rarely see it. If we are to decode the t.co wrapper we must use this parameter so is anyone else seeing this issue and are you guys in the API team aware of any issues? Richard -- 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-dev] Re: request token
Hello Shob, Do you have already run the Twitter status update? Maybe i have the same problem. Regards, Dennis On 6 jul, 16:10, Jacky jaga...@gmail.com wrote: Hullo, POSThttps%3A%2F%2Fapi.twitter.com%2Foauth %2Frequest_tokenoauth_callback%3Doob%26oauth_consumer_key %3DhUMUUZO3Zx9zNzJ9DghcA%26oauth_nonce %3DDA39A3EE5E6B4B0D3255BFEF95601890AFD80709%26oauth_signature_method %3DHMAC-SHA1%26oauth_timestamp%3D1277424969%26oauth_version%3D1.0 and Oauth oauth_callback=oob, oauth_consumer_key=hUMUUZO3Zx9zNzJ9DghcA, oauth_nonce=DA39A3EE5E6B4B0D3255BFEF95601890AFD80709, oauth_signature_method=HMAC-SHA1, oauth_timestamp=1277424969, oauth_version=1.0, oauth_signature=%2Ff8P1dS6QVQnYCIc10kD1%2Bm2DkI %3D using objhttp.Open POST, https://api.twitter.com/oauth/request_token;, False objhttp.setRequestHeader Content-type, application/x-www-form- urlencoded objhttp.setRequestHeader Authorization, strsend objhttp.send() Not working, how can I see the stream that is being loaded...or debug this... and strsend is Oauth and appended by the very first string up on top in this email Cant see the problem... Please help, if you can see anything outright off or wrong... Regards, Shob -- 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: Home timeline without authentication
This won't contain protected accounts, and would only contain tweets from the last ten minutes or so. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Fri, Sep 3, 2010 at 10:12 PM, Karthik fermis...@gmail.com wrote: - Create a fake user that has follows the same accounts, No, I'd like to construct home timeline of any random user. How about this approach? Find friend ids of the user Listen to Streaming API's filter method following user's friends, specify a negative count to receive historic stream (retweets included) Process display the tweets On Sep 4, 1:03 am, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 12:12:19 -0700 (PDT) Karthik fermis...@gmail.com wrote: Is it feasible to construct home timeline of any user without using the API statuses/home_timeline, which requires user's authentication? We could iterate through user's friends graph, gather each friend's statuses and sort them by time. But it's an overkill for an user with more following. Any other options? - Create a fake user that has follows the same accounts, Or, - Pay Twitter for the data, I'm sure they will be happy to accommodate you ;) -- Bernd Stramm bernd.str...@gmail.com -- 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
[twitter-dev] Re: Home timeline without authentication
Ok. I didn't know this 10 minutes limitation. Thanks for confirming. Will tell my client, this is not feasible. On Sep 4, 6:42 pm, John Kalucki j...@twitter.com wrote: This won't contain protected accounts, and would only contain tweets from the last ten minutes or so. -John Kaluckihttp://twitter.com/jkalucki Twitter, Inc. On Fri, Sep 3, 2010 at 10:12 PM, Karthik fermis...@gmail.com wrote: - Create a fake user that has follows the same accounts, No, I'd like to construct home timeline of any random user. How about this approach? Find friend ids of the user Listen to Streaming API's filter method following user's friends, specify a negative count to receive historic stream (retweets included) Process display the tweets On Sep 4, 1:03 am, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 12:12:19 -0700 (PDT) Karthik fermis...@gmail.com wrote: Is it feasible to construct home timeline of any user without using the API statuses/home_timeline, which requires user's authentication? We could iterate through user's friends graph, gather each friend's statuses and sort them by time. But it's an overkill for an user with more following. Any other options? - Create a fake user that has follows the same accounts, Or, - Pay Twitter for the data, I'm sure they will be happy to accommodate you ;) -- Bernd Stramm bernd.str...@gmail.com -- 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: Are IDs globally unique? Or just unique for each object type?
That means no two or more status messages from different users will have same id ever globally or they can have ? Vineet Daniel Cell : +918106217121 Websites : Blog http://vinetedaniel.blogspot.com | Linkedinhttp://in.linkedin.com/in/vineetdaniel | Twitter https://twitter.com/vineetdaniel On Fri, Sep 3, 2010 at 6:54 PM, Colin Howe colintheh...@googlemail.comwrote: Cool. Thanks for the help :) On Sep 3, 2:16 pm, John Kalucki j...@twitter.com wrote: Unique for each object type. On Fri, Sep 3, 2010 at 11:09 AM, Colin Howe colintheh...@googlemail.com wrote: Are IDs globally unique? Or just unique for each object type? In other words, is it possible to have a user with the ID 7 and also a DM with the ID 7? -- 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 -- 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-dev] OAuth query ?
Hi My app is registered with twitter and I have unique keys to access my status messages etc. Can a different user authenticate using the same keys i.e multiple users using same login module and keys. Can the auth api work like an email login page ? Vineet Daniel -- 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-dev] Re: t.co link wrapping and the new 140 characters...
Personally I feed the 140 should be whatever we send totally ignoring the t.co factor otherwise it'll confuse end users and look like apps are broken Still waiting for someone from Twitter to talk about hownthe 140 will work since they reannounced it the other day On Sep 3, 9:02 pm, StuFF mc m...@stuffmc.com wrote: I just want this to be confirmed by @raffi If I understand correctlyhttp://groups.google.com/group/twitter-api-announce/browse_thread/thr... This means that I can securely send a 120 (or less) character message + a link, no matter how long the link is, it will be translated into 20 characters, and so the total being 140 character I'm fine. Right? My Rails app will send hey this is a message with always ahttp://link.com/path/to/resource; and all I need to check is that hey this is a message with always a is 120 chars, right? Thanks for confirming this, that would be amazingly cool because it would mean I don't need (and nobody would need) to call some t.co API to shrink a URL. Then I would only need to count on the updated clients (and twitter.com) to display my http://link.com; as a text and http://t.co/jhdafkjh; as a link! Wouldn't be a big deal if some (most) clients display the t.co as a text :) Cheers. -- 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-dev] Re: Using @anywhere session credentials for REST API
Have there been any updates regarding this subject? Kind regards, Arno / @itavero On 9 aug, 16:06, Taylor Singletary taylorsinglet...@twitter.com wrote: We'll have a solution for this announced soon that will allow you to move more seamlessly between the (non-OAuth 1.0a) access tokens that make up @Anywhere requests and server-side REST requests using OAuth 1.0a access tokens. There are also other things you can do with @Anywhere using advanced portions of the @Anywhere API -- including, for instance, retrieving a list of the user's follower IDs. You can read a bit about this here:http://groups.google.com/group/twitter-dev-anywhere/browse_thread/thr... Taylor On Sat, Aug 7, 2010 at 12:25 AM, knc kishor...@gmail.com wrote: Hi, I am a little confused here. I am using @anywhere's (with the JS file include) to authenticate a user into my application. After this, let's say I would like to retrieve a list of the user's follower IDs - how do I do that? I'm guessing I need to use the REST API for this, but since the user is already authenticated, how will the new flow be? How do I get the Oauth token and secret to make the calls with? -- 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-dev] Re: annotations access
Hi Chris, if I got it right, the feature's indeed not generally available yet, and its rollout does not rank very high in priority any more. Would be great to hear more from Twitter, though. Julien On Sep 2, 2:21 am, Chris Anderson jch...@gmail.com wrote: Howdy, I'm building a Twitter client that needs to make use of annotations to avoid displaying duplicate tweets to the end-user (long story...). Do I need to do something special to get access to the annotations API? I think I am posting my annotations correctly, but I can't be sure, as they are not appearing when I read the statuses with curl, or in my user stream. Is anyone else out there successfully using annotations? Is the feature not generally available yet? If not, how does one go about getting on the beta group? Thanks in advance, Chris -- 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] Are IDs globally unique? Or just unique for each object type?
Status ids are always unique, regardless of the user who posted them. On Friday, September 3, 2010, vineet daniel vineetdan...@gmail.com wrote: That means no two or more status messages from different users will have same id ever globally or they can have ? Vineet Daniel Cell : +918106217121Websites : Blog http://vinetedaniel.blogspot.com | Linkedin http://in.linkedin.com/in/vineetdaniel | Twitter https://twitter.com/vineetdaniel On Fri, Sep 3, 2010 at 6:54 PM, Colin Howe colintheh...@googlemail.com wrote: Cool. Thanks for the help :) On Sep 3, 2:16 pm, John Kalucki j...@twitter.com wrote: Unique for each object type. On Fri, Sep 3, 2010 at 11:09 AM, Colin Howe colintheh...@googlemail.comwrote: Are IDs globally unique? Or just unique for each object type? In other words, is it possible to have a user with the ID 7 and also a DM with the ID 7? -- 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 -- 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
[twitter-dev] Mentions timeline frozen?
Is anyone else seeing the mentions timeline broken? I can see mentions in search but not in the timeline itself -- 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-dev] Re: Mentions timeline frozen?
Scratch that, looks like the home timeline is frozen to all but your own tweets On Sep 4, 5:11 pm, Rich rhyl...@gmail.com wrote: Is anyone else seeing the mentions timeline broken? I can see mentions in search but not in the timeline itself -- 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-dev] twitter oauth incredibly slow?
Yesterday I implemented Twitter oAuth on my site, using really nothing but a cut and paste of the example from the twitteroauth class on github. It's working fine, with one hang-up- it's incredibly slow - like at least 30 seconds to process the connection, even during those occasional instances that Twitter itself overall is running fast. See here: http://www.famousquotesabout.com/widget-apps/ I've noticed that other Twitter web apps I've used seem to be able to process the whole interaction, callback and all, in just a couple seconds. I really have no idea what could cause such a delay, and I'm again using really nothing but the bare example code. Has anyone else seen similar issues? -- 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-dev] Re: Simple status update
Thanks, that's exactly what I need! On 4 zář, 05:42, Abraham Williams 4bra...@gmail.com wrote: On Fri, Sep 3, 2010 at 18:29, Gerard M g...@rivershark.com wrote: I can (well, used to) update using three lines: Here are three lines to tweet with OAuth: http://gist.github.com/564882 Abraham - Abraham Williams | Hacker Advocate |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- 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-dev] oauth verify credentials error
I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. -- 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-dev] Search with :from user clause not returning data sometimes
I'm trying to get the public tweets for certain users, and they come back with no data. Example: user @bhalligan Has 2,773 tweets (as reported by twitter.com) But, when I do a search query (using the web interface) like this: http://search.twitter.com/search?q=ands=phrase=ors=nots=tag=lang=allfrom=bhalliganto=ref=near=within=15units=misince=until=rpp=50 There's no data returned. Same thing happens when I do a search via the API. Any ideas why this user (and possibly others) return no tweet data, even though it's there and public? Thanks. -- 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] oauth verify credentials error
On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- 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-dev] Re: Recent API changes and new fields
Has retweet_count been turned on yet? Is there a live example of a call with it present in the response, and not null? Also, when it's on, is it enabled wherever a tweet is returned. Specifically, will it be in the list statuses: http://api.twitter.com/1/%/lists/%/statuses.json ? On Aug 23, 11:40 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, Thanks for the questions. I'll try and answer them all in this message. 1) are the counts turned on? This weekend the counts were turned off and have remained off. This is because of some bugs we found in the way the value was calculated. I'll let you know when we have this resolved. 2) Will these fields show up in the Search and Streaming API? The fields are already in the Streaming API but be aware the 'retweeted' field is not meaningful here. This is because the streamed status knows nothing of the connected user. The search API does not include this information. 3) How do I know if the feature is turned off? Tweets will contain a retweeted_count if available. If the service is not enabled newer Tweets will likely be missing their retweeted_count. The safest thing to do is code to handle missing values. If they are present use them, if they are not, treat them the same as when the field didn't exist. This way your code works when the retweeted_count is both enabled and disabled. 4) When was the feature turned on? The service was rolled out the week beginning Aug 16th Hope that answers your questions, Matt On Sat, Aug 21, 2010 at 4:33 PM, Joe j...@ajcomputers.com wrote: will we see this in both search and stream API? On Aug 20, 6:45 pm, Matt Harris thematthar...@twitter.com wrote: Hey everyone, This week we rolled out a couple of new data fields for the status and user objects. For a while it has been difficult for you to get the number of lists a user is listed in, or the number of times a Tweet has been retweeted. You were also finding it hard to know if the user had retweeted the status themselves or not. The feature requests you filed and the messages on the developer mailing list showed this is a pain point for many of you as it uses up many of your hourly API requests. These fields are live now and many of you have already seen them in our API responses. We intended to tell you about these changes before they were live, and in the future for things like this we will, but this time around our system for doing that didn't work. The good news is we know what went wrong and have made the necessary improvements needed to ensure you are notified before the changes happen. The recent changes which have been made affect the user and status objects. In both cases we have added fields: To the user object: --- listed_count represents the number of public lists a user is listed in. This field is an integer. As this is a new field it is possible some users will not have a listed_count value yet. follow_request_sent representing whether the user you are authenticating as has requested to follow the user you are viewing. This will be false unless the friendship request is pending. The field is a boolean and will be true or false. To the status object: - retweet_count represents the number of times a status has been retweeted using the Twitter retweet action. This field is an integer. There will not be a value for this field when the feature is turned off, or the Tweet was created before we addedretweet_countsupport. retweeted represents whether the user you are authenticating as has retweeted this status or not. The field is a boolean and can be true or false. Changes to existing methods -- users/show When requesting data for suspended users the user/show used to return an HTTP 404 status code - it now returns HTTP 403. This change is in response to number of users who were asking if there was a way to know if a user they were getting data for had been deleted or was instead suspended. The change means the API agrees with the twitter.com in that we confirm a user exists, but that you may not see their information because they are suspended. If you call /users/show on a suspended user the API response will include the error message User has been suspended. Please remember we sometimes turn features off to maintain site stability. We recommend you always check a field exists before attempting to use it and be prepared for the value to be empty. This will help ensure your code stays stable if we have to turn features off. We'll also be adding this information to the main API documentation soon. Best, Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- Twitter developer documentation
Re: [twitter-dev] oauth verify credentials error
On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. Is it 55 minutes, or 5 minutes and the wrong time zone? In the case of 55 minutes, of course Tom is right: 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- Bernd Stramm bernd.str...@gmail.com -- 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-dev] Re: @user_mentions and profile_image_urls
How are you getting the user mentions? Is it through statuses/mentions or using search? If you're using search, each result includes a field like this: link type=image/png href=http://a3.twimg.com/profile_images/ 5/of_normal.jpg rel=image/ That url is a reference to the user's profile image. On Sep 2, 5:40 pm, Claudia cbern...@gmail.com wrote: I've asked about this before - so apologies if anyone is re-reading this... I'm needing to get the profile_image_urls of all the @user_mentions in a timeline. Right now, it looks like the only way I can do this without killing rate limit in about an hour (which I just did) is to send a comma separated-list to users/lookup. However - this is adding major complications to my app structure, and I'd much rather avoid it. I can store the returned urls in a local DB, but if enough people use the app within an hour, it'll still quickly exceed the rate limit. Does anyone have any suggestions as to how I can get this done? Even better - anyone at Twitter think that the API could return the profile_image_url with the current @user_mention data.. seems it would be useful for many. Thanks in advance, Claudia -- 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-dev] Re: retweeted always returing as false in /1/statuses/user_timeline.json
At this point there are a number of fields on various objects returned by Twitter that should be considered unreliable (mostly on user objects). It might be time for Twitter to consider a better solution than just returning unreliable data, such as either stripping out the fields, giving them an attribute such as fieldstatus=deprecated or fieldstatus=disabled. These expected behaviors are only expected by the engineers on Twitter's end and I've seen lots of posts on the mailinglist where people have had to question why they were getting unreliable data. On Sep 3, 12:25 pm, Matt Harris thematthar...@twitter.com wrote: Hi Michael, Soon after launching those fields we identified some problems with them so had to disable them. That means the behavior you are seeing is expected right now. When the fields are enabled again we'll announce it to this mailing list. Best, Matt On Thu, Sep 2, 2010 at 9:04 PM, Michael Babker mbab...@flbab.com wrote: Hi there, I have a Twitter module I'm improving upon which pulls tweets from /1/statuses/user_timeline.json. An issue that I've noticed is that over the last couple of days, tweets I've retweeted using the retweet link on twitter.com have continued to display as retweeted: false in the JSON. Can someone tell me if this is normal behavior or if it's an issue with the API? Thanks! -- 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 -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- 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] oauth verify credentials error
On 9/4/10 8:13 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. Is it 55 minutes, or 5 minutes and the wrong time zone? In the case of 55 minutes, of course Tom is right: I'd be right in both cases. ;-) Although compensating for the timezone is also an option. (But really, the Unix Timestamp is always UTC, right?) 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- 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] oauth verify credentials error
On Sat, 04 Sep 2010 20:34:50 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 8:13 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. Is it 55 minutes, or 5 minutes and the wrong time zone? In the case of 55 minutes, of course Tom is right: I'd be right in both cases. ;-) Although compensating for the timezone is also an option. (But really, the Unix Timestamp is always UTC, right?) The sever of the website may be configured to a timezone that is different from the server's timezone. And, we don't know how the website code determines the time stamp. 5 minutes off indicates something wrong with the server, but it's not unheard of. 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- Bernd Stramm bernd.str...@gmail.com -- 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] twitter oauth incredibly slow?
This is definitely not how TwitterOAuth should be acting. You can try the example site and it is running fine: http://twitteroauth.labs.poseurtech.com/connect.php Somethings to check for: Are there an for/while/etc loops in your script that might not be functioning properly? Is it possible that there is code somewhere that is waiting for a period of time? Have to broken down the different parts of the OAuth flow to see if a particular part is slow? Could just your connection to twitter.com from your server be slow? Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Sat, Sep 4, 2010 at 08:23, Corey Northcutt corey.northc...@gmail.comwrote: Yesterday I implemented Twitter oAuth on my site, using really nothing but a cut and paste of the example from the twitteroauth class on github. It's working fine, with one hang-up- it's incredibly slow - like at least 30 seconds to process the connection, even during those occasional instances that Twitter itself overall is running fast. See here: http://www.famousquotesabout.com/widget-apps/ I've noticed that other Twitter web apps I've used seem to be able to process the whole interaction, callback and all, in just a couple seconds. I really have no idea what could cause such a delay, and I'm again using really nothing but the bare example code. Has anyone else seen similar issues? -- 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] oauth verify credentials error
On 9/4/10 8:51 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 20:34:50 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 8:13 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. Is it 55 minutes, or 5 minutes and the wrong time zone? In the case of 55 minutes, of course Tom is right: I'd be right in both cases. ;-) Although compensating for the timezone is also an option. (But really, the Unix Timestamp is always UTC, right?) The sever of the website may be configured to a timezone that is different from the server's timezone. And, we don't know how the website code determines the time stamp. 5 minutes off indicates something wrong with the server, but it's not unheard of. Unix time, or POSIX time, is a system for describing points in time, defined as the number of seconds elapsed since midnight proleptic Coordinated Universal Time (UTC) of January 1, 1970, not counting leap seconds. Read the UTC part ;-) 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- 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] oauth verify credentials error
On Sat, 04 Sep 2010 20:55:19 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 8:51 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 20:34:50 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 8:13 PM, Bernd Stramm wrote: On Sat, 04 Sep 2010 19:02:11 +0200 Tom van der Woerdt i...@tvdw.eu wrote: On 9/4/10 6:08 PM, rrd wrote: I have a website which gets friends timeline by twitter api. I use oauth 1.0 My website worked without any problem in the last 1,5 year, but from 1st September something changed. When I try to add a new user my app redirects me to the twitter oauth authentication page, where I could log in with my twitter credentials. After this twitter redirects me to my application. After this when I try to verify credentials I got Could not authenticate you error message. Could it be a timestamp problem? I found a few articles about having authentication problems because of fautty timestamp. If so what should I do if I am not able to change the server time? It seems I have 55 minutes difference from twitter time. Is it 55 minutes, or 5 minutes and the wrong time zone? In the case of 55 minutes, of course Tom is right: I'd be right in both cases. ;-) Although compensating for the timezone is also an option. (But really, the Unix Timestamp is always UTC, right?) The sever of the website may be configured to a timezone that is different from the server's timezone. And, we don't know how the website code determines the time stamp. 5 minutes off indicates something wrong with the server, but it's not unheard of. Unix time, or POSIX time, is a system for describing points in time, defined as the number of seconds elapsed since midnight proleptic Coordinated Universal Time (UTC) of January 1, 1970, not counting leap seconds. Read the UTC part ;-) Yes I am aware of that, oh wise one :) We do not know how the website code is obtaining its time stamp, and whether that time stamp is converted to some kind of local time. There are plenty of function calls that return a time stamp, not all of them give you raw POSIX time. 55 minutes is a lot. You should contact the server owner and tell him/her to synchronize the clock. If that's not an option, then you should simply generate an offset by asking the Twitter server the time and comparing this to the Unix Time of the server (don't do that too often, daily is fine). Later you can use this offset and add it to the Unix Time of the server to generate a time that is closer to the Twitter.com one. Tom -- Bernd Stramm bernd.str...@gmail.com -- 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-dev] Re: t.co link wrapping and the new 140 characters...
Users don't know / don't care about the 140 char limit. If an app allows them to send more than 140, they'll not thing it's a big deal. Twitter can simply communicate that any URL will count for 20 characters, and so, for ex., a tweet could contain 6 veeery long URLs, that would still fit in 140 chars. Not 7, we need spaces between those t.co's ;-) What I really love in the idea of t.co is that we'll display real URLs, and the only way to do it is to not count those real URLs as part of the tweet length. People (myself included) don't really like to see a bit.ly link - ever asked yourself what bit could mean for, for example, a french speaking grand'pa - they won't necessary click on the link coming from the grand son... ;) Anyways, Rich, I got your point, we need it to be clear from Twitter, but I think we should wait another week or two. ps: Congrats to the API team, good things coming lately. Cheers. On Sep 4, 10:14 am, Rich rhyl...@gmail.com wrote: Personally I feed the 140 should be whatever we send totally ignoring the t.co factor otherwise it'll confuse end users and look like apps are broken Still waiting for someone from Twitter to talk about hownthe 140 will work since they reannounced it the other day On Sep 3, 9:02 pm, StuFF mc m...@stuffmc.com wrote: I just want this to be confirmed by @raffi If I understand correctlyhttp://groups.google.com/group/twitter-api-announce/browse_thread/thr... This means that I can securely send a 120 (or less) character message + a link, no matter how long the link is, it will be translated into 20 characters, and so the total being 140 character I'm fine. Right? My Rails app will send hey this is a message with always ahttp://link.com/path/to/resource; and all I need to check is that hey this is a message with always a is 120 chars, right? Thanks for confirming this, that would be amazingly cool because it would mean I don't need (and nobody would need) to call some t.co API to shrink a URL. Then I would only need to count on the updated clients (and twitter.com) to display my http://link.com; as a text and http://t.co/jhdafkjh; as a link! Wouldn't be a big deal if some (most) clients display the t.co as a text :) Cheers. -- 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-dev] Twitter-async now let's you view a sequence diagram of calls
The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json :: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json :: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json :: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] -- 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] Twitter-async now let's you view a sequence diagram of calls
That's a fantastic addition to an already great library. Great work! On 4 Sep 2010, at 21:22, jmathai wrote: The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json :: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json :: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json :: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] http://synfinaty.com smime.p7s Description: S/MIME cryptographic signature
Re: [twitter-dev] Re: Twitter logout - hate to open this can of worms again
On Fri, Sep 3, 2010 at 11:29, Ken k...@cimas.ch wrote: What is the risk of storing a token? It can't be used outside your app. Much less risk that having users register with your app with a password. This is for sites that manage users. There's no need for a registration flow, at least one that is apparent to the user. For new users, send them to Twitter for a one-time Oauth roundtrip. Upon receipt of the token, create a user in your system, assign them a password and use it to log them in. Provide them this password, and/or let them change it. That's pretty pain-free account creation. Having users set up a password is a registration flow. You then also have to set up a mechanism for when they forget their password, keep the password safe, etc. Better then most sign up processes but it is still yet another password. If you need to associate an existing logged-in user with their Twitter account, send them to twitter for Oauth once. When they return they'll still be logged in and you'll have the credentials for future use. Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- 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: Twitter logout - hate to open this can of worms again
On Fri, Sep 3, 2010 at 11:43, Bernd Stramm bernd.str...@gmail.com wrote: On Fri, 3 Sep 2010 11:29:22 -0700 (PDT) Ken k...@cimas.ch wrote: What is the risk of storing a token? It can't be used outside your app. The token being confined to use within an app is very insecure when the app runs on an end-user device. There soon will be a billion smart phones, and many of those will run twitter apps. Humans are very insecure. Most will tell you all of their passwords with the right/wrong type of influences. Then suppose user Alice finds out user Bob's token (perhaps by borrowing or stealing a phone), and publishes it. User Bob now has no way to retire the token, short of disabling the app that runs on millions of phones. Or Bob can get a new twitter user name. This is incorrect. Bob can go to Twitter and revoke the token so it won't work anymore. That's not what is normally called security. OAuth as currently done with twitter only works when the app runs on a small number of secure servers. -- Bernd Stramm bernd.str...@gmail.com Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. -- 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] About OAuth
Have a look at http://gist.github.com/564882
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Sep 2, 2010 at 19:50, David dav...@alltraders.com wrote:
I found out twitter does not support Basic Auth any, and I wonder how
can I change my code from Basic Auth to OAuth.
and my code like following:
$username=username;
$password=password;
$message=message;
$host = http://twitter.com/statuses/update.xml;;
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $host);
//curl_setopt($ch, CURLOPT_VERBOSE, 1);
//curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, $config-timeout );
curl_setopt($ch, CURLOPT_USERPWD, $username:$password);
curl_setopt($ch, CURLOPT_POSTFIELDS,status=$message);
//curl_setopt($ch, CURLOPT_HTTP_VERSION,
CURL_HTTP_VERSION_1_1);
curl_setopt($ch, CURLOPT_POST, 1);
$result = curl_exec($ch);
// Look at the returned header
$resultArray = curl_getinfo($ch);
curl_close($ch);
--
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: Twitter-async now let's you view a sequence diagram of calls
Haha, that can only lead to a better experience for the end users. For what its worth, I only recommend EpiTwitter to folks as a PHP library now, and quite the volume of people at that! Shows you're doing something right! :) Scott. On 4 Sep 2010, at 23:10, jmathai wrote: Thanks Scott :). The same sweetness will be added to my fork of Twilio and Facebook's library as well :). I think my goal in life is to add asynchronous-ness to all php libraries :). On Sep 4, 1:31 pm, Scott Wilcox sc...@dor.ky wrote: That's a fantastic addition to an already great library. Great work! On 4 Sep 2010, at 21:22, jmathai wrote: The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json:: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json:: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json:: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] smime.p7s Description: S/MIME cryptographic signature
Re: [twitter-dev] Re: Twitter-async now let's you view a sequence diagram of calls
++ I only recommend EpiTwitter to folks as a PHP library now, ++ It's solid. On Sat, Sep 4, 2010 at 6:15 PM, Scott Wilcox sc...@dor.ky wrote: Haha, that can only lead to a better experience for the end users. For what its worth, I only recommend EpiTwitter to folks as a PHP library now, and quite the volume of people at that! Shows you're doing something right! :) Scott. On 4 Sep 2010, at 23:10, jmathai wrote: Thanks Scott :). The same sweetness will be added to my fork of Twilio and Facebook's library as well :). I think my goal in life is to add asynchronous-ness to all php libraries :). On Sep 4, 1:31 pm, Scott Wilcox sc...@dor.ky wrote: That's a fantastic addition to an already great library. Great work! On 4 Sep 2010, at 21:22, jmathai wrote: The twitter-async library on github now lets you easily view a sequence diagram of calls. This is specifically useful when you're making multiple calls asynchronously. Here's a sample output (looks better with fixed width font). http://wiki.github.com/jmathai/twitter-async/#sequence (http://api.twitter.com/1/direct_messages.json:: code=200, start=1283577305.2462, end=1283577305.5109, total=0.264562) [] (http://api.twitter.com/1/users/suggestions.json:: code=200, start=1283577305.2726, end=1283577305.3871, total=0.114419) [ = ] (http://api.twitter.com/1/statuses/public_timeline.json:: code=200, start=1283577305.2731, end=1283577305.4195, total=0.146262) [ ] -- 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-dev] Where Is the oauth_verifier ?
Hey all, I'm new to twitter development and am trying to get started. I'm using php My basic problem is when the user gets redirected back to my app after authorizing my app on twitter, I don't get back the oauth_verifier. I do see the oauth_token in my GET parameter, but nothing else. Am I missing something? If there was an error, where can I see that? thanks, Please help, V. -- 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-dev] Where Is the oauth_verifier ?
Hey all, I'm new to twitter development and am trying to get started. I'm using php My basic problem is when the user gets redirected back to my app after authorizing my app on twitter, I don't get back the oauth_verifier. I do see the oauth_token in my GET parameter, but nothing else. Am I missing something? If there was an error, where can I see that? thanks, Please help, V. -- 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-dev] Re: Automated OAuth
The server enters each username and password, so is the current way to have me go get the initial token then afterward have the server use the token programmaticly? On Sep 4, 2:18 am, Matt Harris thematthar...@twitter.com wrote: Hey Cradash, Where do the username and password come from that you use? If they are entered by a user you can handle the OAuth flow at that time. Once you have an OAuth user token and secret it does not expire and will continue to work until either the user revokes access to the application, or the applications keys are changed. This means that when you have the user token and secret you store that instead of the username and password, and use those details to make requests to the API. There is more information about converting Basic to OAuth on our developer resources site: http://dev.twitter.com/pages/basic_to_oauth Hope that helps, Matt On Thu, Sep 2, 2010 at 4:57 PM, Cradash rand...@gmail.com wrote: Yes, but I have not found a way to have the server go out with the consumer Key/secret then get the id # programmaticly, that's what I was looking for. On Sep 3, 9:44 am, Taylor Singletary taylorsinglet...@twitter.com wrote: Each Twitter feed in this case is a user. On Thursday, September 2, 2010, Cradash rand...@gmail.com wrote: Unfortunately that is not an option for us as we have no 'users'. We have a server that gleans information then posts it into twitter feeds, allautomated. -- 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 -- Matt Harris Developer Advocate, Twitterhttp://twitter.com/themattharris -- 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] A helper wrapper for Abraham Williams TwitterOAuth PHP wrapper
Awesome work Nicholas! I've added a link TwitterOAuth's projects page:
http://github.com/abraham/twitteroauth/wiki/links
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Wed, Sep 1, 2010 at 13:29, NdJ nicholas.dej...@gmail.com wrote:
Hi All,
A console application and additional wrapper for Abraham Williams
TwitterOAuth PHP wrapper which makes the process of obtaining OAuth
credentials for plain old single user mode usage a little easier:-
http://www.nicholasdejong.com/story/helper-wrapper-abraham-williams-twitteroauth-php-wrapper
From the README:-
This package has two main components both of which you'll want to
use:-
twitteroauth-helper-console
---
Use the console tool in a shell to create a valid
twitteroauth.credentials file:-
Step 1 - go to Twitter and obtain your API key and secret values.
Step 2 - run the twitteroauth-helper-console tool in a shell.
Step 3 - set your API secret and key using the set_consumer_key and
set_consumer_secret commands within the console tool.
Step 4 - request user authentication using request_user_auth console
command then visit the Twitter URL that is provided in a web browser.
You may need to log into Twitter and you will need to allow your
application.
Step 5 - Using the PIN code that will be displayed in the step above
go back to the console application and use the
verify_user_auth_request command.
Step 6 - Move the twitteroauth.credentials file that has been created
to a safe place.
twitteroauth-wrapper
You don't need to use this wrapper to use the twitteroauth credentials
but it does make things even easier.
All you need to do to make a post is the following:-
include('twitteroauth-helper-wrapper.php');
$TOHW = new TwitterOAuthHelperWrapper('/path/to/credentials.file');
$TOHW-post('statuses/update',array('status'='Hello World!'));
Enjoy,
N
--
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] 400 response from twitterauth statuses/update call
What error code is Twitter returning?
You could be running into a rate limit. You should also check that the
application is read/write and check on your twitter accounts connections
page that it has been granted read/write permissions.
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Wed, Sep 1, 2010 at 13:02, JC O'Donnell j...@springshare.com wrote:
Hello,
I've been transitioning our basic authentication calls over to OAuth.
I'm using the twitterauth PHP library. All of the authentication calls
are working and I receive proper responses from GET requests (ex:
account/verify_credentials, account/rate_limit_status), but when I
attempt a status update POST I get a 400 Bad Request response. From
the account/rate_limit_status call I know I'm below the rate limit.
Here's a PHP snippet...
$content = $connection-post('statuses/update', array(status =
Status update));
Has anybody else been experiencing this behavior?
Thanks,
JC
--
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] Twitter dev
Great having you around Zac and yay for learning ;) Abraham - Abraham Williams | Hacker Advocate | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private. On Mon, Aug 30, 2010 at 22:38, Zac Bowling zbowl...@gmail.com wrote: Well it's been a trip, but like my colleague @abraham, after two years and half years on this list, it has gotten a little too heavy for my inbox. I've been around but I don't comment often anymore since I don't deal with twitter API issues or updates on a day to day basis anymore. Since I left that twitter client company I used to work for 18 months ago, I haven't dealt with any twitter related issues on a day to day basis in pretty long while (except with the streaming API which is all I use anymore). I've learned (and continue to learn) a ton from my friends on the twitter team on their experiences on everything from oauth, to scaling streaming APIs, to ideas for scaling the latest nosql engine but I'm consuming knowledge through different channels (mostly twitter and the dev's own blogs). It's been fun and be sure to connect me on twitter at @zbowling. If anyone needs any help with any of the various open source twitter related things I've developed in the past, you can find my email below. I will always try to be involved with everything twitter I can (can't wait for the next hackathon like thing like we did for the annotations preview). I think I'm going to jump now before the oauth apocalypse and the fall out silly questions :-) Thanks everyone! Zac Bowling z...@zacbowling.com http://twitter.com/zbowling Sent from my iPad -- 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
[twitter-dev] Re: Question about transitioning from basic auth to oAuth
There is an easy workaround for this problem that doesn't require much recoding. It involves rerouting your updates to Twitter via Identi.ca. Create equivalent accounts on Identi.ca. Change your scripts to update the status on your Identi.ca accounts (which is just a matter of replacing http://twitter.com/statuses/update.json by http://identi.ca/api/statuses/update.json and the Twitter API realm by Identi.ca API). Set your identi.ca accounts to auto update your twitter accounts. Otto 7is7.com On Sep 3, 8:23 pm, Yardmaps balazsb...@gmail.com wrote: Hi there, My website, Yardmaps.org, has its own twitter account - actually there's a twitter account for each city that yardmaps will be available in. When I was coding the site using basic auth, I had a simple function that would update the twitter status of a given city whenever a yard sale is posted. Since I own the website, and the twitter accounts, I don't need to ask a 3rd person for permission to update their status. Basic auth was perfect. However, now that basic auth is no more, I'm not sure how I'm supposed to use oAuth to do the same thing? My database has the username and password for each twitter account, and when a yard sale is added, i simply want to tweet it out. Since oAuth doesn't (in my limited understanding) support asynchronous calls, I don't know how I can upgrade? Please help me. Thanks B -- 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-dev] Re: On the demise of basic authentication.
I'm finding it fairly hard to laugh and relax, to be honest. I'm not a developer. I just use perl scripts to automate my twitter feeds. Receiving a notice telling me that the authentication process had permanently changed, and receiving it 2 days AFTER the change had been deployed, was not impressive.. And discovering that there was no legacy basic authentication to keep hobbyists on track was equally unimpressive. Not only, from a user and a hobbyist perspective, a confusing lack of info on the oauth principles as they relate to twitter but there is an absolute lack of examples for some of the simple things we do such as ... how DO I automate my twitter feed using a perl script for which there is no access token, and where the requirement is that of ::duh:: automation. i.e. no user transaction to obtain a token. I get oauth, and the need for it - at least from your perspective. I just can't believe that you club-footed your way into a release schedule without some legacy support. On Aug 31, 6:39 pm, Taylor Singletary taylorsinglet...@twitter.com wrote: *GOODBYE BASIC AUTH* On Tuesday, August 31st 2010 at 16:26:13 UTC, @raffi of @twitterapi/team pressed the button that shut basic auth down for good: set :rate_limit_api_basic_auth, 0 ; puts Time.now Tue Aug 31 16:26:13 + 2010 = nil �...@raffi -http://twitter.com/twitterapi/status/22634515958 And with that issued command, we all said goodbye to Basic Authentication. Basic authentication was the easiest way to get started with the REST API. With that ease came many dangers, giving rise to the term the password anti-pattern. OAuth is obviously more complicated to implement. We'll continue to refine and evolve possible authorization options that present more frictionless user developer experiences without sacrificing user, developer, Twitter security. *A POEM* The time has come, the Walrus said, To talk of many things: Of SHAs--and nonces--and signatures-- Of timestamps--and tokens-- And why the dance-- And whether OAuth has wings. *A WAKE* But let us not go with OAuth in anger, but instead with laughter in our hearts. We've curated some of our favorite tweets on the subject. Not all of them are polite.http://curated.by/episod/oauthpocalypse-- some of them are funny, others are sad, some are just informational. All are proof that the transition to OAuth effects everyone a little differently. *SOME ERRATA* Large-scale migrations are not without their issues, of course. We introduced this bug and will be fixing it as soon as we can. * Non-authenticated resources return a 401 with authorization challenge once the IP-based rate limit is exhausted. - The correct behavior here is for us to return a 400. - This includes public resources like public_timeline, public lists, widgets, etc. *OTHER REMINDERS* * Use api.twitter.com/1/* for all REST API operations (excluding Search and OAuth). - You will have unusual results otherwise eventually your calls will fail * Use search.twitter.com for all Search API operations * Use api.twitter.com/oauth/* for all OAuth token negotiation operations *NOW LAUGH RELAX.* -- 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-dev] Re: About OAuth
But ... but ... I'm trying to do a similar kind of thing from a perl
command line.
I looked at this on github before, and where it says:
// Register an application at http://dev.twitter.com/apps and from
your new apps page get my access token.
There is no application for me to go to in order to get an access
token. I also need the script to run from a cron scheduler so I can't
have it stop and ask me for a verification PIN with each run.
Have you come across similar difficulties elsewhere? My searches are
turning up tantalisingly incomplete and inconsistent code snippets
that don't work ..
On Sep 4, 5:52 pm, Abraham Williams 4bra...@gmail.com wrote:
Have a look athttp://gist.github.com/564882
Abraham
-
Abraham Williams | Hacker Advocate |http://abrah.am
@abraham |http://projects.abrah.am|http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
On Thu, Sep 2, 2010 at 19:50, David dav...@alltraders.com wrote:
I found out twitter does not support Basic Auth any, and I wonder how
can I change my code from Basic Auth to OAuth.
and my code like following:
$username=username;
$password=password;
$message=message;
$host = http://twitter.com/statuses/update.xml;;
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $host);
//curl_setopt($ch, CURLOPT_VERBOSE, 1);
//curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect:'));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_TIMEOUT, $config-timeout );
curl_setopt($ch, CURLOPT_USERPWD, $username:$password);
curl_setopt($ch, CURLOPT_POSTFIELDS,status=$message);
//curl_setopt($ch, CURLOPT_HTTP_VERSION,
CURL_HTTP_VERSION_1_1);
curl_setopt($ch, CURLOPT_POST, 1);
$result = curl_exec($ch);
// Look at the returned header
$resultArray = curl_getinfo($ch);
curl_close($ch);
--
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
[twitter-dev] cron job perl twitter tweeter
Good evening :) I had a really simple perl net::twitter script that ran as a cron job off my laptop. All it did was, for each scheduled run, read a single line of information from a txt file, then tweet the line to any one of three twitter accounts. As I know enough perl to be dangerous, but not enough to be a wiz, I can't figure out how to get the same sweet tweet mechanism using oauth. I've registered the application - which is basically the script run from the command line, obtained the consumer key/secret, and have attempted to educate myself on oauth. But: I am stuck. Appears to need a transaction to take place between the app and twitter before anything can be done. If this is the case, my script will no longer work. If anyone else is aware of similar problems, is there a working example they can point me to? -- 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: On the demise of basic authentication.
There was plenty of notification on when Basic Auth was going to be discontinued. On 9/4/2010 9:29 PM, mikesouthern wrote: I'm finding it fairly hard to laugh and relax, to be honest. I'm not a developer. I just use perl scripts to automate my twitter feeds. Receiving a notice telling me that the authentication process had permanently changed, and receiving it 2 days AFTER the change had been deployed, was not impressive.. And discovering that there was no legacy basic authentication to keep hobbyists on track was equally unimpressive. Not only, from a user and a hobbyist perspective, a confusing lack of info on the oauth principles as they relate to twitter but there is an absolute lack of examples for some of the simple things we do such as ... how DO I automate my twitter feed using a perl script for which there is no access token, and where the requirement is that of ::duh:: automation. i.e. no user transaction to obtain a token. I get oauth, and the need for it - at least from your perspective. I just can't believe that you club-footed your way into a release schedule without some legacy support. On Aug 31, 6:39 pm, Taylor Singletarytaylorsinglet...@twitter.com wrote: *GOODBYE BASIC AUTH* On Tuesday, August 31st 2010 at 16:26:13 UTC, @raffi of @twitterapi/team pressed the button that shut basic auth down for good: set :rate_limit_api_basic_auth, 0 ; puts Time.now Tue Aug 31 16:26:13 + 2010 = nil @raffi -http://twitter.com/twitterapi/status/22634515958 And with that issued command, we all said goodbye to Basic Authentication. Basic authentication was the easiest way to get started with the REST API. With that ease came many dangers, giving rise to the term the password anti-pattern. OAuth is obviously more complicated to implement. We'll continue to refine and evolve possible authorization options that present more frictionless user developer experiences without sacrificing user, developer, Twitter security. *A POEM* The time has come, the Walrus said, To talk of many things: Of SHAs--and nonces--and signatures-- Of timestamps--and tokens-- And why the dance-- And whether OAuth has wings. *A WAKE* But let us not go with OAuth in anger, but instead with laughter in our hearts. We've curated some of our favorite tweets on the subject. Not all of them are polite.http://curated.by/episod/oauthpocalypse-- some of them are funny, others are sad, some are just informational. All are proof that the transition to OAuth effects everyone a little differently. *SOME ERRATA* Large-scale migrations are not without their issues, of course. We introduced this bug and will be fixing it as soon as we can. * Non-authenticated resources return a 401 with authorization challenge once the IP-based rate limit is exhausted. - The correct behavior here is for us to return a 400. - This includes public resources like public_timeline, public lists, widgets, etc. *OTHER REMINDERS* * Use api.twitter.com/1/* for all REST API operations (excluding Search and OAuth). - You will have unusual results otherwise eventually your calls will fail * Use search.twitter.com for all Search API operations * Use api.twitter.com/oauth/* for all OAuth token negotiation operations *NOW LAUGH RELAX.* -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. -- 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: On the demise of basic authentication.
On 9/4/10 11:05 PM, Dustin Shea at demonicpa...@gmail.com wrote: There was plenty of notification on when Basic Auth was going to be discontinued. Dustin, I can't comment on what notification you received, and am glad you received it. I can only comment on the notification that *I* received: this was, on 9/2/10, addressed to the email addys associated with all 11 twitter accounts, the message that 3 days earlier basic auth had been expired. While I may be a perl hobbyist, in my professional life I do know how to identify, open and read an email. -- 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: On the demise of basic authentication.
My notification may have been due to the fact that I've been a member of the Dev List for some time thus foresaw this coming and I think it was mentioned on the old Twitter API wiki. I took notice do to the fact I was working on a TCL twitter app for an IRC eggdrop bot that was using Basic Auth and was struggling and waiting for someone with more knowledge than I to write a TCL resource I could use. I also follow @twitterapi on twitter. On 9/4/2010 10:13 PM, Mike Southern wrote: On 9/4/10 11:05 PM, Dustin Shea at demonicpa...@gmail.com wrote: There was plenty of notification on when Basic Auth was going to be discontinued. Dustin, I can't comment on what notification you received, and am glad you received it. I can only comment on the notification that *I* received: this was, on 9/2/10, addressed to the email addys associated with all 11 twitter accounts, the message that 3 days earlier basic auth had been expired. While I may be a perl hobbyist, in my professional life I do know how to identify, open and read an email. -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. -- 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: On the demise of basic authentication.
* mikesouthern gb1...@cox.net [100904 19:56]: I'm not a developer. I just use perl scripts to automate my twitter feeds. For perl devs, the move to OAuth is really quite easy, especially for automated scripts. Register an application at http://dev.twitter.com. Grab the consumer key and secret, and the access token and secret. use Net::Twitter; my $nt = Net::Twitter-new( traits = [qw/OAuth API::REST/], consumer_key= $YOUR_CONSUMER_KEY, consumer_secret = $YOUR_CONSUMER_SECRET, access_token= $YOUR_ACCESS_TOKEN, access_token_secret = $YOUR_ACCESS_SECRET, ); $nt-update(Bob's your uncle!); Need help? Just drop by #net-twitter at irc.perl.org. -Marc -- 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: About OAuth
* mikesouthern gb1...@cox.net [100904 19:57]: But ... but ... I'm trying to do a similar kind of thing from a perl command line. See my reply in an earlier thread: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/160cb4d3f20ef61 -Marc -- 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] cron job perl twitter tweeter
* mikesouthern gb1...@cox.net [100904 19:59]: I had a really simple perl net::twitter script that ran as a cron job off my laptop. All it did was, for each scheduled run, read a single line of information from a txt file, then tweet the line to any one of three twitter accounts. Copied from an earlier reply, here: http://groups.google.com/group/twitter-development-talk/browse_thread/thread/160cb4d3f20ef61 For perl devs, the move to OAuth is really quite easy, especially for automated scripts. Register an application at http://dev.twitter.com. Grab the consumer key and secret, and the access token and secret. use Net::Twitter; my $nt = Net::Twitter-new( traits = [qw/OAuth API::REST/], consumer_key= $YOUR_CONSUMER_KEY, consumer_secret = $YOUR_CONSUMER_SECRET, access_token= $YOUR_ACCESS_TOKEN, access_token_secret = $YOUR_ACCESS_SECRET, ); $nt-update(Bob's your uncle!); Need help? Just drop by #net-twitter at irc.perl.org. -Marc -- 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
