Re: Request Limit

[Jesse Stay]

Does that apply to the 20,000 requests per hour limit?  I thought that was
more geared to non-whitelisted users.
Jesse


On Sat, Feb 7, 2009 at 11:44 PM, Abraham Williams <4bra...@gmail.com> wrote:

> http://apiwiki.twitter.com/REST+API+Documentation#ratelimitstatus
>
>
> On Sun, Feb 8, 2009 at 00:23, Jesse Stay  wrote:
>
>> Is there a way Twitter could provide the number of requests Twitter has
>> detected an app has used in an hour in various requests?  This will make it
>> easier to determine how close we are to hitting that limit and throttle down
>> if necessary.
>> Thanks,
>>
>> Jesse
>>
>
>
>
> --
> | Abraham Williams | http://the.hackerconundrum.com
> | Web608 | Community Evangelist | http://web608.org
> | This email is: [] blogable [x] ask first [] private
>

Re: Request Limit

[Abraham Williams]

http://apiwiki.twitter.com/REST+API+Documentation#ratelimitstatus

On Sun, Feb 8, 2009 at 00:23, Jesse Stay  wrote:

> Is there a way Twitter could provide the number of requests Twitter has
> detected an app has used in an hour in various requests?  This will make it
> easier to determine how close we are to hitting that limit and throttle down
> if necessary.
> Thanks,
>
> Jesse
>



-- 
| Abraham Williams | http://the.hackerconundrum.com
| Web608 | Community Evangelist | http://web608.org
| This email is: [] blogable [x] ask first [] private

Request Limit

[Jesse Stay]

Is there a way Twitter could provide the number of requests Twitter has
detected an app has used in an hour in various requests?  This will make it
easier to determine how close we are to hitting that limit and throttle down
if necessary.
Thanks,

Jesse

Re: OAuth Documentation Preview

[Jesse Stay]

How long do the access tokens last?  Are they permanent, or do they have an
expiration after which we'll have to re-authenticate the user?
Thanks,

Jesse

On Fri, Feb 6, 2009 at 10:52 PM, Matt Sanford  wrote:

>
> Hi all,
>
>We launched our OAuth code to production yesterday with employee-
> only access to check for any problems that didn't show up during our
> testing. We've been running it through it's paces and fully plan to
> have it open to the closed beta group by next week. If you didn't hear
> back from Alex and I don't worry, we're working to expand the beta
> once things are a bit more stable. As part of a company meeting today
> I presented OAuth to the people who haven't been working on it via a
> demo app I wrote … it was exciting times to see this run on
> production. I think of the application developers on this list as an
> extension of our team so I don't want to wait until next week to send
> you the documentation. I wrote up a quick how-to sort of thing on the
> wiki about writing a very simple OAuth app for Ruby on Rals. Check it
> out at http://bit.ly/api-oauth-ruby.
>With any luck we can add some more examples and things during this
> beta period, most notably in PHP since that seems to be the majority
> of the questions on the list.
>
> Thanks;
>— Matt Sanford

Re: avatar URL returned by API different then what twitter web page returns

[Cameron Kaiser]

> Take a look at @SuperGeeks.   The URL for the avatar image returned by
> the API (xml or json), gets a 404 when you try to retrieve it.
> 
> That same user has a different Avatar URL when looking at my timeline
> from the twitter web site, still goes to amazon but different URL...

Did they recently change their avatar? This might be a caching interaction.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Friends don't let friends use Windows. -

avatar URL returned by API different then what twitter web page returns

[CodeWarden]

Hello,

Take a look at @SuperGeeks.   The URL for the avatar image returned by
the API (xml or json), gets a 404 when you try to retrieve it.

That same user has a different Avatar URL when looking at my timeline
from the twitter web site, still goes to amazon but different URL...

Any ideas?

-CodeWarden

Re: Twitter trends for particular subjects, hashtags, @replies

[Dan]

Thanks for the answers.  Currently we can pull trends for all tweets,
but I am looking through the APIs to find a way to pull trends for all
posts that are a reply to a particular user, or all posts that contain
a particular hashtag.  This way you can find trends from a particular
group of users, as opposed to all of twitter.

