[twitter-dev] Re: Geo XML Format Query

[Steve]

That's perfect, thanks Raffi!

On Jul 6, 5:49 am, Raffi Krikorian  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 and longitude, the coordinates (and
> geo) attributes will be filled.  additionally, if twitter has data for that
> area of the world, we will also immediately populate the place attribute
> with the contextual information.  it is possible that we don't have data for
> that location, at which point the place attribute will be empty.
>
> you can also geotag with a "place" -- that's a neighborhood, a city, state,
> point of interest, etc.  when somebody does that, only the "place" attribute
> is filled.
>
> take a look athttp://api.twitter.com/1/statuses/show/17536619739.xmlas
> that has all the fields populated.
>
> hope that helps!
>
>
>
> On Mon, Jul 5, 2010 at 10:56 AM, Steve <25tol...@gmail.com> wrote:
> > Hi all,
>
> > I've done a search here for this info, and looked through the docs,
> > but I can't find what I'm looking for documented anywhere.
>
> > What I'm after is a full sample of what data might appear in the  > >,  and  tags, when they're populated. At
> > present I've only seen some inner  tags, but I'm curious
> > what else may appear within these.
>
> > I'm creating a "tweet backup" type thing, and pulling out various data
> > items from the tweet to stick into SQL and analyse, and knowing what
> > data might be in here would be handy.
>
> > Thanks!
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

[twitter-dev] Geotagging broken when user is using a foreign language

[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 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
again and they can geo-tag their tweets.

ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client
#Gravity

Re: [twitter-dev] Geotagging broken when user is using a foreign language

[Daniel Schroeder]

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 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
> again and they can geo-tag their tweets.
> 
> ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client
> #Gravity

[twitter-dev] Rate Limiting

[artesea]

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 the reset has been the same since at least 8am.

[twitter-dev] Re: Rate Limiting

[Niklas Hellenbart]

I've got the same problem, according to the api response the reset
time is in the past.

On 6 Jul., 14:20, artesea  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 
> tohttp://api.twitter.com/version/account/rate_limit_status.jsoncomes
> 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 the reset has been the same since at least 8am.

Re: [twitter-dev] @mention messages appear in the timeline

[sh0w3r `uuuuuuh`]

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  > wrote:
>
> hi i want you to implement mention messages to appear in the timeline,
> wont you think that would give the idea of twitter a boost?
>
>
>
>
> -- 
> Raffi Krikorian
> Twitter Platform Team
> http://twitter.com/raffi
no im asking, as i first hear of twitter, and the idea of public "im"
messages, or timelines of life, and lifetime ... i thought i would be
better to show the @ <- "at-messages" for example "@user_ralph" said
that too, should appear in the timeline.

at the moment you have to click the userfield on the right side
@user_abc ... to search in twitter for all mention messages, cant you
implement mentions in the basic timeline, as messages from user you follow?

do you understand what i mean?

Re: [twitter-dev] Rate Limiting

[Cameron Kaiser]

> 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 the reset has been the same since at least 8am.

Confirming. This seems to have started last night.

-- 
 personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- Man who live in glass house dress in basement. -

Re: [twitter-dev] Rate Limiting

[M. Edward (Ed) Borasky]

Quoting Cameron Kaiser :


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 the reset has been the same since at least 8am.


Confirming. This seems to have started last night.


I saw something similar - erratic behavior when non-authenticated.  
Normally it says 75 calls per hour, number of calls left and a fair  
amount of time until reset. But sometimes it jumps down to one second  
left and stays there, eventually causing a hard rate limit. I haven't  
tried this morning - I can try again in about two hours.

Re: [twitter-dev] Rate Limiting

[M. Edward (Ed) Borasky]

Quoting "M. Edward (Ed) Borasky" :


Quoting Cameron Kaiser :


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 the reset has been the same since at least 8am.


Confirming. This seems to have started last night.


I saw something similar - erratic behavior when non-authenticated.
Normally it says 75 calls per hour, number of calls left and a fair
amount of time until reset. But sometimes it jumps down to one second
left and stays there, eventually causing a hard rate limit. I haven't
tried this morning - I can try again in about two hours.


Now it's solidly refusing to let me access the API:

limit: 75, remaining: 0, seconds_to_go: 1, ratio: 0.00, sleep: 1.0
Rate limit exceeded. Clients may not make more than 75 requests per hour.

This was on an unauthenticated rate limit status call in Net::Twitter  
- I'll have to do some digging to get the HTTP data but I can try that  
later (from a different IP address).

[twitter-dev] Favor api not working?

[funkyboy]

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:

  http://twitter.com/prolley/status/17866945968

Am i doing anything wrong? Or is the api not working?

[twitter-dev] Re: Rate Limiting

[artesea]

Finally have access again, with the time to reset now at 15:27 (around
an hour).

Ryan

Re: [twitter-dev] @mention messages appear in the timeline

[John Kalucki]

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. Secondly,
it would open another spam vector that would have to be addressed. We have
considered this feature on www, but I don't know whatever happened to the
idea.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.


On Tue, Jul 6, 2010 at 7:24 AM, sh0w3r `uuh`  wrote:

>  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  wrote:
>
>> hi i want you to implement mention messages to appear in the timeline,
>> wont you think that would give the idea of twitter a boost?
>>
>
>
>
> --
> Raffi Krikorian
> Twitter Platform Team
> http://twitter.com/raffi
>
> no im asking, as i first hear of twitter, and the idea of public "im"
> messages, or timelines of life, and lifetime ... i thought i would be better
> to show the @ <- "at-messages" for example "@user_ralph" said that too,
> should appear in the timeline.
>
> at the moment you have to click the userfield on the right side @user_abc
> ... to search in twitter for all mention messages, cant you implement
> mentions in the basic timeline, as messages from user you follow?
>
> do you understand what i mean?
>

[twitter-dev] Re: Previous_Cursor Not Working

[Ron]

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  wrote:
> This is still not working.  Previous_Cursor_Str for current page less
> than 4 returns an empty object on either Followers or Friends API
> calls.  Nothing showing up on Twitter Status about this.  Does anyone
> at Twitter care to comment?
>
> On Jul 5, 6:38 am, CWorster  wrote:
>
>
>
> > Same problem here. I'm using "previous_cursor_str" and "next_cursor_str".
>
> > "previous_cursor_str" stopped working.
>
> > "next_cursor_str" works as expected.
>
> > 2010/7/5 Ron :
>
> > > Anyone else seeing a problem on Followers or Friends with
> > > Previous_Cursor not working (returning a blank response)?

Re: [twitter-dev] Friend and Follower count - since timestamp

[Raffi Krikorian]

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

> My app http://justunfollow.com extensively uses the friends/ids and
> followers/ids API. Since twitter users have a lot of followers and
> friends and this API is paginated, I find it repetitive to use it.
>
> A "since" param that sends me all new friend and follower ids of a
> user along with the deleted ids (when someone stops being a friend or
> follower) would help a lot. I checked the documentation but found no
> mention of this. Please help!
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] Geotagging broken when user is using a foreign language

[Raffi Krikorian]

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

> 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 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
> > again and they can geo-tag their tweets.
> >
> > ole @ mobileways.de / @janole on Twitter / Symbian S60 Twitter client
> > #Gravity
>
>


