Reply to thread

Message

<blockquote data-quote="yoavain" data-source="post: 752407" data-attributes="member: 92067">Hmm, I see your point.Here's what I found in Twitter API documentation:<a href="http://dev.twitter.com/doc/get/users/profile_image/:screen_name" target="_blank">GET users/profile_image/:screen_name | dev.twitter.com</a>According to that, you can use the following options (for example, with the user &quot;teammediaportal&quot;)<a href="http://api.twitter.com/1/users/profile_image/teammediaportal.xml" target="_blank">http://api.twitter.com/1/users/profile_image/teammediaportal.xml</a><a href="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=normal" target="_blank">http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=normal</a><a href="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=bigger" target="_blank">http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=bigger</a><a href="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=mini" target="_blank">http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=mini</a>And here's the one they do not document:<a href="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=original" target="_blank">http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=original</a>IMO, the one they don't document is still valid, since anything else gives back:[HTML]&lt;errors&gt;&lt;error code=&quot;24&quot;&gt;Unsupported profile image size&lt;/error&gt;&lt;/errors&gt;[/HTML]Anyway, we can always do this:1. Try to get the original (biggest)2. If we get an error return code, try to get &quot;bigger&quot;3, If we get an error return code, try to get &quot;normal&quot;But I'm pretty confident 1. will work great.By the way, I got the idea from the well known HoverZoom Chrome Extension...<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />,Yoav</blockquote>

[QUOTE="yoavain, post: 752407, member: 92067"] Hmm, I see your point. Here's what I found in Twitter API documentation: [url=http://dev.twitter.com/doc/get/users/profile_image/:screen_name]GET users/profile_image/:screen_name | dev.twitter.com[/url] According to that, you can use the following options (for example, with the user "teammediaportal") [URL="http://api.twitter.com/1/users/profile_image/teammediaportal.xml"]http://api.twitter.com/1/users/profile_image/teammediaportal.xml[/URL] [URL="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=normal"]http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=normal[/URL] [URL="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=bigger"]http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=bigger[/URL] [URL="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=mini"]http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=mini[/URL] And here's the one they do not document: [URL="http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=original"]http://api.twitter.com/1/users/profile_image/teammediaportal.xml?size=original[/URL] IMO, the one they don't document is still valid, since anything else gives back: [HTML]<errors> <error code="24">Unsupported profile image size</error> </errors>[/HTML] Anyway, we can always do this: 1. Try to get the original (biggest) 2. If we get an error return code, try to get "bigger" 3, If we get an error return code, try to get "normal" But I'm pretty confident 1. will work great. By the way, I got the idea from the well known HoverZoom Chrome Extension... :thx:, Yoav [/QUOTE]

Verification