On Feb 7, 12:49 pm, Alex Payne  wrote:
> We provide an API method to retrieve current 
> trends:http://apiwiki.twitter.com/Search+API+Documentation#Trends
> More information about the 
> firehose:http://apiwiki.twitter.com/FAQ#Whenwillthefirehosebeready
>
>
>
> On Sat, Feb 7, 2009 at 08:50, Sam Sethi  wrote:
>
> > So when will the firehose be available and on what format xmpp. It
> > used to exist ...  Waiting to see of we use gnip xmpp firehose or
> > Twitter?
>
> > Thanks in advance
>
> > Sam
>
> > W:www.twitblogs.com/ssethi
> > M: +44 7985 705075
>
> > Sent from my iPhone
>
> > On 7 Feb 2009, at 16:31, Chad Etzel  wrote:
>
> > > I believe for that you will need the firehose and do your own analysis
> > > on what defines a "trend" in your point of view... Other than that, I
> > > don't readily see a way to get that kind of info from current
> > > resources.
>
> > > -Chad
>
> > > On Sat, Feb 7, 2009 at 6:11 AM, Dan  wrote:
>
> > >> Has anyone found a way to work the API to get this sort of
> > >> functionality?  We are able to determine the top 10 trends for all of
> > >> twitter at any given time, but what about trends for all @replies
> > >> to a
> > >> particular user, or trends in posts that contain a particular
> > >> hashtag?
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

Re: Best practice for building a community website with ~ 20k tweeters?

[Patrick Minton]

Could you elaborate more on what you mean by this?  How does that  
reduce the amount of api requests I need to make?

On Feb 7, 2009, at 2:31 PM, Andrew Badera wrote:

> If so, you can easily pull the RSS feeds from (a) non-interactive  
> account(s) and use that to populate a good chunk of your data.
>
> Thanks-
> - Andy Badera
> - and...@badera.us
> - (518) 641-1280
> - Tech Valley Code Camp 2009.1: http://www.techvalleycodecamp.com/
> - Google me: http://www.google.com/search?q=andrew+badera
>
>
>
> On Sat, Feb 7, 2009 at 9:09 AM, Daniel Sims  wrote:
>
> The twitter RSS feeds has the same rate limits.
>
> Patrick, you may want to check out http://gnipcentral.com/ I haven't
> used it yet, but they supposedly let you pull tweets by specific
> (public) users.
> For profile info, you would need to spread requests out over multiple
> hours.  I doubt you would need real-time profile info anyways since it
> rarely changes.
>
> @dsims
>
> On Feb 7, 12:36 am, Andrew Badera  wrote:
> > If you're dealing with specific people, why not subscribe to their  
> RSS feeds
> > instead?
> >
> > If you're dealing with specific terms, use hash tags and/or the  
> search API.
> >
> > Thanks-
> > - Andy Badera
> > - and...@badera.us
> > - (518) 641-1280
> > - Tech Valley Code Camp 2009.1:http://www.techvalleycodecamp.com/
> > - Google me:http://www.google.com/search?q=andrew+badera
> >
> > On Fri, Feb 6, 2009 at 7:46 PM, Patrick Minton  
>  wrote:
> > > So I've talked to my boss a bit about this and it appears the  
> upper bound
> > > on tweeters that lextweet  would end up  
> following
> > > is something like 2 - 3 members.
> > > The idea of lextweet is not to follow legal posts (so I can't use
> > > tagging/etc), but instead to act as a page where lawyers can  
> easily discover
> > > other lawyers who tweet -- even if they aren't necessarily  
> tweeting about
> > > the law.  For instance, some lawyer in Georgia might want to  
> connect to
> > > another lawyer in Georgia and then they might both start a  
> conversation
> > > about the Hawks or the Falcons.
> >
> > > So if I am building an app that tracks the tweets and profiles  
> of that many
> > > users, what's the best practice?  Right now I have one  
> (whitelisted) user
> > > following about 2k ppl so that each time I query twitter I only  
> have to make
> > > one request for one timeline, and I only query twitter once a  
> day to update
> > > profile info.  If I abandoned having this special user to follow  
> ppl, and
> > > instead kept the users in a database and queried twitter for  
> each user's
> > > timeline that's a LOT more API requests.
> >
> > > Are there any of you who own apps of a similar scope and scale?   
> What do
> > > you do?  What does the Twitter API team recommend?
> >
> > > Patrick
> >
> > > On Feb 1, 2009, at 5:50 PM, Alex Payne wrote:
> >
> > > Whitelisted users can follow a few more users. But we really don't
> > > encourage following a ton of people.
> >
> > > On Sun, Feb 1, 2009 at 14:38, Patrick Minton  
>  wrote:
> >
> > > Does being whitelisted also mean that you can follow more than  
> 2000
> >
> > > people without having 2000 followed?  Lextweet.com uses a twitter
> >
> > > account to follow members of the legal community and we are  
> rapidly
> >
> > > approaching 2000
> >
> > > Patrick
> >
> > > --
> > > Alex Payne - API Lead, Twitter, Inc.
> > >http://twitter.com/al3x
> >
> > > Patrick Minton
> > > IT Director
> > > LexBlog, Inc.
> > > +1 206 204 3211
>

