equests using the invalid ID and that was why I was getting 404s. Now
that I've fixed that, the friendships/create actually works fine.
Thanks to all who responded :)
Regards,
Fahim
On Oct 6, 8:28 pm, jmathai wrote:
> It also works using twitter-async. You can run the unit tests.
>
I get to see where things might be
going wrong ...
regards,
Fahim
On Oct 6, 7:51 am, Josh Roesslein wrote:
> I have tested friendships/create using my python libraryvia oauth and
> works fine.
> My guess is you are not generating a valid oauth request (ex. invalid
> signature).
>
Nobody knows anything about this? I've tried three different OAuth
frameworks (one in PHP and two in Objective-C) and all of them return
a "Page not found" for a /friendships/create.json
Is anybody on the Twitter team able to confirm or deny whether this is
a bug?
Regards,
Fahi
OAuth requests (status updates, timeline requests
etc.) and they all work fine. So this is not an OAuth issue as far as
I know.
Anybody else encounter something similar and perhaps know of a
workaround?
Regards,
Fahim
And there's no way to fetch more than the cached number of tweets? Or
to get all the tweets that are there on the friends_timeline since a
given ID beyond the cached limit?
Kind regards,
Fahim
On Dec 21, 12:44 am, "Alex Payne" wrote:
> We keep a maximum of 200 status in cac
about
8-10 hours). Isn't the cache supposed to have last 24 hours worth of
tweets? Or am I misreading what you typed?
Kind regards,
Fahim
On Dec 20, 12:19 am, "Alex Payne" wrote:
> We can only return as many pages as we have in cache. For accounts
> with little activity, w
064&page=4&count=200
Is this normal behaviour? I didn't think it worked like this before
and that it returned however many pages (back to 24 hours) of data
there was. Am I imagining things or has something changed?
Regards,
Fahim
1, 6:38 pm, "Brian Gilham" <[EMAIL PROTECTED]> wrote:
> If there are more than 20 results, you can use paging to grab them all.
Kind regards,
Fahim
