[twitter-dev] Is profile_image supposed to be rate limited?
I suspect that the following is rate limited: http://dev.twitter.com/doc/get/users/profile_image/:screen_name In the above link it says rate limited: false. My rate limit status says: hourly_limit=150 remaining_hits=0 reset_time=Wed Mar 30 09:37:17 + 2011 reset_time_in_seconds=1301477837 My remaining_hits is 0. If the above API call is not rate limited, why is it returning a 400 code? The error message: Twitter::BadRequest: GET https://api.twitter.com/1/users/profile_image/ChrisFazz.json: 400: error Can someone explain why this is being rate limited? Is the API doc for this call outdated? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] How to get bigger profile images
How do apps like Twitpic and WeFollow use larger sized profile images?? The Twitter API's largest profile image is 73x73 (http:// dev.twitter.com/doc/get/users/profile_image/:screen_name) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How to get bigger profile images
How would I get 128x128? i.e. from http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_reasonably_small.jpg There is no indication of this in the API anywhere On Dec 13, 4:04 pm, Christian Fazzini christian.fazz...@gmail.com wrote: How do apps like Twitpic and WeFollow use larger sized profile images?? The Twitter API's largest profile image is 73x73 (http:// dev.twitter.com/doc/get/users/profile_image/:screen_name) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How to get bigger profile images
I know that. Thats not what I am asking for. I am wondering how Twitpic is able to get 128x128 when we can only get 73x73 as the largest thumbnail. For example. Image I originally uploaded is stored at this url. http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390.jpg Twitpic uses: http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_reasonably_small.jpg On Dec 13, 4:30 pm, Tom van der Woerdt i...@tvdw.eu wrote: Actually, /1/users/profile_image/tvdw returned my 500x500 image.. All I did was upload it at twitter.com like any other user would. Tom On 12/13/10 9:10 AM, Christian Fazzini wrote: How would I get 128x128? i.e. from http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_re... There is no indication of this in the API anywhere On Dec 13, 4:04 pm, Christian Fazzinichristian.fazz...@gmail.com wrote: How do apps like Twitpic and WeFollow use larger sized profile images?? The Twitter API's largest profile image is 73x73 (http:// dev.twitter.com/doc/get/users/profile_image/:screen_name) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How to get bigger profile images
Ok, how do I connect to the Twitter API to get the reasonably small size? http://dev.twitter.com/doc/get/users/profile_image/:screen_name only accepts the following options: mini, bigger, normal On Dec 13, 5:40 pm, Tom van der Woerdt i...@tvdw.eu wrote: Well, the API returns (in my case)http://a3.twimg.com/profile_images/1079883403/_MG_0016_normal.jpg. Replacing _normal.jpg with _reasonably_small.jpg (so that it becomeshttp://a3.twimg.com/profile_images/1079883403/_MG_0016_reasonably_sma...) seems to work. Tom On 12/13/10 10:15 AM, Christian Fazzini wrote: I know that. Thats not what I am asking for. I am wondering how Twitpic is able to get 128x128 when we can only get 73x73 as the largest thumbnail. For example. Image I originally uploaded is stored at this url. http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390.jpg Twitpic uses: http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_re... On Dec 13, 4:30 pm, Tom van der Woerdti...@tvdw.eu wrote: Actually, /1/users/profile_image/tvdw returned my 500x500 image.. All I did was upload it at twitter.com like any other user would. Tom On 12/13/10 9:10 AM, Christian Fazzini wrote: How would I get 128x128? i.e. from http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_re... There is no indication of this in the API anywhere On Dec 13, 4:04 pm, Christian Fazzinichristian.fazz...@gmail.com wrote: How do apps like Twitpic and WeFollow use larger sized profile images?? The Twitter API's largest profile image is 73x73 (http:// dev.twitter.com/doc/get/users/profile_image/:screen_name) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: How to get bigger profile images
So I would have to use regex or some kind of text function to replace?
A bit dirty. Why isn't reasonably small one of the options in the
API? Is this deprecated?
On Dec 13, 5:49 pm, Tom van der Woerdt i...@tvdw.eu wrote:
A quick look on Google gave me this code :
$(#profile_image).html('img src=' + profile_image.replace('normal',
'reasonably_small') + ' /');
So just get the normal one and replace it with reasonably_small. (Of
course, the above code isn't perfect, as it will also match normal in
the rest of the URL, but I hope that you get the point.
Tom
On 12/13/10 10:44 AM, Christian Fazzini wrote:
Ok, how do I connect to the Twitter API to get the reasonably small
size?
http://dev.twitter.com/doc/get/users/profile_image/:screen_nameonly
accepts the following options:
mini, bigger, normal
On Dec 13, 5:40 pm, Tom van der Woerdti...@tvdw.eu wrote:
Well, the API returns (in my
case)http://a3.twimg.com/profile_images/1079883403/_MG_0016_normal.jpg.
Replacing _normal.jpg with _reasonably_small.jpg (so that it
becomeshttp://a3.twimg.com/profile_images/1079883403/_MG_0016_reasonably_sma...)
seems to work.
Tom
On 12/13/10 10:15 AM, Christian Fazzini wrote:
I know that. Thats not what I am asking for. I am wondering how
Twitpic is able to get 128x128 when we can only get 73x73 as the
largest thumbnail.
For example. Image I originally uploaded is stored at this url.
http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390.jpg
Twitpic uses:
http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_re...
On Dec 13, 4:30 pm, Tom van der Woerdti...@tvdw.eu wrote:
Actually, /1/users/profile_image/tvdw returned my 500x500 image.. All I
did was upload it at twitter.com like any other user would.
Tom
On 12/13/10 9:10 AM, Christian Fazzini wrote:
How would I get 128x128? i.e. from
http://a3.twimg.com/profile_images/290187007/n500024856_39228_3390_re...
There is no indication of this in the API anywhere
On Dec 13, 4:04 pm, Christian Fazzinichristian.fazz...@gmail.com
wrote:
How do apps like Twitpic and WeFollow use larger sized profile
images??
The Twitter API's largest profile image is 73x73 (http://
dev.twitter.com/doc/get/users/profile_image/:screen_name)
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Search by screen name or name?
What API method should I use to search for users based on screen name or name? Currently, the API only offers search by screen name and twitter id... -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Can the Twitter API grab results from the who_to_follow/interests/music url?
Slate. Search wont work It searches ALL users. I want to search for users in an interest group. Basically, the group in users/suggestions is what I want to base the search on On Oct 22, 10:33 pm, Slate Smith sl...@slatesmith.com wrote: http://search.twitter.com/search.json?q=%23OAuth〈=enrpp=100; where .json is the file type, required can be atom, rss or xml. q is your query, remember to break apart special characters [the %23 is a # sign] lang is optional, in this case it's english rpp is optional, defaults to 20 i believe so i specify 100 [the max]. - Slate On Oct 22, 2010, at 6:18 AM, Christian Fazzini wrote: CWorster, how can I searchhttp://api.twitter.com/1/users/suggestions/music.xml for a string? For example, if I wanted to search this list for the string foobar On Oct 21, 7:55 pm, CWorster cwors...@schlimmer.com wrote: Add: http://api.twitter.com/1/users/suggestions/music/members.xml(includes last status) http://api.twitter.com/1/users/suggestions/music.xml(pureuser list) -- Twitter developer documentation and resources:http://dev.twitter.com/doc API updates via Twitter:http://twitter.com/twitterapi Issues/Enhancements Tracker:http://code.google.com/p/twitter-api/issues/list Change your membership to this group:http://groups.google.com/group/twitter-development-talk -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Can the Twitter API grab results from the who_to_follow/interests/music url?
CWorster, how can I search http://api.twitter.com/1/users/suggestions/music.xml for a string? For example, if I wanted to search this list for the string foobar On Oct 21, 7:55 pm, CWorster cwors...@schlimmer.com wrote: Add: http://api.twitter.com/1/users/suggestions/music/members.xml(includes last status) http://api.twitter.com/1/users/suggestions/music.xml(pure user list) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Can the Twitter API grab results from the who_to_follow/interests/music url?
In the Twitter API, is there a way to grab the list of users at the following url http://twitter.com/#!/who_to_follow/interests/music ? http://dev.twitter.com/doc/get/users/search is a bit too general. I need to narrow down my search results based on the interests/music category. Does the Twitter API provide such? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Can the Twitter API grab results from the who_to_follow/interests/music url?
Thanks for that CWorster. It also says: It is recommended that end clients cache this data for no more than one hour. Does anyone know how this can be done in Ruby on Rails? On Oct 21, 7:55 pm, CWorster cwors...@schlimmer.com wrote: Add: http://api.twitter.com/1/users/suggestions/music/members.xml(includes last status) http://api.twitter.com/1/users/suggestions/music.xml(pure user list) -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Hotlinking images
Creating a new Twitter app. I am thinking whether I should save the users images (profile and background) on the local server or hotlink it instead? Whats the e-etiquette for this? Does Twitter encourage us to hotlink images? -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: Retrieving data from the Twitter API
Anyone? On Jul 1, 4:04 pm, Christian Fazzini christian.fazz...@gmail.com wrote: So is this wrong if I save the image and user details locally (on our server) ? Also, how would it be possible to get the users profile pic athttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show using profile_image_url ? At current it only returns _normal.jpg, which is set at 43x43. I need the bigger profile image that is set at 73x73 On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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: Retrieving data from the Twitter API
Anyone? On Jul 1, 4:17 pm, Christian Fazzini christian.fazz...@gmail.com wrote: hmmm On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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: Retrieving data from the Twitter API
Currently, we are saving the images onto our server. If we can hotlink the images to S3. This would save us storage space. However, the only drawback is, whenever a user loads a page on our website, it would have to connect to the S3 servers everytime, to load the images on our site. If, on the other hand, we saved the images on our server, then our website would only have to load everything locally instead of having to connect to the S3 servers. Which method should be used? On Jul 3, 4:05 pm, Christian Fazzini christian.fazz...@gmail.com wrote: Anyone? On Jul 1, 4:04 pm, Christian Fazzini christian.fazz...@gmail.com wrote: So is this wrong if I save the image and user details locally (on our server) ? Also, how would it be possible to get the users profile pic athttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show using profile_image_url ? At current it only returns _normal.jpg, which is set at 43x43. I need the bigger profile image that is set at 73x73 On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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: Retrieving data from the Twitter API
Thanks for clarifying this further Stuart. It makes much sense now. Chris On Jul 3, 5:05 pm, Stuart stut...@gmail.com wrote: 2009/7/3 Christian Fazzini christian.fazz...@gmail.com: Currently, we are saving the images onto our server. If we can hotlink the images to S3. This would save us storage space. However, the only drawback is, whenever a user loads a page on our website, it would have to connect to the S3 servers everytime, to load the images on our site. If, on the other hand, we saved the images on our server, then our website would only have to load everything locally instead of having to connect to the S3 servers. Which method should be used? It's completely up to you. FIrst of all you don't quite understand how a browser loads a web page. It's the browser that connects to S3 to get the images not your server, so there is nothing local about either option. In fact you might see a small improvement in load time by using S3 due to the pipelining algorithms employed by most browsers. If you cache the images on your servers then you guarantee that they will always work without needing to check the Twitter API for changes. The reason for this is that when someone changes their profile image the S3 URL also changes leading to broken images if you're loading them from S3. The downsides are that you're using a lot more bandwidth. If you use the S3 URLs you'll need to regularly check that the S3 URL still exists or hit the API for each user to see if they've changed their image. Which is best for you really depends on what your application is doing with the API and what service it's providing to its users. -Stuart --http://stut.net/projects/twitter On Jul 3, 4:05 pm, Christian Fazzini christian.fazz...@gmail.com wrote: Anyone? On Jul 1, 4:04 pm, Christian Fazzini christian.fazz...@gmail.com wrote: So is this wrong if I save the image and user details locally (on our server) ? Also, how would it be possible to get the users profile pic athttp://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show using profile_image_url ? At current it only returns _normal.jpg, which is set at 43x43. I need the bigger profile image that is set at 73x73 On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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] Logging users on with the Twitter API
Hello, We are developing a website that uses the Twitter API. At current, when a users gets onto our site, a login screen appears, prompting the user to enter his/her twitter username and password. Our system/ website does http://twitter.com/account/verify_credentials.format ( http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0rate_limit_status ) to check if this is a valid user and if their password and username match. If we get a '200' code then we log the user. However, http://apiwiki.twitter.com/Rate-limiting says: The default rate limit for calls to the REST API is 150 requests per hour. The REST API does account- and IP-based rate limiting. Authenticated API calls are charged to the authenticating user's limit while unauthenticated API calls are deducted from the calling IP address' allotment. Does this mean that we can only get 150 users requesting http://twitter.com/account/verify_credentials.format at a given hour? Are we doing our logon process correctly this way? Or should we consider a better approach to this?
[twitter-dev] Re: Logging users on with the Twitter API
Hmm ok just found out that verify_credentials is not rate limited. So I guess we can log as many users on without limitations... Correct me if I am wrong. On Jul 3, 5:22 pm, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are developing a website that uses the Twitter API. At current, when a users gets onto our site, a login screen appears, prompting the user to enter his/her twitter username and password. Our system/ website doeshttp://twitter.com/account/verify_credentials.format (http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ra... ) to check if this is a valid user and if their password and username match. If we get a '200' code then we log the user. However,http://apiwiki.twitter.com/Rate-limitingsays: The default rate limit for calls to the REST API is 150 requests per hour. The REST API does account- and IP-based rate limiting. Authenticated API calls are charged to the authenticating user's limit while unauthenticated API calls are deducted from the calling IP address' allotment. Does this mean that we can only get 150 users requestinghttp://twitter.com/account/verify_credentials.formatat a given hour? Are we doing our logon process correctly this way? Or should we consider a better approach to this?
[twitter-dev] Re: Logging users on with the Twitter API
Yes I've read the documentation. But what is confusing me is the following: If the call I am making states API rate limited: false, in this case for verify_credentials.format , then my API will not have a limit to the number of times I can call this method, since rate limting does not apply for this method. Is this right? On Jul 3, 6:48 pm, Stuart stut...@gmail.com wrote: 2009/7/3 Christian Fazzini christian.fazz...@gmail.com: Hmm this is strange. Also Twitter REST API Method: statuses/update does not have rate limited. Does this mean we can allow an authenticated twitter user to post as many updates to Twitter from our website as he/she wants? Or am I not understanding this correctly? Here's a thought... read all the documentation before posting to this list. POST requests are not limited, but limits do apply to the operations they perform. IOW you can only post x updates a day, and you can only follow y users per day. Ignoring the fact that the method you're talking about is not limited, the answer to your original question was in the documentation you quoted... Authenticated API calls are charged to the authenticating user's limit You may also want to consider whitelisting your application. How do you do that? Details are in the documentation. -Stuart --http://stut.net/projects/twitter On Jul 3, 6:29 pm, Christian Fazzini christian.fazz...@gmail.com wrote: Hmm ok just found out that verify_credentials is not rate limited. So I guess we can log as many users on without limitations... Correct me if I am wrong. On Jul 3, 5:22 pm, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are developing a website that uses the Twitter API. At current, when a users gets onto our site, a login screen appears, prompting the user to enter his/her twitter username and password. Our system/ website doeshttp://twitter.com/account/verify_credentials.format (http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-account%C2%A0ra... ) to check if this is a valid user and if their password and username match. If we get a '200' code then we log the user. However,http://apiwiki.twitter.com/Rate-limitingsays: The default rate limit for calls to the REST API is 150 requests per hour. The REST API does account- and IP-based rate limiting. Authenticated API calls are charged to the authenticating user's limit while unauthenticated API calls are deducted from the calling IP address' allotment. Does this mean that we can only get 150 users requestinghttp://twitter.com/account/verify_credentials.formatatagiven hour? Are we doing our logon process correctly this way? Or should we consider a better approach to this?
[twitter-dev] Re: Retrieving data from the Twitter API
So is this wrong if I save the image and user details locally (on our server) ? Also, how would it be possible to get the users profile pic at http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show using profile_image_url ? At current it only returns _normal.jpg, which is set at 43x43. I need the bigger profile image that is set at 73x73 On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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: Retrieving data from the Twitter API
hmmm On Jun 30, 10:45 pm, Abraham Williams 4bra...@gmail.com wrote: Twitter has said in the past they are more then willing to take care of the bandwidth for smaller applications but if you go huge they ask you to look at local caching. On Tue, Jun 30, 2009 at 08:12, Philip Plantepplante@gmail.com wrote: You can cache the user's profile data so API lookups are kept to a minimum. Though the profile image should be hotlinked using whatever value is stored int he profile_image_url attribute of the user object returned from Twitter. By using S3 as a central source Twitter is able to help alleviate image sync issues that would arise when third party services cache the image locally. Also keep in mind that most of the time your user's should already have their cache primed, via twitter.com or another service, due the caching rules employed by Twitter and S3. On Jun 30, 6:32 am, Christian Fazzini christian.fazz...@gmail.com wrote: Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service (http://s3.amazonaws.com/twitter_production/). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris -- 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] Retrieving data from the Twitter API
Hello, We are in the process of developing a website that uses the Twitter API. I understand that the Twitter API is capable of retrieving a user's profile photo via: http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-users%C2%A0show Other websites that are using the Twitter API are, instead, getting these profile photos from Amazon's S3 storage service ( http://s3.amazonaws.com/twitter_production/ ). At current when a Twitter user logs onto our website, it will retrieve his information and store it our local db. At the same time it will also grab the profile photo from profile_image_url and store it on our server. In my opinion, this seems more appropriate instead of having the site quer the Twitters API and / or hotlink to Amazon's S3 storage service whenever a user loads a page. Especially, if it has to load several profile photos on every page load, on our site. I could be wrong here. What do you guys think the best approach for this is? Hoping to hear from you soon. Best regards, Chris
[twitter-dev] background image
Hello all, Im am currently making a website that uses the twitter api. I am able to obtain the background image of my twitter profile using the url http://twitter.com/users/show.xml?screen_name=screen_name_here Which returns something like this: http://static.twitter.com/images/themes/theme1/bg.gif On my website, I am wondering if I should save this background image onto my own database and loat it from my server or load it directly from the twitter website. I am thinking that the 'friendliest' way is to save the image onto our server and load it from there. This way, we dont have to use Twitter's bandwidth everytime. What are your opinions on this?