Patrick Minton
IT Director
LexBlog, Inc.
+1 206 204 3211

Re: Best practice for building a community website with ~ 20k tweeters?

[Andrew Badera]

If so, you can easily pull the RSS feeds from (a) non-interactive account(s)
and use that to populate a good chunk of your data.

Thanks-
- Andy Badera
- and...@badera.us
- (518) 641-1280
- Tech Valley Code Camp 2009.1: http://www.techvalleycodecamp.com/
- Google me: http://www.google.com/search?q=andrew+badera



On Sat, Feb 7, 2009 at 9:09 AM, Daniel Sims  wrote:

>
> The twitter RSS feeds has the same rate limits.
>
> Patrick, you may want to check out http://gnipcentral.com/ I haven't
> used it yet, but they supposedly let you pull tweets by specific
> (public) users.
> For profile info, you would need to spread requests out over multiple
> hours.  I doubt you would need real-time profile info anyways since it
> rarely changes.
>
> @dsims
>
> On Feb 7, 12:36 am, Andrew Badera  wrote:
> > If you're dealing with specific people, why not subscribe to their RSS
> feeds
> > instead?
> >
> > If you're dealing with specific terms, use hash tags and/or the search
> API.
> >
> > Thanks-
> > - Andy Badera
> > - and...@badera.us
> > - (518) 641-1280
> > - Tech Valley Code Camp 2009.1:http://www.techvalleycodecamp.com/
> > - Google me:http://www.google.com/search?q=andrew+badera
> >
> > On Fri, Feb 6, 2009 at 7:46 PM, Patrick Minton 
> wrote:
> > > So I've talked to my boss a bit about this and it appears the upper
> bound
> > > on tweeters that lextweet  would end up
> following
> > > is something like 2 - 3 members.
> > > The idea of lextweet is not to follow legal posts (so I can't use
> > > tagging/etc), but instead to act as a page where lawyers can easily
> discover
> > > other lawyers who tweet -- even if they aren't necessarily tweeting
> about
> > > the law.  For instance, some lawyer in Georgia might want to connect to
> > > another lawyer in Georgia and then they might both start a conversation
> > > about the Hawks or the Falcons.
> >
> > > So if I am building an app that tracks the tweets and profiles of that
> many
> > > users, what's the best practice?  Right now I have one (whitelisted)
> user
> > > following about 2k ppl so that each time I query twitter I only have to
> make
> > > one request for one timeline, and I only query twitter once a day to
> update
> > > profile info.  If I abandoned having this special user to follow ppl,
> and
> > > instead kept the users in a database and queried twitter for each
> user's
> > > timeline that's a LOT more API requests.
> >
> > > Are there any of you who own apps of a similar scope and scale?  What
> do
> > > you do?  What does the Twitter API team recommend?
> >
> > > Patrick
> >
> > > On Feb 1, 2009, at 5:50 PM, Alex Payne wrote:
> >
> > > Whitelisted users can follow a few more users. But we really don't
> > > encourage following a ton of people.
> >
> > > On Sun, Feb 1, 2009 at 14:38, Patrick Minton 
> wrote:
> >
> > > Does being whitelisted also mean that you can follow more than 2000
> >
> > > people without having 2000 followed?  Lextweet.com uses a twitter
> >
> > > account to follow members of the legal community and we are rapidly
> >
> > > approaching 2000
> >
> > > Patrick
> >
> > > --
> > > Alex Payne - API Lead, Twitter, Inc.
> > >http://twitter.com/al3x
> >
> > > Patrick Minton
> > > IT Director
> > > LexBlog, Inc.
> > > +1 206 204 3211
>

