[twitter-dev] Re: friendship/create, and OAuth?
Turns out that the bug was in a different place - what I get for "from_user_id" via search is not the user's ID but some other ID. I had not looked at the notes for "search" or otherwise I would have known about this defect. So I was happily issuing friendships/create requests 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. > > http://github.com/jmathai/twitter-async/tree/master
[twitter-dev] Re: friendship/create, and OAuth?
I have tested using three different libraries - one is MPOAuth, the other one is the PHP library linked to via the Twitter API wiki and the last one is my own custom Objective-C framework. None of them work - but only for the friendships/create method. The code works fine for other methods, as I mentioned. So I don't believe this is a signature issue. Plus, if the signature is invalid, the error should say "Invalid signature" rather than "Page not found", right? Josh, which Python library did you use? Perhaps I can test using the same library and see what results 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). > Could you provide a link to the code you are trying and what libraries > you are using? It would help > others in diagnosing your issue. > > Best of luck, > > Josh
[twitter-dev] Re: friendship/create, and OAuth?
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, Fahim On Oct 4, 11:27 am, Fahim wrote: > When I issue a friendship/create request using OAuth authentication, > I seem to get a 404 error. The same request sent using basic > authentication appears to work correctly. Is this a known issue or > something new that has not been encountered by anybody else before? > > I've tested other 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
[twitter-dev] friendship/create, and OAuth?
When I issue a friendship/create request using OAuth authentication, I seem to get a 404 error. The same request sent using basic authentication appears to work correctly. Is this a known issue or something new that has not been encountered by anybody else before? I've tested other 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
Re: user_timeline Only Returns 4 Pages?
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 cache (10 pages of 20 tweets), > which may not account for 8 - 10 hours of an active friends_timeline.
Re: user_timeline Only Returns 4 Pages?
Alex, could you please clarify what you mean by "as many pages as we have in cache"? The account I'm talking about is my own and I tweet daily. But I can't seem to get my friends' timeline between the time I go to bed at night and when I wake up in the morning (which is 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, what we have in cache may be very little - just > several pages, as you observed.
user_timeline Only Returns 4 Pages?
Hi, I have an app which keeps track of the last fetched tweet ID and then pulls all tweets since then. In the mornings, when I've had my app offline all night, it usually has to g back and pull multiple pages of tweets by using the page and count parameters in conjunction with the since_id parameter. The last few days it appears that it doesn't fetch anything beyond page 4. For instance, if I use the following URL to fetch all tweets since last night, I only get up to 4 pages and then page 5 onwards has no data: http://twitter.com/statuses/friends_timeline.xml?since_id=1065043064&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
Re: since_id limit
But didn't the since_id parameter return all tweets since that ID originally? I have a Twitter client that I've coded which was working fine with since_id till yesterday (December 1st). But since yesterday it only returns the last 20 tweets. Was a functionality/API change made? On Dec 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
