[twitter-dev] Re: Best practices
Hi, To answer your questions: 1) There is currently no limit. It is up to the user or application to determine if they should delete the direct messages. 2) It seems that the best thing to do when sending DMs programmatically is to attempt to send and gracefully handle any failure that comes your way. That would involve a single API call as opposed to two. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 24, 2009 at 5:03 AM, Nial wrote: > > I did a search but couldn't find anything of relevance. Here are a few > questions on best practice: > > 1) I'm developing a Twitter bot which accepts commands via Direct > Message and was wondering if there's a hard limit to the number of DMs > a user can store. Essentially: should I be deleting the DMs after I > receive and parse them? Will I reach a point where the account is > flooded with Direct Messages and I cannot receive anymore? > > 2) The bot is also capable of sending Direct Messages back to users. > At present, there's no check to see whether or not that particular > user is following the bot account. Is it considered best practice to > perform this check, or just to attempt to send the Direct Message and > fail gracefully if Twitter blocks the message? There seems to be some > difficulty with Twitter not returning valid following data, at > present. I'm just worried that if Twitter see an account sending > numerous DMs to accounts which are not following them, they'll label > the bot as spam. > > Thanks! >
[twitter-dev] Re: OAuth whitelisting?
You are correct. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 24, 2009 at 3:40 AM, Bill Kocik wrote: > > > Thanks, Doug. This was what I was originally thinking, but somehow I > convinced myself I was wrong. > > Hypothetical: It kinda sounds like if I have a large number of > simultaneous users, I'm better off not being whitelisted. Say I have > 1000 simultaneous users (humor me). If I'm not whitelisted, I can make > up to 100 authenticated queries per hour per user, since I'm using > their individual rate limits, but if I'm whitelisted I can only make > 20 calls per hour for each of those users since my limit is 20k/hour. > > Or am I missing something? > > > On Apr 24, 2:21 am, Doug Williams wrote: > > Your application's IP-based whitelisting will apply to all calls > > originating from the IP address. This includes unauthenticated and > > authenticated methods, regardless of user. Additionally, your > > application's authenticated calls made on behalf of a user will not > > count toward their 100 credits elsewhere. > > > > @dougw >
[twitter-dev] Re: OAuth whitelisting?
Your application's IP-based whitelisting will apply to all calls originating from the IP address. This includes unauthenticated and authenticated methods, regardless of user. Additionally, your application's authenticated calls made on behalf of a user will not count toward their 100 credits elsewhere. @dougw On 4/23/09, Bill Kocik wrote: > > Thanks. I realize it isn't available yet; my question could more > simply have been stated as "what will OAuth whitelisting mean, > exactly?", but since after I posted my question I realized I had a > fundamental misunderstanding of the effect whitelisting has on the > rate limits of app users (i.e., none) the question is really no longer > relevant. :) > > Actually, since I'm here, let me try this one (I'm checking my > understanding of what whitelisting does): Am I correct in thinking > that even if my app (or IP) is whitelisted, when I make requests on > behalf of authenticated users, their 100/hr per user rate limit still > applies, and that the elevated limit applies to unauth requests coming > from my app (IP)? > > On Apr 24, 12:16 am, Doug Williams wrote: >> Whitelisting by OAuth is currently not available. You will need a static >> IP >> address if you are running an EC2 applicaiton. >> >> Doug Williams >> Twitter API Supporthttp://twitter.com/dougw >> >> On Thu, Apr 23, 2009 at 8:35 PM, Peter Denton >> wrote: >> >> >> >> > Hi Bill, >> > Whitelisting is done per IP, related to the number of requests by your >> > server. >> >> > -Peter >> >> > On Thu, Apr 23, 2009 at 1:58 PM, Bill Kocik wrote: >> >> >> I was just looking at the form use to apply for whitelisting, which >> >> says you must fill it out while logged in as the account you want the >> >> rate limit raised for. In my case, my app will be used by arbitrary >> >> Twitter account holders, who will not be using my credentials, so >> >> whitelisting my Twitter login will do nothing for my app. I saw Alex >> >> mention in another thread that whitelisting by OAuth will become the >> >> preferred method for whitelisting apps running in clouds (mine will be >> >> in EC2). >> >> >> I am assuming that OAuth whitelisting means I'll be able to whitelist >> >> my app, and the raised limit would apply for requests having OAuth >> >> access tokens obtained by my application, regardless of the Twitter >> >> user they belong to? >> >> >> Thanks, >> >> -Bill >> >> > -- >> > Peter M. Denton >> >www.twibs.com >> > i...@twibs.com >> >> > Twibs makes Top 20 apps on Twitter -http://tinyurl.com/bopu6c > -- Sent from my mobile device Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: friends_timeline and following
This is still being worked on. Follow issue 419 for status updates. @dougw On 4/23/09, Don Park wrote: > > I don't think this is fixed, at least based on responses I am seeing. > If it was fixed then cache/cluster issues are delaying the results I > am expecting. As to the value type, I am seeing following value of 0 > instead of true/false. > -- Sent from my mobile device Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: OAuth whitelisting?
Whitelisting by OAuth is currently not available. You will need a static IP address if you are running an EC2 applicaiton. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 8:35 PM, Peter Denton wrote: > Hi Bill, > Whitelisting is done per IP, related to the number of requests by your > server. > > -Peter > > > On Thu, Apr 23, 2009 at 1:58 PM, Bill Kocik wrote: > >> >> >> I was just looking at the form use to apply for whitelisting, which >> says you must fill it out while logged in as the account you want the >> rate limit raised for. In my case, my app will be used by arbitrary >> Twitter account holders, who will not be using my credentials, so >> whitelisting my Twitter login will do nothing for my app. I saw Alex >> mention in another thread that whitelisting by OAuth will become the >> preferred method for whitelisting apps running in clouds (mine will be >> in EC2). >> >> I am assuming that OAuth whitelisting means I'll be able to whitelist >> my app, and the raised limit would apply for requests having OAuth >> access tokens obtained by my application, regardless of the Twitter >> user they belong to? >> >> Thanks, >> -Bill >> > > > > -- > Peter M. Denton > www.twibs.com > i...@twibs.com > > Twibs makes Top 20 apps on Twitter - http://tinyurl.com/bopu6c > > >
[twitter-dev] Re: What does "following" in user information do?
Please star Issue 419 [1] so you will be notified when the fix is shipped. 1. http://code.google.com/p/twitter-api/issues/detail?id=419 Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 8:11 PM, Carlos wrote: > > Still not working from the results I'm seeing. Has this issue been re- > opened? > > On Apr 19, 9:07 pm, Dossy Shiobara wrote: > > On 4/19/09 11:34 AM, Arnaud wrote: > > > > > And thank you for the update. > > > Unfortunately, it still doesn't seem to be fixed. > > > I still receive a lot of incorrect "following"values(INT and NULL > > > instead of BOOL) using the "statuses/followers" method. > > > > +1 ... users/show method returning empty node instead of > > boolean true/false. > > > > Can Matt re-open issue #157, or should we create a new issue to track > this? > > > > -- > > 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) >
[twitter-dev] Re: oAuth is BACK!
Nic, We are aware that the current lack of dynamic callback is limiting for development. In the meantime, we wanted to get OAuth support restored while we (and the OAuth consortium) develop a fix for this vulnerability. We intend to address this constraint in the near future. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 3:19 PM, Dr Nic wrote: > > If we cannot run-time configure the callback URI then we'll need > multiple application registrations for development + production? > (assuming the need for absolute URIs) > > Cheers > Nic > > On Apr 24, 7:38 am, Matt Sanford wrote: > > Hi there, > > > > I totally forgot about that change. Since the oauth callback is > > unsigned it was too easy to forge that data. I'm trying to find a good > > way to include it but right now calling verify_credentials is the best > > work around. > > > > Thanks; > >– Matt Sanford / @mzsanford > >Twitter API Developer > > > > On Apr 23, 2009, at 02:31 PM, mikehar wrote: > > > > > > > > > > > > > However, the callback no longer contains the user info. Why did this > > > change? > > > > > You can get the user info by calling account/ > > > verify_credentials.format. > > > > > On Apr 23, 2:20 pm, "@pud" wrote: > > >> Great work @al3x and the rest of the Twitter crew! > > > > >> My oAuth seems to be working once again: > http://fast140.com/oauth/authorize >
[twitter-dev] Changes for April 23, 2009
Along with partial OAuth support restoration, the following API changes were shipped: - Fixed (REST): Basic authentication now works with passwords containing a colon. (http://code.google.com/p/twitter-api/issues/detail?id=496) - Fixed (REST): Error message during downtime now matches documented response. (http://code.google.com/p/twitter-api/issues/detail?id=300) - Deprecated (REST): Support for the oauth_callback parameter has been removed due to security vulnerability. (http://bit.ly/18gF5a) - Fixed (OAuth): OAuth images are properly served from through HTTPS. ( http://code.google.com/p/twitter-api/issues/detail?id=476) Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: Twitter's official comment on our disabling of OAuth
Mobasoft, Rest assured we will make an announcement when OAuth support is restored. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 12:42 PM, Mobasoft wrote: > > @mzsanford > > Thanks Matt, no matter what all these other Yahoo's are saying about > you, it's appreciated! > > (j/k to all you Yahoo's) ;^) > > -Michael > > p.s. Is OAuth back on yet? I'd hate to see it start getting the > nickname of NOAuth. > > > On Apr 23, 1:43 pm, Chad Etzel wrote: > > On Thu, Apr 23, 2009 at 2:35 PM, Dossy Shiobara > wrote: > > > > > On 4/23/09 11:33 AM, Chad Etzel wrote: > > > > >> On Thu, Apr 23, 2009 at 11:19 AM, Dossy Shiobara > > >> wrote: > > > > >>> An attacker can't get in the middle of an > > >>> application communicating to Twitter using HTTP Basic Auth. > > > > >> WRONG. Anyone doing any sort of packet sniffing could easily get > > >> user/pass combos at will. Wireless promiscuous mode + WireShark = > > >> instant account hacking. This, of course, holds true only for http > > >> transactions (and not https transactions), but there are a good number > > >> of clients/apps that don't use the https endpoints. > > > > > Packet sniffing as an attack vector is significantly more difficult to > > > achieve than the OAuth attack is. Defend against the more likely > threats > > > before worrying about the less likely ones. > > > > I wholeheartedly disagree. Sit in a tech conference room with a > > laptop and sniff away at least a hundred accounts in under 5 minutes. > > I'm not saying I've done it, but I'm not saying I haven't, either > > > > > > > > >> Man in the middle attacks are certainly possible with Basic Auth as > > >> well. They just eat the original request, steal the user/pass combo, > > >> and do whatever they want with it. > > > > > This is a standard phishing attack, and standard advice for > anti-phishing > > > applies here. > > > > No, phishing != man-in-the-middle. If I hack a router to intercept > > all traffic headed toward twitter.com and then grok out the > > credentials, this is has nothing to do with social engineering or > > phishing... I've just screwed your account, and you have no idea how. > > > > Obviously there are attack vectors with both methods, but I contend > > that Basic Auth is much much much easier to attack than OAuth (even in > > its current state, and even moreso when it is upgraded/patched to deal > > with this new vector). > > > > -Chad >
[twitter-dev] Re: befriending with non-existing account started to return status code 404, it used to be 403
An HTTP 404 is the correct response because you are attempting to access a nonexistent resource. This behavior is correctly documented here [1]. 1. http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 9:03 AM, Yusuke wrote: > > Hi, > > I noticed that now the API returns 404 status code when a client > called /friendships/create/[non-existing-user].xml. > The API used to be returning 403 status code. > Will it be a permanent behavior? Or is it subject to change? > > I'll be nice if the status codes in exceptional cases are explicitly > documented so that client developers can confidently implement error > handling codes. > > Cheers, > Yusuke >
[twitter-dev] Re: weird things on twitter
Please see the post on http://status.twitter.com explaining this behavior. On 4/23/09, ytbryan wrote: > > hi all, > > i notice that a few people appeared under my "friends" pages. when > i click in to investigate further, i realised that i am not following > them. > > did anybody notice this ? > -- Sent from my mobile device Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: How do I find all replies to a status?
Jason, It is authenticated because the statuses/mentions timeline potentially includes protected updates. Making it unauthenticated is therefore not an option. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 1:02 PM, Doug Williams wrote: > Jason, > statuses/mentions would contain this data, and it is available via search. > Let me bring this up with Alex, because you make a good point. > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > On Wed, Apr 22, 2009 at 11:57 AM, Jason Wong wrote: > >> As I see it, replies also contain @screen_name in them. There's already >> an API structure to find these items, via statuses/mentions. Is there a >> reason why it's restricted to only the authenticating user and not open to >> access a screen_name / user_id parameter? >> >> I can easily implement this if I keep everyone's authentication tokens and >> doing statuses/mentions and checking the in_reply_to_status_id. But it's not >> efficient and will have way too many hits against the twitter server. >> >> What do you guys think? >> >> Jason. >> >> >> Doug Williams wrote: >> >> It requires a non trivial change to our architecture which means that >> until the product at large (twitter.com) adopts the idea of conversation >> threads, the API will be unable to offer this feature. >> >> >> Doug Williams >> Twitter API Support >> http://twitter.com/dougw >> >> >> On Wed, Apr 22, 2009 at 11:01 AM, Zac Bowling wrote: >> >>> >>> I see the bug was closed as "WONTFIX". Would it not be possible for >>> search to get a param for in_reply_to_status_id? >>> >>> I'm not working on any twitter projects anymore but it could lead to >>> some very interesting clients. >>> >>> >>> Zac >>> >>> >>> On Wed, Apr 22, 2009 at 10:11 AM, Doug Williams >>> wrote: >>> > Please see http://code.google.com/p/twitter-api/issues/detail?id=142 >>> > >>> > >>> > Doug Williams >>> > Twitter API Support >>> > http://twitter.com/dougw >>> > >>> > >>> > On Wed, Apr 22, 2009 at 10:04 AM, Jason Wong >>> wrote: >>> >> >>> >> I'm trying to find a way to get all replies to a certain status. >>> >> >>> >> I was looking at the statuses/mentions function, but according to the >>> >> documentation it only works with the authenticated user's screen_name. >>> >> If I use statuses/user_timeline and get a status id that I know has >>> >> replies, is there a way for me to get it without searching the >>> >> public_timeline and checking the in_reply_to_status_id field for that >>> >> status? It doesn't seem very efficient. >>> >> >>> >> Thanks, >>> >> Jason. >>> > >>> > >>> >> >> >
[twitter-dev] Re: Incorrect DMs in my feed?
So you see where my mind was going... Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 10:39 PM, Cameron Kaiser wrote: > > > s/data correction/data corruption/; > > > > (I think that's a sign I should go to bed.) > > As long as the corruption is corrected. > > -- > personal: > http://www.cameronkaiser.com/ -- > Cameron Kaiser * Floodgap Systems * www.floodgap.com * > ckai...@floodgap.com > -- Diplomacy is the art of letting someone else get your way. > - >
[twitter-dev] Re: API Changed for April 22, 2009
Hi, > 1) Should I use REST instead of the Search API? Will the REST > deprecate the Search soon, or maybe eventually, or "no worries" at > this moment? The REST and Search API offer separate functionality [1]. They will eventually be merged but for now you should use the Search API for trends and search data, and the REST API for timeline and user information. 2) asking the search API for 100 results seems to work, but does not > appear accessible from the advanced search page - can I expect to > continue to receive a set of 100 results with one request? We do not include the RPP value greater than 50 in advanced search because it does not present the type of user experience we want to provide. We will continue to offer a value of 100 for the API. 3) The search results appear to always be ordered by post time, in > ascending order. Are there currently plans to change this behavior? > For example, in a multiple word "OR" query it might be more > interesting for a human to see the "AND" results for the same words at > the very top, but of course they would not necessarily be in > chronological order. I want to calculate the coolness vector for a > search phrase, and sequence is essential. Search results, like Twitter timelines, will continue to be provided in chronological order, regardless of which operators are included in a query. 1. http://apiwiki.twitter.com/API-Overview Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 10:02 PM, explicious wrote: > > Hello, > > Thank you for the updates. I have a few questions. > > 1) Should I use REST instead of the Search API? Will the REST > deprecate the Search soon, or maybe eventually, or "no worries" at > this moment? > > 2) asking the search API for 100 results seems to work, but does not > appear accessible from the advanced search page - can I expect to > continue to receive a set of 100 results with one request? > > 3) The search results appear to always be ordered by post time, in > ascending order. Are there currently plans to change this behavior? > For example, in a multiple word "OR" query it might be more > interesting for a human to see the "AND" results for the same words at > the very top, but of course they would not necessarily be in > chronological order. I want to calculate the coolness vector for a > search phrase, and sequence is essential. > > Have a great night. > > Waitman > > > > > > > On Apr 22, 9:32 pm, Matt Sanford wrote: > > Hi all, > > > > Fixed (REST): When sending >
[twitter-dev] Re: Twitter's official comment on our disabling of OAuth
Bill, The majority of our developers find OAuth sufficient because they are writing a Web applications. We are pleased that the deprecation of the source parameter lowered our support load and continues to drive adoption of our preferred authentication scheme. There are of course other cases where developers find the current implementation's beta status or browser requirement concerning. I have yet to reject a source parameter request that provides a valid argument explaining why OAuth does not meet the application's needs. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 6:50 PM, Bill Robertson wrote: > > I respectfully disagree. (I would colorfully disagree, but you seem > pretty beat up right now and you don't deserve any guff) I think > developers of smaller apps see that little tag-line as a good source > of advertising, and it seems inaccessible now if you're new (right? > wrong?). You can only get it if you use OAuth, but OAuth is now > disabled? > > Anyway, just my $0.02. Prioritize it like everything else you need to > do (i.e. it's the 37th #1 thing on your list.) > > Good luck. > > On Apr 22, 7:58 pm, Alex Payne wrote: > > We don't consider source registration a "key feature". It's an > > incentive we provide to our developers. We wanted to encourage new > > developers to look into OAuth. It won't be in beta forever, after all. > > > > We have to balance the reality of testing a new technology in our > > stack with encouraging that technology's adoption. OAuth will provide > > the Twitter developer community with a number of benefits, and that's > > the direction in which we want to move, even while there are kinks to > > work out. > > > > > > > > On Wed, Apr 22, 2009 at 15:37, bwannon wrote: > > > > > If beta for you guys means "still in testing, not suitable for > > > production use", then why depreciate key features from basic auth like > > > source registration before you have a production ready release? > > > > > On Apr 22, 3:27 pm, Alex Payne wrote: > > >>http://blog.twitter.com/2009/04/whats-deal-with-oauth.html > > > > >> In short: there's a security issue with OAuth, and the major OAuth > > >> providers are working together to patch the vulnerability before > > >> information about the issue is publicly released. That information > > >> will be available athttp://oauth.net/atmidnight, PST. > > > > >> In cooperation with this consortium of other OAuth providers > > >> (including Yahoo!, Google, Netflix, etc.), we agreed not to disclose > > >> the nature of the vulnerability, nor even that a vulnerability > > >> existed, until all members of the group agreed to do so. I apologize > > >> for what must have seemed unnecessarily tight-lipped communication > > >> around this issue, but please understand that we and the other > > >> companies involved are trying to mitigate the impact of this > > >> vulnerability as much as possible. > > > > >> Please also note that our OAuth support is in beta, albeit public > > >> beta. We have not suggested to developers that they rely solely on > > >> OAuth until our support of the standard leaves beta. I know that some > > >> companies practice a policy of "perpetual beta", but at Twitter, we do > > >> not. For us, "beta" really means "still in testing, not suitable for > > >> production use". > > > > >> Thanks for your patience and understanding. > > > > >> -- > > >> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x > > > > -- > > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >
[twitter-dev] Re: Add an API for knowing last tweet read by all clients
This is included in the V2 roadmap: http://apiwiki.twitter.com/V2-Roadmap Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 3:54 PM, Open Hebrew wrote: > > I have different twitter clients on different OSes and phones, I would > like twitter to have an API which logs globally the last tweet i read > in my friends list, that can be access and updated by all clients. > > This way, when i move between my computer an my iphone I can "sync" > the friend list to the last i read globally, and not of that specific > program I am using. >
[twitter-dev] Re: Incorrect DMs in my feed?
s/data correction/data corruption/; (I think that's a sign I should go to bed.) Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 10:11 PM, Doug Williams wrote: > There was a data correction issue which is being resolved. This should be > fixed shortly. > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > > On Wed, Apr 22, 2009 at 9:59 PM, Lachlan Hardy > wrote: > >> >> > I'm getting incorrect DMs in my received and sent feeds (i.e. to/from >> > different people that aren't me). What info would be helpful to start >> > debugging this? Anyone else seeing this behavior? >> >> Yep! >> >> And I've no idea. I'll just raise a support request if it happens again. >> > >
[twitter-dev] Re: Incorrect DMs in my feed?
There was a data correction issue which is being resolved. This should be fixed shortly. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 9:59 PM, Lachlan Hardy wrote: > > > I'm getting incorrect DMs in my received and sent feeds (i.e. to/from > > different people that aren't me). What info would be helpful to start > > debugging this? Anyone else seeing this behavior? > > Yep! > > And I've no idea. I'll just raise a support request if it happens again. >
[twitter-dev] Re: [twitter-api-announce] Twitter's official comment on our disabling of OAuth
Julio, We intend to keep Basic Auth available until we feel that OAuth can successfully exit beta as a fully functioning authentication offer. This includes support and a positive user experience for desktop clients. Thanks, @dougw On 4/22/09, Julio Biason wrote: > > On Thu, Apr 23, 2009 at 10:23 AM, Chris Latko wrote: >> I'm going to have to side with Alex on this one. The APIs should be >> protected by OAuth and that is what should be pushed out and the basic >> auth deprecated. What I don't really understand is why it has taken >> until now to promote OAuth. I understand OAuth is an evolving >> standard, but it has been around for quite a while. > > Still waiting for a good explanation of how to use OAuth in a > console-only, no-browser environment. Until then, I see that Basic > Auth should remain active. > > -- > Julio Biason > Twitter: http://twitter.com/juliobiason > -- Sent from my mobile device Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: How do I find all replies to a status?
Jason, statuses/mentions would contain this data, and it is available via search. Let me bring this up with Alex, because you make a good point. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 11:57 AM, Jason Wong wrote: > As I see it, replies also contain @screen_name in them. There's already an > API structure to find these items, via statuses/mentions. Is there a reason > why it's restricted to only the authenticating user and not open to access a > screen_name / user_id parameter? > > I can easily implement this if I keep everyone's authentication tokens and > doing statuses/mentions and checking the in_reply_to_status_id. But it's not > efficient and will have way too many hits against the twitter server. > > What do you guys think? > > Jason. > > > Doug Williams wrote: > > It requires a non trivial change to our architecture which means that until > the product at large (twitter.com) adopts the idea of conversation > threads, the API will be unable to offer this feature. > > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > On Wed, Apr 22, 2009 at 11:01 AM, Zac Bowling wrote: > >> >> I see the bug was closed as "WONTFIX". Would it not be possible for >> search to get a param for in_reply_to_status_id? >> >> I'm not working on any twitter projects anymore but it could lead to >> some very interesting clients. >> >> >> Zac >> >> >> On Wed, Apr 22, 2009 at 10:11 AM, Doug Williams wrote: >> > Please see http://code.google.com/p/twitter-api/issues/detail?id=142 >> > >> > >> > Doug Williams >> > Twitter API Support >> > http://twitter.com/dougw >> > >> > >> > On Wed, Apr 22, 2009 at 10:04 AM, Jason Wong >> wrote: >> >> >> >> I'm trying to find a way to get all replies to a certain status. >> >> >> >> I was looking at the statuses/mentions function, but according to the >> >> documentation it only works with the authenticated user's screen_name. >> >> If I use statuses/user_timeline and get a status id that I know has >> >> replies, is there a way for me to get it without searching the >> >> public_timeline and checking the in_reply_to_status_id field for that >> >> status? It doesn't seem very efficient. >> >> >> >> Thanks, >> >> Jason. >> > >> > >> > >
[twitter-dev] Re: OAUTH Feature currently disabled
Our official position has been stated. We will be able to release more details shortly. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 12:51 PM, Jerry Chen wrote: > > On Apr 22, 2:43 pm, Jesse Stay wrote: > > Why are we learning this from CNet? > > Perhaps Twitter has no time to play firefighter here and is instead > actually fixing the problem? >
[twitter-dev] Re: Send status update with OAuth/PHP/cURL
Yes, we temporarily disabled the feature. We will have more words to offer
soon, hopefully by the end of the day.
Thanks,
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Wed, Apr 22, 2009 at 11:41 AM, Burhan TANWEER wrote:
> Hi Doug,
>
> I have downloaded Abraham's code for OAuth. It has worked earlier but now I
> am getting error message
>
> *" This feature is temporarily disabled.
> Thanks for your patience while we work to restore it."*
> **
> I have also tried to test OAuth from his own server but I get the same
> error message. Did something change in OAuth?
> **
>
> On Tue, Apr 21, 2009 at 5:54 PM, Doug D wrote:
>
>>
>> Thanks Chad!
>>
>> I've checked out Abraham's OAuth lib, but I don't see how to update a
>> twitter status. His example seems to only authenticate and return data
>> on the person who's authenticated.
>>
>> doug
>>
>>
>> On Apr 21, 5:00 pm, Chad Etzel wrote:
>> > Take a look at Abraham Williams' excellent Twitter PHP Oauth lib:
>> >
>> > http://twitter.abrah.am/
>> >
>> > -Chad
>> >
>> > On Tue, Apr 21, 2009 at 4:36 PM, Doug D wrote:
>> >
>> > > I've been digging in to the Twitter OAuth stuff and am able to sign
>> > > into my site with the Twitter authentication, but I'm wondering if
>> > > there is a way to use the OAuth credentails to send a status update
>> > > using PHP and cURL. The code below sends an update, but only when a
>> > > static username:password is filled in.
>> >
>> > > My goal it to update (your) Twitter status from my site once you are
>> > > authenticated by Twitter. Any thoughts or tutorials? Thanks!
>> >
>> > > // Set username and password
>> > > $username = 'name';
>> > > $password = 'password';
>> >
>> > > // The message you want to send
>> > > $message = 'My status update';
>> >
>> > > // The twitter API address
>> > > $url = 'http://twitter.com/statuses/update.xml';
>> >
>> > > // Alternative JSON version
>> > > // $url = 'http://twitter.com/statuses/update.json';
>> >
>> > > // Set up and execute the curl process
>> > > $curl_handle = curl_init();
>> >
>> > > curl_setopt($curl_handle, CURLOPT_URL, "$url");
>> > > curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 2);
>> > > curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1);
>> > > curl_setopt($curl_handle, CURLOPT_POST, 1);
>> > > curl_setopt($curl_handle, CURLOPT_POSTFIELDS, "status=$message");
>> > > curl_setopt($curl_handle, CURLOPT_USERPWD, "$username:$password");
>> > > $buffer = curl_exec($curl_handle);
>> > > curl_close($curl_handle);
>> >
>> > > // check for success or failure
>> > > if (empty($buffer)) {
>> > >echo 'message';
>> > > } else {
>> > >echo 'success';
>> > > }
>> >
>> >
>>
>
>
>
> --
> Sincerely,
>
> Burhan Tanweer
> www.explorewww.com
> expl...@explorewww.com
>
>
[twitter-dev] Re: How do I find all replies to a status?
It requires a non trivial change to our architecture which means that until the product at large (twitter.com) adopts the idea of conversation threads, the API will be unable to offer this feature. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 11:01 AM, Zac Bowling wrote: > > I see the bug was closed as "WONTFIX". Would it not be possible for > search to get a param for in_reply_to_status_id? > > I'm not working on any twitter projects anymore but it could lead to > some very interesting clients. > > > Zac > > > On Wed, Apr 22, 2009 at 10:11 AM, Doug Williams wrote: > > Please see http://code.google.com/p/twitter-api/issues/detail?id=142 > > > > > > Doug Williams > > Twitter API Support > > http://twitter.com/dougw > > > > > > On Wed, Apr 22, 2009 at 10:04 AM, Jason Wong > wrote: > >> > >> I'm trying to find a way to get all replies to a certain status. > >> > >> I was looking at the statuses/mentions function, but according to the > >> documentation it only works with the authenticated user's screen_name. > >> If I use statuses/user_timeline and get a status id that I know has > >> replies, is there a way for me to get it without searching the > >> public_timeline and checking the in_reply_to_status_id field for that > >> status? It doesn't seem very efficient. > >> > >> Thanks, > >> Jason. > > > > >
[twitter-dev] Re: How do I find all replies to a status?
Please see http://code.google.com/p/twitter-api/issues/detail?id=142 Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 10:04 AM, Jason Wong wrote: > > I'm trying to find a way to get all replies to a certain status. > > I was looking at the statuses/mentions function, but according to the > documentation it only works with the authenticated user's screen_name. > If I use statuses/user_timeline and get a status id that I know has > replies, is there a way for me to get it without searching the > public_timeline and checking the in_reply_to_status_id field for that > status? It doesn't seem very efficient. > > Thanks, > Jason. >
[twitter-dev] Re: OAUTH Feature currently disabled
Shannon, More details to come. Thank you for your patience. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 22, 2009 at 8:43 AM, Shannon Whitley wrote: > > Hi, Doug. I think we understand the part about "authenticate" being > down, but oAuth isn't working at all right now. > > On Apr 22, 8:33 am, Doug Williams wrote: > > The feature was disabled over the weekend. It will hopefully be > > restore within a day. That is all we can say at this time, but more > > details will flow after restoration. We appreciate your patience. > > > > Doug > > > > On 4/22/09, Dossy Shiobara wrote: > > > > > > > > > On 4/22/09 11:15 AM, iematthew wrote: > > >> If I'm not mistaken, OAuth is still in public Beta. Or did I miss the > > >> memo? (wouldn't have been the first time). I doubt it is wise at this > > >> point to push OAuth features live to the public. :) > > > > > You forgot to put the new cover page on your TPS report. > > > > > -- > > > 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) > > > > -- > > Sent from my mobile device > > > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw >
[twitter-dev] Re: OAUTH Feature currently disabled
The feature was disabled over the weekend. It will hopefully be restore within a day. That is all we can say at this time, but more details will flow after restoration. We appreciate your patience. Doug On 4/22/09, Dossy Shiobara wrote: > > On 4/22/09 11:15 AM, iematthew wrote: >> If I'm not mistaken, OAuth is still in public Beta. Or did I miss the >> memo? (wouldn't have been the first time). I doubt it is wise at this >> point to push OAuth features live to the public. :) > > You forgot to put the new cover page on your TPS report. > > -- > 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) > -- Sent from my mobile device Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: Twitter4J 2.0.0 released, supports OAuth authorization scheme
I updated the library page to reflect your new release. Thanks for giving back! Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 21, 2009 at 5:06 PM, Yusuke Yamamoto wrote: > > Hi all, > > I'm glad to announce that Twitter4J 2.0.0 is now available. > > http://yusuke.homeip.net/blog/2009/04/19/twitter4j_2_0_0_released_now_officially_supports_oauth_authorization_scheme.html > > Twitter4J is an open-sourced, mavenized and Google App Engine safe Java > library for the Twitter API which is released under the BSD license. > > This version is already available in the Maven central repository. > http://repo1.maven.org/maven2/net/homeip/yusuke/twitter4j/ > > Finally, Twitter4J supports OAuth authorization scheme. > Projects depending on Twitter4J are encouraged to migrate to the latest > version to support OAuth. > > Best regards, > -- > Yusuke Yamamoto > yus...@mac.com > >
[twitter-dev] Issues list and transparency
All, Until today, overwhelming and burgeoning were both adjectives that described our issue list [1]. Today I am proud to report that it is now consumable, pleasant, and even helpful. Everything that you find in that list is currently owned by our team or awaiting verification. Moving forward this is how we want to continue to use this list. We want developers to know what we are currently working on so they can plan accordingly. This list should serve as the definitive guide. Some of you have already noticed [2] that we have closed or moved many of the defects or enhancements that used to reside on that list. We have created a V2 Roadmap document [3] where we will store such longterm goals. Please note that the introduction indicates we make no promises or guarantees when or if these items will be delivered. Finally, there were a few issues that were simply closed to reflect that they were not going to be fixed in the foreseeable future. We think that this physical separation of priorities will continue to assist developers in understanding where our priorities lie. As such we are going to implement the following policy changes for the issues list: 1) We are going to be more frank with priorities. If something is of value but not a high priority in the near-term, it will be placed on the Roadmap [3] document. 2) If a reported issue can be classified as a defect, a high value enhancement, or as low-hanging fruit it will be assigned accordingly. 3) If a defect is reported without a detailed explanation, it will be promptly closed. We want to promote good habits where defect reports are more about helping engineers find problems, and less about discussing proper bug reporting (as is often the case). Finally, there is but one change we will be making over the next few weeks to communicate more effectively with developers. Transparency and predictability are a common concern so one step at a time, let's fix the fractured conversation. As always, please forward me any suggestions: http://twitter.com/twitterapi 1. http://code.google.com/p/twitter-api/issues/list 2. http://twitter.com/h0h0h0/status/1578636888 3. http://apiwiki.twitter.com/V2-Roadmap Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: Only 1 of Several Twits are Sent as Device Updates
Are the updates exactly the same? Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 21, 2009 at 10:17 AM, Gilbert wrote: > > Hi, > > I notice that if I post updates in succession (within a very short > time), only the first one gets sent to my followers' device. > > Is this to avoid spam? > > What's the exact policy on this? >
[twitter-dev] Re: Search friends timeline
Integrating search into your friends_timeline is something we want to do in the future. With the separation of the Search and REST APIs, it isn't a trivial feature. For now, you have to parse out results from timelines client side. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 21, 2009 at 9:44 AM, mikejablonski wrote: > > That was my plan for now. It just makes it harder to get the next X > friend status messages that have "XYZ" in them. I'm surprised this > isn't a more requested feature. Thanks! > > On Apr 21, 8:28 am, Chad Etzel wrote: > > You can't. > > > > Just get the friends timeline and filter it client-side. You'll have > > more granular control over the filtering that way anyway. > > > > -Chad > > > > On Tue, Apr 21, 2009 at 11:16 AM, mikejablonski > wrote: > > > > > I've looked at the docs and searched the group, but I can't find any > > > way to search your friends timeline. How can I get a filtered set of > > > friend status messages based on a query? Is this possible? I know I > > > could use the search API and throw away all my non-friends, but that > > > won't work well for a lot of reasons. Thanks! >
[twitter-dev] Re: Read and store Twitter responses
Nick, Batch INSERTs are great for people looking to for performance tweaks. Serial INSERT statements within the iteration loop keeps things simple for those just starting out. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 4:14 PM, Nick Arnett wrote: > > > On Mon, Apr 20, 2009 at 3:16 PM, Doug Williams wrote: > > 3. For each status in the set, perform an SQL insert to save the status. > > > Or, I would hope, create an array of inserts and do a multi-insert, which > will be far faster than iterating through a list. > > http://www.desilva.biz/mysql/insert.html > > I'll bet you knew that, but I just had to note it because the performance > difference is enormous. > > Nick > (not really a PHP guy, but years of (often painfully gained) MySQL > performance knowledge) >
[twitter-dev] Re: Search API Rate Limited even with OAuth
Please see our article on rate limiting [1]. You will learn why the Search API does not have a notion of authentication and how its rate limiting differs from the REST API. 1. http://apiwiki.twitter.com/Rate-limiting Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 3:14 PM, Ammo Collector wrote: > > Hello, > > We're getting 503 rate limit responses from Search API even when > passing in OAuth tokens. The same tokens used on friends/followers/ > statuses go through fine so we know the tokens are good. It appears > we're getting IP limited even with OAuth... > > Klout.net >
[twitter-dev] Re: Search API Rate Limited even with OAuth
Please see our article on rate limiting [1]. You will learn why the Search API does not have a notion of authentication and how its rate limiting differs from the REST API. 1. http://apiwiki.twitter.com/Rate-limiting Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 3:14 PM, Ammo Collector wrote: > > Hello, > > We're getting 503 rate limit responses from Search API even when > passing in OAuth tokens. The same tokens used on friends/followers/ > statuses go through fine so we know the tokens are good. It appears > we're getting IP limited even with OAuth... > > Klout.net >
[twitter-dev] Re: Read and store Twitter responses
I've broken the task into logical steps to get you started. I'd suggest searching Google and the wiki [1] for the libraries and implementation details for each: 1. Download a timeline or a set of statuses. 2. Iterate through that set of statuses, pulling out each individual status. 3. For each status in the set, perform an SQL insert to save the status. A great way to learn is to try and find sample code that gets you each of these steps separately, then put them together. There is plenty of PHP and MySQL sample code available online or in books to get you started. 1. http://apiwiki.twitter.com/Libraries#PHP Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 1:53 PM, Andrew Badera wrote: > This isn't a SQL tutorial nor a MySQL list. Some might suggest you'd be > better off learning the basics of what you're trying to do -- learning how > to walk before you can run and all that. > > Thanks- > - Andy Badera > - and...@badera.us > - Google me: http://www.google.com/search?q=andrew+badera > > > > > On Mon, Apr 20, 2009 at 4:41 PM, CWitt wrote: > >> >> Is there anywhere I could take a look at some of this code to store >> the Twitter data in a MySQL databases? >> >> On Apr 19, 8:50 pm, Nick Arnett wrote: >> > On Sun, Apr 19, 2009 at 2:45 PM, CWitt wrote: >> > >> > > My skills are rather limited, but I was thinking PHP and MySQL. I was >> > > thinking about hiring it out, but putting together the process flow to >> > > help the programmer and also help me find the correct programmer. >> > >> > PHP and MySQL sound appropriate to what you're hoping to do. Storing >> > Twitter data in MySQL is generally not a big deal, since there is such >> > limited data. A lot of us have probably created similar schemas for >> that >> > purpose. The rest of your code sounds slightly more complex, especially >> if >> > you're trying to do some sort of natural language parsing, which is >> always >> > hard. I don't know if there are libraries in PHP for that purpose. >> There >> > are in other languages. >> > >> > In any case, without specifics, it would be hard for anyone to guide >> you. >> > >> > Nick >> > >
[twitter-dev] Re: Reciprocal protected updates
>From a Twitter point of view, being followed by someone and following someone are two distinctly different relationships. To get access to protected tweets, you must follow that user and get approval. This behavior is not going to change and following a protected user will remain as a requirement to access their statuses. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 1:57 PM, Sean Randall wrote: > > Hello, > > New on group so pardon my mistakes, I'm happy to be slapped down a little. > > This isn't directly an API question I think but here goes: > > If Bob is following me and has protected updates, I still cannot see them > unless I follow Bob. Is this intentional/likely to change? Doesn't being > followed indicate some semblance of connectivity? They are two discrete > functions, granted, but wouldn't this kill a little overhead when we come > to > reciprocate following people? > > Sean. > >
[twitter-dev] Re: How long until a @reply can be duplicated / repeated?
Adding this to the statuses/update documentation. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 1:34 PM, Ryan wrote: > > Thanks Chad! > > On Apr 20, 1:08 pm, Chad Etzel wrote: > > You would NOT see the duplicate update. Twitter effectively drops the > > update when it's a duplicate. It's cast into the void. The fail > > whale noms it. It's a dead parrot :) > > > > -Chad > > > > > > > > On Mon, Apr 20, 2009 at 4:01 PM, Ryan wrote: > > > > > Chad, > > > > > If Twitter ignores duplicate updates than I WOULD or WOULD NOT see the > > > updates? > > > > > On Apr 20, 12:35 pm, Chad Etzel wrote: > > >> twitter ignores updates that are an exact duplicate of the previous > update. > > >> if you post > > >> @bob hi! > > >> then > > >> @bob hi!! > > > > >> you should see both. > > >> -chad > > > > >> On Mon, Apr 20, 2009 at 3:31 PM, Ryan > wrote: > > > > >> > I send the following message: @bob hi! and wait two minutes and send > > >> > the same message, @bob hi! > > > > >> > I only see one message when polling the "mentions/replies" API. > > > > >> > Is there an undocumented interval on how long one has to wait until > > >> > the second message shows up in the API? Or... how long the user > > >> > sending the @reply has to wait??? >
[twitter-dev] Re: API returning 0 and false for Boolean XML elements
Please see 419 [1] and 474 [2]. 1. http://code.google.com/p/twitter-api/issues/detail?id=419 2. http://code.google.com/p/twitter-api/issues/detail?id=474 Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 20, 2009 at 10:42 AM, Dimebrain wrote: > > I'm calling /direct_messages.xml and getting back this: > > > - > > 98485094 > 780830 > - > > Top secret DM of incalculable value. > > 11173402 > Mon Apr 20 17:14:39 + 2009 > BPAndrew > dimebrain > - > > 780830 > Andrew M > BPAndrew > Ottawa > - > > First Sea Lord Admiral Sir BPAndrew McHugeWangington III > > - > > > http://s3.amazonaws.com/twitter_production/profile_images/145551479/DSC03176_normal_normal.JPG > > > false > 171 > 1A1B1F > 66 > 2FC2EF > 252429 > 181A1E > 40 > Mon Feb 19 19:15:39 + 2007 > 99 > -18000 > Eastern Time (US & Canada) > - > > http://static.twitter.com/images/themes/theme9/bg.gif > > false > 6221 > false > false > > - > > 11173402 > Daniel Crenna > dimebrain > Ottawa (soon) > - > > Daniel Crenna builds social software. Writing a book on Twitter > development, and creating TweetSharp with @jdiller. > > - > > > http://s3.amazonaws.com/twitter_production/profile_images/87135858/0065_540_normal.png > > http://www.dimebrain.com > false > 378 > 050f10 > 33 > 0084B4 > e0e0e0 > 00 > 290 > Fri Dec 14 18:48:52 + 2007 > 63 > -14400 > Atlantic Time (Canada) > - > > > http://s3.amazonaws.com/twitter_production/profile_background_images/3243957/Social_Background.png > > false > 894 > 0 > 0 > > > > > The part of interest is the fact that the sender's notifications/ > following elements are populated with "false" while the recipient's > values for the same are 0's --> smells like a bug, but wanted to check > here first. >
[twitter-dev] Re: API limits - what am I missing? Seeking clarity on API request limits.
> > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request? You can get 200 statuses per requests. Therefore you will have to use 10 calls to retrieve 1950 statuses. Paging in this way is the most effective, server friendly way to do this. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 1:07 PM, Khyron wrote: > I see the 2 following statements made, in the following order within > moments > of each other at http://apiwiki.twitter.com/REST+API+Documentation. > > > Under "Pagination Limiting": > > "Clients may request up to 3,200 statuses via the page and count > parameters. Requests for more than the limit will result in a reply with a > status code of 200 and an empty result in the format requested." > > Under "Be Nice to the Servers": > > "If your application keeps a local archive that persists between sessions, > it's > okay to request an entire timeline up to 200 statuses." > > > So I can only request up to 200 statuses even though the limit using page > or count is 3200? What gives? > > I'd like to pull about 1950 statuses, all of my updates, in one API > connection. > Is my limit 200 per API request (requiring 10 API requests) OR is my limit > 1950 in one API request? Are there other parameters besides page and > count which are more server friendly, thus allowing larger requests? > > What am I missing? Can someone clarify please? Now that I figured out > how to do what I want to do, I want to make sure that I play by the rules > so that I don't get blacklisted for killing the servers. > > Thanks in advance yet again! > > -- > "You can choose your friends, you can choose the deals." - Equity Private > > AlphaGuy - http://alphaguy.blogspot.com > On Twitter - @khyron4eva > >
[twitter-dev] Re: Test Account Procedures
We do not have any notion of a test account. Developers occasionally create development accounts to keep personal or application accounts clear of noise from development and debugging efforts. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 10:40 PM, Greg wrote: > > Hi Alex, > > I was wondering if you have a provision/process for obtaining Test > Accounts and Data. I want to try to avoid creating test accounts. > > Thanks, > Greg. >
[twitter-dev] Re: Link in updates from api
Simply include the URL in the status field of the update. Twitter will automatically recognize it is a link and display it as such. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 2:39 PM, Vaibhav wrote: > > Hi All, > > I want to add a link in the tweet, I send from my application using > apis. Please let me know how can I do that? > > Thanks >
[twitter-dev] Re: About statuses/friends_timeline
For performance reasons, we cache each status object and construct the timeline from these cached objects at request-time. Therefore, complete user objects are returned with each status in a timeline. If you have a project that is bandwidth constrained, you should set up a proxy that strips unnecessary fields before forwarding the data to the edge device. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 12:13 PM, Vitus wrote: > > Hi2all! > > I've found, that http://twitter.com/statuses/friends_timeline.xml > response with XML document, where info about user is repeated for > every status. I think, it's so uneffective by traffic volume reason! > > How can I get friend's statuses without full info about the author? > > Thanks! >
[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?
Jeff, We are still thinking internally about how we want to get around the browser for OAuth token requests. Although, at this time we don't have a particular implementation to share. Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Apr 19, 2009 at 9:41 PM, Jeff Bishop wrote: > Doug, > > I think if the user could log in to Twitter from a link and then be > redirected to a place where the code could be shown to paste into the > desktop application then that would work fine. Heck, you could even put a > "copy to clipboard" button on that page so that the user could paste it in. > Is this something planned or does it already exist? > > Jeff > > > - Original Message - > *From:* Doug Williams > *To:* twitter-development-talk@googlegroups.com > *Sent:* Sunday, April 19, 2009 9:22 PM > *Subject:* [twitter-dev] Re: oAUTH - can it be done without interaction > with a core browser? > > The call to http://twitter.com/oauth/authorize (or the Sign in with > Twitter equivalent http://twitter.com/oauth/authenticate) requires a > browser to render the HTML necessary for the user prompt. This is a > limitation we recognize with the current beta release of the OAuth > implementation. > > Doug Williams > Twitter API Support > http://twitter.com/dougw > > > On Sun, Apr 19, 2009 at 1:37 PM, Guan Yang wrote: > >> >> On Sun, Apr 19, 2009 at 14:37, Jeff Bishop wrote: >> > 1. Get all of the required items from the user outside of Twitter's >> > interface? >> > 2. Authenticate (like with basic auth of some type using XML posts)? >> > 3. Be able to post back to get the token information. >> >> I'm not completely sure what you want, but you could do something like >> this: >> >> - Obtain a request token and secret. >> - Start up a browser and send the user to >> http://twitter.com/oauth/authorize >> - Display a button that says something like "click here when you're done" >> - When the user clicks that button, assume that you're authorized with >> Twitter, and make a request to obtain the access token. >> - If that's not the case, repeat the process. >> >> The point is that you don't really need any information back through >> the callback other than the fact that the user has completed the >> authorization process. But that can be accomplished simply by having >> the user click a button. >> >> If you are able to register URI schemes in the operating system that >> will launch your app, there is a different way of doing this. Suppose >> you've registered mycoolapp:// with the operating system. Then you can >> supply an oauth_callback parameter to >> http://twitter.com/oauth/authorize that looks something like this: >> >> mycoolapp://twitter-authorize-complete >> >> After successful authorization, Twitter will then redirect to something >> like >> >> >> mycoolapp://twitter-authorize-complete?oauth_token=xxx&screen_name=guan&user_id=1234&other_params=values >> >> That way your app will automatically be launched after authorization >> and you can call access_token at that point. >> >> Guan >> > >
[twitter-dev] Re: Update on product category
As Nick said this does not sound like a good reason to create multiple accounts. Though Twitter currently has no official policy on this type of usage, it is expected that you will create as few accounts as possible for your application. Since all of the ad updates will be coming from the same site, it is advisable for you to create a single account, and use things like hashtags or keywords to help your followers find which updates are relevant to them. Also, I don't know what type of ads you will be tweeting, but apps blasting users with spam-like updates (e.g. "We've got a new deal for you guys: http://mysite.com/deals) will be reported to @spam and suspended. So please, make sure any updates coming from your application are relevant, useful, and definitively not spam. Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Apr 19, 2009 at 1:34 PM, Nick Arnett wrote: > > > On Sun, Apr 19, 2009 at 1:14 PM, Clodoaldo Pinto Neto < > clodoaldo.pi...@gmail.com> wrote: >> >> >> Now the question: Is there a way to create different kinds of posts >> for a single user (the site's bot) that can be followed individually? >> Or must I create more than two thousand users? >> >> If this use is against any Twitter policy please excuse me as I have >> no experience with it. > > > I think you'll find that Twitter has said repeatedly that this is not an > appropriate reason to create lots of accounts, though they'll make > exceptions if there's a very good reason. > > Seems to me that you might be able to accomplish your goal with hash tags, > but that means that the "followers" would not follow them in the usual way, > but would subscribe to a service that filtered by hash tag. > > If hash tags are going to survive and prosper, it seems that clients would > do well to allow them to serve as filters (only show me tweets from user X > with tags [a, b, c] or never show me tweets from user X with tags [a, b, > d]). That sort of thing. > > Nick >
[twitter-dev] Re: oAUTH - can it be done without interaction with a core browser?
The call to http://twitter.com/oauth/authorize (or the Sign in with Twitter equivalent http://twitter.com/oauth/authenticate) requires a browser to render the HTML necessary for the user prompt. This is a limitation we recognize with the current beta release of the OAuth implementation. Doug Williams Twitter API Support http://twitter.com/dougw On Sun, Apr 19, 2009 at 1:37 PM, Guan Yang wrote: > > On Sun, Apr 19, 2009 at 14:37, Jeff Bishop wrote: > > 1. Get all of the required items from the user outside of Twitter's > > interface? > > 2. Authenticate (like with basic auth of some type using XML posts)? > > 3. Be able to post back to get the token information. > > I'm not completely sure what you want, but you could do something like > this: > > - Obtain a request token and secret. > - Start up a browser and send the user to > http://twitter.com/oauth/authorize > - Display a button that says something like "click here when you're done" > - When the user clicks that button, assume that you're authorized with > Twitter, and make a request to obtain the access token. > - If that's not the case, repeat the process. > > The point is that you don't really need any information back through > the callback other than the fact that the user has completed the > authorization process. But that can be accomplished simply by having > the user click a button. > > If you are able to register URI schemes in the operating system that > will launch your app, there is a different way of doing this. Suppose > you've registered mycoolapp:// with the operating system. Then you can > supply an oauth_callback parameter to > http://twitter.com/oauth/authorize that looks something like this: > > mycoolapp://twitter-authorize-complete > > After successful authorization, Twitter will then redirect to something > like > > > mycoolapp://twitter-authorize-complete?oauth_token=xxx&screen_name=guan&user_id=1234&other_params=values > > That way your app will automatically be launched after authorization > and you can call access_token at that point. > > Guan >
[twitter-dev] Re: Oauth button
Shannon, I have asked our newly-staffed design team to create official Twitter buttons. We would like to give users a standardized experience around the Web. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 18, 2009 at 6:13 PM, Shannon Whitley wrote: > > I wish someone could have been there when I created the "Twit Connect" > WordPress plugin. > > http://www.voiceoftech.com/swhitley/?p=683#twc_button > > I begged for someone to help me create a button, but I had to make my > own. Thanks to Peter, I'll now be able to standardize on the next > version. > > > On Apr 6, 4:23 am, Alberto Bajo wrote: > > Is there any button similar to "Facebook connect"? (http://spedr.com/ > > rze1) > > > > Otherwise, are there any plans for that? > > > > Thanks :) >
[twitter-dev] Re: What precisely does notification mean?
Allen, Notifications are for device notifications (like SMS or IM) if the user has them enabled. Following means that a user's updates are included in your timeline. Notifications mean that a user's updates appear in your timeline AND are sent to your enabled devices. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 3:13 PM, Allen wrote: > > Seeing all the posts here, I'm getting confused as to what the term > notification means. Does it mean, for example: > > a) the person has it enabled to get email when someone starts > following them > > b) the person has it enabled to notices sent to their mobile phone > > c) something else? > > Seriously, I've seen the term used in different contexts and the api > says "Enables notifications for updates from the specified user to the > authenticating user. Returns the specified user when successful." but > then it says that notification is a "boolean indicating if a user is > receiving device updates for a given user", which sounds like it's a > mobile phone (i.e., device). > > Can anybody clarify what this is? > > Thanks > Allen >
[twitter-dev] Re: OAuth and screen name
Matt has done an amazing job this week. Just want to throw it out there that I'm super impressed. Now... to drop Sign in with Twitter around the web. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 2:45 PM, Dossy Shiobara wrote: > > On 4/17/09 5:28 PM, Matt Sanford wrote: > >> It's working fine for me, and it sounds like for Abraham as well. >> Perhaps some more details about how you're calling it would help. Go >> ahead and fill out a bug report [1] with the headers and whatnot and >> I'll take a look. >> > > Done! Thanks. > > http://code.google.com/p/twitter-api/issues/detail?id=478 > > > -- > 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) >
[twitter-dev] Re: To link the @ or not to link the @, that is the question
I agree. I'm all for convention... It helps users navigate and build confidence in the Twitter experience, where ever it may be. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 7:45 AM, Abraham Williams <4bra...@gmail.com> wrote: > I don't link the @ sign because 1) I don't like how it looks and 2) > Twitter.com does not. > > > On Fri, Apr 17, 2009 at 09:21, Chad Etzel wrote: > >> >> A more lighthearted discussion to see where people stand on this >> convention. >> >> We all know the convention of prefixing usernames with the @ symbol, >> the interesting thing I notice is that different sites (and even >> within tiwtter's site itself) decide to link or not link the @ symbol >> along with it. >> >> Main twitter site: is NOT linked >> search.twitter.com: IS linked >> new twitter integrated sidebar search: IS linked (i suppose this uses >> the same code as search.twitter) >> >> TweetGrid: is NOT linked >> Tweetie: IS linked >> etc.. >> >> just curious how people decided which convention to use. >> >> From a visual perspective I prefer having the @ be plaintext since it >> provides a nice visual difference looking at word, whereas normal >> links are bounded by whitespace. This makes the usernames pop out (to >> my eyes anyway). >> >> -Chad >> > > > > -- > Abraham Williams | http://the.hackerconundrum.com > Hacker | http://abrah.am | http://twitter.com/abraham > Web608 | Community Evangelist | http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. > Sent from Madison, Wisconsin, United States
[twitter-dev] Re: Rate limit status's "remaining_hits" element scope
It is the number of hits you have left until the reset-time is hit. So it's part of that rolling window. 19933 2 2009-04-08T21:57:23+00:00 1239227843 Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 17, 2009 at 6:27 AM, Dimebrain wrote: > > I just realized I don't know whether the remaining_hits element > returned for /account/rate_limit_status is a static number from the > beginning of the current hour, or if it is the remaining hits on a > rolling sixty minute cycle. Does anyone know? >
[twitter-dev] Re: Search API throwing 404's
I just sent 200 queries through without seeing the 404. Are you still seeing this? Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 6:32 PM, Chad Etzel wrote: > > Search is throwing 404's for search.json about every 7 or 8 requests... > > > > 404 Not Found > > Not Found > The requested URL /search.json was not found on this server. > > > Also got a "Forbidden" return when trying to connect to > http://search.twitter.com/ about 10 minutes ago. > > -Chad >
[twitter-dev] Re: Twitter user picture sizes
I just pinged the developer who was supposed to be working on this and as he has had his hand on other fires this week. Thanks for the patience, we realize it is a pain. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 5:16 PM, mikejablonski wrote: > > Found another big one killing my scroll butter: > http://twitter.com/robjcain > > On Apr 4, 6:01 pm, Zac Bowling wrote: > > Any news? > > > > I'm still getting caught up on huge profile images (like this userhttp:// > twitter.com/TheDivawho's <http://twitter.com/TheDivawho%27s> profile image > is 1024x768 and 324 KB) > > > > Really hurting on the mobile side. > > > > Zac Bowling > > > > On Wed, Apr 1, 2009 at 11:47 AM, Zac Bowling wrote: > > > Thanks Alex for making sure this gets taken care of. It's been driving > > > me nuts here chasing ghosts why my IO appears to be blocked when its > > > actually trying to just pull a massive image. > > > > > Basically I'm having all the same issue other are having... My IO > > > library doesn't make it easy to cancel a transfer that is partially > > > complete for our client (doable but increases the complexity a lot), > > > one big image can invalidate several older images in my cache engine > > > because of memory constraints and I don't want to write resizing code > > > before I put it in the cache, and it creates a bottleneck because our > > > client runs where bandwidth is usually small quiet often, etc, etc. > > > You know the deal :-) > > > > > Zac Bowling > > > > > On Mon, Mar 30, 2009 at 12:23 PM, Alex Payne wrote: > > > > >> It's one of our top issues right now. > > > > >> On Sun, Mar 29, 2009 at 23:05, Andrew Maizels < > andrew.maiz...@gmail.com> wrote: > > > > >>> We'd really like to see a fix for this too. Having a few hundred > > >>> unexpectedly large images floating around is playing havoc with our > > >>> memory usage. > > > > >>> Regards, > > > > >>> Andrew Maizels > > >>> PeopleBrowsr > > > > >>> On Mar 26, 2:53 pm, Jason Schroeder wrote: > > >>>> Here is a 480x480 _normal image: > http://s3.amazonaws.com/twitter_production/profile_images/108666778/I... > > > > >>>> Any progress on working with the UX team to resize these? > TwitterBerry > > >>>> is expecting a 48x48-pixel image. > > > > >>>> Cheers, > > >>>> Jason > > >>>> TwitterBerry > > > > >>>> On Mar 24, 7:49 am, Shannon Whitley > wrote: > > > > >>>> > Don't forget the _mini. :) > > > > >>>> > This is my list: > > > > >>>> > (original) > > >>>> > _mini > > >>>> > _normal > > >>>> > _bigger > > > > >>>> > On Feb 25, 12:15 am, Dave Briccetti wrote: > > > > >>>> > > Hi. I’ve searched around for 1/2 hour or so, and haven’t found > an > > >>>> > > authoritative explanation of the sizes of pictures, and how to > > >>>> > > retrieve them. > > > > >>>> > > It seems that profile_image_url leads to a tiny picture: > > >>>> > > > http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... > > > > >>>> > > But there is also a slighter bigger version: > > >>>> > > > http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... > > > > >>>> > > And then a proper full-sizeone: > > >>>> > > > http://s3.amazonaws.com/twitter_production/profile_images/66123958/IM... > > > > >>>> > > Am I correct in this? That the big version URL can be derived > from > > >>>> > > that in profile_image_url by dropping the _normal from the name? > Is > > >>>> > > this part of the API spec? Safe to use? > > > > >>>> > > Thanks. > > > > >> -- > > >> Alex Payne - API Lead, Twitter, Inc. > > >>http://twitter.com/al3x >
[twitter-dev] Re: Getting Source Parameter in Java from XML returns "<"
No, you will have to parse that client-side.
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 16, 2009 at 2:11 PM, Travis James wrote:
>
> Thank you Doug. That is where I was wrong. Is there anyway to excuse
> the HTML and just get the Application Name?
>
> On Apr 16, 12:01 pm, Doug Williams wrote:
> > Source parameters that come from outside apps are encoded HTML. Are you
> > accounting for this Travis? See the "source" heading on the Return Values
> > page [1]
> >
> > 1.http://apiwiki.twitter.com/Return-Values
> >
> > Doug Williams
> > Twitter API Supporthttp://twitter.com/dougw
> >
> > On Thu, Apr 16, 2009 at 9:47 AM, Chad Etzel wrote:
> >
> > > On Thu, Apr 16, 2009 at 12:35 PM, Doug Williams
> wrote:
> > > > What is the source parameter you are passing with your application?
> >
> > > I don't think that's what he's asking. I think he's having trouble
> > > parsing the source info of tweets coming from *other* apps. I looked
> > > through the Java and didn't really see where it is doing the parsing
> > > so I must be missing it. I'm assuming it is looking at XML version of
> > > the data? Is this for REST or Search API?
> > > -Chad
> >
> > > > Doug Williams
> > > > Twitter API Support
> > > >http://twitter.com/dougw
> >
> > > > On Thu, Apr 16, 2009 at 7:34 AM, Travis James <
> > > deadscene...@hyperhack.com>
> > > > wrote:
> >
> > > >> package jtwitter;
> >
> > > >> import java.net.MalformedURLException;
> > > >> import java.text.ParseException;
> > > >> import java.text.SimpleDateFormat;
> > > >> import java.util.Date;
> > > >> import java.util.Locale;
> >
> > > >> public class TwitterEntry {
> >
> > > >>// Twitter Entry Nodes (each corresponds to a XML node with
> the
> > > >> same
> > > >> name)
> > > >>public static final String CREATED_AT = "created_at";
> > > >>public static final String ID = "id";
> > > >>public static final String TEXT = "text";
> > > >>public static final String SOURCE = "source";
> >
> > > >>private Date createdAt;
> > > >>private int id;
> > > >>private String text;
> > > >>private String source;
> > > >>private TwitterUser user;
> >
> > > >>//This is currently the date format used by twitter
> > > >>public static final String TWITTER_DATE_FORMAT = "EEE MMM dd
> > > >> kk:mm:ss
> > > >> Z ";
> >
> > > >>public TwitterEntry(Date createdAt, int id, String text,
> String
> > > >> source, TwitterUser user) {
> > > >>super();
> > > >>this.createdAt = createdAt;
> > > >>this.id = id;
> > > >>this.text = text;
> > > >>this.source = source;
> > > >>this.user = user;
> > > >>}
> >
> > > >>public TwitterEntry() {
> > > >>this.user = new TwitterUser();
> > > >>}
> >
> > > >>public Date getCreatedAt()
> > > >>{
> > > >>return createdAt;
> > > >>}
> >
> > > >>public void setCreatedAt(Date createdAt)
> > > >>{
> > > >>this.createdAt = createdAt;
> > > >>}
> >
> > > >>public int getId()
> > > >>{
> > > >>return id;
> > > >>}
> >
> > > >>public void setId(int id)
> > > >>{
> > > >>this.id = id;
> > > >>}
> >
> > > >>public String getText()
> > > >>{
> > > >>return text;
> > > >>}
> >
> > > >>public void setText(String text)
> > > >>{
> > > >>this.text = text;
> > > >>}
> >
> >
[twitter-dev] Re: Sign in with Twitter
Allen, OAuth is the third-party authorization protocol that we have decided to embrace. You can search the group's archives [1] for past discussion on OpenID and the Twitter API. 1. http://groups.google.com/group/twitter-development-talk/search?group=twitter-development-talk&q=openid&qt_g=Search+this+group Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 12:51 PM, Allen Tom wrote: > > On Apr 16, 9:52 am, Doug Williams wrote: > > Matt has deployed our answer for one click login. It requires only a > small > > change to the normal Twitter OAuth workflow and is documented here: > > > > http://apiwiki.twitter.com/Sign-in-with-Twitter > > > > This is the perfect tool for web applications wanting to offer users the > > ability to sign in with a Twitter account and a single mouse click. We > want > > to see it in the wild so please let us know if you roll this out in your > > application. > > > > Hi Doug, > > Signing into websites using your Twitter account is an awesome idea, > Twitter accounts would make fantastic portable identities that can be > used to sign into 3rd party sites. Most sites using using Facebook > Connect or OpenID really just want your profile, follower graph, and > the ability to receive viral referral traffic by writing to your > activity stream. > > OAuth is great for 3rd party applications that are built on top of > Twitter, however, I'm not sure if it's appropriate to use OAuth token > for Signing In to a website, because it allows that site to spam your > followers by tweeting on your behalf. Using OpenID is safer for Sign- > in, because OpenID would allow Twitter users to verify their Twitter > identity, and share their Twitter Profile and Follower Graph (by > scraping the microformats on the Twitter Profile Page), without having > to authorize access to their Twitter account. If Twitter users sign in > with OpenID, 3rd party sites could still generate viral referral > traffic by giving users a UI to preview and approve the tweet, by > opening a modal dialog or popup that reuses the user's twitter browser > session to tweet. > > Allen >
[twitter-dev] Re: API Limit
We provide you the ability to programmatically throttle your API usage on the client side. I've documented it here [1]. If your users are complaining, then you should take the time to use the tools described in the documentation to gracefully handle API usage. 1. http://apiwiki.twitter.com/Rate-limiting Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 12:43 PM, Alex Payne wrote: > > We always supply a reason when rejecting whitelisting requests. That > reason should be in the body of the rejection email. > > If you create a bunch of accounts, our spam team is likely to suspend > them. Please address the issues mentioned in the rejection email and > re-apply. > > On Thu, Apr 16, 2009 at 12:34, Brandon Geiger > wrote: > > > > Our users continue to complain about hitting API limits for our app. I > > applied to get whitelisted, but got rejected. I'm thinking of creating > > several "test" accounts that run the more intensive API call > > procedures as cron jobs, to not use our users' api calls. > > > > Any idea why we got rejected? (app name is Swattr) > > Any objections to this approach? > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
[twitter-dev] Re: multiple tokens for the same user/application
Marlo, You should currently only have one working token per user per application. There is an open issue [1] that will allow multiple tokens per user per application. 1. http://code.google.com/p/twitter-api/issues/detail?id=372 Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 10:18 AM, Mario Menti wrote: > Hi there, > the way my current (not live yet) twitter OAuth implementation works, it's > possible to authenticate the same user more than once, leading to my app > storing multiple tokens for the same user. From my testing so far this > doesn't seem to be a problem (all tokens still work, and re-authenticating > doesn't invalidate any earlier tokens), but I wanted to check if this is by > design - in other words, is this likely to continue working in future, or > are there some plans to expire tokens when the same app/user requests a new > one? > > Cheers, > Mario. >
[twitter-dev] Re: Sign in with Twitter
Zac, Matt and I agree there is value here. I've opened Issue 469 [1] to track this enhancement. 1. http://code.google.com/p/twitter-api/issues/detail?id=469 Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 11:48 AM, Dossy Shiobara wrote: > > On 4/16/09 2:33 PM, Matt Sanford wrote: > >> The initial token required is a RequestToken rather than an AccessToken. >> Making the request for the RequestToken requires you know the consumer >> key/secret and (a) let's us know what application this is for >> (callback_url alone would not) and (b) prevent the token-shooting method >> you described. >> > > How does this prevent (b)? If I know a third-party application's callback > URL, I can currently brute-force a user's oauth_token, assisted by a basic > session-fixation attack. The callback URL isn't signed by Twitter. > > Perhaps oauth/authenticate would require a signed request that doesn't > include/require oauth_token. Upon successful process flow, Twitter would > send the user back using a signed callback URL that includes the user's > oauth_token. Then, all we would need is a method to retrieve the > oauth_token_secret for that oauth_token. > > This would enable third-party applications to completely use Twitter for > its authentication, in lieu of OpenID. > > > > -- > 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) >
[twitter-dev] Sign in with Twitter
Matt has deployed our answer for one click login. It requires only a small change to the normal Twitter OAuth workflow and is documented here: http://apiwiki.twitter.com/Sign-in-with-Twitter This is the perfect tool for web applications wanting to offer users the ability to sign in with a Twitter account and a single mouse click. We want to see it in the wild so please let us know if you roll this out in your application. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: Getting Source Parameter in Java from XML returns "<"
Source parameters that come from outside apps are encoded HTML. Are you
accounting for this Travis? See the "source" heading on the Return Values
page [1]
1. http://apiwiki.twitter.com/Return-Values
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 16, 2009 at 9:47 AM, Chad Etzel wrote:
>
> On Thu, Apr 16, 2009 at 12:35 PM, Doug Williams wrote:
> > What is the source parameter you are passing with your application?
> >
>
> I don't think that's what he's asking. I think he's having trouble
> parsing the source info of tweets coming from *other* apps. I looked
> through the Java and didn't really see where it is doing the parsing
> so I must be missing it. I'm assuming it is looking at XML version of
> the data? Is this for REST or Search API?
> -Chad
>
>
> > Doug Williams
> > Twitter API Support
> > http://twitter.com/dougw
> >
> >
> > On Thu, Apr 16, 2009 at 7:34 AM, Travis James <
> deadscene...@hyperhack.com>
> > wrote:
> >>
> >> package jtwitter;
> >>
> >> import java.net.MalformedURLException;
> >> import java.text.ParseException;
> >> import java.text.SimpleDateFormat;
> >> import java.util.Date;
> >> import java.util.Locale;
> >>
> >>
> >> public class TwitterEntry {
> >>
> >>// Twitter Entry Nodes (each corresponds to a XML node with the
> >> same
> >> name)
> >>public static final String CREATED_AT = "created_at";
> >>public static final String ID = "id";
> >>public static final String TEXT = "text";
> >>public static final String SOURCE = "source";
> >>
> >>private Date createdAt;
> >>private int id;
> >>private String text;
> >>private String source;
> >>private TwitterUser user;
> >>
> >>//This is currently the date format used by twitter
> >>public static final String TWITTER_DATE_FORMAT = "EEE MMM dd
> >> kk:mm:ss
> >> Z ";
> >>
> >>public TwitterEntry(Date createdAt, int id, String text, String
> >> source, TwitterUser user) {
> >>super();
> >>this.createdAt = createdAt;
> >>this.id = id;
> >>this.text = text;
> >>this.source = source;
> >>this.user = user;
> >>}
> >>
> >>public TwitterEntry() {
> >>this.user = new TwitterUser();
> >>}
> >>
> >>public Date getCreatedAt()
> >>{
> >>return createdAt;
> >>}
> >>
> >>public void setCreatedAt(Date createdAt)
> >>{
> >>this.createdAt = createdAt;
> >>}
> >>
> >>public int getId()
> >>{
> >>return id;
> >>}
> >>
> >>public void setId(int id)
> >>{
> >>this.id = id;
> >>}
> >>
> >>public String getText()
> >>{
> >>return text;
> >>}
> >>
> >>public void setText(String text)
> >>{
> >>this.text = text;
> >>}
> >>
> >>public String getSource()
> >>{
> >>return source;
> >>}
> >>
> >>public void setSource(String source)
> >>{
> >>this.source = source;
> >>}
> >>
> >>public TwitterUser getUser()
> >>{
> >>return user;
> >>}
> >>
> >>public void setUser(TwitterUser user)
> >>{
> >>this.user = user;
> >>}
> >>
> >>@Override
> >>public int hashCode()
> >>{
> >>final int PRIME = 31;
> >>int result = 1;
> >>result = PRIME * result + id;
> >>return result;
> >>}
> >>
> >>@Override
> >>public boolean equals(Object obj)
> >>{
> >>
[twitter-dev] Re: Sign in with Twitter
Related: More OAuth documentation is to come throughout the day so some of the links will be broken. It's a glaring omission in the documentation. Let's use this thread to fill the holes people find while implementing Sign in with Twitter for the time being. Cheers, Doug Williams Twitter API Support http://twitter.com/dougw On Apr 16, 9:52 am, Doug Williams wrote: > Matt has deployed our answer for one click login. It requires only a small > change to the normal Twitter OAuth workflow and is documented here: > > http://apiwiki.twitter.com/Sign-in-with-Twitter > > This is the perfect tool for web applications wanting to offer users the > ability to sign in with a Twitter account and a single mouse click. We want > to see it in the wild so please let us know if you roll this out in your > application. > > Thanks, > Doug Williams > Twitter API Supporthttp://twitter.com/dougw
[twitter-dev] Re: How to whitelist an app engine twitter app.
>From the docs [1]: "There is no general idea of a whitelist for the Search API as with the REST API. However, under extraordinary circumstances we work with developers to raise rate limiting for Search requests. If you feel that your application is doing everything it can to limit and combine queries where appropriate, please contact Twitter <http://apiwiki.twitter.com/Support> to discuss your needs. The Search API is only able to whitelist IP addresses, not user accounts. This works in most situations but for cloud platforms like Google App Engine, applications without a static IP addresses cannot receive Search whitelisting." 1. http://apiwiki.twitter.com/Rate-limiting Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 16, 2009 at 9:11 AM, Guillermo Esteves wrote: > > What if my Google App Engine app uses the Search API instead? If I'm > not mistaken, I can't make an authenticated call to the Search API. > What should I do if I hit any limits in that case? > > —Guillermo (http://twitter.com/gesteves) > > On Mar 26, 12:43 pm, Alex Payne wrote: > > Indeed, whitelisting by authenticated user credentials (and soon, > > OAuth) is our preferred way to handle "clouds" and hosting farms. > > > > -- > > Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x >
[twitter-dev] Re: Getting Source Parameter in Java from XML returns "<"
What is the source parameter you are passing with your application?
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 16, 2009 at 7:34 AM, Travis James wrote:
>
> package jtwitter;
>
> import java.net.MalformedURLException;
> import java.text.ParseException;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> import java.util.Locale;
>
>
> public class TwitterEntry {
>
>// Twitter Entry Nodes (each corresponds to a XML node with the same
> name)
>public static final String CREATED_AT = "created_at";
>public static final String ID = "id";
>public static final String TEXT = "text";
>public static final String SOURCE = "source";
>
>private Date createdAt;
>private int id;
>private String text;
>private String source;
>private TwitterUser user;
>
>//This is currently the date format used by twitter
>public static final String TWITTER_DATE_FORMAT = "EEE MMM dd
> kk:mm:ss
> Z ";
>
>public TwitterEntry(Date createdAt, int id, String text, String
> source, TwitterUser user) {
>super();
>this.createdAt = createdAt;
>this.id = id;
>this.text = text;
>this.source = source;
>this.user = user;
>}
>
>public TwitterEntry() {
>this.user = new TwitterUser();
>}
>
>public Date getCreatedAt()
>{
>return createdAt;
>}
>
>public void setCreatedAt(Date createdAt)
>{
>this.createdAt = createdAt;
>}
>
>public int getId()
>{
>return id;
>}
>
>public void setId(int id)
>{
>this.id = id;
>}
>
>public String getText()
>{
>return text;
>}
>
>public void setText(String text)
>{
>this.text = text;
>}
>
>public String getSource()
>{
>return source;
>}
>
>public void setSource(String source)
>{
>this.source = source;
>}
>
>public TwitterUser getUser()
>{
>return user;
>}
>
>public void setUser(TwitterUser user)
>{
>this.user = user;
>}
>
>@Override
>public int hashCode()
>{
>final int PRIME = 31;
>int result = 1;
>result = PRIME * result + id;
>return result;
>}
>
>@Override
>public boolean equals(Object obj)
>{
>if (this == obj)
>return true;
>if (obj == null)
>return false;
>if (getClass() != obj.getClass())
>return false;
>final TwitterEntry other = (TwitterEntry) obj;
>if (id != other.id)
>return false;
>return true;
>}
>
>public void addAttribute(String key, String value)
>throws ParseException, MalformedURLException {
>
>if(key.equals(CREATED_AT))
>this.setCreatedAt(makeDate(value));
>else if(key.equals(ID))
>this.setId(Integer.parseInt(value));
>else if (key.equals(TEXT))
>this.setText(value);
>else if (key.equals(SOURCE))
>this.setSource(value);
>else if (key.equals(TwitterUser.NAME))
>this.getUser().setName(value);
>else if (key.equals(TwitterUser.SCREEN_NAME))
>this.getUser().setScreenName(value);
>else if (key.equals(TwitterUser.LOCATION))
>this.getUser().setLocation(value);
>else if (key.equals(TwitterUser.DESCRIPTION))
>this.getUser().setDescription(value);
>else if (key.equals(TwitterUser.PROFILE_IMAGE_URL))
>this.getUser().setProfileImageURL(value);
>else if (key.equals(TwitterUser.URL))
>this.getUser().setUrl(value);
>else if (key.equals(TwitterUser.IS_PROTECTED))
>
> this.getUser().setProtected(Boolean.parseBoolean(value));
>
[twitter-dev] since_id too recent, poll less frequently
Cameron, Chad, and the Tweetfall duo pinged me this afternoon to let me know there is a new error cropping up from the search API. The error text is "since_id too recent, poll less frequently". I found out that is a permanent addition to our error checks from the maintainers of the search code (the software that powers the API). If you are seeing this error and you believe it is a mistake, please reply with the details. Simply put, we are running thin on search capacity so the team is pulling out the stops to keep clients honest. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: double escape
Chad speaks the truth. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 3:08 PM, Chad Etzel wrote: > > It's probably collateral damage in whatever fix when in regarding the > worms this weekend but yes, a bit distracting. > -Chad > > On Wed, Apr 15, 2009 at 5:50 PM, voorwiel wrote: > > > > Just in case the Twitter developers missed it: right now, 'dangerous' > > characters such as & and > are being printed as & and > > > in bio's on the web site. Doesn't look very nice. > > > > Cheers! > > >
[twitter-dev] Re: OAuth for site login
Yes, we are working on something that will make what you are asking for, djMax, a working feature. I'm writing the documentation now. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 2:53 PM, Abraham Williams <4bra...@gmail.com> wrote: > * Feature (OAuth): Added provisional support for "Sign in via >> Twitter" for OAuth applications. An official annoucement will follow >> after full support is available. >> » More on this to come in subsequent mails. I need to get >> another piece in place first. >> >> > http://groups.google.com/group/twitter-development-talk/browse_thread/thread/5822fbfd5ea857c6 > > > On Wed, Apr 15, 2009 at 16:44, Dossy Shiobara wrote: > >> >> On 4/15/09 5:38 PM, djMax wrote: >> >>> I want to use OAuth via Twitter for login to our site. The first time >>> I get the flow, user clicks allow. But is there a method that I use >>> given the token and secret for the next time, so that if they're >>> already logged in they see nothing but if they're not they have to >>> login? >>> >> >> This is why it would be desirable for Twitter to also implement an OpenID >> provider, so folks could log into our third-party applications with their >> Twitter account using OpenID. >> >> Then, we'd bind their OpenID to their OAuth token and be happy. >> >> Sadly, Alex has clearly stated that Twitter as an OpenID provider "won't >> happen in 2009"[1]. >> >> [1] >> http://groups.google.com/group/twitter-development-talk/browse_thread/thread/98def90952bdab9c >> >> -- >> 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) >> > > > > -- > Abraham Williams | http://the.hackerconundrum.com > Hacker | http://abrah.am | http://twitter.com/abraham > Web608 | Community Evangelist | http://web608.org > This email is: [ ] blogable [x] ask first [ ] private. >
[twitter-dev] Re: Twitter API returning truncated XML responses
Thanks for the report Dossy, et. al. I see your problem now with the supplied output. I'll the operations folks know about this. Not an API issue but something higher up the chain. Stay tuned... Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 2:19 PM, Dossy Shiobara wrote: > > On 4/15/09 5:08 PM, Chris Thomson wrote: > >> I'm having this issue as well. Here's the full response (including the >> headers returned): >> http://dl.getdropbox.com/u/14675/twittercom_statuses_followers.xml.txt >> > > Phew! I thought I was the only one ... > > > -- > 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) >
[twitter-dev] Re: Updating icon for OAuth applications
Matt has a fix ready to ship for this. Thanks for letting us know. Doug Williams Twitter API Support http://twitter.com/dougw 2009/4/15 Guan Yang > > I tried again just a few seconds ago. I tested with both my > applications, 1396 and 1798. > > Guan > > 2009/4/15 Doug Williams : > > Issue 374 [1] was supposed to fix this issue. When did you see this > problem? > > > > 1. http://code.google.com/p/twitter-api/issues/detail?id=374 > > > > Doug Williams > > Twitter API Support > > http://twitter.com/dougw > > > > > > On Wed, Apr 15, 2009 at 12:56 AM, null wrote: > >> > >> hi Guan I have encounter this problem,but dont have solution for that > >> > >> > >> 在2009-04-15，"Guan Yang" 写道： > >> > >> I have trouble updating the icon for my OAuth applications. I tried > >> several different GIF and PNG files, much smaller than 700k and always > >> get the error message: > >> > >> Your application was registered, but there was a problem with your > >> application image. Probably too big. > >> > >> Has anyone else had this problem, or is it just that every image file > >> on my computer is corrupted? > >> > >> Guan > >> > >> > >> > >> > >> 网易邮箱，中国第一大电子邮件服务商 > > > > > > -- > > Mitch Hedberg - "I drank some boiling water because I wanted to > whistle." - > http://www.brainyquote.com/quotes/authors/m/mitch_hedberg.html >
[twitter-dev] Re: Twitter API returning truncated XML responses
Dossy, More details would certainly help track down the problem. Headers, response bodies, etc.? Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 12:57 PM, Dossy Shiobara wrote: > > Hi, > > Is there something actively killing the Twitter web farm? This happened > once before, where XML API responses were being truncated randomly somewhere > mid-response. > > It's going on _right now_ and has effectively shut down Twitter Karma for > all its users. > > :-( > > -- > 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) >
[twitter-dev] Re: Could we delete the direct message with simple return?
Most mobile developers will have some form of proxy to intermediate the communication between the API and edge devices if bandwidth is a problem. Some of the larger mobile applications use this technique with great success. Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 12:05 AM, Liu Huadong wrote: > > As we know the return of delete inbox item will return the direct > message, > > For mobile phone, it is really waste the time, > Could Twitter API just return a simple xml to show the operator. > such as > > > 0 > > > to indicator successfully > > Regards > Huadong >
[twitter-dev] Re: Updating icon for OAuth applications
Issue 374 [1] was supposed to fix this issue. When did you see this problem? 1. http://code.google.com/p/twitter-api/issues/detail?id=374 Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 12:56 AM, null wrote: > hi Guan I have encounter this problem,but dont have solution for that > > > 在2009-04-15，"Guan Yang" 写道： > > I have trouble updating the icon for my OAuth applications. I tried > several different GIF and PNG files, much smaller than 700k and always > get the error message: > > Your application was registered, but there was a problem with your > application image. Probably too big. > > Has anyone else had this problem, or is it just that every image file > on my computer is corrupted? > > Guan > > > > > -- > 网易邮箱，中国第一大电子邮件服务商 <http://email.163.com>
[twitter-dev] Re: Objective-C/Cocoa open source Twitter client
Nick, Thanks for sharing! Doug Williams Twitter API Support http://twitter.com/dougw On Wed, Apr 15, 2009 at 8:35 AM, Chad Etzel wrote: > > Awesome! I've been trying to learn Cocoa slowly but surely, and this > will help a great deal. > > Thanks! > -Chad > > On Wed, Apr 15, 2009 at 10:12 AM, Nick Toumpelis > wrote: > > Hi, Just wanted to let everyone know that I've released my (beta) > > Obj-C/Cocoa twitter client (Canary) as open source here: > > http://github.com/macsphere/canary, under an MIT-style license. > > It is a fully-fledged client, with multi-user support, multiple > timelines, > > filters, TwitPic support, automatic URL shortening, iTunes integration > etc. > > Plus, you can do anything you like with the code. :) It uses some > > third-party code like Growl, Sparkle and BWToolkit controls and icons > that > > are open to use. > > This is the culmination of my learning experience (though there is still > > much to learn) but I wanted to give something back to the community as > I've > > gained so much by them. I would also appreciate any feedback. > > Hope it's of use to you, > > Nick > > > > > > > > Nick Toumpelis > > email: n...@toumpelis.me.uk > > twitter: macsphere > > > > > > > > > > > > > > > > > > > > >
[twitter-dev] Re: sending DM to all followers?
No, There is no special arrangement needed to send DMs through the API. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 4:58 PM, Alex wrote: > > I understand the negative implications of doing this. The main reason > I ask is that I've had my users ask me. > > There are other sites offering such features, and their web sites > imply they have some kind of special relationship with Twitter that > allows them to do this. I'm not sure if that's true or not? > > > > On Apr 14, 7:46 pm, Doug Williams wrote: > > Alex, > > That sounds very spamish although there are certainly some use cases > where > > it is acceptable. Proceed with caution when sending mass DMs. Ensure the > > messages you are sending are relevant and of value to your followers. > > > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > > On Tue, Apr 14, 2009 at 4:41 PM, Chad Etzel wrote: > > > > > I believe that's called "Tweeting" > > > -Chad > > > > > On Tue, Apr 14, 2009 at 7:24 PM, Alex wrote: > > > > > > I'm wondering if there is a way - or if you would consider adding a > > > > way - to send a DM to all followers via the API? > > > > > > Obviously we could grab the followers list and iterate over it to > send > > > > the DM to all, though that could require thousands of API calls > > > > depending on the user. (And could therefore take hours to do with the > > > > 100 API query/hour limit.) >
[twitter-dev] Re: sending DM to all followers?
Alex, That sounds very spamish although there are certainly some use cases where it is acceptable. Proceed with caution when sending mass DMs. Ensure the messages you are sending are relevant and of value to your followers. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 4:41 PM, Chad Etzel wrote: > > I believe that's called "Tweeting" > -Chad > > On Tue, Apr 14, 2009 at 7:24 PM, Alex wrote: > > > > I'm wondering if there is a way - or if you would consider adding a > > way - to send a DM to all followers via the API? > > > > Obviously we could grab the followers list and iterate over it to send > > the DM to all, though that could require thousands of API calls > > depending on the user. (And could therefore take hours to do with the > > 100 API query/hour limit.) > > > > >
[twitter-dev] Re: combined DM feed?
There has been some chatter before of offering combined feeds (user_timeline, friends_timeline, direct_messages, etc...) in a single call. However, we have recommended people build a proxy to do such aggregation until time and resources allow us to look into it. Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 4:20 PM, Alex wrote: > > Was hoping you would consider offering an API call that would return a > combined DM feed of both sent and received DMs. > > Thoughts? >
[twitter-dev] Re: Deprecation of source parameter registration
We've finished the removal of this functionality from the site so third-party registration is no longer supported. If you feel that you have an extraordinary need for explicit source parameter registration, please email a...@twitter.com. Include why you need to register an application manually and why OAuth will not work in your case. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Apr 12, 7:39 am, Sam Johnston wrote: > Hi Doug, > > On Apr 9, 4:14 am, Doug Williams wrote: > > > > > Beginning late this week or early next week, application developers will no > > longer be able to request APIsourceparameters. Instead, newsource > > parameters will only be available for OAuth applications, and will be > > managed by the developer through the registration and management interface > > (http://twitter.com/oauth_clients). > > This seems a little premature don't you think? Thesourceparameter is > important for marketing applications as well as gauging popularity - > OAuth is both still in beta and unsupported by many clients/ > applications. > > I've just started developing a Twitter app using python-twitter that > is to run on Google AppEngine, but it will be some time after the next > release before we have OAuth support (and even then it's dependent on > a "major overhaul of the HTTP layer")[1]. > > Sam > > 1.http://code.google.com/p/python-twitter/issues/detail?id=37&q=oauth#c4
[twitter-dev] Re: autenticating user using OAuth
That is a design decision we leave up to the application developer. So long as you aren't storing credentials (OAuth applications never do) then we are happy campers. It makes sense for a lot of Twitter applications to use the Twitter user id as the application's internal account id. However it can make growing difficult if the service will move to support other services other than Twitter. When developing an application that will likely support more than one service, a level of indirection (application dependent user ids) would be recommended. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 9:08 AM, Arik Fraimovich wrote: > > On Apr 13, 10:37 pm, Matt Sanford wrote: > > It is currently the case that you will get the Accept/Deny page > > every time. We're working on a redirect like Zachary mentioned and > > hope to have it out by the end of the week. > > Is this kind of usage you will encourage or is it still be better to > create our own user login system? > > Thanks > Arik >
[twitter-dev] Re: Request for documentation review
Ahmed and Chad, I'm rolling in all of those suggestions right now. Thank you both for thorough perusal. Any REST guys out there that can offer the similar insight? Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 9:50 AM, Chad Etzel wrote: > > A note on the "Trends" page: > > / QUOTE ***/ > > Twitter Search API Method: trends > > Returns the top ten queries that are currently trending on Twitter. > The response includes the time of the request, the name of each > trending topic, and the url to the Twitter Search results page for > that topic. > > / END QUOTE ***/ > > > "Returns the top ten *queries* that are currently trending on Twitter" > is inaccurate. They are the top ten trends being posted by people on > twitter. It should really be the "... top ten (phrases/words/topics) > that are currently trending on Twitter". > > -Chad > > > On Tue, Apr 14, 2009 at 12:40 PM, Chad Etzel wrote: > > More feedback about the Search API section: > > > > # Mentioning a user: > http://search.twitter.com/search.atom?q=to%3Amzsanford > > > > "to:user" in Search-land means that the tweet physically begins with > > @user. This would be the stricter "reply" definition. I would change > > "Mentioning" to "Replies to a user" or "Strict Replies to a user" > > > > > > # Referencing a user: http://search.twitter.com/search.atom?q=%40biz > > > > "Referencing" should really be "Mentioning" here since that is in line > > with the nomenclature of "mentions" in Twitter/REST-land. > > > > # Combine any of the operators together: > > http://search.twitter.com/search.atom?q="happy+hour"+near%3ASF > > > > The Search API does *NOT* support the "near:location" operator (even > > though the website does). You must send in a geocoded lat/lang/radius > > style argument in order to accomplish this with the API. Ask Matt > > about the official format. > > > > # Originating from an application: > > http://search.twitter.com/search.atom?q=landing from:tweetie > > > > 4 things: > > 1) searching for an application uses the "source:" operator, not "from:" > > 2) you should mention somewhere that you *cannot* just search for > > tweets from a source, but that you must at least pass in some other > > keyword to search along with the source: operator. > > 3) On a more general note, the spaces should be urlencoded as well. > > It would probably help to mention somewhere in the doc that all > > queries must be urlencoded before sending them. > > 4) For some reason the link in this example does not actually go to that > query. > > Other thoughts: > > > > Where are the Optional Arguments like "since_id", "max_id", "rpp", and > "page" ? > > > > I believe I was told by Matt that queries are actually limited to 138 > > characters since it counts the "q=" characters in the request as part > > of the query. That should probably be noted. > > > > I'll have a look at the REST sections later, but I don't exercise > > those as heavily, so I might not be the best to review it. > > > > -Chad > > > > On Mon, Apr 13, 2009 at 7:11 PM, Doug Williams wrote: > >> Coderz, > >> I am refactoring the API documentation [1] to make it friendlier on the > eyes > >> and easier on new developers. Please give it a once over and reply with > any > >> of errors, addition requests, or suggestions. We will be using these new > >> docs officially in a few days (linked from the apiwiki.twitter.com) > once any > >> glaring omissions and/or errors are addressed. > >> > >> My goal is to make the documentation more robust and example laden to > help > >> new developers get going without needing help. Suggestions and critism > along > >> those lines is welcome. > >> > >> A final plea for help: > >> If you have some spare time and examples to borrow from, please send > >> a...@twitter.com any code/instructions that I can then paste into method > body > >> to help new devs get started. Basic Hello World! style usage examples > for > >> each method would go a long way to curbing new developer problems. Be > sure > >> to include a link to any libraries your example is using. Working full > >> length example code hosted on github would be preferred. > >> > >> 1. http://apiwiki.twitter.com/Twitter-API-Documentation > >> > >> Thanks, > >> Doug Williams > >> Twitter API Support > >> http://twitter.com/dougw > > >
[twitter-dev] Re: Request for documentation review
Ahmed and Chad, I'm rolling in all of those suggestions right now. Thank you both for thorough perusal. Any REST guys out there that can offer the similar insight? Doug Williams Twitter API Support http://twitter.com/dougw On Tue, Apr 14, 2009 at 9:50 AM, Chad Etzel wrote: > > A note on the "Trends" page: > > / QUOTE ***/ > > Twitter Search API Method: trends > > Returns the top ten queries that are currently trending on Twitter. > The response includes the time of the request, the name of each > trending topic, and the url to the Twitter Search results page for > that topic. > > / END QUOTE ***/ > > > "Returns the top ten *queries* that are currently trending on Twitter" > is inaccurate. They are the top ten trends being posted by people on > twitter. It should really be the "... top ten (phrases/words/topics) > that are currently trending on Twitter". > > -Chad > > > On Tue, Apr 14, 2009 at 12:40 PM, Chad Etzel wrote: > > More feedback about the Search API section: > > > > # Mentioning a user: > http://search.twitter.com/search.atom?q=to%3Amzsanford > > > > "to:user" in Search-land means that the tweet physically begins with > > @user. This would be the stricter "reply" definition. I would change > > "Mentioning" to "Replies to a user" or "Strict Replies to a user" > > > > > > # Referencing a user: http://search.twitter.com/search.atom?q=%40biz > > > > "Referencing" should really be "Mentioning" here since that is in line > > with the nomenclature of "mentions" in Twitter/REST-land. > > > > # Combine any of the operators together: > > http://search.twitter.com/search.atom?q="happy+hour"+near%3ASF > > > > The Search API does *NOT* support the "near:location" operator (even > > though the website does). You must send in a geocoded lat/lang/radius > > style argument in order to accomplish this with the API. Ask Matt > > about the official format. > > > > # Originating from an application: > > http://search.twitter.com/search.atom?q=landing from:tweetie > > > > 4 things: > > 1) searching for an application uses the "source:" operator, not "from:" > > 2) you should mention somewhere that you *cannot* just search for > > tweets from a source, but that you must at least pass in some other > > keyword to search along with the source: operator. > > 3) On a more general note, the spaces should be urlencoded as well. > > It would probably help to mention somewhere in the doc that all > > queries must be urlencoded before sending them. > > 4) For some reason the link in this example does not actually go to that > query. > > Other thoughts: > > > > Where are the Optional Arguments like "since_id", "max_id", "rpp", and > "page" ? > > > > I believe I was told by Matt that queries are actually limited to 138 > > characters since it counts the "q=" characters in the request as part > > of the query. That should probably be noted. > > > > I'll have a look at the REST sections later, but I don't exercise > > those as heavily, so I might not be the best to review it. > > > > -Chad > > > > On Mon, Apr 13, 2009 at 7:11 PM, Doug Williams wrote: > >> Coderz, > >> I am refactoring the API documentation [1] to make it friendlier on the > eyes > >> and easier on new developers. Please give it a once over and reply with > any > >> of errors, addition requests, or suggestions. We will be using these new > >> docs officially in a few days (linked from the apiwiki.twitter.com) > once any > >> glaring omissions and/or errors are addressed. > >> > >> My goal is to make the documentation more robust and example laden to > help > >> new developers get going without needing help. Suggestions and critism > along > >> those lines is welcome. > >> > >> A final plea for help: > >> If you have some spare time and examples to borrow from, please send > >> a...@twitter.com any code/instructions that I can then paste into method > body > >> to help new devs get started. Basic Hello World! style usage examples > for > >> each method would go a long way to curbing new developer problems. Be > sure > >> to include a link to any libraries your example is using. Working full > >> length example code hosted on github would be preferred. > >> > >> 1. http://apiwiki.twitter.com/Twitter-API-Documentation > >> > >> Thanks, > >> Doug Williams > >> Twitter API Support > >> http://twitter.com/dougw > > >
[twitter-dev] Request for documentation review
Coderz, I am refactoring the API documentation [1] to make it friendlier on the eyes and easier on new developers. Please give it a once over and reply with any of errors, addition requests, or suggestions. We will be using these new docs officially in a few days (linked from the apiwiki.twitter.com) once any glaring omissions and/or errors are addressed. My goal is to make the documentation more robust and example laden to help new developers get going without needing help. Suggestions and critism along those lines is welcome. A final plea for help: If you have some spare time and examples to borrow from, please send a...@twitter.com any code/instructions that I can then paste into method body to help new devs get started. Basic Hello World! style usage examples for each method would go a long way to curbing new developer problems. Be sure to include a link to any libraries your example is using. Working full length example code hosted on github would be preferred. 1. http://apiwiki.twitter.com/Twitter-API-Documentation Thanks, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: autenticating user using OAuth
Where are you storing the secret upon authorization? Is it going into persistent storage (such as a database) for future use? Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 11:07 AM, Hameedullah Khan wrote: > > > > On Apr 13, 11:59 am, Zachary Voase wrote: > > As far as I know this is not an issue. Users only have to accept the > > first time they use an application; on subsequent authorization > > requests, Twitter will redirect them to your app straight away. > > > > Strange, > > I always get that Accept/Deny Page. I am wondering what I am missing. > > Here is what I am doing: > > 1. request a token from twitter. > 2. Redirect user to authorization url with the token requested in 1 > 3. once the user returns from twitter, get the access token (or > secret) from twitter based on token requested in 1. > 4. use the secret for further api requests to twitter. > > Thanks, > Hameedullah Khan >
[twitter-dev] Re: Is there a way to tell if a tweet has been favorited (regardless of user)?
Ed, I'd love to see some apps crop up that display favorite content in interested ways. Can you create an issue? Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 8:50 AM, e.p.c. wrote: > > I am playing with favorites and am trying to determine if a given > tweet has been favorited by anyone at all. > That is, given this tweet: https://twitter.com/epc/status/1500168995 > which I’ve favorited with another account (@artificllc), is there a > way to determine that it's been favorited, either by the author of the > tweet (@epc) or by any other authenticated user? > > My checks with the API seem to indicate that @artificllc will get > true when retrieving that tweet, but @epc and > any other id will receive false. > > The API seems geared to showing what tweets a given user has marked as > favorites, but there doesn't appear to be a way to see which of a > user's tweets have been marked as favorites by others. Should I open > an issue? > -- > -ed costello > @epc >
[twitter-dev] Re: Limit for following new people (per hour)?
Please refer to the link Matt included to understand the following limit policy. Whitelisting allows access to more API calls. It does not affect follower limits. The follower limits are in place to promote healthy following behavior. Twitter wants users to follow people they are interested in. High levels of churn in the users that you are following are indicative of possible spam usage and will be flagged. It is a waste of time to develop tools to allow users to mass follow users serially. It is easy to detect and will lead to a suspended account. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 7:15 AM, Madu7 wrote: > > OK, thank you. Does the limit exist even if you are on the whitelist? > > But that's the general limit. I wonder if there's a limit per hour. > For example: You are allowed to create 50 friendships per 60 minutes > time period. If you reach the limit after 30 minutes, you have to wait > for 30 minutes to create the next ones. Is there such a limit? > > On 13 Apr., 04:07, Nick Arnett wrote: > > I believe there is a limit of 2000 until 2000 people are following > > you, then it increases. > > > > Nick > > > > On 4/12/09, Madu7 wrote: > > > > > > > > > I am on the whitelist for the Twitter API and use the friendships/ > > > create method to follow new people. But now I cannot follow a user any > > > more. So is there a limit which controls how many users you can follow > > > (per hour/day...)? I hope you can help me. Thanks in advance! >
[twitter-dev] Re: New Ruby Twitter API Library: Grackle
Thanks Hayes! Added to the libraries page. Doug Williams Twitter API Support http://twitter.com/dougw On Mon, Apr 13, 2009 at 9:19 AM, Hayes Davis wrote: > Hi all, > > Just wanted to let everyone know that I've released a new Ruby Twitter API > library called Grackle. It's at http://github.com/hayesdavis/grackle > > It works with both the search and REST APIs and supports both basic and > OAuth authentication. The main thing that sets it apart is that it's > designed to be resilient in the face of changes to the API. Everything's > dynamic, so new API methods, changes to parameters or modifications to > returned data don't require changes to the library itself. That has been > quite helpful in my projects (and others that use it as well) as the guys > move forward very quickly with new API functionality. > > Would it be possible to have it included among the available libraries on > the wiki? > > Please let me know if you have any feedback, suggestions for improvement, > etc. > > Thanks. > > Hayes Davis > @hayesdavis > >
[twitter-dev] Re: Using OAuth or API can u monitor Tweets & have 3rd party app react
The API is stateless and requires polling. We do not offer any sort of trigger or push based alerts. Therefore, your application will either have to use the Search API or REST API to monitor a search term or account, respectively, then act on it accordingly. Thanks, Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 11, 2009 at 8:08 PM, rpsfan wrote: > > Hi > > Im wondering if our users whom have given us their Twitter name either > via OAuth or API would be able to Twitter a command or even a word and > when they do have it call to our app to take action? > > If this can not be done then could we monitor our users Twitter > account every four hours to see if they have stated this action and if > so then we would take action? Is there a limit to how many hits an > app can hit Twitter a day? > > If the above was not clear here is an example > > Im Joe and Im on Twitter and this new thing a mo bob service. Joe is > selling a couch in Murfreesboro, TN and Tweets Im selling a couch. > The word sell is what would trigger this thing a mo bob 3rd party app > and the app would search the web (craigslist and other sites) to find > buyers and send joe an email listing those buyers. > > Thanks >
[twitter-dev] Re: counting rate limits against an oauth consumer
The behavior of a whitelisted IP address is what you are requesting. Whitelisted IP addresses making calls on behalf of a user will use the IP address' rate limit, not the users. Doug Williams Twitter API Support http://twitter.com/dougw On Sat, Apr 11, 2009 at 10:21 PM, Julio Biason wrote: > > Hey, > > I'm guessing it would allow some abuse. Someone would start requesting > application IDs like crazy and spam the hell of the system. Once he > blow up one application ID, it would just switch to another one. > > Although some sort of list-of-applications-sorted-by-requests would > allow a user to easily see the applications that are not behaving > nicely. > > On Sun, Apr 12, 2009 at 1:16 PM, cpatil wrote: > > > > Hi, > > > > Is there a reason why the rate limit is not applied to an oauth > > consumer (the application) instead of the authenticating user? > > It would prevent an offending application to use up the limits of a > > user and allow > > other applications continue to be able to service the user. > > > > thx/c > > > > > > -- > Julio Biason > Twitter: http://twitter.com/juliobiason >
[twitter-dev] Re: Does the Search API have an hourly limit like the main API?
No, search is not limited by the same rate limiter as the REST API. There is still a limit but it is well north of 100 request per hour. You'll receive 503 HTTP responses if the limit is hit. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 11:59 AM, Brandon Geiger wrote: > > So if we want to make over 100 search API requests in an hour, we need > to get whitelisted? > > On Apr 10, 12:54 pm, Doug Williams wrote: > > There is no authentication for the search API. Rate limiting is based on > IP > > address alone. > > > > Doug Williams > > Twitter API Supporthttp://twitter.com/dougw > > > > On Fri, Apr 10, 2009 at 11:49 AM, Brandon Geiger >wrote: > > > > > > > > > We are debating whether or not we need to authenticate users when > > > making a call against the search API. > > > > > Thanks >
[twitter-dev] Re: Source isn't working for me anymore
It worked for me. How are you submitting your source parameter? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 3:33 PM, Andrew Badera wrote: > Your flux capacitor must be on the flimflam. > > > On Fri, Apr 10, 2009 at 4:54 PM, rfurlan wrote: > >> >> Since the 7th or the 8th (April) it seems like Twitter is ignoring my >> source (twitzap). I have confirmed that the source string is being >> submitted correctly when a status update is posted but all the tweets >> show as "from web" on the Twitter website. >> >> Any ideas? >> >> -rfurlan >> > >
[twitter-dev] Re: Does the Search API have an hourly limit like the main API?
There is no authentication for the search API. Rate limiting is based on IP address alone. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 11:49 AM, Brandon Geiger wrote: > > We are debating whether or not we need to authenticate users when > making a call against the search API. > > Thanks >
[twitter-dev] Re: 400 bad request from verify_credentials
Are you making a GET request? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 11:34 AM, nattu wrote: > > Hi, > > I am getting 400 Bad Request error from Twitter for the API call > 'account/verify_credentials'. > As per http://apiwiki.twitter.com this occurs when the rate limit of > 100 requests per 60 minute is exceeded. But I have verified thrice > that the requests have not exceeded this limit at any time. Also I am > not receiving any notification in return to the API call, as mentioned > in the documentation. What might be the possible cause? This is > crucial for our application's performance. > > Kindly help me out. Thanks >
[twitter-dev] Re: search by link
Search only by source is not supported. Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 10:38 AM, joop23 wrote: > > I was hoping to find a way to search for source through the search api > without having to pass in some text. Just source through api. > > On Apr 9, 11:48 am, Chad Etzel wrote: > > It should be noted that you can't just search for a source alone, you > > must pass in some sort of query with it. So you can't really get all > > tweets from a particular source... > > > > One interesting way to use the "source" data handed back by the search > > API is to gauge "market share" for certain keywords/phrases. I > > created a tool here to do this: > > > > http://tweetgrid.com/sources > > > > it's interesting to search for different people (e.g. from:user) to > > see what clients they are frequently using... > > > > -Chad > > > > On Thu, Apr 9, 2009 at 2:37 PM, Doug Williams wrote: > > > The search "twitter source:tweetdeck" [1] will return any tweet with > > > 'twitter' from the source with parameter 'tweetdeck'. Add your > appropriate > > > format to the URL and you're good to go! > > > > > 1.http://search.twitter.com/search?q=twitter+source%3Atweetdeck > > > > > Doug Williams > > > Twitter API Support > > >http://twitter.com/dougw > > > > > On Thu, Apr 9, 2009 at 11:22 AM, joop23 wrote: > > > > >> Hello, > > > > >> Is there a way to search by link on the status message? For instance, > > >> I'd like to pull all statuses submitted by TweetDeck application. > > > > >> thank you >
[twitter-dev] Re: Settings/connections
This is a dupe thread --- let's move this discussion to the other settings/connections problem thread found here: http://groups.google.com/group/twitter-development-talk/browse_frm/thread/689524038d8baec4/d34690416db08670?lnk=gst&q=settings#d34690416db08670 Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 5:36 PM, Petermdenton wrote: > Hi Matt > I am still unable to access my connections tab to revoke priveldges and > re-test, but the first part was working great. > > Thanks > Peter > > Sent from my iPhone > > On Apr 9, 2009, at 5:32 PM, Matt Sanford wrote: > > Hi all, > The fix for this was just deployed. I'm updating the change log now and > will send the standard announcement email. > > Thanks; > — Matt > > On Apr 9, 2009, at 03:46 PM, Doug Williams wrote: > > This is a bug and Matt is currently working on the fix. > > Doug Williams > Twitter API Support > <http://twitter.com/dougw>http://twitter.com/dougw > > > On Thu, Apr 9, 2009 at 3:04 PM, Pauly < > paulypo...@gmail.com> wrote: > >> >> Just seen someone else twittering @twitterapi with a similar issue... >> I try to post: >> >> <http://twitter.com/direct_messages/new.xml?user=foo567&text=Ticketmaster+UK%3A+16.00+%281779%29> >> http://twitter.com/direct_messages/new.xml?user=foo567&text=Ticketmaster+UK%3A+16.00+%281779%29 >> >> and get back the following xml (removed a url). I am following this >> user, if I try to direct message an account I'm not following I get >> the expected error message. No direct message is sent in either case. >> Anyone any idea? I'm posting but with a query string like this (using >> curl in php), instead of actually posting the params, this is the only >> way that works for me to update my status, so could be I'm doing >> something odd there... >> >> >> >> >> 19482771 >> Come join me on Utterz! We can have multimedia discussions >> from our mobile phone o... >> Join at http://... >> 13881572 >> >> MasAdhie >> Pat_Lorna >> >>19482771 >>Mas Adhie >>MasAdhie >>Semarang >>silahkan kontak sya di YM AdiSucipto atau SKYPE ID >> MasAdhie >> >> <http://s3.amazonaws.com/twitter_production/%0Aprofile_images/73051328/Johnny-Depp-and-Wajahku_normal.jpg> >> http://s3.amazonaws.com/twitter_production/ >> profile_images/73051328/Johnny-Depp-and-Wajahku_normal.jpg> profile_image_url> >> <http://www.100juta.co.cc>http://www.100juta.co.cc >>false >>269 >> >> >>13881572 >>Pat and Lorna Shanks >>Pat_Lorna >>Edmonton, AB. Canada >>We teach entrepreneurs how to create, market and >> monetize presentations for more prospects and profits. >> >> <http://s3.amazonaws.com/twitter_production/%0Aprofile_images/65659291/sp_logo_300x300_normal.jpg> >> http://s3.amazonaws.com/twitter_production/ >> profile_images/65659291/sp_logo_300x300_normal.jpg >> <http://PatAndLorna.com>http://PatAndLorna.com >>false >>14596 >> >> >> > > >
[twitter-dev] A note on our API change policy
Twitter's development model is pragmatically agile where features enter the code base right alongside bug fixes. You can see this in our changelog [1]. What is not clear from the log is that most of the code is written just days before. April 8th's rapid deprecation of the since parameter/If-Modified-Since header (and to a lesser extent, the removal of undocumented HTTP POST access to accounts/verify_credentials) [5] caught a number of developers off guard. The criticism of this hasty change on the impact to hackers and businesses alike was both valid and appropriate. The results from last month's survey [6] lead us to believe that the use of this parameter was minimal and that it was safe to capture performance gains through the deprecation. In hindsight, our sample size was statistically insignificant because we made a mistake. It is apparent we need to make a change towards transparency. Openness demands we give developers a clear line of communication when changes are made that will break current functionality. While these changes are rare, they do happen. As a result of this week's conversation, we will give a minimum of 5 business days notice before we ship code that removes currently documented functionality. Two notable exceptions are critical security and performance fixes. Five days may seem short notice but it is a compromise from our standard. There are two major concerns we must consider when shelving code that is ready for deploy: 1) We do not write unnecessary code. Code only exists in the deploy pipeline for a feature or defect fix that is ready to go out the door. We view deployable code as an asset that should be handling requests as quickly as possible. 2) Un-merged code adds complexity. The Twitter code base is constantly moving. Deploying code requires merging with the master branch which grows in complexity as an undeployed branch sits idle. We currently use the changelog [1], @twitterapi [2], The API Announce List [3], and the Dev Group [4] to inform developers of changes in hopes that features will get used, and deprecations will be honored. I'd suggest any developer with a long-running application to subscribe to the low noise, only signal, API Announce mailing-list [3] to receive API updates as they are released. Lastly, lets work together. Tell me what you developers need that we are not currently providing. How can we better manage this communication? Which method of notifications work best for you? Aside from transparency with API changes, what else do you want to know? 1. http://apiwiki.twitter.com/REST+API+Changelog 2. http://twitter.com/twitterapi 3. http://groups.google.com/group/twitter-api-announce?hl=en 4. http://groups.google.com/group/twitter-development-talk 5. http://groups.google.com/group/twitter-api-announce/browse_frm/thread/5822fbfd5ea857c6?hl=en 6. http://groups.google.com/group/twitter-api-announce/browse_frm/thread/68f2667f4e9842aa?hl=en# Keep the bytes flying, Doug Williams Twitter API Support http://twitter.com/dougw
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Before opening an issue [1] it would have been nice to discuss. What are you trying to do? What steps have you taken to debug? Why do you think this is on our end and not a bug in your code? We can't help without knowing what's going on. 1. http://code.google.com/p/twitter-api/issues/detail?id=447 Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 8:56 AM, HSL wrote: > > I;ve created an issue,.. can you all comment there too? > > http://shortr.me/lz > > > > > On Apr 10, 12:19 pm, Dominik Schwind wrote: > > Hi everyone, > > > > since about half an hour ago I seem to be getting 401 Unauthorized > > responses to my OAuth-ed API calls. > > > > Is that a known problem? > > > > Regards, > > > > Dominik >
[twitter-dev] Re: Requesting Twitter API
Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 10:50 PM, Omer rosen wrote: > For some reason I can't find the link to the requesting page of > Twitter API. > Can someone reply me with the link? > Thanks! >
[twitter-dev] Re: If your OAuth 'verify_credentials.xml' API just broke....
Thanks for sharing the code. The change notice was here [1] for posterity.
1.
http://groups.google.com/group/twitter-development-talk/browse_frm/thread/5822fbfd5ea857c6/1e6e14b9c96f74ca#1e6e14b9c96f74ca
Doug Williams
Twitter API Support
http://twitter.com/dougw
On Thu, Apr 9, 2009 at 6:52 PM, kosso wrote:
>
> ... they appear to have changed the call from a POST to a GET.
>
> I didn't see an update/change about this.
>
> So, in PHP use:
>
> $to = new TwitterOAuth($consumer_key, $consumer_secret,
> $twitterOAuthToken, $twitterOAuthSecret);
> $content = $to->OAuthRequest('https://twitter.com/account/
> verify_credentials.xml<https://twitter.com/account/%0Averify_credentials.xml>',
> array(), 'GET');
>
>
> In the original example PHP scripts, the call was a POST, which used
> to work. Until I saw the API returning 'this method requires a GET.'
> this morning.
>
> hth
>
[twitter-dev] Re: http://twitter.com/direct_messages/new.json failed
Gary, direct_messages/new requires a HTTP POST request. I can see from the URL you pasted in the post that you have a query string. If you are sending a POST request you would have no query string. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 10:21 PM, Alex Payne wrote: > > 400 is the response code we return for rate limiting. Are you sure > you're making the request using an HTTP POST? What was the body of the > response? > > On Thu, Apr 9, 2009 at 18:22, Gary Zhao wrote: > > http://twitter.com/direct_messages/new.json?user=qinqi7&text=test > > I got "The remote server returned an error: (400) Bad Request." Anything > > wrong with this API invocation? > > Thanks > > > > -- > > Gary > > http://twitter.com/garyzhao > > > > > > -- > Alex Payne - API Lead, Twitter, Inc. > http://twitter.com/al3x >
[twitter-dev] Re: 401 Unauthorized on OAuth calls?
Guys, Details are essential to help track down claims like these. What are you doing, and more importantly, how are you doing it? Doug Williams Twitter API Support http://twitter.com/dougw On Fri, Apr 10, 2009 at 6:48 AM, Bluespark wrote: > > Same here. > > On Apr 10, 10:19 pm, Dominik Schwind wrote: > > Hi everyone, > > > > since about half an hour ago I seem to be getting 401 Unauthorized > > responses to my OAuth-ed API calls. > > > > Is that a known problem? > > > > Regards, > > > > Dominik >
[twitter-dev] Re: Having Twitter clients support proxies for enhanced (filtered) tweet fetching
Dave, This is certainly an idea that has been thrown around in conversation, but there is no current development bandwidth to accomplish the task. Hopefully this post can get some attention with the developers on the boards. Are there any coders interested in working together to get a prototype together? Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 4:10 PM, Dave Briccetti wrote: > > (Please let me know if this has been discussed already. I searched for > “proxy” and didn’t quickly find anything related.) > > At different times I like to have different “filters” on my tweet > viewing. When I’m in the office I can tolerate a large flow but when > I’m on a mobile device I want a subset of the feed. I’ve added > filtering capability to the “Simple Twitter Client” for the desktop > that I’m developing. But unless I write a mobile client I can’t use > those filters when I’m on the go. There are lots of nice mobile > clients already. > > What I’d like to do is have part of my Twitter application run as a > web site/service and proxy, and let people “apply” filters to their > stream, through the application. Then when they’re out they can tell > their mobile Twitter clients to get the status feed through my proxy, > instead of twitter.com. > > Ideally, Twitter would let people create filter sets and activate > them, and filter the feed using them. But if that’s not gonna happen > right away, I’d like to see if the development community can do > this. > > What do you think of all of this, especially the idea of Twitter > client developers allowing users to set a proxy for twitter.com? > > Dave Briccetti > > http://davebsoft.com/applications/simple-twitter-client >
[twitter-dev] Re: Trying to send a direct message to myself, getting someone else's direct message back in retunr
This is a bug and Matt is currently working on the fix. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 3:04 PM, Pauly wrote: > > Just seen someone else twittering @twitterapi with a similar issue... > I try to post: > > > http://twitter.com/direct_messages/new.xml?user=foo567&text=Ticketmaster+UK%3A+16.00+%281779%29 > > and get back the following xml (removed a url). I am following this > user, if I try to direct message an account I'm not following I get > the expected error message. No direct message is sent in either case. > Anyone any idea? I'm posting but with a query string like this (using > curl in php), instead of actually posting the params, this is the only > way that works for me to update my status, so could be I'm doing > something odd there... > > > > > 19482771 > Come join me on Utterz! We can have multimedia discussions > from our mobile phone o... > Join at http://... > 13881572 > > MasAdhie > Pat_Lorna > >19482771 >Mas Adhie >MasAdhie >Semarang >silahkan kontak sya di YM AdiSucipto atau SKYPE ID > MasAdhie >http://s3.amazonaws.com/twitter_production/ > profile_images/73051328/Johnny-Depp-and-Wajahku_normal.jpg<http://s3.amazonaws.com/twitter_production/%0Aprofile_images/73051328/Johnny-Depp-and-Wajahku_normal.jpg> > profile_image_url> >http://www.100juta.co.cc >false >269 > > >13881572 >Pat and Lorna Shanks >Pat_Lorna >Edmonton, AB. Canada >We teach entrepreneurs how to create, market and > monetize presentations for more prospects and profits. >http://s3.amazonaws.com/twitter_production/ > profile_images/65659291/sp_logo_300x300_normal.jpg<http://s3.amazonaws.com/twitter_production/%0Aprofile_images/65659291/sp_logo_300x300_normal.jpg> > >http://PatAndLorna.com >false >14596 > > >
[twitter-dev] Re: Connection Keep-Alive and Max Simultaneous Connections
Right on, Chad. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 1:34 PM, Chad Etzel wrote: > > I would guess that when you have millions of connection requests a day > coming into a few different servers, you don't want the connection to > stay open for any longer than it needs to be. Get in, serve data, get > out. > -Chad > > On Thu, Apr 9, 2009 at 2:02 PM, orange80 wrote: > > > > Any reason why not? Just curious. Nice API by the way :) > > > > Thanks, > > Jamie > > > > On Apr 9, 12:47 am, John Adams wrote: > >> On Apr 8, 2009, at 10:33 PM, orange80 wrote: > >> > >> > Yeah, I started checking the headers and realized that. It doesn't > >> > seem like there's any hard limit on simultaneous connections though so > >> > that helps quite a bit. > >> > >> Our web servers do not support Keep-Alive. > >> > >> -j > >> > >> --- > >> John Adams > >> Twitter Operations > >> j...@twitter.comhttp://twitter.com/netik > > >
[twitter-dev] Re: search by link
The search "twitter source:tweetdeck" [1] will return any tweet with 'twitter' from the source with parameter 'tweetdeck'. Add your appropriate format to the URL and you're good to go! 1. http://search.twitter.com/search?q=twitter+source%3Atweetdeck Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 9, 2009 at 11:22 AM, joop23 wrote: > > Hello, > > Is there a way to search by link on the status message? For instance, > I'd like to pull all statuses submitted by TweetDeck application. > > thank you >