Re: New API methods to retrieve social graph without pagination

[Stuart]

http://code.google.com/p/twitter-api/issues/detail?id=271

Cheers.

-Stuart

2009/2/7 Alex Payne :
> If you file a ticket, I can check with our engineers to see how performance
> would look if we try to support that filter on the collection we return.
>
> On Sat, Feb 7, 2009 at 11:53, Stuart  wrote:
>>
>> Loving these new methods, but was disappointed to see that they don't
>> support the If-Modified-Since header. Any chance of that to reduce
>> data transfer at both ends and unnecessary processing at our end?
>>
>> -Stuart
>>
>> 2009/2/4 Alex Payne :
>> >
>> > Happy to announce two new API methods today, delivered in response to
>> > developer demand for an easier way to keep tabs on users' social graphs.
>> > The
>> > methods, /friends/ids and /followers/ids, return the entire list of
>> > numeric
>> > user IDs for a user's set of followed and following users, respectively.
>> > Responses to these methods are cached until the user's social graph
>> > changes.
>> > The responses come direct from our denormalized list data stores, and
>> > should
>> > be reasonably fast even for users with a large number of
>> > followers/follows.
>> >
>> > These new methods are most useful for services that are maintaining a
>> > cache
>> > of user details. If you see a user ID that you don't have cached, you'll
>> > have to call /users/show to retrieve that user's details. But for
>> > services
>> > with large user bases, or those that simply want to diff a user's social
>> > graph over time, we hope these methods will come in handy.
>> >
>> > You can find the documentation at
>> > http://apiwiki.twitter.com/REST-API-Documentation#SocialGraphMethods.
>> >
>> > --
>> > Alex Payne - API Lead, Twitter, Inc.
>> > http://twitter.com/al3x
>> >
>> >
>>
>> --
>> http://stut.net/
>
>
>
> --
> Alex Payne - API Lead, Twitter, Inc.
> http://twitter.com/al3x
>

-- 
http://stut.net/

Re: New API methods to retrieve social graph without pagination

[Alex Payne]

If you file a ticket, I can check with our engineers to see how performance
would look if we try to support that filter on the collection we return.

On Sat, Feb 7, 2009 at 11:53, Stuart  wrote:

>
> Loving these new methods, but was disappointed to see that they don't
> support the If-Modified-Since header. Any chance of that to reduce
> data transfer at both ends and unnecessary processing at our end?
>
> -Stuart
>
> 2009/2/4 Alex Payne :
> >
> > Happy to announce two new API methods today, delivered in response to
> > developer demand for an easier way to keep tabs on users' social graphs.
> The
> > methods, /friends/ids and /followers/ids, return the entire list of
> numeric
> > user IDs for a user's set of followed and following users, respectively.
> > Responses to these methods are cached until the user's social graph
> changes.
> > The responses come direct from our denormalized list data stores, and
> should
> > be reasonably fast even for users with a large number of
> followers/follows.
> >
> > These new methods are most useful for services that are maintaining a
> cache
> > of user details. If you see a user ID that you don't have cached, you'll
> > have to call /users/show to retrieve that user's details. But for
> services
> > with large user bases, or those that simply want to diff a user's social
> > graph over time, we hope these methods will come in handy.
> >
> > You can find the documentation at
> > http://apiwiki.twitter.com/REST-API-Documentation#SocialGraphMethods.
> >
> > --
> > Alex Payne - API Lead, Twitter, Inc.
> > http://twitter.com/al3x
> >
> >
>
> --
> http://stut.net/
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Re: Twitter trends for particular subjects, hashtags, @replies

