Hi,

If you go to http://dev.twitter.com/console and choose
statuses/home_timeline.json, then type count in the parameter field
then 1 in the parameter value field, the result is many tweets,  not
one.

The 'request' tab doesn't show the parameter anywhere, I also tried
added three other parameters and they don't show up... should they?...

opening connection to api.local.twitter.com...
opened
<- "GET /1/statuses/home_timeline.json HTTP/1.1
Accept: */*
Connection: close
User-Agent: OAuth gem v0.3.4.1
Authorization: OAuth oauth_nonce=\"xxx\",
oauth_signature_method=\"HMAC-SHA1\", oauth_timestamp=\"1299691694\",
oauth_consumer_key=\"xxx\", oauth_token=\"xxx\",
oauth_signature=\"xxx\", oauth_version=\"1.0\"
Host: api.local.twitter.com:9000

My iphone application uses MGTwitterEngine and the variables indicate...

Request https://twitter.com/statuses/friends_timeline.xml

parameters (objective C dictionary - this will be mapped to paramters
in the request somewhere in their API)

"{
    count = 1;
}"

Cheers,
Rob.


On 9 March 2011 06:52, Matt Harris <[email protected]> wrote:
> Hey Rob,
> Can you share the exact URL you are requesting. When I use the count
> parameter with a value of 1 I only get 1 tweet back. The URL I am requesting
> looks like this:
>     https://api.twitter.com/1/statuses/home_timeline.json?count=1
> Best,
> @themattharris
> Developer Advocate, Twitter
> http://twitter.com/themattharris
>
>
> On Tue, Mar 8, 2011 at 10:45 PM, Rob Wilson <[email protected]> wrote:
>>
>> Hi,
>>
>> When my application first starts up, I want to display only the very
>> last tweet, so I ask for the timeline with the COUNT parameter set to
>> 1, oddly I then receive say 20-30 tweets.
>>
>> I then plan to periodically ask for any new tweets since the highest
>> ID last returned, then keep repeating the request for new tweets.
>>
>> Why do I receive more than one tweet in the return?  If I set it to 20
>> or 30, I still get the same size XML returned.  I've tried it with a
>> PAGE=1, but that didn't seem to make any difference.  The API
>> documentation implies that this should all be okay; it should return x
>> tweets.
>>
>> Thanks,
>> Rob.
>>
>> --
>>
>>
>> Please visit...
>>
>> SpikyOrange.co.uk A portal for anything I create, including...
>>
>> BitBanter.com A technical podcast 50% Tech + 50% software development
>> = 100% Entertaining!
>>
>> --
>> 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
>



-- 


Please visit...

SpikyOrange.co.uk A portal for anything I create, including...

BitBanter.com A technical podcast 50% Tech + 50% software development
= 100% Entertaining!

-- 
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

Reply via email to