-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] @mention messages appear in the timeline

[Raffi Krikorian]

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
together, how do you make sure to deal with that mismatch.  how would you
juggle the two since IDs that you may want to work with either?  one idea
could be to let clients use the home timeline and mentions timeline
separately to "catch up" with real time, and then get them both from there
on out...

On Tue, Jul 6, 2010 at 6:47 AM, 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. So, it would have to be an option. Secondly,
> it would open another spam vector that would have to be addressed. We have
> considered this feature on www, but I don't know whatever happened to the
> idea.
>
> -John Kalucki
> http://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
>
>
> On Tue, Jul 6, 2010 at 7:24 AM, sh0w3r `uuh`  wrote:
>
>>  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  wrote:
>>
>>> hi i want you to implement mention messages to appear in the timeline,
>>> wont you think that would give the idea of twitter a boost?
>>>
>>
>>
>>
>> --
>> Raffi Krikorian
>> Twitter Platform Team
>> http://twitter.com/raffi
>>
>> no im asking, as i first hear of twitter, and the idea of public "im"
>> messages, or timelines of life, and lifetime ... i thought i would be better
>> to show the @ <- "at-messages" for example "@user_ralph" said that too,
>> should appear in the timeline.
>>
>> at the moment you have to click the userfield on the right side @user_abc
>> ... to search in twitter for all mention messages, cant you implement
>> mentions in the basic timeline, as messages from user you follow?
>>
>> do you understand what i mean?
>>
>
>


-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] Re: Rate Limiting

[M. Edward (Ed) Borasky]

Quoting artesea :


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.

Re: [twitter-dev] "Failed to validate oauth signature and token" using ColdFusion8

[Raffi Krikorian]

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 through.  however, i would
*strongly* recommend using a library if possible.  a simple google search
turned up http://oauth.riaforge.org/.

On Mon, Jul 5, 2010 at 10:42 AM, Carlos Villarreal Mora wrote:

> Hello I've been trying to solve this since Friday to no avail. I've
> searched and used tips from a bunch of other discussions here but I
> still haven't gotten it right.
>
> I'm using ColdFusion 8 to generate my OAuth signature. These are the
> tweaks I've done from tips in this discussion list:
> 1) For the timestamp I convert to UTC time with this function:
>var nowUTC = dateConvert('local2UTC', now());
>var epochStart = CreateDateTime('1970','1','1','00','00','00');
>var timestamp = dateDiff("s", epochStart, nowUTC);
>
>This results in these values:
>nowUTC = {ts '2010-07-05 17:22:30'}
>epochStart = {ts '1970-01-01 00:00:00'}
>timestamp = 1278346950
>
> 2) For the Nonce I use ColdFusion's createUUID function and then,
> based on this (http://www.cflib.org/udf/CreateGUID) from CFLib.org I
> convert that UUID into a GUID like so:
>var uuid = createUUID();
>//Convert the UUID to a GUID by inserting a dash in the 23rd
> position
>var nonce = insert("-", uuid, 23);
>
>This is an example of a resulting nonce:
>A3A1648E-F1F0-4032-75F4-712F676BE7E6
>
> 3) The most difficult part, and where I'm sure the error is, is the
> SHA1 hashing, ColdFusion sucks at it so I'm using Java in the
> function:
> output="false">
> required="true" />
> />
>
>var jMsg =
> javaCast("string",arguments.signMessage).getBytes("UTF8");
>var jKey =
> javaCast("string",arguments.signKey).getBytes("UTF8");
>var key  =
> createObject("java","javax.crypto.spec.SecretKeySpec");
>var mac  = createObject("java","javax.crypto.Mac");
>var ret  = "";
>
>key = key.init(jKey,"HmacSHA1");
>mac = mac.getInstance(key.getAlgorithm());
>mac.init(key);
>mac.update(jMsg);
>
>ret = lCase(binaryEncode(mac.doFinal(), 'Hex'));
>
>return(ret);
>
>
>
> When I sign the base using my Consumer Secret appended by a "&" using
> this function the result is something like this:
> 01eb730a110b1e09ccc9bbff9dbca73c5047f4d4
>
> Here's the Signature Base and the Header I create (my consumer key is
> masked for security reasons):
> - Signature Base:
> POST&https%3A%2F%2Fapi%2Etwitter%2Ecom%2Foauth%2Frequest
> %5Ftoken&oauth_callback%3Dhttp%3A%2F%2Fcommunitydev%2Epaperthin%2Ecom
> %2FTwitter%2FoAuth%2Ecfm%26oauth_consumer_key%3D
> %26oauth_nonce%3DA394B8B8-
> F1F0-4032-72C8-701CEC482A20%26oauth_signature_method%3DHMAC-
> SHA1%26oauth_timestamp%3D1278328119
>
> - OAuht Authorization Header:
> OAuth oauth_nonce="A394B8B8-F1F0-4032-72C8-701CEC482A20",
> oauth_callback="http%3A%2F%2Fcommunitydev%2Epaperthin%2Ecom%2FTwitter
> %2FoAuth%2Ecfm", oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1278328119", oauth_consumer_key="xxx",
> oauth_signature="4799dd5a6891474d603a3546c14e9b41ea47088d",
> oauth_version="1.0"
>
> There are no line breaks in either of them btw. Can anybody help me
> with this? Try as I might I haven't been able to get beyond the
> "Failed to validate oauth signature and token" response.
>
> Thank you.
>



-- 
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

Re: [twitter-dev] Favor api not working?

[CWorster]

Hi,

>  https://api.twitter.com/1/favorites/17866945968/create.json

post this url : https://api.twitter.com/1/favorites/create/17866945968.json

[twitter-dev] Re: Rate Limiting

[Jeff Randall]

On Jul 6, 9:23 am, "M. Edward (Ed) Borasky"  wrote:
> Quoting artesea :
>
> > 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. The status keeps reporting 0
remaining, yet I'm well past the reset time. When I try on another IP
address, using the same authentication, I get 75 remaining. I don't
understand how my IP address could have gotten blocked. My application
does not attempt any further access to the API once the rate limit has
been reached.

[twitter-dev] Search API rate limit

[Ramanean]

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 from the IP address of the website?

I am little bit confused here...

Thanks
Shan

[twitter-dev] request token

[Jacky]

Hullo,

POST&https%3A%2F%2Fapi.twitter.com%2Foauth
%2Frequest_token&oauth_callback%3Doob%26oauth_consumer_key
%3DhUMUUZO3Zx9zNzJ9DghcA%26oauth_nonce
%3DDA39A3EE5E6B4B0D3255BFEF95601890AFD80709%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1277424969%26oauth_version%3D1.0


and

Oauth oauth_callback="oob",
oauth_consumer_key="hUMUUZO3Zx9zNzJ9DghcA",
oauth_nonce="DA39A3EE5E6B4B0D3255BFEF95601890AFD80709",
oauth_signature_method="HMAC-SHA1", oauth_timestamp="1277424969",
oauth_version="1.0", oauth_signature="%2Ff8P1dS6QVQnYCIc10kD1%2Bm2DkI
%3D"

using

 objhttp.Open "POST", "https://api.twitter.com/oauth/request_token";,
False

 objhttp.setRequestHeader "Content-type", "application/x-www-form-