[Alex Payne]

We provide an API method to retrieve current trends:
http://apiwiki.twitter.com/Search+API+Documentation#Trends
More information about the firehose:
http://apiwiki.twitter.com/FAQ#Whenwillthefirehosebeready

On Sat, Feb 7, 2009 at 08:50, Sam Sethi  wrote:

>
> So when will the firehose be available and on what format xmpp. It
> used to exist ...  Waiting to see of we use gnip xmpp firehose or
> Twitter?
>
> Thanks in advance
>
> Sam
>
> W: www.twitblogs.com/ssethi
> M: +44 7985 705075
>
> Sent from my iPhone
>
> On 7 Feb 2009, at 16:31, Chad Etzel  wrote:
>
> >
> > I believe for that you will need the firehose and do your own analysis
> > on what defines a "trend" in your point of view... Other than that, I
> > don't readily see a way to get that kind of info from current
> > resources.
> >
> > -Chad
> >
> > On Sat, Feb 7, 2009 at 6:11 AM, Dan  wrote:
> >>
> >> Has anyone found a way to work the API to get this sort of
> >> functionality?  We are able to determine the top 10 trends for all of
> >> twitter at any given time, but what about trends for all @replies
> >> to a
> >> particular user, or trends in posts that contain a particular
> >> hashtag?
> >>
>



-- 
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x

Re: New API methods to retrieve social graph without pagination

[Stuart]

Loving these new methods, but was disappointed to see that they don't
support the If-Modified-Since header. Any chance of that to reduce
data transfer at both ends and unnecessary processing at our end?

-Stuart

2009/2/4 Alex Payne :
>
> Happy to announce two new API methods today, delivered in response to
> developer demand for an easier way to keep tabs on users' social graphs. The
> methods, /friends/ids and /followers/ids, return the entire list of numeric
> user IDs for a user's set of followed and following users, respectively.
> Responses to these methods are cached until the user's social graph changes.
> The responses come direct from our denormalized list data stores, and should
> be reasonably fast even for users with a large number of followers/follows.
>
> These new methods are most useful for services that are maintaining a cache
> of user details. If you see a user ID that you don't have cached, you'll
> have to call /users/show to retrieve that user's details. But for services
> with large user bases, or those that simply want to diff a user's social
> graph over time, we hope these methods will come in handy.
>
> You can find the documentation at
> http://apiwiki.twitter.com/REST-API-Documentation#SocialGraphMethods.
>
> --
> Alex Payne - API Lead, Twitter, Inc.
> http://twitter.com/al3x
>
>

-- 
http://stut.net/

Re: Feedback for Adobe?

[gsmaverick]

I would definitely talk to them about the memory issues.  They are
definitely discouraging me from using AIR.

On Feb 5, 7:41 pm, Alex Payne  wrote:
> All,
>
> I'm going to be giving a presentation about the Twitter API to Adobe
> employees this coming Tuesday. If you have constructive feedback for
> Adobe, this is a chance to have your suggestions, praises, and
> criticisms hand-delivered to the folks who work there.
>
> My general impresssion is that Adobe's limited HTTP libraries have posed
> some serious challenges for developers working with our APIs and many
> others. I'm not a Flash or AIR developer by any stretch, though, so I
> need your experienced opinions to guide my feedback to their team.
>
> If you'd prefer not to share your feedback publicly, please email me
> off-list.
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x

Re: Twitter trends for particular subjects, hashtags, @replies

[Sam Sethi]

So when will the firehose be available and on what format xmpp. It  
used to exist ...  Waiting to see of we use gnip xmpp firehose or  
Twitter?

Thanks in advance

Sam

W: www.twitblogs.com/ssethi
M: +44 7985 705075

Sent from my iPhone

On 7 Feb 2009, at 16:31, Chad Etzel  wrote:

>
> I believe for that you will need the firehose and do your own analysis
> on what defines a "trend" in your point of view... Other than that, I
> don't readily see a way to get that kind of info from current
> resources.
>
> -Chad
>
> On Sat, Feb 7, 2009 at 6:11 AM, Dan  wrote:
>>
>> Has anyone found a way to work the API to get this sort of
>> functionality?  We are able to determine the top 10 trends for all of
>> twitter at any given time, but what about trends for all @replies  
>> to a
>> particular user, or trends in posts that contain a particular  
>> hashtag?
>>

Re: Twitter trends for particular subjects, hashtags, @replies

[Chad Etzel]

I believe for that you will need the firehose and do your own analysis
on what defines a "trend" in your point of view... Other than that, I
don't readily see a way to get that kind of info from current
resources.

-Chad

On Sat, Feb 7, 2009 at 6:11 AM, Dan  wrote:
>
> Has anyone found a way to work the API to get this sort of
> functionality?  We are able to determine the top 10 trends for all of
> twitter at any given time, but what about trends for all @replies to a
> particular user, or trends in posts that contain a particular hashtag?
>

Re: OAuth Documentation Preview

[Ivan]

Awesome, thanks!

I'll try to post some Python / Django code as we get things working
for Tipjoy.

Ivan
http://tipjoy.com


On Feb 7, 12:52 am, Matt Sanford  wrote:
> Hi all,
>
>     We launched our OAuth code to production yesterday with employee-
> only access to check for any problems that didn't show up during our
> testing. We've been running it through it's paces and fully plan to
> have it open to the closed beta group by next week. If you didn't hear
> back from Alex and I don't worry, we're working to expand the beta
> once things are a bit more stable. As part of a company meeting today
> I presented OAuth to the people who haven't been working on it via a
> demo app I wrote … it was exciting times to see this run on
> production. I think of the application developers on this list as an
> extension of our team so I don't want to wait until next week to send
> you the documentation. I wrote up a quick how-to sort of thing on the
> wiki about writing a very simple OAuth app for Ruby on Rals. Check it
> out athttp://bit.ly/api-oauth-ruby.
>     With any luck we can add some more examples and things during this
> beta period, most notably in PHP since that seems to be the majority
> of the questions on the list.
>
> Thanks;
>    — Matt Sanford

Twitter trends for particular subjects, hashtags, @replies

[Dan]

Has anyone found a way to work the API to get this sort of
functionality?  We are able to determine the top 10 trends for all of
twitter at any given time, but what about trends for all @replies to a
particular user, or trends in posts that contain a particular hashtag?

Re: Best practice for building a community website with ~ 20k tweeters?

[Daniel Sims]

The twitter RSS feeds has the same rate limits.

Patrick, you may want to check out http://gnipcentral.com/ I haven't
used it yet, but they supposedly let you pull tweets by specific
(public) users.
For profile info, you would need to spread requests out over multiple
hours.  I doubt you would need real-time profile info anyways since it
rarely changes.

@dsims

