I've noticed that several accounts that no longer exist on twitter are
still returned when accessed via the API.
Example: http://twitter.com/users/show/fitnesstwit.xml (returns a
valid xml dataset)
Despite the fact that http://twitter.com/fitnesstwitt returns a "sorry
that page doesn't exist" e
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 m
On Mon, Oct 5, 2009 at 11:52 PM, JK wrote:
>
> What api do I use to identify the last or latest tweet of the account
> owner?
>
> http://twitter.com/users/show could contain a tweet by a follower.
> http://twitter.com/statuses/user_timeline - states that it returns the
> 20 most recent statuses p
Yea, I understood the differences. My question was why are there
different response codes for the same result? I can understand the
503 being inherited from Summize. However, the 400 vs 403 seems like
poor planning when building out the API. Is there a chance or are
there any plans to unify th
What api do I use to identify the last or latest tweet of the account
owner?
http://twitter.com/users/show could contain a tweet by a follower.
http://twitter.com/statuses/user_timeline - states that it returns the
20 most recent statuses posted from the authenticating user but it
shows status up
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.
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:2
Hello,
On Mon, Oct 5, 2009 at 8:53 PM, jmathai wrote:
>
> Why are 400, 403 and 503 valid response codes to signify that a call
> is being rate limited? Was there a dart board involved?
I don't know, but it would be really hard to play 301 with that dartboard.
>
> * 400 Bad Request: The requ
Why are 400, 403 and 503 valid response codes to signify that a call
is being rate limited? Was there a dart board involved?
* 400 Bad Request: The request was invalid. An accompanying error
message will explain why. This is the status code will be returned
during rate limiting.
* 403 For
A number of clients are still connecting on the deprecated Streaming
API URLs. Be sure that your client is connecting to the documented /1/
statuses/* resources and not the unsupported /gardenhose, /spritzer, /
shadow, /follow, /track, etc. resources. The old URLs have been
unsupported for about 2
> A followup to this for those that are interested:
>
> My real problem wasn't Data::Dumper, but rather the use of JSON::DWIW
>
> It turns out that that module will convert a number into a
> Math::BigInt object if the number is too large to be represented
> natively and the Math::BigInt module i
Tom,
We have a number of services doing this. Facebook was the first, and
probably last service that we'll actively push updates into. All the
rest grab statuses from Twitter. The easiest way is to put a widget on
the page and let the browser include the Tweets. If you want a deeper
integration,
I am pretty sure there are custom headers on the App Engine that indicate
the application that is sending the request.
2009/10/5 elkelk
>
> Hi all,
>
> I am having the same issue. I have tried setting a custom user-agent,
> but this doesn't seem to affect the fact that twitter is limiting
> bas
A followup to this for those that are interested:
My real problem wasn't Data::Dumper, but rather the use of JSON::DWIW
It turns out that that module will convert a number into a
Math::BigInt object if the number is too large to be represented
natively and the Math::BigInt module is installed.
I'm noticing this problem as well. I'm making only a couple requests
per hour. I have tried setting the user-agent and the HTTP_REFERER
headers to a custom name, but Twitter doesn't seem to care.
On Oct 5, 2:59 am, steel wrote:
> Hi. I have this problem too.
> My application does two request p
Hi all,
I am having the same issue. I have tried setting a custom user-agent,
but this doesn't seem to affect the fact that twitter is limiting
based on I.P. address. I'm only making about 5 searches an hour and
80% of them are failing on app engine due to a 503 rate limit.
Twitter needs to det
Hello,
I'm developing for the E.Factor, an entrepreneurial website. I have a
question that I am wondering if it's possible to do.
Facebook has an app that allows a user to configure their Facebook
status updates to automatically be updated when they post something to
their Twitter feed.
Is it po
I recently registered an app under @MacksMind, but the account I'll
use for support etc is @TweetMention.
So 2 questions: Should I care, because I'm not sure it really matters.
And then how would I fix it?
Anyone else still confused at how this works? I'm still confused at how
this is any different than the way it was before with the paging (other than
one-less API call).
Jesse
On Sun, Oct 4, 2009 at 10:57 PM, John Kalucki wrote:
>
> If an API is untrusted, it must be treated as entirely untrust
Yes, it was Perl ...
This obviously wasn't JSON. It was the output of Data::Dumper that
produced this.
I guess I should get more sleep.
Thanks,
Scott
On Oct 5, 1:35 pm, Cameron Kaiser wrote:
> > I hadn't looked at this in a while, but apparently the status id
> > format has changed in th
> I hadn't looked at this in a while, but apparently the status id
> format has changed in the JSON response.
>
> I see a live example such as:
>
> 'id' => ( {
> 'value' => [
>'2050382',
>'463'
>
To be fair to the newer Twitter apps shouldn't all API posts not using
OAUTH show up as "from API" ?
On Oct 5, 12:11 am, ryan alford wrote:
> Twitter removed that functionality just recently. Any application that
> used if before it was removed is still allowed to use it.
>
> On Oct 5, 2009, at
I hadn't looked at this in a while, but apparently the status id
format has changed in the JSON response.
I see a live example such as:
'id' => ( {
'value' => [
'2050382',
'463'
Why not request whitelisting? You'll be able to make 20,000 requests
per hour. Provided you have a legitimate application, there's no
reason why you wouldn't be whitelisted, and it generally seems to
happen pretty quickly.
http://twitter.com/help/request_whitelisting
See more under "Whitelis
I'm working through the backlog now...
-Chad
On Mon, Oct 5, 2009 at 8:28 AM, Waldron Faulkner
wrote:
>
> Hey, Twitter API staff, can you recommend a next step for me to take?
> It's been more than a week since I issued a rate-limit request, and I
> haven't heard anything, nor seen any changes. W
Hey, Twitter API staff, can you recommend a next step for me to take?
It's been more than a week since I issued a rate-limit request, and I
haven't heard anything, nor seen any changes. What to do when the rate
limit request form yields radio silence? Thanks!
- Waldron Faulkner
@WaldronFaulkner
I only can talk for .NET - A Dictionary(of Long, Boolean) with 5000
Id's needs around 500 Ticks If I request the Method .ContainsKey. I
don't think that an API Request with parsing xml can be faster.
Additional you nail the server with unneeded requests which are
"expensive" (rate limits) too
I d
Hi Tomas, another question to collaborate,
do you think that is faster to find the ID in array by iterating it
rather that searching for a string in the XML
with some well known search function
On Oct 5, 10:54 am, twittme_mobi wrote:
> Hi Tomas,
>
> Thanks for the clarification.
> One questi
Hi Tomas,
Thanks for the clarification.
One question - if you have many users, you will need to load all the
IDs
for All the users in the memory - isn't that too heavy?some of the
users have 10+ followers.
Thanks.
On Oct 4, 6:26 pm, Thomas Hübner wrote:
> the problem is that a friendship e
Hi. I have this problem too.
My application does two request per hour and it get "rate limit".
What is wrong? I think it is twitter's problems
On 1 окт, 01:45, Paul Kinlan wrote:
> Hi Guys,
> I have an app on the App engine using the search API and it is getting
> heavily rate limited agai
30 matches
Mail list logo