urlencoded"
  objhttp.setRequestHeader "Authorization", strsend
objhttp.send("")

Not working, how can I see the stream that is being loaded...or debug
this...
and strsend is "Oauth " and appended by the very first string up on
top in this email

Cant see the problem...

Please help, if you can see anything outright off or wrong...

Regards,
Shob

Re: [twitter-dev] @mention messages appear in the timeline

[sh0w3r `uuuuuuh`]

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. So, it would have to be an option.
> Secondly, it would open another spam vector that would have to be
> addressed. We have considered this feature on www, but I don't know
> whatever happened to the idea.
>
> -John Kalucki
> http://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
>
>
> On Tue, Jul 6, 2010 at 7:24 AM, sh0w3r `uuh`  > wrote:
>
> 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 > > wrote:
>>
>> hi i want you to implement mention messages to appear in the
>> timeline,
>> wont you think that would give the idea of twitter a boost?
>>
>>
>>
>>
>> -- 
>> Raffi Krikorian
>> Twitter Platform Team
>> http://twitter.com/raffi
> no im asking, as i first hear of twitter, and the idea of public
> "im" messages, or timelines of life, and lifetime ... i thought i
> would be better to show the @ <- "at-messages" for example
> "@user_ralph" said that too, should appear in the timeline.
>
> at the moment you have to click the userfield on the right side
> @user_abc ... to search in twitter for all mention messages, cant
> you implement mentions in the basic timeline, as messages from
> user you follow?
>
> do you understand what i mean?
>
>
i would appreciate you to implement that feature maybe in the future, as
spam or... maybe to many @mention messages would waste the timeline, but
the appear in you site anywise, as you effort to read all mention
messages that are directed to you ...

ok, thank you

Re: [twitter-dev] Re: Rate Limiting

[John Kalucki]

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

> On Jul 6, 9:23 am, "M. Edward (Ed) Borasky"  research.net> wrote:
> > Quoting artesea :
> >
> > > 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. The status keeps reporting 0
> remaining, yet I'm well past the reset time. When I try on another IP
> address, using the same authentication, I get 75 remaining. I don't
> understand how my IP address could have gotten blocked. My application
> does not attempt any further access to the API once the rate limit has
> been reached.
>

[twitter-dev] XML feed not loading as before - PHP

[colin....@digital.fco.gov.uk]

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

Initally it had been working with "simplexml_load_file" but now
everything has stopped.  It is working on my local environment, but as
soon as the file is tested on the server, nothing is working.

I have tested this with different XMLs and they're fine.

The error showing is:

Fatal error: Uncaught exception 'Exception' with message 'String could
not be parsed as XML' in /home/bhammers/demophon/dashboard/test.php:5
Stack trace: #0 /home/bhammers/demophon/dashboard/test.php(5):
SimpleXMLElement->__construct('') #1 {main} thrown in /home/bhammers/
demophon/dashboard/test.php on line 5

I have google this and it seems suggest this is a twitter error?

Thanks in advance

[twitter-dev] lockouts are the new black

[Isaiah Carew]

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 is to improve the latency and failures (i.e. "whales") 
that you guys were seeing during the world cup.  But creating lockouts to 
reduce failures is cutting off your nose to spite your face.

Failures, lagging, and latency are frustrating but at least *feel* egalitarian. 
 Service disruption is nothing new -- we understand it whether it's AT&T, 
temporary power failures, or whatever.  

Lockouts feel punitive and targeted.  Users really really don't like it.

I think it's safe to say that this is now *the* critical issue.  All other 
twitter concerns seem dwarfed by this massive problem.

isaiah
http://twitter.com/isaiah

Re: [twitter-dev] lockouts are the new black

[John Kalucki]

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
issue. There's absolutely no intention to lock people out.

-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.



On Tue, Jul 6, 2010 at 9:00 AM, Isaiah Carew  wrote:

>
> 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 is to improve the latency and failures (i.e. "whales")
> that you guys were seeing during the world cup.  But creating lockouts to
> reduce failures is cutting off your nose to spite your face.
>
> Failures, lagging, and latency are frustrating but at least *feel*
> egalitarian.  Service disruption is nothing new -- we understand it whether
> it's AT&T, temporary power failures, or whatever.
>
> *Lockouts feel punitive and targeted.  Users really really don't like it.*
>
> I think it's safe to say that this is now *the* critical issue.  All other
> twitter concerns seem dwarfed by this massive problem.
>
> isaiah
> http://twitter.com/isaiah
>
>

[twitter-dev] Re: Invalid timescale error on location trends

[Heidi Hysell]

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 throws the error I
mentioned.

The urls you provided did work, but I think in this instance the
documentation needs to be updated to reflect the correct url format.

Let me know if I'm wrong reading the documentation incorrectly.

Thanks,
Heidi

On Jul 6, 1:04 am, Raffi Krikorian  wrote:
> hey heidi.
>
> can you provide more information?  i just tried the following few things:
>
> http://api.twitter.com/1/trends/2487956.xml(trends in 
> SF)http://api.twitter.com/1/trends/2487956/current.xml(same as 
> above)http://api.twitter.com/1/trends/2487956/hourly.xml(hourly version of 
> trends
> from SF)http://api.twitter.com/1/trends/2487956/daily.xml(the day's trends 
> from SF)
>
> and those worked.  what's the exact call you're trying?
>
>
>
> On Mon, Jul 5, 2010 at 2:35 PM, Heidi Hysell  wrote:
> > I'm trying to use the trends/location/woeid functionality (http://
> > dev.twitter.com/doc/get/trends/location/:woeid) and keep on getting
> > the following error:
> > code: 31 message: "Invalid timescale: must be 'current', 'hourly', or
> > 'daily'"
>
> > The documentation doesn't specify anything about sending in a
> > timescale. I try and send in the "timescale=current" as a parameter,
> > however it still gives me the same error.
> > I've tried using different woeid's and they all result in the same
> > error.
> > Using the twitter provided console also yields the same error (http://
> > dev.twitter.com/console).
>
> > Any insight is appreciated.
>
> > Thanks,
> > Heidi
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] lockouts are the new black

[Pascal Jürgens]

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 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 
> issue. There's absolutely no intention to lock people out.
> 
> -John Kalucki
> http://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
> 

Re: [twitter-dev] XML feed not loading as before - PHP

[Taylor Singletary]

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 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 returned.
>
> Initally it had been working with "simplexml_load_file" but now
> everything has stopped.  It is working on my local environment, but as
> soon as the file is tested on the server, nothing is working.
>
> I have tested this with different XMLs and they're fine.
>
> The error showing is:
>
> Fatal error: Uncaught exception 'Exception' with message 'String could
> not be parsed as XML' in /home/bhammers/demophon/dashboard/test.php:5
> Stack trace: #0 /home/bhammers/demophon/dashboard/test.php(5):
> SimpleXMLElement->__construct('') #1 {main} thrown in /home/bhammers/
> demophon/dashboard/test.php on line 5
>
> I have google this and it seems suggest this is a twitter error?
>
> Thanks in advance
>
>

Re: [twitter-dev] lockouts are the new black