On Feb 7, 12:36 am, Andrew Badera  wrote:
> If you're dealing with specific people, why not subscribe to their RSS feeds
> instead?
>
> If you're dealing with specific terms, use hash tags and/or the search API.
>
> Thanks-
> - Andy Badera
> - and...@badera.us
> - (518) 641-1280
> - Tech Valley Code Camp 2009.1:http://www.techvalleycodecamp.com/
> - Google me:http://www.google.com/search?q=andrew+badera
>
> On Fri, Feb 6, 2009 at 7:46 PM, Patrick Minton  wrote:
> > So I've talked to my boss a bit about this and it appears the upper bound
> > on tweeters that lextweet  would end up following
> > is something like 2 - 3 members.
> > The idea of lextweet is not to follow legal posts (so I can't use
> > tagging/etc), but instead to act as a page where lawyers can easily discover
> > other lawyers who tweet -- even if they aren't necessarily tweeting about
> > the law.  For instance, some lawyer in Georgia might want to connect to
> > another lawyer in Georgia and then they might both start a conversation
> > about the Hawks or the Falcons.
>
> > So if I am building an app that tracks the tweets and profiles of that many
> > users, what's the best practice?  Right now I have one (whitelisted) user
> > following about 2k ppl so that each time I query twitter I only have to make
> > one request for one timeline, and I only query twitter once a day to update
> > profile info.  If I abandoned having this special user to follow ppl, and
> > instead kept the users in a database and queried twitter for each user's
> > timeline that's a LOT more API requests.
>
> > Are there any of you who own apps of a similar scope and scale?  What do
> > you do?  What does the Twitter API team recommend?
>
> > Patrick
>
> > On Feb 1, 2009, at 5:50 PM, Alex Payne wrote:
>
> > Whitelisted users can follow a few more users. But we really don't
> > encourage following a ton of people.
>
> > On Sun, Feb 1, 2009 at 14:38, Patrick Minton  wrote:
>
> > Does being whitelisted also mean that you can follow more than 2000
>
> > people without having 2000 followed?  Lextweet.com uses a twitter
>
> > account to follow members of the legal community and we are rapidly
>
> > approaching 2000
>
> > Patrick
>
> > --
> > Alex Payne - API Lead, Twitter, Inc.
> >http://twitter.com/al3x
>
> > Patrick Minton
> > IT Director
> > LexBlog, Inc.
> > +1 206 204 3211

Re: Changing profile image via PHP/Curl

[Noah]

I owe you guys a beer. This really helped!

On Jan 6, 4:26 pm, "Chad Etzel"  wrote:
> We figured this out off-list, but I'm posting the fix for completeness:
>
> For some reason $newfilename was missing a "." in the filename before "jpg".
>
> try tweaking this line:
> $newfilename = substr($tmpfilename, 0, strlen($tmpfilename) -
> strlen($ext))  . $ext;
> to
> $newfilename = substr($tmpfilename, 0, strlen($tmpfilename) -
> strlen($ext))  . "." . $ext;
>
> That seemed to fix it for James.  Not sure why the code acted
> differently on my server and his, but we got it working for him this
> way.
>
> -Chad
>
> On Tue, Jan 6, 2009 at 4:05 PM, James N. Weber  wrote:
>
>
>
> > Chad- Thanks for all your help with this! I downloaded it from
> > pastebin, and then uploaded it to my server, no changes. It is giving
> > me the "There was a problem with your picture. Probably too big."
> > error still, with several photos. Any ideas what's going on?
>
> > On Jan 6, 1:31 pm, "Chad Etzel"  wrote:
> >> So after some fiddling with your code, I got it to work:
>
> >> I think part of the problem was that you can't use URLs to the image
> >> (like you were doing).
>
> >> Anyway, the following code (see pastebin link) gives examples of how
> >> to do it with File Uploading through a form, or just using canned
> >> local images from your server.
>
> >>http://pastebin.com/f6eb4650c
>
> >> Hope this helps,
> >> -Chad
>
> >> On Tue, Jan 6, 2009 at 3:15 PM, Stuart  wrote:
>
> >> > 2009/1/6 James N. Weber :
>
> >> >> Thanks for the help, Chad. I think I need the PHP equivalent of -F in
> >> >> curl- I'm not sure how to set that.
>
> >> >> I tried changing it to CURLOPT_POSTFIELDS, and Twitter gave me a
> >> >> "Something is technically wrong." page- the robot lobster with a
> >> >> broken claw.
> >> >> Any ideas?
>
> >> > The code I took the below line from is not uploading an image to
> >> > Twitter, but rather between two internal servers on one of the sites I
> >> > maintain and it works fine for me...
>
> >> > curl_setopt($ch, CURLOPT_URL, $url);
> >> > curl_setopt($ch, CURLOPT_HTTPHEADER, array('Expect: '));
> >> > curl_setopt($ch, CURLOPT_POST, 1);
> >> > curl_setopt($ch, CURLOPT_POSTFIELDS, array('img' => '@'.$filename));
> >> > curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
> >> > $result = curl_exec($ch);
>
> >> > Hope it helps you.
>
> >> > -Stuart
>
> >> > --
> >> >http://stut.net/