[twitter-dev] Re: direct_messages/sent broken?
I should clarify that .rss and .atom are not supported. Only .json and .xml work. -Chad On Mon, Aug 24, 2009 at 10:40 PM, Chad Etzel wrote: > Hi Kevin, > > These calls are working for me at the moment. Are you still seeing errors? > -Chad > > On Mon, Aug 24, 2009 at 9:43 PM, sentience wrote: >> >> Looks like the direct_messages/sent API is currently broken. Any >> attempt to load any of these pages (at least for our account, >> @sitepointdotcom) results in a "Something is technically wrong" error: >> >> http://twitter.com/direct_messages/sent.atom >> http://twitter.com/direct_messages/sent.json >> http://twitter.com/direct_messages/sent.rss >> http://twitter.com/direct_messages/sent.xml >> >> -- >> Kevin Yank >> CTO, sitepoint.com >> >
[twitter-dev] Re: direct_messages/sent broken?
Hi Kevin, These calls are working for me at the moment. Are you still seeing errors? -Chad On Mon, Aug 24, 2009 at 9:43 PM, sentience wrote: > > Looks like the direct_messages/sent API is currently broken. Any > attempt to load any of these pages (at least for our account, > @sitepointdotcom) results in a "Something is technically wrong" error: > > http://twitter.com/direct_messages/sent.atom > http://twitter.com/direct_messages/sent.json > http://twitter.com/direct_messages/sent.rss > http://twitter.com/direct_messages/sent.xml > > -- > Kevin Yank > CTO, sitepoint.com >
[twitter-dev] direct_messages/sent broken?
Looks like the direct_messages/sent API is currently broken. Any attempt to load any of these pages (at least for our account, @sitepointdotcom) results in a "Something is technically wrong" error: http://twitter.com/direct_messages/sent.atom http://twitter.com/direct_messages/sent.json http://twitter.com/direct_messages/sent.rss http://twitter.com/direct_messages/sent.xml -- Kevin Yank CTO, sitepoint.com
[twitter-dev] Re: Tweet's Track api?
Hi Chad, Thanks for your kind reply. It would be really helpful for me to know any ideas about how to get all replies for a particular tweet. Thanks, Guru On Aug 24, 3:35 pm, Chad Etzel wrote: > Hi Guru, > > There is currently no API method to return replies to a particular tweet ID. > > Thanks, > -Chad > > On Mon, Aug 24, 2009 at 4:30 PM, Guru wrote: > > > Hi, > > > Is there an API which I could use to tract tweets. > > For ex: I will search for a tweet called "Star Trek" and I will find > > many tweets. I will like a tweet in that.. Is there any way to know > > all the reply's for that particular tweet? > > > Thanks, > > Guru
[twitter-dev] Re: Tweet's Track api?
Hi Guru, There is currently no API method to return replies to a particular tweet ID. Thanks, -Chad On Mon, Aug 24, 2009 at 4:30 PM, Guru wrote: > > Hi, > > Is there an API which I could use to tract tweets. > For ex: I will search for a tweet called "Star Trek" and I will find > many tweets. I will like a tweet in that.. Is there any way to know > all the reply's for that particular tweet? > > Thanks, > Guru >
[twitter-dev] Tweet's Track api?
Hi, Is there an API which I could use to tract tweets. For ex: I will search for a tweet called "Star Trek" and I will find many tweets. I will like a tweet in that.. Is there any way to know all the reply's for that particular tweet? Thanks, Guru
[twitter-dev] Re: OAuth API for Third Party Services
On Mon, 24 Aug 2009 11:14:12 -0700 (PDT) Greg wrote: > When I first started programming Twitter application using OAuth - I > thought that eventually it would open up to allow Third Party API > (TwitPic, TweetPhoto) to start using OAuth tokens to authenticate. > However - its been a while since this has gain any air. Twitter got burned with early adoption and the sesion-fixation vulnerability. Not that their service gat hacked through it, but because they didn't point the finger of blame when they pulled the API. There might be quite a bit of wait and see going on because of that, because of the way SSO has faltered, and because of the general FUD that always surrounds security issues. > Is this something that would should be seeing from third-party > services in the future? Thinking about it - your tokens authenticate > you only for that specific application with the consumer key and > consumer secret - how could it be possible to authenticate you on > another service? By design, the user has to authorize each combination of Consumer and Service Provider separately. Trust me, you wouldn't want the kind of interoperability that you seem to be asking for here. It would either open up tons of man in the middle vulnerabilities or be horridly complicated to implement, which has its own risks. > If not - what's the point of OAuth? You can't integrate with other > Twitter Services without having the user sign in again. OAuth will be gaining traction as part of OpenSocial. There could very well be sites that are waiting for this or waiting for better support infrastructure. I have a game site that I'm looking to let users promote by pushing information about forming games out to as many social media outlets as I can support. Facebook is low on my list because it already has an implementation of the game I offer and, even though the implementation isn't very good, the Facebook API is too involved for me to make a run at share shifting them until I've built more share elsewhere. High on my list are sites that are using Open Social, like Avatars United, or where I only need one or two features of the API, like MeetUps. Twitter is on my list because the API is just simple and well-used enough that it would be worthwhile to write and maintain a library on my own. Seriously, though, if we're busting out of our skulls thinking how this affects us as Consumers, think about how it has to be affecting the service providers with 100's of thousands or 44.5 millions of users. Chris
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Aug 24, 2:45 pm, Chris Babcock wrote: > apps need to plan to fail any time a > request goes out over the wire. That's a reality of the programming > environment that isn't specific to OAuth and Twitter. Planning to fail is not the issue. Getting thousands of users to reauthorize your app, when they did nothing wrong, is the real issue. Dewald
[twitter-dev] Get Followers information effectively
Is there a way to get that kind information but for all followers of a user? http://twitter.com/users/show/roosoft.xml Some users have many thousands of followers. I would like to compute something about that information. I doubt that Twitter would appreciate me if I make thousands of call to the previous URL in one shot changing the username each call. I know it's possible to get a list of the currently logged user's followers this way but it only outputs ids. http://twitter.com/friends/ids.xml Thanks! Marc
[twitter-dev] Blank screen using oauth
I am trying to get Twitters oauth working on my site so people can login/register. I thought I had it setup properly, but when I try to login via Tiwtters oauth, I get a blank screen, but the URL bar shows: www.mysitename.com/confirm.php?oauth_token=NemSbS4XJ0VjlPTQki5ovu8pTnC0DvQDXX9ruObCdjY Is there a permission setting I need to change? Or, any other ideas on what it could be? Thanks.
[twitter-dev] OAuth API for Third Party Services
When I first started programming Twitter application using OAuth - I thought that eventually it would open up to allow Third Party API (TwitPic, TweetPhoto) to start using OAuth tokens to authenticate. However - its been a while since this has gain any air. Is this something that would should be seeing from third-party services in the future? Thinking about it - your tokens authenticate you only for that specific application with the consumer key and consumer secret - how could it be possible to authenticate you on another service? If not - what's the point of OAuth? You can't integrate with other Twitter Services without having the user sign in again. Thanks, Greg
[twitter-dev] Re: batch API calls
As long as you stay within the rate limits you should be fine. Also check out this blog post about the best times to run calls: http://apiblog.twitter.com/scheduling-your-twitter-bots Abraham On Thu, Aug 20, 2009 at 07:22, Swan wrote: > > I have been whitelisted. We are currently developing our caching > strategy. > > We store Twitter user information for the hosts of events that we get > from the user.xml API call. We would like to refresh our cache daily > to update the follower/following info as well as any possible Bio, > Name, or photo changes in Twitter. > > Will Twitter care if we do a large batch all at one time as long as we > are not hitting the API throughout the day? > Also, if we do the batch, at what time of day does Twitter API have > the lowest traffic for us to do our update? > > Thx for the help, > Swan > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private. Sent from Madison, WI, United States
[twitter-dev] Re: appended to API works in progress
lul. That's like asking the Duke Nukem Forever team when they'll release. "When its done" While I love the twitter dev team, I'm not sure how hard they are able to stick to deadlines in their development, so its probably just better to say, "the future" On Aug 24, 10:15 am, "METROmilwaukee ..." wrote: > It’s great to see new API items are getting marked up. I would find it very > helpful if [COMING SOON] was replaced by [MM-DD-] when the new item is > officially released presuming why to do so is obvious marking the milestone.
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Mon, 24 Aug 2009 22:06:21 +0530 srikanth reddy wrote: > > Sign in with Twitter isn't conceptually compatible with the design > > of OAuth authentication, but it makes an attempt to deliver on what > > the consumer expects from it. > > > i am not sure i get this But from Desktop app point of view it > perfectly makes sense. You do not ask the user to login again rather > you use the stored tokens . For a desktop, the consumer app lives on the same machine that the end user is using. In that case, the only reasons to use OAuth instead of Basic would be that an HTTPS connection cannot be reliably established or the server application has stated that it intends not to support Basic after some time. That's not the target use case for Oauth Authentication, which was designed so that end users could delegate a third party to authenticate as the end user and act on his behalf. Authentication there means allowing the app to authenticate as the user, which makes it a needless complication for a desktop application, and counter intuitive for a Consumer who is expecting "Authenticate the End User to me" instead of "Authenticate me to the Service Provider as the End User." That is why there have been such hacks to get it to work with iPhone and why there are still "open issues." There is acknowledgement in the spec that Service Providers should not trust the Consumer Secret, but good luck educating end users not to approve a token unless they initiate the request. Paradoxically, probably because of the length of the distribution cycle, desktop apps seem to have been among the first to implement OAuth. Chris
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Mon, 24 Aug 2009 09:53:33 -0700 (PDT) Dewald Pretorius wrote: > That gives me absolute nightmares, when I need to do API calls on user > accounts when the user is not logged in to my site. > > I need the OAuth tokens, which will stored in my database, to remain > valid until the user revokes the access of my app. Meaning, once a > user authorizes my app and until he removes that authorization, there > must be no reason whatsoever for the user to again be physically > involved in any authorization process. > > This is not unique to my app. > > This is required by any app that does batch API calls on Twitter > accounts. Welcome to the wild world of HTTP. HTTP 1.1 defines 38 response codes, only one of which you would accept graciously from a contractor working on your bathroom if you urgently had to go pee. Think, "Two weeks." I'm not being blasé. There are only three things you can count on in an Internet environment - uncertainty, desktop application programmers' having nightmares and system programmers realizing belatedly that they might possibly have been more sensitive - well, two things you can count on. Twitter plainly intends for specific tokens to persist (and they may even do so already), but even so apps need to plan to fail any time a request goes out over the wire. That's a reality of the programming environment that isn't specific to OAuth and Twitter. Chris Babcock
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
Yes. user details are returned along with access tokens/secret. There is really no need to call verify_credentials < > This way of doing things is against the "Sign in with Twitter" > philosophy, but then I also don't see a way of re-using the access > token if you are going with "Sign in with Twitter" philosophy. You are > going to ask the user everytime (which means a If you use a cookie, > or HTTP Basic Auth with anonymous users.new access token), Sign in with Twitter isn't conceptually compatible with the design of OAuth authentication, but it makes an attempt to deliver on what the consumer expects from it. > i am not sure i get this But from Desktop app point of view it perfectly makes sense. You do not ask the user to login again rather you use the stored tokens . On Mon, Aug 24, 2009 at 9:45 PM, Chris Babcock wrote: > > On Mon, 24 Aug 2009 20:43:57 +0530 > srikanth reddy wrote: > > > just to add you can obtain the user id , screen name along with access > > token/secret . You need to cache this. > > > I stopped development on my own API library and decided to use Python > for my app when Twython was introduced, so I haven't had a chance to > send an OAuth request and examine the returns, which aren't documented. > > Do you mean to say that the OAuth call returns the user record? That > makes sense, but it doesn't explain the pathological obsession with > working the verify credentials call into the work flow that I've seen. > > Chris Babcock > >
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
That gives me absolute nightmares, when I need to do API calls on user accounts when the user is not logged in to my site. I need the OAuth tokens, which will stored in my database, to remain valid until the user revokes the access of my app. Meaning, once a user authorizes my app and until he removes that authorization, there must be no reason whatsoever for the user to again be physically involved in any authorization process. This is not unique to my app. This is required by any app that does batch API calls on Twitter accounts. Dewald On Aug 24, 12:19 pm, Chris Babcock wrote: > Even if access tokens do not expire, there are other reasons why they > may fail to persist. Your algorithm for using a token should include a > recovery method in the event that authentication fails.
[twitter-dev] Re: Getting access to Birddog or Shadow
Lyn, Please describe your application in an email to a...@twitter.com. Also, create a new account for this access, read and accept the EULA at twitter.com/help/request_streaming, and send this account along in your email. -John On Aug 20, 3:27 pm, Lyn Headley wrote: > Hello, > > My company is working on a newsgathering application that needs to > listen to a number of different sources at once. The scale of the > application is such that each gatherer must listen to several thousand > sources, and we hope to scale our application up to many different > gatherers. We believe that the best way to accomplish this is to get > access to the shadow or, preferably, birddog levels of access. > > How do I get in touch with somebody about doing that? > > Thanks, > LynHeadley > > http://payyattention.com
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Mon, 24 Aug 2009 20:43:57 +0530 srikanth reddy wrote: > just to add you can obtain the user id , screen name along with access > token/secret . You need to cache this. I stopped development on my own API library and decided to use Python for my app when Twython was introduced, so I haven't had a chance to send an OAuth request and examine the returns, which aren't documented. Do you mean to say that the OAuth call returns the user record? That makes sense, but it doesn't explain the pathological obsession with working the verify credentials call into the work flow that I've seen. Chris Babcock
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Mon, 24 Aug 2009 03:04:52 -0700 (PDT) abhishek sanoujam wrote: > You don't need to get permission everytime from the user if you are > going to store it in a DB. The problem with this is that you will have > to implement another level of authorization in your site/app, kind of > a password for your app, so that when the session times out, or a user > comes back again, he can authorize with your site's password and thus > you can use the initial access token granted behind the scenes. Right, you need your own session management. That can be anything from HTTP Auth to cookies to your own User Database and the authentication routines native to your scripting language or framework. > This way of doing things is against the "Sign in with Twitter" > philosophy, but then I also don't see a way of re-using the access > token if you are going with "Sign in with Twitter" philosophy. You are > going to ask the user everytime (which means a If you use a cookie, > or HTTP Basic Auth with anonymous users.new access token), Sign in with Twitter isn't conceptually compatible with the design of OAuth authentication, but it makes an attempt to deliver on what the consumer expects from it. OAuth authentication allows the Consumer App to use the Service Provider in the place of the user without knowledge of the user name or password. It serves those authentication needs, but as you see it doesn't meet some of the other expectations. That some of these expectations are faulty, isn't of concern to our users, nor should we necessarily expect the service provider to bear the full brunt of building the bridge between the spec and the expectation. Otherwise, what are you getting paid for? :-) > and after getting a new access token, you are going to do > verifyCredentials (to find out who logged in actually)... Everyone assumes that this is something they need to know and that the verify credentials is the only way to find that out. Both assumptions are false, at least as far as the functionality provided by the Twitter API. You don't need to know the user name to use OAuth. Access to API methods using OAuth is as agnostic of usernames as it is passwords. If you do need to know the user name then verify credentials is the easiest and most obvious, but not the best, way to get it. > and verify- > credentials is limited to only 15 requests per 1 hour. This seems like > using "Sign in with Twitter" and not reusing access token, you can > login only 15 times in an hour? I hope this is not correct... but thts > what I understand from > http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0verify_credentials... > If my assumptions are correct, 15 wrong verify-credentials requests > from your site will halt your site for at least 1 hour .. and another > 15 wrong requests for another 1 hour... which seems too easy for your > competitors to block your app!! I'd rather add another authorization > level in my app than face this... No, you get 15 verify credentials requests per user regardless of correctness or source. Since OAuth does not know the user, you may get unlimited rejections but only 15 confirmations - shared with all other apps regardless of their authentication method. That is why you can't rely on it. Instead, use http://twitter.com/statuses/user_timeline.xml?count=1 if obtaining the user name is critical. If you are using Twitter accounts to authenticate users on your site for non-Twitter services then remember that screen names can change. Use the user_id instead. Chris Babcock
[twitter-dev] Re: using Twitter API with PHP
You can just use the JSON responses with a callback and do it using JavaScript. If you really want to do it server-side, I suggest this very simple library: http://github.com/tcdent/php-twitter/ You can also check out @jmathai's full-featured OAuth-compatible library: http://github.com/jmathai/twitter-async/ On Aug 24, 4:41 am, Termanater13 wrote: > I understand PHP well enough to code some website (like the site im > working on). I can get by but I cant create some of the site with PHP > out there just yet. > > I sterted woking with the http requests and so far so good, but I just > cant fugure how to get it to authenticate though a http request. also > its going to be a read only script just getting my last few updates to > show on the site. > > On Aug 23, 11:46 pm, Scott Haneda wrote: > > > If you don't want a public community API, and want to write it in your > > own, then you are sort stuck. > > > The docs show you sample curl commands or you can http request in a > > browser to test simulate. > > > You have sample curl examples, if you are objectionable to libraries, > > then warp your php around those curl commands. > > > If that is not what you want, it sounds like you should look for an > > introduction to php tutorial, or a general introduction to web based > > scripting languages. > > > -- > > Scott > > Iphone says hello. > > > On Aug 23, 2009, at 1:45 PM, Termanater13 wrote: > > > > Ive been looking to use the Twitter API with my php Site and I cant > > > find much just a bunch of URLs used wuth the Twitter API and the curl > > > commands used with the API. Can someone point me in the direction of > > > where to start, and please nothing done by the comunity unless its a > > > tutorial on how to write my own if at al possible.- Hide quoted text - > > > - Show quoted text -
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
just to add you can obtain the user id , screen name along with access token/secret . You need to cache this. On Mon, Aug 24, 2009 at 3:56 PM, Chris Babcock wrote: > > > > I understand that we can store the access token in DB. > > but how do i know the logged in user's screen name after session > > timeout? > > Nowhere in the entire OAuth workflow do you handle users' passwords or > their usernames. A benefit is that you do not need the Twitter username > to perform any function on the users' behalf with the Twitter API any > more than you need the password. > > If it happens that you need the username for some other business reason > then you can call a GET method that returns user profile information to > obtain the user name. The account/verify_credentials methods is most > common for this purpose, but reliance on this method can make your app > subject to DoS because the call has a low, per-user rate limit to > protect against brute force password hacking. You can obtain the user > id from statuses/user_timeline as well. Send count=1 if you do not need > the statuses themselves. > > Better yet, design your app to not require that you know the username, > if possible. > > Chris Babcock > >
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
Currently access tokens do not expire. You get same access token for a user sending request via particular consumer. Limit is per account not ip. On Mon, Aug 24, 2009 at 3:34 PM, abhishek sanoujam wrote: > > You don't need to get permission everytime from the user if you are > going to store it in a DB. The problem with this is that you will have > to implement another level of authorization in your site/app, kind of > a password for your app, so that when the session times out, or a user > comes back again, he can authorize with your site's password and thus > you can use the initial access token granted behind the scenes. > This way of doing things is against the "Sign in with Twitter" > philosophy, but then I also don't see a way of re-using the access > token if you are going with "Sign in with Twitter" philosophy. You are > going to ask the user everytime (which means a new access token), and > after getting a new access token, you are going to do > verifyCredentials (to find out who logged in actually)... and verify- > credentials is limited to only 15 requests per 1 hour. This seems like > using "Sign in with Twitter" and not reusing access token, you can > login only 15 times in an hour? I hope this is not correct... but thts > what I understand from > http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0verify_credentials. > .. > If my assumptions are correct, 15 wrong verify-credentials requests > from your site will halt your site for at least 1 hour .. and another > 15 wrong requests for another 1 hour... which seems too easy for your > competitors to block your app!! I'd rather add another authorization > level in my app than face this... > > corrections please!! >
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
On Mon, 24 Aug 2009 05:21:05 -0700 (PDT) "J. Dale" wrote: > I've read the http://apiwiki.twitter.com/Sign-in-with-Twitter FAQ and > they say that access tokens don't expire. However, it appears that > they do. Has anyone else noticed that storing access tokens in the > database doesn't really work? Even if access tokens do not expire, there are other reasons why they may fail to persist. Your algorithm for using a token should include a recovery method in the event that authentication fails. Given the work flow for Sign-in-with-Twitter, that should be a matter of storing the request in a way that the landing page for your app can recover it and direct the user there after re-authenticating. If the user is logged into Twitter and hasn't revoked your App then they won't see anything while the redirection is occuring. Chris Babcock
[twitter-dev] [COMING SOON] appended to API works in progress
It’s great to see new API items are getting marked up. I would find it very helpful if [COMING SOON] was replaced by [MM-DD-] when the new item is officially released presuming why to do so is obvious marking the milestone.
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
You don't need to get permission everytime from the user if you are going to store it in a DB. The problem with this is that you will have to implement another level of authorization in your site/app, kind of a password for your app, so that when the session times out, or a user comes back again, he can authorize with your site's password and thus you can use the initial access token granted behind the scenes. This way of doing things is against the "Sign in with Twitter" philosophy, but then I also don't see a way of re-using the access token if you are going with "Sign in with Twitter" philosophy. You are going to ask the user everytime (which means a new access token), and after getting a new access token, you are going to do verifyCredentials (to find out who logged in actually)... and verify- credentials is limited to only 15 requests per 1 hour. This seems like using "Sign in with Twitter" and not reusing access token, you can login only 15 times in an hour? I hope this is not correct... but thts what I understand from http://apiwiki.twitter.com/Twitter-REST-API-Method:-account%C2%A0verify_credentials... If my assumptions are correct, 15 wrong verify-credentials requests from your site will halt your site for at least 1 hour .. and another 15 wrong requests for another 1 hour... which seems too easy for your competitors to block your app!! I'd rather add another authorization level in my app than face this... corrections please!!
[twitter-dev] Re: Track API Limit message meaning
Alex,
I think the documentation is clear, but then again, I wrote it, so I'm
the worst judge of clarity in this case.
The number is the cumulative count of statuses that matched your
predicate but were not delivered to you. If this number is high and or
rapidly increasing, it is an indication that your predicate is too
broad, and you should consider a predicate with higher selectivity.
Alternatively, you can apply for higher levels of track access that
allow a higher proportion of statuses to be delivered.
-John Kalucki
http://twitter.com/jkalucki
Services, Twitter Inc.
On Aug 21, 12:49 pm, Alex Popescu
wrote:
> Hi guys,
>
> I am currently testing a library for using the track API in order to
> make sure that I'm following all the rules exposed on the docs. While
> running against the real API I have noticed sporadic messages in the
> form:
>
> {"limit":{"track":121564}}
>
> According to the docs:
>
> [q]Track streams may also contain limitation notices, where the
> integer track is an enumeration of statuses that matched the track
> predicate but were administratively limited. [/q]
>
> I am not very sure that I'm correctly interpreting the above text as:
>
> 1. the "track" value seems to always be a single value
> 2. the "track" value seems to be growing in time
> 3. the "track" value doesn't seem to be a twitter message id
>
> Could you please clarify a bit the meaning of these messages?
>
> Many thanks in advance,
>
> ./alex
>
> PS: I've asked John (@jkalucki) about this and while I've got an
> answer from him (thanks a bunch John), I'm still not sure I'm getting
> it.
[twitter-dev] Re: streaming api - track method with oauth ?
OAuth is desired, but it's a very low priority right now. We're focused on supporting Twitter to Services interactions in the Streaming API, while attempting to not preclude Twitter to Client interactions. John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Aug 18, 3:40 pm, lquerel wrote: > Hi guys, > > Are there plans to allow oauth instead of the basic auth to access > thetrackservice ? Typically this service can be used in a third > application to follow several subject in a more efficient way that the > current polling method based on the standard API. > > Thanks > > Laurent Quérel
[twitter-dev] Twitter API Authentication
Hi All, I am a web developer using twitter apis in my web application. Here are the steps that i want to do in my application - 1. User is able to see own twitter home page, the on which user can see it's own statuses and it's follow's statues 2. User is not required it re-login for each update. means once user logged in through my application need not to re-login to see statues changes. Any one can help me in this. I am developing ASP.NET web appclication Thanks
[twitter-dev] Re: Track vs. Search
If you want a larger proportion of the statuses, you can apply for a higher level of track access. -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Aug 22, 8:17 am, Mark Nutter wrote: > @Will Yeah, that's what we're currently using, and it works well > enough, but I would really love an unthrottledtrackbecause it > includes the user profile information inline. That would be sooo > nice. > > On Aug 20, 11:54 am, Wil Kern wrote: > > > > > Have you thought about just using the filter:links in yoursearchquery? > > Will > > > On Thu, Aug 20, 2009 at 10:21 AM, Mark Nutter wrote: > > > > I'm writing an application that needs a realtime stream of the links > > > being posted on Twitter. I've been using thesearchapi with asearch > > > for the term 'http' but I stumbled across thetrackfirehose method > > > which appears to offer the same functionality but with the added bonus > > > of including the user profile information inline. Doestrackprovide > > > the same real-time stream that thesearchapi does? Would I be > > > missing links at all by usingtrack? If not, I'll switch over to that > > > immediately. This will greatly reduce the number of API calls I need > > > to make to update user information. Thanks! > > > -- > > Will Kernwww.tweetmart.com > > (c) 703-431-9393
[twitter-dev] Re: statuses/followers stops returning results after page 101
I can confirm this issue; we’re having the exact same problem. -- Kevin Yank CTO, sitepoint.com On Aug 22, 8:11 am, yonnage wrote: > Trying to quickly get follower information (screen name, bio, etc). > Usingstatuses/followersbut after page 101 it no longer returns > results. I believe this used to go far past page 101 in the past. > > I don't believe the docs say that there is a limitation on pages.. is > this a bug?
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
I've read the http://apiwiki.twitter.com/Sign-in-with-Twitter FAQ and they say that access tokens don't expire. However, it appears that they do. Has anyone else noticed that storing access tokens in the database doesn't really work? On Aug 24, 1:11 am, DesignFellow wrote: > Hi, > > I am learning Twitter oAuth. I have a doubt of using oAuth. > > do we need to get access permission everytime from the user to get an > access token? > > I understand that we can store the access token in DB. > but how do i know the logged in user's screen name after session > timeout? > > is there any method to get the logged in users id with asking > permission of the user? > > Thanks in advance :) > DesignFellow
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
> I understand that we can store the access token in DB. > but how do i know the logged in user's screen name after session > timeout? Nowhere in the entire OAuth workflow do you handle users' passwords or their usernames. A benefit is that you do not need the Twitter username to perform any function on the users' behalf with the Twitter API any more than you need the password. If it happens that you need the username for some other business reason then you can call a GET method that returns user profile information to obtain the user name. The account/verify_credentials methods is most common for this purpose, but reliance on this method can make your app subject to DoS because the call has a low, per-user rate limit to protect against brute force password hacking. You can obtain the user id from statuses/user_timeline as well. Send count=1 if you do not need the statuses themselves. Better yet, design your app to not require that you know the username, if possible. Chris Babcock
[twitter-dev] Re: oAuth doubt : do we need get access permission from user every time
Check out: http://apiwiki.twitter.com/Sign-in-with-Twitter Abraham On Mon, Aug 24, 2009 at 00:11, DesignFellow wrote: > > Hi, > > I am learning Twitter oAuth. I have a doubt of using oAuth. > > do we need to get access permission everytime from the user to get an > access token? > > I understand that we can store the access token in DB. > but how do i know the logged in user's screen name after session > timeout? > > is there any method to get the logged in users id with asking > permission of the user? > > Thanks in advance :) > DesignFellow > -- Abraham Williams | Community Evangelist | http://web608.org Hacker | http://abrah.am | http://twitter.com/abraham Project | http://fireeagle.labs.poseurtech.com This email is: [ ] blogable [x] ask first [ ] private.
[twitter-dev] Re: How long does it take to get on white list?
Hi All, We received an enormous number of whitelist requests as a result of people freaking out over the DDoS situation. We are working on going through each request. We realize this is taking longer than normal, but please bear with us. We're getting to all of them ASAP. Thanks, -Chad Twitter Platform Support On Mon, Aug 24, 2009 at 4:30 AM, acmshanyi wrote: > > I have sent my application for the white list two days ago, and > twitter says it will get back to me ASAP. > But I got no response since then. I wander does it means my > application is declined or is still suspended? >
[twitter-dev] How long does it take to get on white list?
I have sent my application for the white list two days ago, and twitter says it will get back to me ASAP. But I got no response since then. I wander does it means my application is declined or is still suspended?
[twitter-dev] Re: using Twitter API with PHP
I understand PHP well enough to code some website (like the site im working on). I can get by but I cant create some of the site with PHP out there just yet. I sterted woking with the http requests and so far so good, but I just cant fugure how to get it to authenticate though a http request. also its going to be a read only script just getting my last few updates to show on the site. On Aug 23, 11:46 pm, Scott Haneda wrote: > If you don't want a public community API, and want to write it in your > own, then you are sort stuck. > > The docs show you sample curl commands or you can http request in a > browser to test simulate. > > You have sample curl examples, if you are objectionable to libraries, > then warp your php around those curl commands. > > If that is not what you want, it sounds like you should look for an > introduction to php tutorial, or a general introduction to web based > scripting languages. > > -- > Scott > Iphone says hello. > > On Aug 23, 2009, at 1:45 PM, Termanater13 wrote: > > > > > Ive been looking to use the Twitter API with my php Site and I cant > > find much just a bunch of URLs used wuth the Twitter API and the curl > > commands used with the API. Can someone point me in the direction of > > where to start, and please nothing done by the comunity unless its a > > tutorial on how to write my own if at al possible.- Hide quoted text - > > - Show quoted text -