[Isaiah Carew]

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 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 
> issue. There's absolutely no intention to lock people out.
> 
> -John Kalucki
> http://twitter.com/jkalucki
> Infrastructure, Twitter Inc.
> 
> 
> 
> On Tue, Jul 6, 2010 at 9:00 AM, Isaiah Carew  wrote:
> 
> 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 is to improve the latency and failures (i.e. "whales") 
> that you guys were seeing during the world cup.  But creating lockouts to 
> reduce failures is cutting off your nose to spite your face.
> 
> Failures, lagging, and latency are frustrating but at least *feel* 
> egalitarian.  Service disruption is nothing new -- we understand it whether 
> it's AT&T, temporary power failures, or whatever.  
> 
> Lockouts feel punitive and targeted.  Users really really don't like it.
> 
> I think it's safe to say that this is now *the* critical issue.  All other 
> twitter concerns seem dwarfed by this massive problem.
> 
> isaiah
> http://twitter.com/isaiah
> 
> 

[twitter-dev] problem with statuses/destroy

[Claudia A. V. Callegari]

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 me a light?


Thanks
Claudia A. V. Callegari
Brazil

In portuguese

Ola !
Estou usando a api statuses/destroy  com  oauth  para excluir
mensagens.
Retorna  http = 200 , vejo que diminui a quantidade de tweets que
mostra no perfil da conta. Porém  a mensagem  continua la  e não é
excluida.
Tem algum problema com essa api  ou será que falta algum procedimento.
Podem me dar uma luz ?


Obrigada
Claudia A. V. Callegari
Brasil

[twitter-dev] Re: Rate Limiting

[Johnson]

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  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 
> tohttp://api.twitter.com/version/account/rate_limit_status.jsoncomes
> 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 the reset has been the same since at least 8am.

Re: [twitter-dev] Re: Rate Limiting

[Pascal Jürgens]

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 thru, some don't.

[twitter-dev] Re: Failed to validate oauth signature and token with xauth

[ntortarolo]

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 having there the consumer secret but i dont have
another way to do it.
I get access token right, but now i have another problem, i dont know
exactly what parameters i must add for a call, for example calling
friends timeline, i have seen tutorials about xauth but i get this
response "could not authenticate with oauth".
Sorry of my english.

Thanks, Nadia

On Jun 24, 5:58 pm, Taylor Singletary 
wrote:
> Hi there,
>
> Are you still having this issue?
>
> In the past when I've seen other developers having issues accomplishing this
> in Javascript, it's come down to an issue in the library used for HMAC-SHA1
> and Base64 encoding. While it works in most conditions, there are apparently
> some edge cases where it does the wrong thing. I generally don't advocate
> using Javascript and OAuth together for a variety of reasons. Have you tried
> tracing the request to see exactly the HTTP request being sent to the
> server?
>
> Are you writing a browser extension or WebOS app? If the former, how are you
> keeping your consumer secret at least somewhat secured?
>
> Have you tried other requests using an access token obtained through other
> means?
>
> Taylor
>
> On Thu, Jun 17, 2010 at 11:25 AM, ntortarolo  wrote:
> > Hi, i have problem requesting an access_token, i think my source is
> > right, i dont know where is the problem, i have maken some test with
> > base_string,  oauth_consumer_key and oauth_consumer_secret shown on
> >http://dev.twitter.com/pages/xauthand i get the same oauth_signature
> > shown there so i think problem is not there when i use the real
> > base_string, my oauth_consumer_key and oauth_consumer_secret.
> >        My source is this, i hope someone can help me (to preserve my secret
> > and key i will put the same as the ones used on
> >http://dev.twitter.com/pages/xauth)
>
> >        xauth: function xauth()
> >        {
>
> >         var username = encodeURIComponent(""),
> >             password = encodeURIComponent(""),
> >             url= "https://api.twitter.com/oauth/access_token";,
> >             key = "sGNxxnqgZRHUt6NunK3uw",
> >             timestamp = (new Date()).getTime(),
> >             nonce = Math.random();
>
> >        var access_token = "oauth_consumer_key=" + key +
> >        "&oauth_nonce=" + nonce +
> >        "&oauth_signature_method=HMAC-SHA1" +
> >        "&oauth_timestamp=" + timestamp +
> >        "&oauth_version=1.0" +
> >        "&x_auth_mode=client_auth" +
> >        "&x_auth_password=" + password +
> >        "&x_auth_username=" + username;
>
> >        var base_string = "POST&" + encodeURIComponent(url) + "&" +
> > encodeURIComponent(access_token);
>
> >        var oauth_signature =
> > b64_hmac_sha1("5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&",
> > base_string);
>
> >        oauth_signature = encodeURIComponent(oauth_signature+"=");
>
> >        var auth_header = 'OAuth oauth_nonce="' + nonce + '"' +
> >        ', oauth_signature_method="HMAC-SHA1"' +
> >        ', oauth_timestamp="' + timestamp + '"' +
> >        ', oauth_consumer_key="' + key + '"' +
> >        ', oauth_signature="' + oauth_signature + '"' +
> >        ', oauth_version="1.0"';
>
> >        $.ajax({
> >             url:url,
> >             method: "POST",
> >             data: {
> >                     x_auth_username: username,
> >                     x_auth_password: password,
> >                     x_auth_mode: "client_auth"
> >             },
> >             beforeSend: function(xhr){
> >                     xhr.setRequestHeader("Authorization", auth_header);
> >             },
> >             success: function(data){
> >                     alert(data);
> >             },
> >             error: function(xhr){
> >                     alert(xhr.responseText);
> >             }
> >        }) ;
>
> >        * What language or library are you using? What versions?
> >          i'm using it on javascript
>
> >        * What oauth application is this for?
> >        http://twitter.com/apps/edit/181924
>
>

[twitter-dev] Rate limit exceeded. Clients may not make more than 75 requests per hour.

[goodtest]

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.

Re: [twitter-dev] Rate limit exceeded. Clients may not make more than 75 requests per hour.

[M. Edward (Ed) Borasky]

Quoting goodtest :


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 am also seeing tweets from friends that Tweetdeck is running into  
problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?

[twitter-dev] Re: Rate Limiting

[Johnson]

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 twurl, it works.
I tried on mobile, Echolfon, failed, but twitbird goes thru.
Obviously the web works!
What other experiments do u want me to run?
Are twitter giving favor on specific accounts?

On Jul 6, 9:57 am, Pascal Jürgens
 wrote:
> 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 thru, some don't.

[twitter-dev] Re: "Failed to validate oauth signature and token" using ColdFusion8

[Carlos Villarreal Mora]

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  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 do the oauth
> signature, please 
> consulthttp://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
> its a great interactive walk through.  however, i would
> *strongly* recommend using a library if possible.  a simple google search
> turned uphttp://oauth.riaforge.org/.
>
> On Mon, Jul 5, 2010 at 10:42 AM, Carlos Villarreal Mora 
> wrote:
>
>
>
> > Hello I've been trying to solve this since Friday to no avail. I've
> > searched and used tips from a bunch of other discussions here but I
> > still haven't gotten it right.
>
> > I'm using ColdFusion 8 to generate my OAuth signature. These are the
> > tweaks I've done from tips in this discussion list:
> > 1) For the timestamp I convert to UTC time with this function:
> >        var nowUTC = dateConvert('local2UTC', now());
> >        var epochStart = CreateDateTime('1970','1','1','00','00','00');
> >        var timestamp = dateDiff("s", epochStart, nowUTC);
>
> >        This results in these values:
> >        nowUTC = {ts '2010-07-05 17:22:30'}
> >        epochStart = {ts '1970-01-01 00:00:00'}
> >        timestamp = 1278346950
>
> > 2) For the Nonce I use ColdFusion's createUUID function and then,
> > based on this (http://www.cflib.org/udf/CreateGUID) from CFLib.org I
> > convert that UUID into a GUID like so:
> >        var uuid = createUUID();
> >        //Convert the UUID to a GUID by inserting a dash in the 23rd
> > position
> >        var nonce = insert("-", uuid, 23);
>
> >        This is an example of a resulting nonce:
> >        A3A1648E-F1F0-4032-75F4-712F676BE7E6
>
> > 3) The most difficult part, and where I'm sure the error is, is the
> > SHA1 hashing, ColdFusion sucks at it so I'm using Java in the
> > function:
> >         > output="false">
> >                 > required="true" />
> >                 > />
> >                
> >                        var jMsg =
> > javaCast("string",arguments.signMessage).getBytes("UTF8");
> >                        var jKey =
> > javaCast("string",arguments.signKey).getBytes("UTF8");
> >                        var key  =
> > createObject("java","javax.crypto.spec.SecretKeySpec");
> >                        var mac  = createObject("java","javax.crypto.Mac");
> >                        var ret  = "";
>
> >                        key = key.init(jKey,"HmacSHA1");
> >                        mac = mac.getInstance(key.getAlgorithm());
> >                        mac.init(key);
> >                        mac.update(jMsg);
>
> >                        ret = lCase(binaryEncode(mac.doFinal(), 'Hex'));
>
> >                        return(ret);
> >                
> >        
>
> > When I sign the base using my Consumer Secret appended by a "&" using
> > this function the result is something like this:
> > 01eb730a110b1e09ccc9bbff9dbca73c5047f4d4
>
> > Here's the Signature Base and the Header I create (my consumer key is
> > masked for security reasons):
> > - Signature Base:
> > POST&https%3A%2F%2Fapi%2Etwitter%2Ecom%2Foauth%2Frequest
> > %5Ftoken&oauth_callback%3Dhttp%3A%2F%2Fcommunitydev%2Epaperthin%2Ecom
> > %2FTwitter%2FoAuth%2Ecfm%26oauth_consumer_key%3D
> > %26oauth_nonce%3DA394B8B8-
> > F1F0-4032-72C8-701CEC482A20%26oauth_signature_method%3DHMAC-
> > SHA1%26oauth_timestamp%3D1278328119
>
> > - OAuht Authorization Header:
> > OAuth oauth_nonce="A394B8B8-F1F0-4032-72C8-701CEC482A20",
> > oauth_callback="http%3A%2F%2Fcommunitydev%2Epaperthin%2Ecom%2FTwitter
> > %2FoAuth%2Ecfm", oauth_signature_method="HMAC-SHA1",
> > oauth_timestamp="1278328119", oauth_consumer_key="xxx",
> > oauth_signature="4799dd5a6891474d603a3546c14e9b41ea47088d",
> > oauth_version="1.0"
>
> > There are no line breaks in either of them btw. Can anybody help me
> > with this? Try as I might I haven't been able to get beyond the
> > "Failed to validate oauth signature and token" response.
>
> > Thank you.
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] US Location Stream

