[twitter-dev] Re: Properties and Methods of T object of @anywhere
On Apr 28, 12:06 am, MJ lor...@gmail.com wrote: Also I am using @anywhere to login but I also have some server side code with java. Is there a way that I can pass the credentials of the @anywhere logged in user to the server side code? Or does that happen automatically (once someone authorizes the Twitter application via @anywhere a server side library with the same apikey and secretkey is authorized). I doubt you'll have access to the credentials, as that would mean you'd have login credentials for any twitter user that hit your page which wouldn't be what end users would expect. -- Glenn http://glenngillen.com/
[twitter-dev] Re: @anywhere Current user properties are undefined
On Apr 28, 2:27 am, MJ lor...@gmail.com wrote:
I'm working with the @anywhere api and trying to do a authcomplete
span id=twitter-login-box/span
script type=text/javascript
twttr.anywhere(function (T) {
if(T.isConnected()){
twttr.anywhere.signOut();
}
T(#twitter-login-box).connectButton({ size: large,
authComplete: function(user) {
// triggered when auth completed successfully
window.location.href = /twitter/twitterlogin.jsp?
twitterid=+T.currentUser.id;
} });
});
/script
It keeps saying id is undefined and I tried other properties as well.
It looks like from the code above, you actually want to be using user
(there parameter passed into the callback), so:
authComplete: function(user) {
// triggered when auth completed successfully
window.location.href = /twitter/twitterlogin.jsp?
twitterid=+user.id;
}
Is that any better?
--
Glenn
http://glenngillen.com/
[twitter-dev] TwitterVB
To whoever is developing the dev.twitter.com website could you update the url of twittervb to http://twittervb.codeplex.com. Also, while the source code is in VB.NET the binary library itself can be used across any .NET-compatable language so it probably should be grouped more properly with the C#/.NET group. John Meyer TwitterVB
[twitter-dev] Looking for simple single user-pw Oauth tutorial
Reading the Oauth docs, is quite confusing. The complexity deals with the Oauth dance, in order to not have to store a user and pw. My usage doesn't need this capability. I use one user-pw only (my own). Looking for a simple tutorial for this usage only.
[twitter-dev] Differences between docs and Search API behavior
I've found a number of things that don't seem to behave as documented on either the old API wiki or the new Dev site. I'm writing a tutorial on this portion of the API, so I'd like to know if the docs are correct, and I'm just getting weird results, or if the docs are wrong. I'm using PHP and cURL to test this. I'm sending a very simple search request of: http://api.twitter.com/1/search.json?q=recipe 1. Docs say Search API is not limited by the same 150 requests per hour limit as the REST API. The number is quite a bit higher and we feel it is both liberal and sufficient for most applications. When I try calling the Search API, the rate limit shown in the header is 150. Exceeding 150 in an hour does cause a rate limit failure, so this number does seem to be 150. 2. Docs say Consumers using the Search API but failing to include a User Agent string will receive a lower rate limit. I got the same rate limit of 150 whether or not I use the cURL user agent option. I tried an application name of twitter app tutorial and a standard Mozilla user agent string. 3. Docs say An application that exceeds the rate limitations of the Search API will receive HTTP 420 response codes to requests. When I exceed 150 requests, I get a 400 HTTP response code, not 420. 4. Docs say It is a best practice to watch for this error condition and honor the Retry-After header that instructs the application when it is safe to continue. When I exceed 150 requests, I don't see a retry-After header value. Thanks for your help with this.
[twitter-dev] Re: @anywhere Current user properties are undefined
Figured it out it's user.data('id') not user.id
On Apr 27, 9:27 pm, MJ lor...@gmail.com wrote:
I'm working with the @anywhere api and trying to do a authcomplete
span id=twitter-login-box/span
script type=text/javascript
twttr.anywhere(function (T) {
if(T.isConnected()){
twttr.anywhere.signOut();
}
T(#twitter-login-box).connectButton({ size: large,
authComplete: function(user) {
// triggered when auth completed successfully
window.location.href = /twitter/twitterlogin.jsp?
twitterid=+T.currentUser.id;
} });
});
/script
It keeps saying id is undefined and I tried other properties as well.
Anyone have an idea what is going on?
Thanks
[twitter-dev] address book
Hi , Is there any api or methods available to display the address book or contacts of twitter account.? my website is implemented in java,j2ee and . my task is to display the twitter address book(i.e mail ids) of twitter user in my website ... is there any methods/api avilable to display the user address book (mail id) . Thanks and Regards Satish.
[twitter-dev] App needs more calls than what Twitter Whitelisted Account offers!
Hi there, We are very excited to develop an App on Twitter ecosystem. We are developing something which removes all the spam from user's followers list and shows him how much exactly non-spam followers he has. But to perform such task, we need way more than what Twitter Whitelisted account offers (20,000). For an instance, Twitter CEO @EV himself has around 1.1 Million Followers. What we do is we have designed a set of algorithms which removes all the spam, inactive and such other followers and show how many exactly real followers the particular user has. But to do this (by rest api) we need to spend 1 call to calculate every 100 followers of the user. And once we get those 100 follower we need 1 more call to filter out spam followers. Also there are few more such tasks we need to perform to filter out the spam which needs more calls. So if for instance a user has more than 1 million followers, our system will not be able to calculate his overall non-spam followers. Also there is a chance when multiple users can try to check how many non-spam followers they have at the same time. All I need to ask is, how am I able to get more than one IP addresses white-listed (white-listing form states that we are able to whitelist more than one ip) and if such thing is possible, how can we use both the ip's to perform one single task of user having more than 1 million followers. Also we were thinking of getting more than one Twitter account white- listed associated to our business and then use them one by one when we use all the calls from one id. Is this feasible? If both the methods (White-listing IP and White-listing Accounts) are not a proper way to perform such task, what would you recommend us to do? We have spent countless nights getting this algorithms work and we even have tested them on small user account having less than 1000 followers and it works like charm. We are searching for solution since a month now. I hope we will get help here. Eagerly waiting for reply from Twitter. Thanks a lot in advance!
Re: [twitter-dev] address book
On 4/28/2010 6:10 AM, satish wrote: Hi , Is there any api or methods available to display the address book or contacts of twitter account.? my website is implemented in java,j2ee and . my task is to display the twitter address book(i.e mail ids) of twitter user in my website ... is there any methods/api avilable to display the user address book (mail id) . Thanks and Regards Satish. if you are asking e-mail addresses, then no.
[twitter-dev] Really, You're not going to suspend @julianperretta?
He's been plagiarizing people for weeks, and has been reported for spam by dozens of people that I know about. Here's just one example: http://twitter.com/sween/status/3736262373 http://twitter.com/julianperretta/status/12991042505 But hey, I guess he's famous, so why make him follow the same rules as everyone else? TjL ps - yeah I know it's not about the API but it's not like you get a response from Twitter anywhere else. No, I'm not expecting one here /rant
Re: [twitter-dev] dev.twitter.com usability - FAIL
Yeah one improvement may be to place the API hurl tool into each API documentation page with all parameter pre-filled so it is ready to be experiment with to see how the responses look. This also helps avoid out of date info if the responses should change. Josh On Tue, Apr 27, 2010 at 4:21 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.comwrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] Really, You're not going to suspend @julianperretta?
On 4/28/2010 7:50 AM, TJ Luoma wrote: He's been plagiarizing people for weeks, and has been reported for spam by dozens of people that I know about. Spam I understand, but are you actually trying to report plagarism on a bloody tweet? Are you kidding me? We're you planning on selling that bit of wisdom somewhere? Spinning it off for a book deal?
Re: [twitter-dev] @Anywhere tweet box performance issue
On Wed, Apr 28, 2010 at 5:32 AM, Adi aditya.sa...@gmail.com wrote: [..snip..] This whole thing takes quite some time (15 seconds) for the first time to display the tweet box. In subsequent calls this thing is as fast as expected. The wait between pressing tweet and watching the tweet box appear for the first time when someone presses tweet is extremely long, and almost entirely taken up the anywhere function call (I checked with my ajax call - doesn't take any time). Do you have Speed Tracer (http://code.google.com/webtoolkit/speedtracer/) or Firebug installed? Can you see if the time spent is waiting on the request for the iframe content to be returned from the twitter origin servers? If I had to guess it's the response being slow returning and that's the delay that you are seeing. We've got some World Cup stuff we are starting working which is going to have @Anywhere on it so I'll have more experience with it. Having gone through this with another companies Social Widget launch recently I can tell you it's a crapshoot as to how quickly the content renders in the browser. -steve
Re: [twitter-dev] Really, You're not going to suspend @julianperretta?
On 4/28/2010 8:21 AM, Dossy Shiobara wrote: On 4/28/10 10:18 AM, John Meyer wrote: Spam I understand, but are you actually trying to report plagarism on a bloody tweet? Are you kidding me? We're you planning on selling that bit of wisdom somewhere? Spinning it off for a book deal? You mean, like @shitmydadsays? I would assume that if you're bundling tweets that you send out for free to another format (aka a book) you would be adding some value in between the two.
Re: [twitter-dev] dev.twitter.com usability - FAIL
Personally thought the new pages were a vast improvement on the old ones in terms of finding what I need. Usability is in the way the user thinks, I suppose. On 28 April 2010 15:11, Josh Roesslein jroessl...@gmail.com wrote: Yeah one improvement may be to place the API hurl tool into each API documentation page with all parameter pre-filled so it is ready to be experiment with to see how the responses look. This also helps avoid out of date info if the responses should change. Josh On Tue, Apr 27, 2010 at 4:21 PM, Taylor Singletary taylorsinglet...@twitter.com wrote: Thanks for the feedback, Jonathon. We're working to address all these pain points on an ongoing basis. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 2:17 PM, Jonathon Hill jhill9...@gmail.comwrote: The new dev.twitter.com website that launched at Chirp a few weeks ago is very nice and attractive but there are several major usability issues: * The new API documentation does not provide return values of the API calls. The old wiki provided this information, along with usage notes that are not present either on the new site. * It is difficult to look up API endpoints required for a given type of functionality. If you don't remember the exact endpoint to look for, it can be frustrating trying to find the right one. This would easily be fixed using a more descriptive list of endpoints, and/or more visual contrast between headings and list items. * I tend to overlook the endpoint description in the blue header section. My eyes expect it in the white area below. Please move it, and make it stand out more. * The Supported formats, Supported request methods, Requires Authentication, and Rate Limited sections use up an awful lot of vertical space on the page unnecessarily. Making each one of these a heading also dilutes the visual hierarchy on the page and takes away from more detailed and important information on the page, from a reference standpoint. I think these would be more effectively presented as a list under a Metadata heading, or as a small table. * The API console is very restricted without login and registration of an app. I think this is a mistake. Login should be required only for those calls that require authentication. * The API console would be much easier to use if there were parameter hints for each call on the page somewhere. Prepopulating the parameter list would be awesome! These are all things that have been kindof in my face as I've tried to use dev.twitter.com in my day to day development work. I would be delighted if you would address these issues. Thanks! Jonathon Hill Company52 http://company52.com @compwright
Re: [twitter-dev] Really, You're not going to suspend @julianperretta?
What do you care why or why not someone is concerned with plagiarism? John L Meyer: Twitter Women's Auxiliary Air Force, in effect! ∞ Andy Badera ∞ +1 518-641-1280 Google Voice ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Apr 28, 2010 at 10:23 AM, John Meyer john.l.me...@gmail.com wrote: On 4/28/2010 8:21 AM, Dossy Shiobara wrote: On 4/28/10 10:18 AM, John Meyer wrote: Spam I understand, but are you actually trying to report plagarism on a bloody tweet? Are you kidding me? We're you planning on selling that bit of wisdom somewhere? Spinning it off for a book deal? You mean, like @shitmydadsays? I would assume that if you're bundling tweets that you send out for free to another format (aka a book) you would be adding some value in between the two.
Re: [twitter-dev] dev.twitter.com usability - FAIL
I miss the RSS feeds. -- Little androids dreaming of Nexus Ones compiled this text. On Apr 28, 2010 7:27 AM, Nigel Legg nigel.l...@gmail.com wrote: Personally thought the new pages were a vast improvement on the old ones in terms of finding what I need. Usability is in the way the user thinks, I suppose. On 28 April 2010 15:11, Josh Roesslein jroessl...@gmail.com wrote: Yeah one improvement may b...
Re: [twitter-dev] Differences between docs and Search API behavior
First off, the address for search is currently search.twitter.com i.e. the documentation and the information should use the following url: http://search.twitter.com/search.json?q=recipe See http://dev.twitter.com/doc/get/search All of your other issues are a result of not using the proper URL. At some point we look to combine the 2 API,, but issues like you have noted will cause this to be painful. Jonathan @twittersearch On Tue, Apr 27, 2010 at 8:45 PM, Adam Green 140...@gmail.com wrote: I've found a number of things that don't seem to behave as documented on either the old API wiki or the new Dev site. I'm writing a tutorial on this portion of the API, so I'd like to know if the docs are correct, and I'm just getting weird results, or if the docs are wrong. I'm using PHP and cURL to test this. I'm sending a very simple search request of: http://api.twitter.com/1/search.json?q=recipe 1. Docs say Search API is not limited by the same 150 requests per hour limit as the REST API. The number is quite a bit higher and we feel it is both liberal and sufficient for most applications. When I try calling the Search API, the rate limit shown in the header is 150. Exceeding 150 in an hour does cause a rate limit failure, so this number does seem to be 150. 2. Docs say Consumers using the Search API but failing to include a User Agent string will receive a lower rate limit. I got the same rate limit of 150 whether or not I use the cURL user agent option. I tried an application name of twitter app tutorial and a standard Mozilla user agent string. 3. Docs say An application that exceeds the rate limitations of the Search API will receive HTTP 420 response codes to requests. When I exceed 150 requests, I get a 400 HTTP response code, not 420. 4. Docs say It is a best practice to watch for this error condition and honor the Retry-After header that instructs the application when it is safe to continue. When I exceed 150 requests, I don't see a retry-After header value. Thanks for your help with this.
Re: [twitter-dev] countdown to OAuth / basic auth removal / OAuthcalypse
Raffi, does the discontinuation of basic authorization on the API also effect the Streaming API or just the REST API? Thanks, Jason. Raffi Krikorian wrote: hi all. you're going to be hearing a lot from me over the next 9 weeks. our plan is to turn off basic authorization on the API by june 30, 2010 -- developers will have to switch over to OAuth by that time. between now and then, there will be a /lot/ of information coming along with tips on how to use OAuth Echo, xAuth, etc. we really want to make this transition as easy as we can for everybody. as always, please feel free to reach out to this group, or to @twitterapi directly. if you need help remembering the date - http://bit.ly/twcountdown. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: App needs more calls than what Twitter Whitelisted Account offers!
I'm gonna poke some gentle fun at you here. I'm spidering the whole social graph. I'm 25% done with my first pass. I will need two passes to accomplish my goal. I hope to be done sometime in 2011. You can limit your service to the vast majority of people who have far fewer than one million followers. I can't. I just have to keep crawling, 24x7. Twitter should provide a quarterly snapshot of everyone's friends and followers, or even just a quarterly snapshot of which accounts are considered active. This would save twitter millions of API calls. Until that day, we cache.
[twitter-dev] Re: Properties and Methods of T object of @anywhere
Don't mean the credentials (password) but if a user authorizes my app to for example post tweets to their account via @anywhere will my server side libraries (using JTwitter) have the same permissions provided that they are using the same API Key and Secret Key? On Apr 28, 4:06 am, glenn gillen gl...@rubypond.com wrote: On Apr 28, 12:06 am, MJ lor...@gmail.com wrote: Also I am using @anywhere to login but I also have some server side code with java. Is there a way that I can pass the credentials of the @anywhere logged in user to the server side code? Or does that happen automatically (once someone authorizes the Twitter application via @anywhere a server side library with the same apikey and secretkey is authorized). I doubt you'll have access to the credentials, as that would mean you'd have login credentials for any twitter user that hit your page which wouldn't be what end users would expect. -- Glennhttp://glenngillen.com/
Re: [twitter-dev] Re: Properties and Methods of T object of @anywhere
Hi MJ, The access tokens used transparently behind the scenes in @Anywhere aren't compatible with the OAuth 1.0A access tokens Twitter uses in the standard API implementation. We're looking at creative ways to bridge the gap but won't have an easy solution for this for a bit. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 28, 2010 at 9:18 AM, MJ lor...@gmail.com wrote: Don't mean the credentials (password) but if a user authorizes my app to for example post tweets to their account via @anywhere will my server side libraries (using JTwitter) have the same permissions provided that they are using the same API Key and Secret Key? On Apr 28, 4:06 am, glenn gillen gl...@rubypond.com wrote: On Apr 28, 12:06 am, MJ lor...@gmail.com wrote: Also I am using @anywhere to login but I also have some server side code with java. Is there a way that I can pass the credentials of the @anywhere logged in user to the server side code? Or does that happen automatically (once someone authorizes the Twitter application via @anywhere a server side library with the same apikey and secretkey is authorized). I doubt you'll have access to the credentials, as that would mean you'd have login credentials for any twitter user that hit your page which wouldn't be what end users would expect. -- Glennhttp://glenngillen.com/
[twitter-dev] Re: Hovercards without Follow Button?
In my case (I can't speak for Greg), I'd like to use @anywhere in a read-only way. For following, I want the user to utilize my server side code (and their credentials from OAuth). It would be great if I could use the @anywhere simply to display that user's twitter profile. Until twitter solves the @anywhere = OAuth v1 issue, I don't think I'll use it. I suspect the livequery plugin could possibly be utilized to hide the follow button. I'll do some testing on that. On Apr 27, 10:51 am, Abraham Williams 4bra...@gmail.com wrote: Why would you not want to give the user the option to follow the account? Abraham On Tue, Apr 27, 2010 at 06:05, Greg gregory.av...@gmail.com wrote: Hello everyone, Is is possible to disable the follow button on the hovercard using Twitter Anywhere? My issue is that I want the user just to see the user's hovercard - not to follow them. Thanks, Greg -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- Abraham Williams | Developer for hire |http://abrah.am @abraham |http://projects.abrah.am|http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] Differences between docs and Search API behavior
I now see that http://search.twitter.com is at the top of the search docs on dev.twitter.com, but all the example URLs on that page use http://api.twitter.com/1/, which is where I got it. Oddly, apiwiki.twitter.com uses http://search.twitter.com in its examples, but I thought the dev site was the more authoritative source now. I'll be sure to change my tutorial to use the right one. I need to do more testing, but the other issues do seem to be due to this confusion. Thanks much. On Wed, Apr 28, 2010 at 12:05 PM, Jonathan Reichhold jonathan.reichh...@gmail.com wrote: First off, the address for search is currently search.twitter.com i.e. the documentation and the information should use the following url: http://search.twitter.com/search.json?q=recipe See http://dev.twitter.com/doc/get/search All of your other issues are a result of not using the proper URL. At some point we look to combine the 2 API,, but issues like you have noted will cause this to be painful. Jonathan @twittersearch On Tue, Apr 27, 2010 at 8:45 PM, Adam Green 140...@gmail.com wrote: I've found a number of things that don't seem to behave as documented on either the old API wiki or the new Dev site. I'm writing a tutorial on this portion of the API, so I'd like to know if the docs are correct, and I'm just getting weird results, or if the docs are wrong. I'm using PHP and cURL to test this. I'm sending a very simple search request of: http://api.twitter.com/1/search.json?q=recipe 1. Docs say Search API is not limited by the same 150 requests per hour limit as the REST API. The number is quite a bit higher and we feel it is both liberal and sufficient for most applications. When I try calling the Search API, the rate limit shown in the header is 150. Exceeding 150 in an hour does cause a rate limit failure, so this number does seem to be 150. 2. Docs say Consumers using the Search API but failing to include a User Agent string will receive a lower rate limit. I got the same rate limit of 150 whether or not I use the cURL user agent option. I tried an application name of twitter app tutorial and a standard Mozilla user agent string. 3. Docs say An application that exceeds the rate limitations of the Search API will receive HTTP 420 response codes to requests. When I exceed 150 requests, I get a 400 HTTP response code, not 420. 4. Docs say It is a best practice to watch for this error condition and honor the Retry-After header that instructs the application when it is safe to continue. When I exceed 150 requests, I don't see a retry-After header value. Thanks for your help with this.
[twitter-dev] Working with OAuth and Wordpress
I am in the process of creating a plugin for wordpress. I was told that when using oauth with a plugin I can't actually make the plugin act natively because each time that the plugin is installed each user has to have their own api credentials is this correct? Thanks in advance!
Re: [twitter-dev] Working with OAuth and Wordpress
Hi Andrew, If you're distributing your plugin for WordPress, you would want to ensure that it doesn't contain any OAuth consumer keys (API keys) or secrets within the source code. You'd instruct implementors to come to http://dev.twitter.com/apps to create an application and give them a UI or configuration file to enter their consumer key and consumer secret in a safe place resistant to tampering. In short, your analysis is correct. There are cases where you might more tightly control the distribution of your plugin and the hosts that utilize it where these best practices might be a bit more flexible. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 28, 2010 at 10:54 AM, Andrew tweetligh...@gmail.com wrote: I am in the process of creating a plugin for wordpress. I was told that when using oauth with a plugin I can't actually make the plugin act natively because each time that the plugin is installed each user has to have their own api credentials is this correct? Thanks in advance!
[twitter-dev] Re: Increasing 502/503 errors on Search API
It happens now just about every time when I'm trying to get the second page of results for a complex query. For example, this one is failing at the moment: http://search.twitter.com/search.atom?max_id=13019381815page=2q=snappatx+OR+%22capital+metro%22+OR+%22cap+metro%22+OR+capmetro+OR+%28%28bus+OR+rail+OR+dillo+OR+transit+OR+train+OR+streetcar%29+%28austin+OR+atx%29%29rpp=100 The first page of results comes through fine. And if I make the query less complex, the results come through fine as well. On Apr 27, 10:42 pm, rcauvin ro...@cauvin.org wrote: My program that uses the search API has over the past couple of days been getting a lot of 502errors. On Apr 26, 5:15 pm, mikawhite mikawh...@me.com wrote: Unit = an 'internal tweet' for each null/502/503 result from the Search API. -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Looking for simple single user-pw Oauth tutorial
Hi Moshe, While a direct tutorial from using basic auth and converting to an OAuth-enabled application is actually really difficult and entirely platform-dependent, we just made it easier to retrieve an access token on your own behalf for your own applications on http://dev.twitter.com/apps -- you can read more about using an access token without having to do all of the OAuth dance here: http://bit.ly/1token Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, Apr 27, 2010 at 5:09 PM, Moshe C. mos...@gmail.com wrote: Reading the Oauth docs, is quite confusing. The complexity deals with the Oauth dance, in order to not have to store a user and pw. My usage doesn't need this capability. I use one user-pw only (my own). Looking for a simple tutorial for this usage only.
[twitter-dev] Re: Increasing 502/503 errors on Search API
Yes, due to lots of recent growth we're bumping up against some capacity limits and working on them right now. In the mean time, some very complex queries will time out. I'd encourage you to back off on your rates, and please to not aggressively retry the complex queries that fail [we don't cache the failures, but will probably begin doing so in order to prevent people from pounding the system with retries while it is already straining] thanks On Apr 28, 11:08 am, rcauvin ro...@cauvin.org wrote: It happens now just about every time when I'm trying to get the second page of results for a complex query. For example, this one is failing at the moment: http://search.twitter.com/search.atom?max_id=13019381815page=2q=sna... The first page of results comes through fine. And if I make the query less complex, the results come through fine as well. On Apr 27, 10:42 pm, rcauvin ro...@cauvin.org wrote: My program that uses the search API has over the past couple of days been getting a lot of 502errors. On Apr 26, 5:15 pm, mikawhite mikawh...@me.com wrote: Unit = an 'internal tweet' for each null/502/503 result from the Search API. -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] App needs more calls than what Twitter Whitelisted Account offers!
There might be a rate limit trick or two that you might find useful: http://blog.abrah.am/2010/04/little-known-twitter-and-twitterapi.html You should also make sure to read the API TOS thoroughly. You are not auto following/unfollowing but you are still performing bulk operations. http://dev.twitter.com/pages/api_terms Abraham On Wed, Apr 28, 2010 at 04:41, deadlychaos deadlychaos...@gmail.com wrote: Hi there, We are very excited to develop an App on Twitter ecosystem. We are developing something which removes all the spam from user's followers list and shows him how much exactly non-spam followers he has. But to perform such task, we need way more than what Twitter Whitelisted account offers (20,000). For an instance, Twitter CEO @EV himself has around 1.1 Million Followers. What we do is we have designed a set of algorithms which removes all the spam, inactive and such other followers and show how many exactly real followers the particular user has. But to do this (by rest api) we need to spend 1 call to calculate every 100 followers of the user. And once we get those 100 follower we need 1 more call to filter out spam followers. Also there are few more such tasks we need to perform to filter out the spam which needs more calls. So if for instance a user has more than 1 million followers, our system will not be able to calculate his overall non-spam followers. Also there is a chance when multiple users can try to check how many non-spam followers they have at the same time. All I need to ask is, how am I able to get more than one IP addresses white-listed (white-listing form states that we are able to whitelist more than one ip) and if such thing is possible, how can we use both the ip's to perform one single task of user having more than 1 million followers. Also we were thinking of getting more than one Twitter account white- listed associated to our business and then use them one by one when we use all the calls from one id. Is this feasible? If both the methods (White-listing IP and White-listing Accounts) are not a proper way to perform such task, what would you recommend us to do? We have spent countless nights getting this algorithms work and we even have tested them on small user account having less than 1000 followers and it works like charm. We are searching for solution since a month now. I hope we will get help here. Eagerly waiting for reply from Twitter. Thanks a lot in advance! -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] countdown to OAuth / basic auth removal / OAuthcalypse
I guess to be more specific, will we still be able to use the Streaming API with basic auth after June 30th if there is no oAuth implementation for it? John Kalucki wrote: Eventually the Streaming API will be all oAuth as well, but on a different, yet to be determined, schedule. User Streams will launch with oAuth. The preview will switch over to oAuth soon. -John On Wed, Apr 28, 2010 at 9:05 AM, Jason Wong ja...@kratedesign.com wrote: Raffi, does the discontinuation of basic authorization on the API also effect the Streaming API or just the REST API? Thanks, Jason. Raffi Krikorian wrote: hi all. you're going to be hearing a lot from me over the next 9 weeks. our plan is to turn off basic authorization on the API by june 30, 2010 -- developers will have to switch over to OAuth by that time. between now and then, there will be a lot of information coming along with tips on how to use OAuth Echo, xAuth, etc. we really want to make this transition as easy as we can for everybody. as always, please feel free to reach out to this group, or to @twitterapi directly. if you need help remembering the date - http://bit.ly/twcountdown. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] countdown to OAuth / basic auth removal / OAuthcalypse
yes. On Wed, Apr 28, 2010 at 12:32 PM, Jason Wong ja...@kratedesign.com wrote: I guess to be more specific, will we still be able to use the Streaming API with basic auth after June 30th if there is no oAuth implementation for it? John Kalucki wrote: Eventually the Streaming API will be all oAuth as well, but on a different, yet to be determined, schedule. User Streams will launch with oAuth. The preview will switch over to oAuth soon. -John On Wed, Apr 28, 2010 at 9:05 AM, Jason Wong ja...@kratedesign.com wrote: Raffi, does the discontinuation of basic authorization on the API also effect the Streaming API or just the REST API? Thanks, Jason. Raffi Krikorian wrote: hi all. you're going to be hearing a lot from me over the next 9 weeks. our plan is to turn off basic authorization on the API by june 30, 2010 -- developers will have to switch over to OAuth by that time. between now and then, there will be a lot of information coming along with tips on how to use OAuth Echo, xAuth, etc. we really want to make this transition as easy as we can for everybody. as always, please feel free to reach out to this group, or to @twitterapi directly. if you need help remembering the date - http://bit.ly/twcountdown. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Policy restrictions on what we can do with Streaming sample and filter endpoints?
I'm thinking about releasing some of my simpler uses of the streaming sample and filter endpoints in open source. I missed the Chirp session on policy, so I didn't get a chance to ask the questions there. Are there any policy restrictions on what one can do with sample and filter data that aren't covered in the standard developers' pages already? -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Policy restrictions on what we can do with Streaming sample and filter endpoints?
Basically, you cannot resyndicate the data. You can't make the raw data available to others via an API or other bulk means. Summaries of the data are fine, as is display of the data. But you can't be a pass-through to other third-parties. -John On Wed, Apr 28, 2010 at 12:56 PM, M. Edward (Ed) Borasky zn...@comcast.net wrote: I'm thinking about releasing some of my simpler uses of the streaming sample and filter endpoints in open source. I missed the Chirp session on policy, so I didn't get a chance to ask the questions there. Are there any policy restrictions on what one can do with sample and filter data that aren't covered in the standard developers' pages already? -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
[twitter-dev] New portal feature: Easy issuance of an access token for your account with your applications
Hi Developers, In the interests of continuing to make the transition from basic authentication easier for the many different kinds of developers interfacing with the Twitter API, we introduced a new feature to the dev.twitter.comdeveloper portal today that will allow you to create an access token on your own behalf for any of the applications registered under your account. You can find this feature by viewing the application detail page for any of your applications at http://dev.twitter.com/apps and clicking on the My Access Token link in the right-hand sidebar. You'll be presented with both the oauth_token and oauth_token_secret for your user account and the application currently being viewed. With the collective access token pieces, your API/consumer key and consumer secret, you have all the pieces of information you need to make authenticated REST API calls to Twitter when used in conjunction with an OAuth library or a home brew solution. Application developers who are primarily writing applications for a single-user use case (and are not providing the application through direct distribution to the public) will be best served by this feature, though it also provides you a quick and easy way to get up and running with the API without having to master all the complicated steps of the token negotiation dance. It is not recommended to include a hard-coded access token in any application: desktop, web, or otherwise. We're collecting examples using different combinations of programming languages, OAuth and Twitter libraries at http://bit.ly/1token -- if you have an example of using the Twitter API after massaging an oauth_token and oauth_token_secret into an access token object (or however the internal logic of the libraries you use handle this relationship) and would like to see it included, drop me an email. This is a familiar pattern to any OAuth-based implementation that persistently stores access tokens. In addition, we've recently revised our OAuth documentation with more examples on the best path to using OAuth at Twitter. This document is by no means complete and will continue to expand and be refined. You can find this at http://dev.twitter.com/auth We hope you find this enhancement useful while contemplating the mandatory transition to OAuth. Today is April 28th. You have 8 weeks and 6 days to make the transition. http://countdowntooauth.com/ Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod
Re: [twitter-dev] Policy restrictions on what we can do with Streaming sample and filter endpoints?
On 04/28/2010 01:17 PM, John Kalucki wrote: Basically, you cannot resyndicate the data. You can't make the raw data available to others via an API or other bulk means. Summaries of the data are fine, as is display of the data. But you can't be a pass-through to other third-parties. -John On Wed, Apr 28, 2010 at 12:56 PM, M. Edward (Ed) Borasky zn...@comcast.net wrote: I'm thinking about releasing some of my simpler uses of the streaming sample and filter endpoints in open source. I missed the Chirp session on policy, so I didn't get a chance to ask the questions there. Are there any policy restrictions on what one can do with sample and filter data that aren't covered in the standard developers' pages already? -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős OK ... that's fine! -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] New portal feature: Easy issuance of an access token for your account with your applications
Awesome. However since everything needed to act on behalf of developers Twitter accounts is now transfered in plain text it would be awesome to get http://dev.twitter.com moved to https://dev.twitter.com. Abraham On Wed, Apr 28, 2010 at 13:41, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, In the interests of continuing to make the transition from basic authentication easier for the many different kinds of developers interfacing with the Twitter API, we introduced a new feature to the dev.twitter.comdeveloper portal today that will allow you to create an access token on your own behalf for any of the applications registered under your account. You can find this feature by viewing the application detail page for any of your applications at http://dev.twitter.com/apps and clicking on the My Access Token link in the right-hand sidebar. You'll be presented with both the oauth_token and oauth_token_secret for your user account and the application currently being viewed. With the collective access token pieces, your API/consumer key and consumer secret, you have all the pieces of information you need to make authenticated REST API calls to Twitter when used in conjunction with an OAuth library or a home brew solution. Application developers who are primarily writing applications for a single-user use case (and are not providing the application through direct distribution to the public) will be best served by this feature, though it also provides you a quick and easy way to get up and running with the API without having to master all the complicated steps of the token negotiation dance. It is not recommended to include a hard-coded access token in any application: desktop, web, or otherwise. We're collecting examples using different combinations of programming languages, OAuth and Twitter libraries at http://bit.ly/1token -- if you have an example of using the Twitter API after massaging an oauth_token and oauth_token_secret into an access token object (or however the internal logic of the libraries you use handle this relationship) and would like to see it included, drop me an email. This is a familiar pattern to any OAuth-based implementation that persistently stores access tokens. In addition, we've recently revised our OAuth documentation with more examples on the best path to using OAuth at Twitter. This document is by no means complete and will continue to expand and be refined. You can find this at http://dev.twitter.com/auth We hope you find this enhancement useful while contemplating the mandatory transition to OAuth. Today is April 28th. You have 8 weeks and 6 days to make the transition. http://countdowntooauth.com/ Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] @Anywhere tweet box performance issue
You could probably start loading the TweetBox immediately on first visit but
hide it with CSS so it is quick loading when a user actually clicks on the
tweet button.
Abraham
On Wed, Apr 28, 2010 at 02:32, Adi aditya.sa...@gmail.com wrote:
Hi all,
I've got this use case:
I have a button, clicking which opens up a tweet box with text
defaulted by my application. Here's how I've implemented:
1. Have a tweet button.
2. On clicking tweet, call javascript method showTweetBox which
- 2.1 Makes ajax call to my application to fetch some text (default
tweet text)
- 2.2 on successful ajax calls this (copied and modified from
@anywhere documentation)
---
twttr.anywhere(function (T) {
T(boxid).tweetBox({
height: 40,
width: 480,
defaultContent: msg, // this is my default text
obtained through ajax call dynamically
label: Tweet this video,
onTweet: removeTweetBox
});
---
This whole thing takes quite some time (15 seconds) for the first
time to display the tweet box. In subsequent calls this thing is as
fast as expected.
The wait between pressing tweet and watching the tweet box appear
for the first time when someone presses tweet is extremely long, and
almost entirely taken up the anywhere function call (I checked with my
ajax call - doesn't take any time).
I understand this post has quite a few subjective elements (my
browser, my net speed etc) but is there a way to speed up the
anywhere call which replaces a div tag with the iframe
containing the tweet box? Do you recommend some other way?
--
Abraham Williams | Developer for hire | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first [ ] private.
Re: [twitter-dev] New portal feature: Easy issuance of an access token for your account with your applications
I'd very much like that as well, Abraham. Thanks for the reminder. Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Wed, Apr 28, 2010 at 2:09 PM, Abraham Williams 4bra...@gmail.com wrote: Awesome. However since everything needed to act on behalf of developers Twitter accounts is now transfered in plain text it would be awesome to get http://dev.twitter.com moved to https://dev.twitter.com. Abraham On Wed, Apr 28, 2010 at 13:41, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Developers, In the interests of continuing to make the transition from basic authentication easier for the many different kinds of developers interfacing with the Twitter API, we introduced a new feature to the dev.twitter.comdeveloper portal today that will allow you to create an access token on your own behalf for any of the applications registered under your account. You can find this feature by viewing the application detail page for any of your applications at http://dev.twitter.com/apps and clicking on the My Access Token link in the right-hand sidebar. You'll be presented with both the oauth_token and oauth_token_secret for your user account and the application currently being viewed. With the collective access token pieces, your API/consumer key and consumer secret, you have all the pieces of information you need to make authenticated REST API calls to Twitter when used in conjunction with an OAuth library or a home brew solution. Application developers who are primarily writing applications for a single-user use case (and are not providing the application through direct distribution to the public) will be best served by this feature, though it also provides you a quick and easy way to get up and running with the API without having to master all the complicated steps of the token negotiation dance. It is not recommended to include a hard-coded access token in any application: desktop, web, or otherwise. We're collecting examples using different combinations of programming languages, OAuth and Twitter libraries at http://bit.ly/1token -- if you have an example of using the Twitter API after massaging an oauth_token and oauth_token_secret into an access token object (or however the internal logic of the libraries you use handle this relationship) and would like to see it included, drop me an email. This is a familiar pattern to any OAuth-based implementation that persistently stores access tokens. In addition, we've recently revised our OAuth documentation with more examples on the best path to using OAuth at Twitter. This document is by no means complete and will continue to expand and be refined. You can find this at http://dev.twitter.com/auth We hope you find this enhancement useful while contemplating the mandatory transition to OAuth. Today is April 28th. You have 8 weeks and 6 days to make the transition. http://countdowntooauth.com/ Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod -- Abraham Williams | Developer for hire | http://abrah.am @abraham | http://projects.abrah.am | http://blog.abrah.am This email is: [ ] shareable [x] ask first [ ] private.
[twitter-dev] twitter oauth
hello one questionn ,, i can have a oauth authentication in web browse and app desktop the same time ... why the methos are diferents thanks in advance
Re: [twitter-dev] twitter oauth
On 4/28/2010 4:15 PM, nav wrote: hello one questionn ,, i can have a oauth authentication in web browse and app desktop the same time ... why the methos are diferents thanks in advance The methods are different because the targets are different. With a web application, you are sending the client to twitter from you web site, and twitter can send the client back to you with the oAuth data. With a local desktop, on the other hand, you can not redirect the user as easily. So in place, the user receives a PIN that they can input into the oAuth desktop app and then the app can use to get the access tokens. HTH.
Re: [twitter-dev] To Raffi or Taylor re: xAuth
A question on this and how it relates to User Streams. Unless I'm mistaken (only took a cursory look/played around with User Streams), User Streams uses Basic Auth. So if my app uses both the User Streams API and the REST API, I have to both use xAuth for the REST calls and store the username/password to use for User Streams. Am I missing something? Thanks, Aral On Tue, Apr 27, 2010 at 11:48 PM, John Meyer john.l.me...@gmail.com wrote: On 4/27/2010 4:38 PM, Taylor Singletary wrote: The twitter screen name is less of a concern, yes John. But a Twitter username can take an email address also, which isn't information otherwise provided by the API and is personally identifiable and especially dangerous when stored in conjunction with a password. A screen name, in context with data we return to you falls under our rather liberal caching policies -- you get the screen name along with the user id as a response to a valid access token request. snip
[twitter-dev] Re: App needs more calls than what Twitter Whitelisted Account offers!
To be quite frank, you are filling a hole. The functionality you are describing, identifying and getting rid of spam followers, is Twitter's job and should be part of their core system. On Apr 28, 8:41 am, deadlychaos deadlychaos...@gmail.com wrote: Hi there, We are very excited to develop an App on Twitter ecosystem. We are developing something which removes all the spam from user's followers list and shows him how much exactly non-spam followers he has. But to perform such task, we need way more than what Twitter Whitelisted account offers (20,000). For an instance, Twitter CEO @EV himself has around 1.1 Million Followers. What we do is we have designed a set of algorithms which removes all the spam, inactive and such other followers and show how many exactly real followers the particular user has. But to do this (by rest api) we need to spend 1 call to calculate every 100 followers of the user. And once we get those 100 follower we need 1 more call to filter out spam followers. Also there are few more such tasks we need to perform to filter out the spam which needs more calls. So if for instance a user has more than 1 million followers, our system will not be able to calculate his overall non-spam followers. Also there is a chance when multiple users can try to check how many non-spam followers they have at the same time. All I need to ask is, how am I able to get more than one IP addresses white-listed (white-listing form states that we are able to whitelist more than one ip) and if such thing is possible, how can we use both the ip's to perform one single task of user having more than 1 million followers. Also we were thinking of getting more than one Twitter account white- listed associated to our business and then use them one by one when we use all the calls from one id. Is this feasible? If both the methods (White-listing IP and White-listing Accounts) are not a proper way to perform such task, what would you recommend us to do? We have spent countless nights getting this algorithms work and we even have tested them on small user account having less than 1000 followers and it works like charm. We are searching for solution since a month now. I hope we will get help here. Eagerly waiting for reply from Twitter. Thanks a lot in advance!
[twitter-dev] Re: Really, You're not going to suspend @julianperretta?
Ducking the artillery shells and verbal mortar rounds in this thread, I just want to ask: Did you know @shitmydadsays actually uses status.net, and pushes its tweets from there into Twitter via the StatusNet-Twitter bridge? On Apr 28, 11:21 am, Dossy Shiobara do...@panoptic.com wrote: On 4/28/10 10:18 AM, John Meyer wrote: Spam I understand, but are you actually trying to report plagarism on a bloody tweet? Are you kidding me? We're you planning on selling that bit of wisdom somewhere? Spinning it off for a book deal? You mean, like @shitmydadsays? -- Dossy Shiobara | do...@panoptic.com |http://dossy.org/ Panoptic Computer Network |http://panoptic.com/ He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on. (p. 70)
Re: [twitter-dev] To Raffi or Taylor re: xAuth
user streams, right now, uses basic auth. user streams are in a preliminary / experimental stage - we do not recommend (john would use stronger words) using them in production. we will be implementing oauth on the streaming api soon-ish. On Wed, Apr 28, 2010 at 4:10 PM, Aral Balkan aralbal...@gmail.com wrote: A question on this and how it relates to User Streams. Unless I'm mistaken (only took a cursory look/played around with User Streams), User Streams uses Basic Auth. So if my app uses both the User Streams API and the REST API, I have to both use xAuth for the REST calls and store the username/password to use for User Streams. Am I missing something? Thanks, Aral On Tue, Apr 27, 2010 at 11:48 PM, John Meyer john.l.me...@gmail.com wrote: On 4/27/2010 4:38 PM, Taylor Singletary wrote: The twitter screen name is less of a concern, yes John. But a Twitter username can take an email address also, which isn't information otherwise provided by the API and is personally identifiable and especially dangerous when stored in conjunction with a password. A screen name, in context with data we return to you falls under our rather liberal caching policies -- you get the screen name along with the user id as a response to a valid access token request. snip -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: server app publishing twitter status updates with oauth?
To reply to myself: I've figured most of this out now. (1) Yes, the app should be registered. Log on to the twitter account that messages will be published to, then go to dev.twitter.com/apps and add a new app. (2) When an app is defined by an account, the app is automatically added to that account's connections. (3) No, xauth is not the right tool. On the app page (either just after defining the app, or later by account settings | connections), the my access token button will create an authentication (token, secret) pair that can be used to authenticate the server app against the account. The web-based authentication step is then unnecessary. These auth tokes do not expire (unless you explicitly log onto the account and revoke the token). (4) It looks like the signing is not too complicated, but also non- trivial; oauth is simply more complex than basic auth. So using a lib is probably the best solution. The Signpost project (google) appears to have a nice small implementation.
Re: [twitter-dev] Really, You're not going to suspend @julianperretta?
On Wed, Apr 28, 2010 at 10:18 AM, John Meyer john.l.me...@gmail.com wrote: On 4/28/2010 7:50 AM, TJ Luoma wrote: He's been plagiarizing people for weeks, and has been reported for spam by dozens of people that I know about. Spam I understand, but are you actually trying to report plagarism on a bloody tweet? Are you kidding me? We're you planning on selling that bit of wisdom somewhere? Spinning it off for a book deal? http://help.twitter.com/forums/26257/entries/18311 under spam If you repeatedly post other users' Tweets as your own But Twitter ought to just enforce the rules *you* care about. TjL
[twitter-dev] Twitter API ME 1.2 released!!!
Hi, I am pleased to announce that *Twitter API ME* version 1.2 is finally released. This new version comes with some great new stuffs, e.g., direct messages, timelines, friendship management, retweet, etc. For those who do not know Twitter API ME, this a Twitter Java API designed to run on any Java Platform. Currently this API provides support for Java ME and Android. The Android version can be used for Java SE development as well. To know more about Twitter API ME, visit us at www.twitterapime.com Now it is time to work on OAuth support. We have a tight deadline to meet. I hope you enjoy it! Regards, -- Ernandes Jr. - ALL programs are poems. However, NOT all programmers are poets.
[twitter-dev] Re: Invalid / used nonce but only for certain user names?
Anyone have any ideas about this? I'm really not sure where to go or what to check from here, and I need to get this taken care of. Any information would be appreciated!
[twitter-dev] Re: Invalid / used nonce but only for certain user names?
Cory, I have had similar issues. When you get that 401 error, you need to back off for a second or two, recalculate the nonce, and then resubmit the request. On Apr 28, 10:52 pm, Cory cory.imdi...@gmail.com wrote: Anyone have any ideas about this? I'm really not sure where to go or what to check from here, and I need to get this taken care of. Any information would be appreciated!
[twitter-dev] How to transition from basic auth to oAuth for my website
I have a website. It posts status updates to a single twitter account automatically. I store user name and password in a configuration file. I tried using oAuth to do the same thing, but this does not work because 1. twitter asks for user name and password 2. my website will not be able to automatically fill out the user name and password fields. Can you PLEASE tell me how I can achieve this? I'm assuming all the things I could do with basic auth is also possible with oAuth. Thank you.
Re: [twitter-dev] How to transition from basic auth to oAuth for my website
hi! because you are only posting to a single twitter account, what you need to do is create a client application (you can do this from http://dev.twitter.com/apps/new, and then bring up your application http://dev.twitter.com/apps and click on my access token. great - you now have everything you need token-wise. now, you can use any variety of oauth libraries. once you've chosen your library, then just feed it the consumer token / consumer secret / access token / access secret and you should be set. On Wed, Apr 28, 2010 at 8:40 PM, ebae eric...@gmail.com wrote: I have a website. It posts status updates to a single twitter account automatically. I store user name and password in a configuration file. I tried using oAuth to do the same thing, but this does not work because 1. twitter asks for user name and password 2. my website will not be able to automatically fill out the user name and password fields. Can you PLEASE tell me how I can achieve this? I'm assuming all the things I could do with basic auth is also possible with oAuth. Thank you. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Really, You're not going to suspend @julianperretta?
On 04/28/2010 04:23 PM, Dewald Pretorius wrote: Ducking the artillery shells and verbal mortar rounds in this thread, I just want to ask: Did you know @shitmydadsays actually uses status.net, and pushes its tweets from there into Twitter via the StatusNet-Twitter bridge? No, I didn't know that! Interesting ... -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
[twitter-dev] get public replies (or mentions) to following
Hi all, In my apps, I want to (1)get all recent official replies (or mentions) to my following and also the tweet's ids that replies reply to OR (2)get all replies to a tweet I found that I can use search API to get all recent replies to a username or m, but the results don't give me the tweet's id that each search result reply to. To get that id I need to use statuses/show/ id API to get full information of result-tweet. But this approach costs a lot of requests to server. Do you have any idea to solve this? Thanks.
