we don't support the original in this endpoint - just the three that you
listed.

On Sun, Apr 18, 2010 at 3:33 PM, Abraham Williams <4bra...@gmail.com> wrote:

> Mini, normal, and bigger are work but what about original?
>
> Abraham
>
>
> On Sun, Apr 18, 2010 at 13:37, Raffi Krikorian <ra...@twitter.com> wrote:
>
>> http://api.twitter.com/1/users/profile_image/raffi?size=bigger
>>
>> we will document this endpoint this week.
>>
>>
>> On Sun, Apr 18, 2010 at 1:34 PM, WBC <wooden.brain.conce...@gmail.com>wrote:
>>
>>> Thanks Raffi... I knew there had to be something more simple!  Is
>>> there a way to get the bigger image?  I can parse the HTML and just
>>> replace _normal with _bigger of course... Anyway, cheers.
>>>
>>> On Apr 18, 8:50 am, Raffi Krikorian <ra...@twitter.com> wrote:
>>> > e.g.http://api.twitter.com/1/users/profile_image/raffi
>>> >
>>> > On Sat, Apr 17, 2010 at 9:41 PM, WBC <wooden.brain.conce...@gmail.com
>>> >wrote:
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > > Hello all, please forgive a newbie here.
>>> >
>>> > > I would like to accomplish one simple task as described in the
>>> > > title:   get the URL of a user profile picture by user name, in the
>>> > > context of a Mac application.  At this time (and in the foreseeable
>>> > > future) I have no interest in doing more with the API(s).
>>> >
>>> > > I do not want to ask users to authenticate with their own accounts
>>> for
>>> > > this simple purpose, and I don't want to run into an
>>> application-based
>>> > > rate-limit for my distributed, desktop application.   I do plan to
>>> > > cache and honestly I can't imagine more than 50 calls a WEEK per IP
>>> > > for this purpose.
>>> >
>>> > > I assume based on this from the FAQ:
>>> >
>>> > > "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."
>>> >
>>> > > ... that the user's IP is the one "deducted" if unauthenticated,
>>> which
>>> > > is perfectly fine.
>>> >
>>> > > But the search API requires authentication:
>>> >
>>> > >http://api.twitter.com/1/users/search.xml?q=username
>>> >
>>> > > I've spent quite a lot of time trying to figure this out already, so
>>> a
>>> > > simple "yes, you can do it and here's the URL" would be very kind.
>>>  (I
>>> > > can easily accomplish what I want just by parsing some HTML... but I
>>> > > thought I'd try to be legit about it ;-)
>>> >
>>> > > --
>>> > > Subscription settings:
>>> > >
>>> http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
>>> >
>>> > --
>>> > Raffi Krikorian
>>> > Twitter Platform Teamhttp://twitter.com/raffi
>>>
>>
>>
>>
>> --
>> Raffi Krikorian
>> Twitter Platform Team
>> http://twitter.com/raffi
>>
>
>
>
> --
> Abraham Williams | Developer for hire | http://abrah.am
> PoseurTech Labs | Projects | http://labs.poseurtech.com
> This email is: [ ] shareable [x] ask first [ ] private.
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Reply via email to