[James Kim]

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  
wrote:
> Hello James,
>
> may be you would be interested in looking at our API which provides
> language and location filtering on tweets.
>
> More specifically, you'll find an example for filtering tweets based
> on location and on language under "Example: filtering by language and
> location", located at the URL
> http://developer.semiocast.com/tutorial/twitter
>
>
> Do not hesitate to visit our API website: http://developer.semiocast.com
> or ask for more information.
>
>
> Hope you'll find this useful.
>
> Best regards,
> Jean-Charles Campagne
> Semiocast
>
> On Sat, Jul 3, 2010 at 1:26 AM, James Kim  wrote:
>>
>> Hi John,
>>
>> Thanks for the quick reply. Is there a way to exclude non-english
>> tweets from the stream like the search api does?
>>
>>
>> On Fri, Jul 2, 2010 at 4:03 PM, John Kalucki  wrote:
>> > Hi James,
>> > Nope. Even if we allowed all the bounding boxes to cover the US, you'd only
>> > get the tweets that are geo-tagged, which isn't a large proportion.
>> > -John
>> >
>> >
>> > On Fri, Jul 2, 2010 at 3:55 PM, James Kim  wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I'm trying to capture all the tweets originating from the US. Is there
>> >> a simple way to do this without creating many bounding boxes?
>> >
>> >
>>
>>
>>
>> --
>> James C. Kim @jamesckim
>> http://keytweet.com - a learning filter for twitter
>



-- 
James C. Kim @jamesckim
http://keytweet.com - a learning filter for twitter

Re: [twitter-dev] Search API rate limit

[Matt Harris]

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 handled by the default filter limits
available through the streaming API.

Best,
Matt

On Tue, Jul 6, 2010 at 7:31 AM, Ramanean  wrote:

> 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 from the IP address of the website?
>
> I am little bit confused here...
>
> Thanks
> Shan
>
>
>


-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Which one are you using in your mobile app? xAuth or oAuth?

[Oscar Cortes]

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

Re: [twitter-dev] Re: Previous_Cursor Not Working

[Matt Harris]

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 investigating ways to fix it.

Matt

On Tue, Jul 6, 2010 at 7:03 AM, Ron  wrote:

> 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  wrote:
> > This is still not working.  Previous_Cursor_Str for current page less
> > than 4 returns an empty object on either Followers or Friends API
> > calls.  Nothing showing up on Twitter Status about this.  Does anyone
> > at Twitter care to comment?
> >
> > On Jul 5, 6:38 am, CWorster  wrote:
> >
> >
> >
> > > Same problem here. I'm using "previous_cursor_str" and
> "next_cursor_str".
> >
> > > "previous_cursor_str" stopped working.
> >
> > > "next_cursor_str" works as expected.
> >
> > > 2010/7/5 Ron :
> >
> > > > Anyone else seeing a problem on Followers or Friends with
> > > > Previous_Cursor not working (returning a blank response)?
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Can't execute an API call after successful authentication (Flash/AS3)

[Federico Campo Piombi]

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 from subsequent calls to
the api.
This is the response I get from the "home_timeline" method:

oauth_nonce=DD48F2A4-665E-B684-F407-
A99446876D8D&oauth_consumer_key=1CyFSBYA5tXIZ6TH3PlWTg&oauth_version=1.0&oauth_timestamp=1278450353&oauth_signature_method=HMAC-
SHA1&oauth_signature=2of4596/fO7VfcCHUcX7JoKPYb0=
Error opening URL 'http://api.twitter.com/1/statuses/
home_timeline.json'
Error #2044: unhandled ioError : text=Error #2032: Sequence Error.
URL: http://api.twitter.com/1/statuses/home_timeline.json

Any ideas? That error keeps coming up.
I'm using the "soenkerohde" Twitter+oAuth as3 library to perform
authentication.

I've tried sending the oAuth data both as Querystring as well as in
the "Authentication" header.. nothing happens.

If you need more code to help you out let me know.
Thanks a lot in advance!!

