That's perfect, thanks Raffi!
On Jul 6, 5:49 am, Raffi Krikorian ra...@twitter.com wrote:
hi steve.
there are two different ways to geotag a tweet. there is geotagging with
an exact latitude and longitude, and then there is geotagging with a place.
when you geotag with an exact latitude
Please see bug report 1725 - http://bit.ly/anxAiC
Apparently, you cannot geotag tweets anymore when a user's account is
configured to any non-English language.
My client users started to report this error a couple of days ago.
When they switch back to English (lang = en), everything's fine
Oh dear, thanks a lot for this info. I was trying for two days to get this
working!
Thanks!
Daniel
Am 06.07.2010 um 13:24 schrieb janole:
Please see bug report 1725 - http://bit.ly/anxAiC
Apparently, you cannot geotag tweets anymore when a user's account is
configured to any non-English
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request to
http://api.twitter.com/version/account/rate_limit_status.json comes
back saying I have 8 calls left and it will be reset at 07:54, but the
time is currently 13:18!
The time for
I've got the same problem, according to the api response the reset
time is in the past.
On 6 Jul., 14:20, artesea ryancul...@gmail.com wrote:
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request
On 07/06/10 06:50, Raffi Krikorian wrote:
i'm sorry, i'm not sure what you're asking. the mentions timeline has
mentions information in
it: http://dev.twitter.com/doc/get/statuses/mentions
On Mon, Jul 5, 2010 at 12:12 PM, show3r sho...@gmail.com
mailto:sho...@gmail.com wrote:
hi i
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request to
http://api.twitter.com/version/account/rate_limit_status.json comes
back saying I have 8 calls left and it will be reset at 07:54, but the
time is currently 13:18!
The time
Quoting Cameron Kaiser spec...@floodgap.com:
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request to
http://api.twitter.com/version/account/rate_limit_status.json comes
back saying I have 8 calls left and it will be reset at 07:54,
Quoting M. Edward (Ed) Borasky zn...@borasky-research.net:
Quoting Cameron Kaiser spec...@floodgap.com:
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request to
http://api.twitter.com/version/account/rate_limit_status.json comes
Hello,
I am trying to work with favor api. For example I am trying to load
this url:
https://api.twitter.com/1/favorites/17866945968/create.json
and the result is:
{request:/1/favorites/17866945968/create.json,error:Not
found}
But the tweet exists, as you can see:
Finally have access again, with the time to reset now at 15:27 (around
an hour).
Ryan
I think the request is that @mentions are merged in with home_timeline.
There may be desktop clients that support this functionality, for all I
know.
The risks are that some users receive a lot of @mentions, and their home
timelines would be unreadable. So, it would have to be an option.
Anyone, please. This is still a problem. Previous_Cursor_Str is
returning an empty object when trying to return from pages 2 or 3.
This is affecting all my apps. Does anyone have any idea what's gone
wrong and what if anything I can do about it?
On Jul 5, 9:15 am, Ron rbther...@gmail.com wrote:
unfortunately, we don't yet support that functionality. the list is sorted
with the newest items being first - you could grab the first page, and
then go backwards until you start to see data that you've seen before.
On Mon, Jul 5, 2010 at 10:34 PM, nischalshetty nischalshett...@gmail.comwrote:
can you all please provide a concrete example? i just geotagged a tweet
from my test account, switched my test account to spanish, then successfully
geotagged another tweet, switched to japanese, and then geotagged yet
another tweet.
On Tue, Jul 6, 2010 at 4:43 AM, Daniel Schroeder
another way of stating is to wonder how you handle the mismatch of the
number of tweets the home and mentions timeline receives. most people do
not want to miss any results in the mentions timeline, but a lot of people
do not mind missing tweets in the home timeline. if you mash the two
Quoting artesea ryancul...@gmail.com:
Finally have access again, with the time to reset now at 15:27 (around
an hour).
Ryan
Ouch - sounds like my IP address got blocked then.
hi carlos.
i'm sorry that i'm not sure i can help to debug this code right now. if you
are going to insist on creating your own functions to do the oauth
signature, please consult
http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signing-requests/as
its a great interactive walk
Hi,
https://api.twitter.com/1/favorites/17866945968/create.json
post this url : https://api.twitter.com/1/favorites/create/17866945968.json
On Jul 6, 9:23 am, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Quoting artesea ryancul...@gmail.com:
Finally have access again, with the time to reset now at 15:27 (around
an hour).
Ryan
Ouch - sounds like my IP address got blocked then.
I appear to have the same issue.
I am developing a normal twitter search application
Inorder to beat the search rate limit if I ask a user to authenticate
whether that would be helpful?
Whether the calls made by the user for search api will be counted in
the user's account ? or whether that would be
still counted as a call
On 07/06/10 15:47, John Kalucki wrote:
I think the request is that @mentions are merged in with
home_timeline. There may be desktop clients that support this
functionality, for all I know.
The risks are that some users receive a lot of @mentions, and their
home timelines would be unreadable.
We're looking into this rate limiting issue.
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, Jul 6, 2010 at 7:45 AM, Jeff Randall jeffr...@swbell.net wrote:
On Jul 6, 9:23 am, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Quoting artesea
With the following feed/script:
$twitter_url = http://twitter.com/statuses/user_timeline/
britishabroad.xml?count=1;
$buffer = file_get_contents($twitter_url);
$xml = new SimpleXMLElement($buffer);
$status_item = $xml - status;
$status = $status_item - text;
echo $status;
Nothing is being
Lockouts are now common and frequent for everyday users doing normal things.
I have dozens of reports from my users being locked out. And I've noticed that
nearly every Twitter client developer has posted about this in a blog or Tweet.
Several in just the last 24 hours.
I know that the goal
These lockouts are almost certainly due to a performance optimization
intended to reduce network utilization by increasing physical reference
locality in a multi-level loosely-coordinated best-effort distributed cache.
Not easy to get right, and the engineers involved are working to resolve the
The api documentation (http://dev.twitter.com/doc/get/trends/
location/:woeid) lists the url format as
http://api.twitter.com/version/trends/location/:woeid.format
and shows as an example the following url:
http://api.twitter.com/1/trends/location/1.xml
This example url in the documentation also
With multi-level loosely-coordinated best-effort distributed cache you
certainly got the naming, all that's left is the cache invalidation. :)
Pascal
On Jul 6, 2010, at 18:10 , John Kalucki wrote:
These lockouts are almost certainly due to a performance optimization
intended to reduce
Hi Colin,
You're missing the api subdomain and version 1.. this should work for you
instead:
http://api.twitter.com/1/statuses/user_timeline/britishabroad.xml?count=1
Taylor
On Tue, Jul 6, 2010 at 8:18 AM, colin@digital.fco.gov.uk
colin@digital.fco.gov.uk wrote:
With the following
John,
Do you measure the number of lockouts?
Or maybe a better question is: do you have metrics on how reducing rate limits
is impacting users?
isaiah
http://twitter.com/isaiah
On Jul 6, 2010, at 9:10 AM, John Kalucki wrote:
These lockouts are almost certainly due to a performance
Hello!
I'm using the api statuses / destroy with OAuth to delete messages.
Returns HTTP = 200, I see that decreases the amount of tweets that
shows the profile of the account. But the message continues and it is
not excluded.
Got a problem with this api or is missing some procedure.
Can you give
I notice that the rate limit is application specific. I've tried a few
clients, some of them goes thru, some don't.
On Jul 6, 5:20 am, artesea ryancul...@gmail.com wrote:
I'm being locked out on my account using the API and I'm seeing
reports from others. At the moment making a request
Just a sidenote: This can be coincidental. Unless you try several dozen times
with each client, no valid inference can be drawn from the tests.
Pascal
On Jul 6, 2010, at 18:46 , Johnson wrote:
I notice that the rate limit is application specific. I've tried a few
clients, some of them goes
Hi Taylor, i have fixed this, the problem wasnt on hmac-sha1 and
base64 encoding, on my ajax call with jquery something wrong happened,
i have changed it to HttpRequest of firefox component and it works. My
app is an addon for firefox and its client side (javascript and xul).
I know its not secure
We make only about 20-25 requests per hour. We didnt have any problems
until today morning. And all of a sudden I am seeing Rate limit
exceeded. Clients may not make more than 75 requests per hour.
This is Zimbra Collaboration Suite's Social Zimlet.
Quoting goodtest goodtest...@gmail.com:
We make only about 20-25 requests per hour. We didnt have any problems
until today morning. And all of a sudden I am seeing Rate limit
exceeded. Clients may not make more than 75 requests per hour.
This is Zimbra Collaboration Suite's Social Zimlet.
I
I want to know what's the metrics of this dynamic logout.
I have several twitter account/twitter development accounts.
It started around 1am PST, one of my account keep getting 400. I woke
up this morning, that only account is still getting 400.
I tried a different pair comsumer key/token using
Thanks Raffi,
I'll check that library out. I didn't know there were libraries I
could use.
On Jul 6, 7:23 am, Raffi Krikorian ra...@twitter.com wrote:
hi carlos.
i'm sorry that i'm not sure i can help to debug this code right now. if you
are going to insist on creating your own functions to
Hi JC.
What are the limits on free? We're wary of locking ourselves into a
service that we won't be able to afford.
On Mon, Jul 5, 2010 at 2:44 AM, Jean-Charles Campagne a...@semiocast.com
wrote:
Hello James,
may be you would be interested in looking at our API which provides
language and
Hi Shan,
The Search API is anonymous so authenticating makes no difference to the
rate limit there. If you are requesting a lot of information from the search
API you may want to look at the streaming API instead:
http://dev.twitter.com/pages/streaming_api
The majority of search cases can be
We are about to integrate Twitter support in our iOS library and we
are seeing that some devs prefer xAuth over oAuth? Which one are you
using and why? Does Twitter push for one of them more?
Thanks
This is a known issue with the list cursors which we are working on.
It is being tracked in the API issue tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1572
We'll be updating the issue log when we have news. For the moment the source
of the error has been identified and we
I'm quite new to this, os I'd really appreciate any help.
I'm developing a Flash desktop app that will integrate with a twitter
user's timeline to display tweets in a custom way.
The thing is, that even though I can authenticate properly (the whole
PIN process works great) I can't get anything
We are aware rate limits are being reported incorrectly. We are tracking the
issue on the API tracker:
http://code.google.com/p/twitter-api/issues/detail?id=1728
Matt
On Tue, Jul 6, 2010 at 10:10 AM, Johnson johnson...@gmail.com wrote:
I want to know what's the metrics of this dynamic logout.
Hi Awahid,
The trends calls work on the search.twitter.com domain but we recommend
using http://api.twitter.com/1/trends/* instead.
In answer to your query trends and search have an index of about 7-10 days
depending on the traffic, except weekly trends which go back about a month.
Hope that
Yep I'm now locked out of my own account with this issue
On Jul 6, 10:38 pm, Matt Harris thematthar...@twitter.com wrote:
We are aware rate limits are being reported incorrectly. We are tracking the
issue on the API
tracker:http://code.google.com/p/twitter-api/issues/detail?id=1728
Matt
Hi Daniel,
I've tested this a couple of times on my accounts and it is working
correctly. Rather than the PHP object can you instead show the actual
XML/JSON response you get back.
Thanks,
Matt
On Mon, Jul 5, 2010 at 8:19 AM, meto deeme...@googlemail.com wrote:
Hi guys,
I'm having problems
On Jul 6, 6:47 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
Quoting goodtest goodtest...@gmail.com:
We make only about 20-25 requests per hour. We didnt have any problems
until today morning. And all of a sudden I am seeing Rate limit
exceeded. Clients may not make more
Thank you everyone.
You've given me quite a few good options to look into.
Lucas
On Mon, Jul 5, 2010 at 5:57 AM, Jean-Charles Campagne a...@semiocast.com
wrote:
Hello Lucas,
We do not provide, yet, exactly what you are looking for, but for now
we might help you on the language filtering
Hi Claudia,
Where are you seeing the Tweet get displayed? Is this on the website or
through a particular API request?
Matt
On Tue, Jul 6, 2010 at 9:48 AM, Claudia A. V. Callegari
claudia.avcalleg...@gmail.com wrote:
Hello!
I'm using the api statuses / destroy with OAuth to delete messages.
We are using oAuth on the iPhone. It works great and I don't see why
xAuth should be allowed on iPhone as the embedded web browser is more
than capable
On Jul 6, 8:55 pm, Oscar Cortes ocort...@gmail.com wrote:
We are about to integrate Twitter support in our iOS library and we
are seeing that
We only use documented versioned api calls and seeing rate limit
issues. I've not been aplenty to use my account for hours. Change ip
address and it's fine
On Jul 6, 10:45 pm, Bruno Renié bubu...@gmail.com wrote:
On Jul 6, 6:47 pm, M. Edward (Ed) Borasky zn...@borasky-
research.net wrote:
We have a known issue with Rate Limits which we're working on a fix for.
Updates will be posted to http://status.twitter.com.
Matt
On Tue, Jul 6, 2010 at 3:31 PM, Rich rhyl...@gmail.com wrote:
We only use documented versioned api calls and seeing rate limit
issues. I've not been aplenty to
Hi Ron,
Did this work for you in the end? A 500 error is usually a result of
something going wrong on our side, like an over capacity error. When that
happens we suggest waiting a short time and trying again.
Let us know if that works out.
Matt
On Thu, Jul 1, 2010 at 7:48 PM, Ron
Hi J,
We have an issue tracker and enhancements list which I think you should add
this to. To other subscribers to the list, if you think this is a feature
you would like to see us work on please 'star' it on the issue tracker.
The issue tracker can be found here:
I have just fixed my last error. My oauth_token wasnt in correct orden
on my base string.
Thanks!
On Jul 6, 2:19 pm, ntortarolo ntortar...@gmail.com wrote:
Hi Taylor, i have fixed this, the problem wasnt on hmac-sha1 and
base64 encoding, on my ajax call with jquery something wrong happened,
i
Thanks for sharing the solution. Glad it's all working for you now.
Matt
On Tue, Jul 6, 2010 at 4:24 PM, ntortarolo ntortar...@gmail.com wrote:
I have just fixed my last error. My oauth_token wasnt in correct orden
on my base string.
Thanks!
On Jul 6, 2:19 pm, ntortarolo
In Search API ,always the created_at time is getting displayed in
UTC,So it creates more problems for me when I am trying to display
latest search results as it shows same time for a query
Whether there are any plans to display localtime of the user in search
api?
For E.g
Thanks. That would help me in listing out new followers. But if any of
a users old friends stopped following them, I wouldn't get it :(
Anyways, hoping to see a 'since' param with new and deleted ids sent.
I know you guys are pretty tied up with other important stuff, but
hope to see this someday
59 matches
Mail list logo