Re: [twitter-dev] Re: Rate Limiting

[Matt Harris]

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

> 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 twurl, it works.
> I tried on mobile, Echolfon, failed, but twitbird goes thru.
> Obviously the web works!
> What other experiments do u want me to run?
> Are twitter giving favor on specific accounts?
>
> On Jul 6, 9:57 am, Pascal Jürgens
>  wrote:
> > 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 thru, some don't.
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Re: [twitter-dev] unable to get the previous trend...

[Matt Harris]

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

Matt

On Sun, Jul 4, 2010 at 10:45 AM, awahid  wrote:

> I am trying to fetch the weekly trends of previous dates.
>
> making a curl call
> http://search.twitter.com/trends/daily.json?date=2010-06-03
> http://search.twitter.com/trends/weekly.json?date=2010-06-03
>
> and empty in trend result ...
>
> Am I not able to fetch the previous trends???
> Is there any possibility to get the trends of previous days?
>
> please enlighten me.
>
> Thanks
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Re: Rate Limiting

[Rich]

Yep I'm now locked out of my own account with this issue

On Jul 6, 10:38 pm, Matt Harris  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
>
>
>
>
>
> On Tue, Jul 6, 2010 at 10:10 AM, Johnson  wrote:
> > 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 twurl, it works.
> > I tried on mobile, Echolfon, failed, but twitbird goes thru.
> > Obviously the web works!
> > What other experiments do u want me to run?
> > Are twitter giving favor on specific accounts?
>
> > On Jul 6, 9:57 am, Pascal Jürgens
> >  wrote:
> > > 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 thru, some don't.
>
> --
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris

Re: [twitter-dev] Can't get geotagging to work.

[Matt Harris]

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

> Hi guys,
>
> I'm having problems with submitting my geo-location with a status.
>
> I'm using the twitteroauth (PHP, by abraham on github) which works
> pretty fine. My call looks like this
>
>
> $parameters = array(
>'status'=> 'This is a call',
>'lat'   => "37.78",
>'long'  => "-122.40",
>'display_coordinates'   => 1,
> );
> $status = $connection->post('statuses/update', $parameters);
>
> The status is being submitted, though the result doesn't contain any
> geodata.
>
> It looks like this:
>
> Object
> (
>[coordinates] =>
>[in_reply_to_screen_name] =>
>[truncated] =>
>[source] => My Test App
>[created_at] => Mon Jul 05 14:51:37 + 2010
>[geo] =>
>[in_reply_to_status_id] =>
>[contributors] =>
>[user] => stdClass Object
>(
>[favourites_count] => 0
>[description] =>
>[location] => Berlin
>[verified] =>
>[profile_text_color] => 00
>[time_zone] => Greenland
>[profile_link_color] => ff
>[lang] => de
>[profile_background_image_url] =>
> http://s.twimg.com/a/1278188204/images/themes/theme1/bg.png
>[created_at] => Tue May 11 13:36:19 + 2010
>[profile_sidebar_fill_color] => e0ff92
>[notifications] =>
>[profile_background_tile] =>
>[profile_image_url] =>
> http://s.twimg.com/a/1278188204/images/default_profile_3_normal.png
>[statuses_count] => 20
>[following] =>
>[profile_sidebar_border_color] => 87bc44
>[protected] =>
>[profile_use_background_image] => 1
>[followers_count] => 0
>[screen_name] => MyTestAccount
>[name] => Well this is a Test
>[contributors_enabled] =>
>[friends_count] => 0
>[url] =>
>[id] => 1234567890
>[geo_enabled] => 1
>[utc_offset] => -10800
>[profile_background_color] => fff
>)
>
>[in_reply_to_user_id] =>
>[place] =>
>[favorited] =>
>[id] => 1234567890
>[text] => This is a call
> )
>
> As you can see "geo_enabled" is true, coordinates and geo are empty.
> So my lat and long parameters are ignored.
>
> Also with a place_id it doesn't work.
>
> This is definitely not a problem with twitteroauth.
>
> I tested with the old API, which is still available.
>
> curl -u {USER}:{PASSWORD} -d "status=This is a
> call&lat=51.52362&long=12.38064"
> https://api.twitter.com/1/statuses/update.xml
>
> Which results in the same result. This exact same call worked back on
> may 11th, when I took my first steps with the Twitter API.
>
> Can anyone pls point me in the right direction? Is this working at all
> at the moment or is it just disabled?
>
> Kind regards,
> Daniel
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Re: Rate limit exceeded. Clients may not make more than 75 requests per hour.

[Bruno Renié]

On Jul 6, 6:47 pm, "M. Edward (Ed) Borasky"  wrote:
> Quoting goodtest :
>
> > 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 am also seeing tweets from friends that Tweetdeck is running into  
> problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?

I had that problem too. I was using OAuth with old-style URLs, such
as:

https://twitter.com/direct_messages.json

instead of:

https://api.twitter.com/1/direct_messages.json

The former started to gave me "Rate limit exceeded, don't do more that
75 req/hour" all the time (even after waiting for the reset time) and
switching to the latter works as expected: the rate limit is 175
requests per hour and the countdown actually works.

So, if you're getting rate limit errors and you're using OAuth, make
sure you're using the URLs documented on http://dev.twitter.com/doc,
especially if your app is a bit old.

Hope that helps,
Bruno

Re: [twitter-dev] Farsi Twitter App

[Lucas Vickers]

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  
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 part.
> We provide an API for language and location filtering for
> micro-messages (Tweets and Facebook messages, etc.).
>
> You'll find more info on the API website: http://developer.semiocast.com
>
> Regarding the feature you are looking for, we made a request to
> Twitter to be able to redistribute a "filtered API", so we will be
> able to provide something closer to what you are looking for. You can,
> more or less, achieve the same today with our current state of the API
> but it'll be more plumbing on your side.
>
>
> Best regards,
> Jean-Charles Campagne
> Semiocast
>
> On Sat, Jul 3, 2010 at 12:36 AM, Lucas Vickers  wrote:
>> Hello,
>>
>> I am trying to create an app that will show tweets and trends in
>> Farsi, for native speakers.  I would like to somehow get a sample
>> 'garden hose' of Farsi based tweets, but I am unable to come up with
>> an elegant solution.
>>
>

Re: [twitter-dev] problem with statuses/destroy

[Matt Harris]

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.
> 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 me a light?
>
>
> Thanks
> Claudia A. V. Callegari
> Brazil
>
> In portuguese
>
> Ola !
> Estou usando a api statuses/destroy  com  oauth  para excluir
> mensagens.
> Retorna  http = 200 , vejo que diminui a quantidade de tweets que
> mostra no perfil da conta. Porém  a mensagem  continua la  e não é
> excluida.
> Tem algum problema com essa api  ou será que falta algum procedimento.
> Podem me dar uma luz ?
>
>
> Obrigada
> Claudia A. V. Callegari
> Brasil
>
>
>


-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Re: Which one are you using in your mobile app? xAuth or oAuth?

[Rich]

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

[twitter-dev] Re: Rate limit exceeded. Clients may not make more than 75 requests per hour.

[Rich]

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é  wrote:
> On Jul 6, 6:47 pm, "M. Edward (Ed) Borasky" 
> research.net> wrote:
> > Quoting goodtest :
>
> > > 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 am also seeing tweets from friends that Tweetdeck is running into  
> > problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?
>
> I had that problem too. I was using OAuth with old-style URLs, such
> as:
>
> https://twitter.com/direct_messages.json
>
> instead of:
>
> https://api.twitter.com/1/direct_messages.json
>
> The former started to gave me "Rate limit exceeded, don't do more that
> 75 req/hour" all the time (even after waiting for the reset time) and
> switching to the latter works as expected: the rate limit is 175
> requests per hour and the countdown actually works.
>
> So, if you're getting rate limit errors and you're using OAuth, make
> sure you're using the URLs documented onhttp://dev.twitter.com/doc,
> especially if your app is a bit old.
>
> Hope that helps,
> Bruno

Re: [twitter-dev] Re: Rate limit exceeded. Clients may not make more than 75 requests per hour.

[Matt Harris]

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

>
> 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é  wrote:
> > On Jul 6, 6:47 pm, "M. Edward (Ed) Borasky"  >
> > research.net> wrote:
> > > Quoting goodtest :
> >
> > > > 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 am also seeing tweets from friends that Tweetdeck is running into
> > > problems. I don't have Tweetdeck, so I can't confirm it. Perfect storm?
> >
> > I had that problem too. I was using OAuth with old-style URLs, such
> > as:
> >
> > https://twitter.com/direct_messages.json
> >
> > instead of:
> >
> > https://api.twitter.com/1/direct_messages.json
> >
> > The former started to gave me "Rate limit exceeded, don't do more that
> > 75 req/hour" all the time (even after waiting for the reset time) and
> > switching to the latter works as expected: the rate limit is 175
> > requests per hour and the countdown actually works.
> >
> > So, if you're getting rate limit errors and you're using OAuth, make
> > sure you're using the URLs documented onhttp://dev.twitter.com/doc,
> > especially if your app is a bit old.
> >
> > Hope that helps,
> > Bruno
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Re: [twitter-dev] why i can not connect to api.twitter.com??

[Matt Harris]

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

> yeap, yesterday night i found that i can not connect to the api host..
> anyone has any idea???
>
> i implement oauth protocol by myself in symbian.
> then, one more question:
> what can i do when i got the PIN code?
> set as parammeter 'oauth_verifier' in basestring before signature?
> if i do so, just made a authorization request like reques_token, and
> send it to http://api.twitter.com/oauth/access_token, then i got a 500
> err from api server...
>
> can someone tell me what'wrong about it?
> thx very much.
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

Re: [twitter-dev] Rich content in tweets as entities/annotations?

[Matt Harris]

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:
http://code.google.com/p/twitter-api/issues/list

Matt

On Thu, Jul 1, 2010 at 10:25 PM, Jaanus  wrote:

> This is a request to the Twitter API team but rather than sending it
> in private, I'm posting it here so others can chime in too.
>
> Tweets are 140 characters. But sometimes Twitter decides that some
> content is interesting enough to annotate with graphical icons on
> Twitter.com. Examples are red ribbon/aids that I think happened a
> while ago, and now during World Cup, the #worldcup hashtag gets a
> football icon and all the #country 3-letter abbreviations get a flag.
>
> These things happen quickly and spontaneously enough inside Twitter
> that it's not possible or necessary to coordinate with dev community
> beforehand. I appreciate that, and that's perfectly fine. But perhaps
> you can send developers this data as metadata, so should the apps "opt
> in" to displaying these, they could do that too? You already have two
> mechanisms in place for this that you could utilize — the "entities"
> where you transmit the URLs and hashtags, and of course "annotations".
> Could we have these icons transmitted as part of either of these
> mechanisms? And maybe you can standardize the height or size so we
> could consider it in our UI layouts?
>
>
> J
> cremeapp.com
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] Re: Failed to validate oauth signature and token with xauth

[ntortarolo]

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  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 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 having there the consumer secret but i dont have
> another way to do it.
> I get access token right, but now i have another problem, i dont know
> exactly what parameters i must add for a call, for example calling
> friends timeline, i have seen tutorials about xauth but i get this
> response "could not authenticate with oauth".
> Sorry of my english.
>
> Thanks, Nadia
>
> On Jun 24, 5:58 pm, Taylor Singletary 
> wrote:
>
> > Hi there,
>
> > Are you still having this issue?
>
> > In the past when I've seen other developers having issues accomplishing this
> > in Javascript, it's come down to an issue in the library used for HMAC-SHA1
> > and Base64 encoding. While it works in most conditions, there are apparently
> > some edge cases where it does the wrong thing. I generally don't advocate
> > using Javascript and OAuth together for a variety of reasons. Have you tried
> > tracing the request to see exactly the HTTP request being sent to the
> > server?
>
> > Are you writing a browser extension or WebOS app? If the former, how are you
> > keeping your consumer secret at least somewhat secured?
>
> > Have you tried other requests using an access token obtained through other
> > means?
>
> > Taylor
>
> > On Thu, Jun 17, 2010 at 11:25 AM, ntortarolo  wrote:
> > > Hi, i have problem requesting an access_token, i think my source is
> > > right, i dont know where is the problem, i have maken some test with
> > > base_string,  oauth_consumer_key and oauth_consumer_secret shown on
> > >http://dev.twitter.com/pages/xauthandi get the same oauth_signature
> > > shown there so i think problem is not there when i use the real
> > > base_string, my oauth_consumer_key and oauth_consumer_secret.
> > >        My source is this, i hope someone can help me (to preserve my 
> > > secret
> > > and key i will put the same as the ones used on
> > >http://dev.twitter.com/pages/xauth)
>
> > >        xauth: function xauth()
> > >        {
>
> > >         var username = encodeURIComponent(""),
> > >             password = encodeURIComponent(""),
> > >             url= "https://api.twitter.com/oauth/access_token";,
> > >             key = "sGNxxnqgZRHUt6NunK3uw",
> > >             timestamp = (new Date()).getTime(),
> > >             nonce = Math.random();
>
> > >        var access_token = "oauth_consumer_key=" + key +
> > >        "&oauth_nonce=" + nonce +
> > >        "&oauth_signature_method=HMAC-SHA1" +
> > >        "&oauth_timestamp=" + timestamp +
> > >        "&oauth_version=1.0" +
> > >        "&x_auth_mode=client_auth" +
> > >        "&x_auth_password=" + password +
> > >        "&x_auth_username=" + username;
>
> > >        var base_string = "POST&" + encodeURIComponent(url) + "&" +
> > > encodeURIComponent(access_token);
>
> > >        var oauth_signature =
> > > b64_hmac_sha1("5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&",
> > > base_string);
>
> > >        oauth_signature = encodeURIComponent(oauth_signature+"=");
>
> > >        var auth_header = 'OAuth oauth_nonce="' + nonce + '"' +
> > >        ', oauth_signature_method="HMAC-SHA1"' +
> > >        ', oauth_timestamp="' + timestamp + '"' +
> > >        ', oauth_consumer_key="' + key + '"' +
> > >        ', oauth_signature="' + oauth_signature + '"' +
> > >        ', oauth_version="1.0"';
>
> > >        $.ajax({
> > >             url:url,
> > >             method: "POST",
> > >             data: {
> > >                     x_auth_username: username,
> > >                     x_auth_password: password,
> > >                     x_auth_mode: "client_auth"
> > >             },
> > >             beforeSend: function(xhr){
> > >                     xhr.setRequestHeader("Authorization", auth_header);
> > >             },
> > >             success: function(data){
> > >                     alert(data);
> > >             },
> > >             error: function(xhr){
> > >                     alert(xhr.responseText);
> > >             }
> > >        }) ;
>
> > >        * What language or library are you using? What versions?
> > >          i'm using it on javascript
>
> > >        * What oauth application is this for?
> > >        http://twitter.com/apps/edit/181924
>
>

Re: [twitter-dev] Re: Failed to validate oauth signature and token with xauth

[Matt Harris]

Thanks for sharing the solution. Glad it's all working for you now.
Matt

On Tue, Jul 6, 2010 at 4:24 PM, ntortarolo  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  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 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 having there the consumer secret but i dont have
> > another way to do it.
> > I get access token right, but now i have another problem, i dont know
> > exactly what parameters i must add for a call, for example calling
> > friends timeline, i have seen tutorials about xauth but i get this
> > response "could not authenticate with oauth".
> > Sorry of my english.
> >
> > Thanks, Nadia
> >
> > On Jun 24, 5:58 pm, Taylor Singletary 
> > wrote:
> >
> > > Hi there,
> >
> > > Are you still having this issue?
> >
> > > In the past when I've seen other developers having issues accomplishing
> this
> > > in Javascript, it's come down to an issue in the library used for
> HMAC-SHA1
> > > and Base64 encoding. While it works in most conditions, there are
> apparently
> > > some edge cases where it does the wrong thing. I generally don't
> advocate
> > > using Javascript and OAuth together for a variety of reasons. Have you
> tried
> > > tracing the request to see exactly the HTTP request being sent to the
> > > server?
> >
> > > Are you writing a browser extension or WebOS app? If the former, how
> are you
> > > keeping your consumer secret at least somewhat secured?
> >
> > > Have you tried other requests using an access token obtained through
> other
> > > means?
> >
> > > Taylor
> >
> > > On Thu, Jun 17, 2010 at 11:25 AM, ntortarolo 
> wrote:
> > > > Hi, i have problem requesting an access_token, i think my source is
> > > > right, i dont know where is the problem, i have maken some test with
> > > > base_string,  oauth_consumer_key and oauth_consumer_secret shown on
> > > >http://dev.twitter.com/pages/xauthandi get the same oauth_signature
> > > > shown there so i think problem is not there when i use the real
> > > > base_string, my oauth_consumer_key and oauth_consumer_secret.
> > > >My source is this, i hope someone can help me (to preserve my
> secret
> > > > and key i will put the same as the ones used on
> > > >http://dev.twitter.com/pages/xauth)
> >
> > > >xauth: function xauth()
> > > >{
> >
> > > > var username = encodeURIComponent(""),
> > > > password = encodeURIComponent(""),
> > > > url= "https://api.twitter.com/oauth/access_token";,
> > > > key = "sGNxxnqgZRHUt6NunK3uw",
> > > > timestamp = (new Date()).getTime(),
> > > > nonce = Math.random();
> >
> > > >var access_token = "oauth_consumer_key=" + key +
> > > >"&oauth_nonce=" + nonce +
> > > >"&oauth_signature_method=HMAC-SHA1" +
> > > >"&oauth_timestamp=" + timestamp +
> > > >"&oauth_version=1.0" +
> > > >"&x_auth_mode=client_auth" +
> > > >"&x_auth_password=" + password +
> > > >"&x_auth_username=" + username;
> >
> > > >var base_string = "POST&" + encodeURIComponent(url) + "&" +
> > > > encodeURIComponent(access_token);
> >
> > > >var oauth_signature =
> > > > b64_hmac_sha1("5kEQypKe7lFHnufLtsocB1vAzO07xLFgp2Pc4sp2vk&",
> > > > base_string);
> >
> > > >oauth_signature = encodeURIComponent(oauth_signature+"=");
> >
> > > >var auth_header = 'OAuth oauth_nonce="' + nonce + '"' +
> > > >', oauth_signature_method="HMAC-SHA1"' +
> > > >', oauth_timestamp="' + timestamp + '"' +
> > > >', oauth_consumer_key="' + key + '"' +
> > > >', oauth_signature="' + oauth_signature + '"' +
> > > >', oauth_version="1.0"';
> >
> > > >$.ajax({
> > > > url:url,
> > > > method: "POST",
> > > > data: {
> > > > x_auth_username: username,
> > > > x_auth_password: password,
> > > > x_auth_mode: "client_auth"
> > > > },
> > > > beforeSend: function(xhr){
> > > > xhr.setRequestHeader("Authorization",
> auth_header);
> > > > },
> > > > success: function(data){
> > > > alert(data);
> > > > },
> > > > error: function(xhr){
> > > > alert(xhr.responseText);
> > > > }
> > > >}) ;
> >
> > > >* What language or library are you using? What versions?
> > > >  i'm using it on javascript
> >
> > > >* What oauth application is this for?
> > > >http://twitter.com/apps/edit/181924
> >
> >
>



-- 

[twitter-dev] Search API -Timezones problem

[Ramanean]

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

http://search.twitter.com/search.json?from=xxx


The search results display only GMT time for "created_at"

[twitter-dev] Re: Friend and Follower count - since timestamp

[nischalshetty]

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

-Nischal

On Jul 6, 7:04 pm, Raffi Krikorian  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 
> wrote:
>
> > My apphttp://justunfollow.comextensively uses the friends/ids and
> > followers/ids API. Since twitter users have a lot of followers and
> > friends and this API is paginated, I find it repetitive to use it.
>
> > A "since" param that sends me all new friend and follower ids of a
> > user along with the deleted ids (when someone stops being a friend or
> > follower) would help a lot. I checked the documentation but found no
> > mention of this. Please help!
>
> --
> Raffi Krikorian
> Twitter Platform Teamhttp://twitter.com/raffi

Re: [twitter-dev] Re: Friend and Follower count - since timestamp

[Matt Harris]

Hey Nischal,

So this doesn't get lost in the email archive would you be able to create
this as an enhancement request in our issue tracker:
http://code.google.com/p/twitter-api/issues/list

Thanks,
Matt

On Tue, Jul 6, 2010 at 10:00 PM, nischalshetty wrote:

> 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 :)
>
> -Nischal
>
> On Jul 6, 7:04 pm, Raffi Krikorian  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.com>wrote:
> >
> > > My apphttp://justunfollow.comextensively uses the friends/ids and
> > > followers/ids API. Since twitter users have a lot of followers and
> > > friends and this API is paginated, I find it repetitive to use it.
> >
> > > A "since" param that sends me all new friend and follower ids of a
> > > user along with the deleted ids (when someone stops being a friend or
> > > follower) would help a lot. I checked the documentation but found no
> > > mention of this. Please help!
> >
> > --
> > Raffi Krikorian
> > Twitter Platform Teamhttp://twitter.com/raffi
>



-- 


Matt Harris
Developer Advocate, Twitter
http://twitter.com/themattharris

[twitter-dev] XML format change???

[Pete]

Did you change the XML format today our application which has worked
for a year reading XML data all of the sudden does not function
today?  Was there a format change without notice?