Re: [twitter-dev] Re: trivial doubt

[Matt Harris]

Hi André,

Could you check you don't have javascript disabled? I know it sounds funny
but I want to make sure it didn't get disabled. Otherwise, try copying and
pasting the widget code fresh from our site and putting it between
Unedited Widget Code

See if that works for you
Matt


On Tue, Jun 22, 2010 at 4:39 PM, André Luís Moura Lima  wrote:

> Matt,
> I added the comma,but the widget is not rendering at all.What's happening
> here??
>
>
>
> 2010/6/22 themattharris 
>
>> Hi André,
>>
>> Looking at your code it looks like you have added the line:
>>  id : 'twitterdiv'
>> but forgotten to put the comma after it.
>> If you add the comma the widget will work.
>>
>> Matt
>>
>> You don't need the  as the widget will
>> automatically create that for you.
>>
>> On Jun 22, 6:25 am, André Lima  wrote:
>> > any suggestion of what I'm doing wrong here??
>> >
>> > On 21 jun, 22:00, André Luís Moura Lima  wrote:
>> >
>> >
>> >
>> > > Hello everybody,
>> > > I'm doing some tests with twitter widget profile...i do everything
>> right on
>> > > the site,copy the resulting code to my html,but the twitter widget is
>> not
>> > > shown,it isn't rendering.What can be wrong?for those who can help me,I
>> will
>> > > post the code here.I guess I'm doing some confusion with some html
>> tags like
>> > > body,head,html,etc...are they necessary to the code work
>> right?anyway,i hope
>> > > so,cause this code that I'm posting is,obviously,an example...the real
>> html
>> > > have head,body,html tags.anyway,here is the code:
>> > > 
>> > > http://widgets.twimg.com/j/2/widget.js";>
>> > > 
>> > > new TWTR.Widget({
>> > >   id : 'twitterdiv'
>> > >   version: 2,
>> > >   type: 'profile',
>> > >   rpp: 4,
>> > >   interval: 6000,
>> > >   width: 250,
>> > >   height: 300,
>> > >   theme: {
>> > > shell: {
>> > >   background: '#33',
>> > >   color: '#ff'
>> > > },
>> > > tweets: {
>> > >   background: '#00',
>> > >   color: '#ff',
>> > >   links: '#4aed05'
>> > > }
>> > >   },
>> > >   features: {
>> > > scrollbar: true,
>> > > loop: false,
>> > > live: false,
>> > > hashtags: true,
>> > > timestamp: true,
>> > > avatars: false,
>> > > behavior: 'all'
>> > >   }}).render().setUser('andre').start();
>> >
>> > > 
>>
>
>


-- 


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

Re: [twitter-dev] Re: trivial doubt

[Peter Denton]

Hi Andre

this works for me:



 new TWTR.Widget({
  version: 2,
  type: 'profile',
  rpp: 10,
  interval: 6000,
  width: 200,
  height: 300,
  theme: {
   shell: {
background: '#f3f3f3',
color: '#425e6a'
   },
   tweets: {
background: '#f3f3f3',
color: '#425e6a',
links: '#0099FF'
   }
  },
  features: {
   scrollbar: false,
   loop: false,
   live: false,
   hashtags: true,
   timestamp: true,
   avatars: false,
   behavior: 'all'
  }
}).render().setUser('andre').start();



On Tue, Jun 22, 2010 at 4:39 PM, André Luís Moura Lima  wrote:

> Matt,
> I added the comma,but the widget is not rendering at all.What's happening
> here??
>
>
>
> 2010/6/22 themattharris 
>
> Hi André,
>>
>> Looking at your code it looks like you have added the line:
>>  id : 'twitterdiv'
>> but forgotten to put the comma after it.
>> If you add the comma the widget will work.
>>
>> Matt
>>
>> You don't need the  as the widget will
>> automatically create that for you.
>>
>> On Jun 22, 6:25 am, André Lima  wrote:
>> > any suggestion of what I'm doing wrong here??
>> >
>> > On 21 jun, 22:00, André Luís Moura Lima  wrote:
>> >
>> >
>> >
>> > > Hello everybody,
>> > > I'm doing some tests with twitter widget profile...i do everything
>> right on
>> > > the site,copy the resulting code to my html,but the twitter widget is
>> not
>> > > shown,it isn't rendering.What can be wrong?for those who can help me,I
>> will
>> > > post the code here.I guess I'm doing some confusion with some html
>> tags like
>> > > body,head,html,etc...are they necessary to the code work
>> right?anyway,i hope
>> > > so,cause this code that I'm posting is,obviously,an example...the real
>> html
>> > > have head,body,html tags.anyway,here is the code:
>> > > 
>> > > http://widgets.twimg.com/j/2/widget.js";>
>> > > 
>> > > new TWTR.Widget({
>> > >   id : 'twitterdiv'
>> > >   version: 2,
>> > >   type: 'profile',
>> > >   rpp: 4,
>> > >   interval: 6000,
>> > >   width: 250,
>> > >   height: 300,
>> > >   theme: {
>> > > shell: {
>> > >   background: '#33',
>> > >   color: '#ff'
>> > > },
>> > > tweets: {
>> > >   background: '#00',
>> > >   color: '#ff',
>> > >   links: '#4aed05'
>> > > }
>> > >   },
>> > >   features: {
>> > > scrollbar: true,
>> > > loop: false,
>> > > live: false,
>> > > hashtags: true,
>> > > timestamp: true,
>> > > avatars: false,
>> > > behavior: 'all'
>> > >   }}).render().setUser('andre').start();
>> >
>> > > 
>>
>
>


-- 
Peter Denton
Co-Founder, Product Marketing
www.mombo.com
cell: (206) 427-3866
twitter @Mombo_movies
twitter - personal: @petermdenton

[twitter-dev] Re: Hashtags in prepopulated status's when the user was not logged in

[maestrojed]

Thanks Matt, I submitted an issue on the Google Code page.

On Jun 22, 11:56 am, Matt Harris  wrote:
> You want to make sure you URL encode the entire status you are sending,
> including the spaces. That being said the hashtag is dropped so that's a bug
> at our end. Can you file it 
> onhttp://code.google.com/p/twitter-api/issuesandi'll pass it onto the
> team.
>
> Thanks,
> Matt
>
> On Tue, Jun 22, 2010 at 10:27 AM, maestrojed
> wrote:
>
>
>
> > You can pre-populate a tweet by doing something like:  > href="http://twitter.com/home?status=Iam asking a question on
> > stackoverflow">http://twitter.com/home?status=Iam asking a question
> > on stackoverflow
>
> > If you want to use a hashtag you have to urlencode it http://twitter.com/home?status=Iam asking a
> > question on %23stackoverflow
>
> > If the user is not already logged into twitter, once they do log in,
> > they are redirected to a 404 because of these hashtags. I am sure its
> > because twitter has to save/pass through this status query string
> > while you log in.
>
> > Any one have suggestions? A hashtag is important to me in this
> > situation.
>
> --
>
> Matt Harris
> Developer Advocate, Twitterhttp://twitter.com/themattharris

Re: [twitter-dev] Re: trivial doubt

[André Luís Moura Lima]

Matt,
I added the comma,but the widget is not rendering at all.What's happening
here??



2010/6/22 themattharris 

> Hi André,
>
> Looking at your code it looks like you have added the line:
>  id : 'twitterdiv'
> but forgotten to put the comma after it.
> If you add the comma the widget will work.
>
> Matt
>
> You don't need the  as the widget will
> automatically create that for you.
>
> On Jun 22, 6:25 am, André Lima  wrote:
> > any suggestion of what I'm doing wrong here??
> >
> > On 21 jun, 22:00, André Luís Moura Lima  wrote:
> >
> >
> >
> > > Hello everybody,
> > > I'm doing some tests with twitter widget profile...i do everything
> right on
> > > the site,copy the resulting code to my html,but the twitter widget is
> not
> > > shown,it isn't rendering.What can be wrong?for those who can help me,I
> will
> > > post the code here.I guess I'm doing some confusion with some html tags
> like
> > > body,head,html,etc...are they necessary to the code work right?anyway,i
> hope
> > > so,cause this code that I'm posting is,obviously,an example...the real
> html
> > > have head,body,html tags.anyway,here is the code:
> > > 
> > > http://widgets.twimg.com/j/2/widget.js";>
> > > 
> > > new TWTR.Widget({
> > >   id : 'twitterdiv'
> > >   version: 2,
> > >   type: 'profile',
> > >   rpp: 4,
> > >   interval: 6000,
> > >   width: 250,
> > >   height: 300,
> > >   theme: {
> > > shell: {
> > >   background: '#33',
> > >   color: '#ff'
> > > },
> > > tweets: {
> > >   background: '#00',
> > >   color: '#ff',
> > >   links: '#4aed05'
> > > }
> > >   },
> > >   features: {
> > > scrollbar: true,
> > > loop: false,
> > > live: false,
> > > hashtags: true,
> > > timestamp: true,
> > > avatars: false,
> > > behavior: 'all'
> > >   }}).render().setUser('andre').start();
> >
> > > 
>

Re: [twitter-dev] Multiple users with the same screen name?

[Taylor Singletary]

Hi Adam,

I'm taking a look and will get back to you with findings. This is certainly
an odd case that shouldn't generally happen.

Thanks,
Taylor

On Tue, Jun 22, 2010 at 4:22 PM, Adam Fortuna wrote:

> A user recently joined our system that ran into a bit of a problem.
> It seems like there are multiple accounts with the same screen name,
> but with different IDs.  Here are the two accounts in question for
> this.
>
> view-source:http://api.twitter.com/1/users/show.xml?id=34455954
> view-source:http://api.twitter.com/1/users/show.xml?id=34456073
>
> This resulted in them having multiple accounts in our system. It seems
> like when they signed up for our site on 6/16 it used the 34455954 ID,
> but now it's using the 34456073 ID. Any idea what could cause
> something like this? I was initially thinking they just changed
> usernames around (which is what usually happens when they try to
> switch accounts not knowing things are tied to an ID), but in this
> case it's the ID that's different and the screen name that's the same.
>

[twitter-dev] Multiple users with the same screen name?

[Adam Fortuna]

A user recently joined our system that ran into a bit of a problem.
It seems like there are multiple accounts with the same screen name,
but with different IDs.  Here are the two accounts in question for
this.

view-source:http://api.twitter.com/1/users/show.xml?id=34455954
view-source:http://api.twitter.com/1/users/show.xml?id=34456073

This resulted in them having multiple accounts in our system. It seems
like when they signed up for our site on 6/16 it used the 34455954 ID,
but now it's using the 34456073 ID. Any idea what could cause
something like this? I was initially thinking they just changed
usernames around (which is what usually happens when they try to
switch accounts not knowing things are tied to an ID), but in this
case it's the ID that's different and the screen name that's the same.

[twitter-dev] api.twitter.com/1/search.* is no longer functional, use search.twitter.com/search instead

[Taylor Singletary]

Hi Everyone,

As we warned back in May ( http://bit.ly/9vBx5m ), we've now removed Search
API access from our undocumented endpoint at api.twitter.com. If you're
using the Search API, all of your requests should be sent to
http://search.twitter.com/search instead.

For those using http://twitter.com/search, http://api.twitter.com/search, or
http://api.twitter.com/1/search -- you'll need to modify your code to point
to the correct location.

Though we should have rejected traffic to that end point long ago to avoid
confusion, it was never intended as a valid resource for search queries.

If you attempt to use the now removed endpoint, you'll get something similar
to this as a response:

(In JSON)
  {"errors":[{"code":37,"message":"Not authorized to use this
endpoint"}]}{"errors":[{"code":37,"message":"Not authorized to use this
endpoint"}]}

(In XML)
  
  
Not authorized to use this endpoint
  

So if, for example, you were making a request to
http://api.twitter.com/1/search.json?q=raffi you should be making the
request to http://search.twitter.com/search.json?q=raffi instead.

Thanks everyone!
Taylor

[twitter-dev] Twitter backup script

[Kai Hendry]

Hello everyone,

I wrote a twitter backup script for shell geeks like myself. I would
appreciate review and any constructive comments:
http://twitter.natalian.org/hgweb.cgi/file/tip/fetch-tweets.sh


Where can I find http://api.twitter.com/1/statuses/user_timeline.xml
on http://dev.twitter.com/status btw?


Many thanks from a warm summer's night in England,

Re: [twitter-dev] Invalid signature - but it's fine

[Dustin Shea]

I'm having the same issue with my client.

Debug information:
URL: http://api.twitter.com/1/statuses/home_timeline.json
Oauth Token: 6339722-C6ciVM1DS5dsbezoxX25K2DM0LDysexMD0QDm28s
Oauth Token Secret: XRLC2XcJ1gpPd3qyOHR9szIWs1OXMOkY3NljpM36Vo
Consumer Key: CabFljpBvebzTnWpsUtw
Consumer Secret: what_is_on_my_app_page
Nonce: 88c65140bb4caeb02264c1c02dcd5e3a44c1e7cb
Time: 1277241300
Version: 1.0
Signature: FuB86c97j9VBnbC7JmJzqbRwBOQ%3D

I'll see what I can do about providing you any more information you may require.

-Dustin
(Demonicpagan on Twitter)

On 6/22/2010 1:12 PM, Tom wrote:

Hi all,

I'm trying to write a simple Twitter client but so far I'm not making
a lot of progress.

I already got as far as retrieving the timeline, but I seem to be
unable to sign the request. When I re-calculate the signature with a
different application, it's exactly the same. Yet Twitter reports that
it's wrong! ("Incorrect signature" with a 401 error)

Of course, I'm using a proper secret and not the one below, but that
one was used to calculate the signature for the request below.

Can anyone confirm that I'm using the proper signature? Information is
below.

Debug information :
URL: http://api.twitter.com/1/statuses/home_timeline.json
Token: 18911703-HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU
Customer key: QetEw0FtIfvaNyBfgxRYmw
Secret: this_has_been_used_as_the_secret
Nonce: jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
Time: 1277230019
Version: 1.0

Signature: aiUvshdfeRz2Z6G6a9DkYDbXJEc=
Str1: GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fhome_timeline.json&oauth_consumer_key%3DQetEw0FtIfvaNyBfgxRYmw
%26oauth_nonce%3DjOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1277230019%26oauth_token%3D18911703-
HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU%26oauth_version%3D1.0
Str2: OAuth oauth_signature="aiUvshdfeRz2Z6G6a9DkYDbXJEc%3D",
oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
oauth_nonce="jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE",
oauth_consumer_key="QetEw0FtIfvaNyBfgxRYmw",
oauth_timestamp="1277230019", oauth_token="18911703-
HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU"
No post body.

Tom


--
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and delete 
this e-mail from your system. E-mail transmission cannot be guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. The sender therefore 
does not accept liability for any errors or omissions in the contents of this 
message, which arise as a result of e-mail transmission.

Re: [twitter-dev] Hashtags in prepopulated status's when the user was not logged in

[Matt Harris]

You want to make sure you URL encode the entire status you are sending,
including the spaces. That being said the hashtag is dropped so that's a bug
at our end. Can you file it on
http://code.google.com/p/twitter-api/issuesand i'll pass it onto the
team.

Thanks,
Matt

On Tue, Jun 22, 2010 at 10:27 AM, maestrojed
wrote:

> You can pre-populate a tweet by doing something like:  href="http://twitter.com/home?status=I am asking a question on
> stackoverflow">http://twitter.com/home?status=I am asking a question
> on stackoverflow
>
> If you want to use a hashtag you have to urlencode it http://twitter.com/home?status=I am asking a
> question on %23stackoverflow
>
> If the user is not already logged into twitter, once they do log in,
> they are redirected to a 404 because of these hashtags. I am sure its
> because twitter has to save/pass through this status query string
> while you log in.
>
> Any one have suggestions? A hashtag is important to me in this
> situation.
>



-- 


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

Re: [twitter-dev] Re: Which IETF standard has the year appearing after the time?

[Daniel Atik]

*Question:*
I'm tweeting throught twitter for iPhone and geotagging each tweet.

When I try this search API query
http://search.twitter.com/search.json?geocode=-33.4135,-70.5999,10mi&q=danielatik

I
cannot see GEO lat, long information. Any idea?


Daniel Atik

2010/6/22 Peter Cross 

> Thanks for the explanation.  It's easy enough to parse, it just seemed
> so bizarre (and I was having a bad oAuth day!).  -ZPC
>
> On Jun 21, 4:37 pm, themattharris  wrote:
> > The time format is a little weird and as far as I know, doesn't match
> > any RFC. Instead it matches the ruby default and is represented in
> > tokens by:
> >   %a %b %d %H:%M:%S %Z %Y
> >
> > The format has been like this since the API was first released which
> > means, for backwards compatibility with other applications, we can't
> > easily change it with this version of the API.
> >
> > I hope that explains the why it is still in the format it is.
> > Hopefully you can use the token string above to parse the date using
> > the time parsing functions of your chosen language.
> >
> > Matt
> >
> > On Jun 21, 12:40 pm, Peter Cross  wrote:
> >
> >
> >
> > > This date is from a call tohttp://
> api.twitter.com/1/statuses/user_timeline.xml:
> >
> > > Mon Jun 21 19:06:21 + 2010
> >
> > > 
> >
> > > I've never seen the year come after the time... in any standard date
> > > format.  It's as if someone thought "Hmmm... how can we make this date
> > > format more difficult to work with?".  Why, why why?  Now I have to
> > > write a special handler for this one exception.  It's sloppy.
> >
> > > 
> >
> > > This isn't an XML standard date format either.
> >
> > > -ZPC

Re: [twitter-dev] Invalid signature - but it's fine

[Taylor Singletary]

Hi Tom,

I'm happy to help diagnose this, but need a couple pieces more information
-- you may want to use more "fake details" to make this process easy for me
to replicate -- in addition to the access token, the access token secret
would be necessary to recreate this request (are you utilizing the access
token secret when generating your signature?)

Your signature base string and authorization header look otherwise correct.

Taylor



On Tue, Jun 22, 2010 at 11:12 AM, Tom  wrote:

> Hi all,
>
> I'm trying to write a simple Twitter client but so far I'm not making
> a lot of progress.
>
> I already got as far as retrieving the timeline, but I seem to be
> unable to sign the request. When I re-calculate the signature with a
> different application, it's exactly the same. Yet Twitter reports that
> it's wrong! ("Incorrect signature" with a 401 error)
>
> Of course, I'm using a proper secret and not the one below, but that
> one was used to calculate the signature for the request below.
>
> Can anyone confirm that I'm using the proper signature? Information is
> below.
>
> Debug information :
> URL: http://api.twitter.com/1/statuses/home_timeline.json
> Token: 18911703-HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU
> Customer key: QetEw0FtIfvaNyBfgxRYmw
> Secret: this_has_been_used_as_the_secret
> Nonce: jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
> Time: 1277230019
> Version: 1.0
>
> Signature: aiUvshdfeRz2Z6G6a9DkYDbXJEc=
> Str1: GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> %2Fhome_timeline.json&oauth_consumer_key%3DQetEw0FtIfvaNyBfgxRYmw
> %26oauth_nonce%3DjOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
> %26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
> %3D1277230019%26oauth_token%3D18911703-
> HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU%26oauth_version%3D1.0
> Str2: OAuth oauth_signature="aiUvshdfeRz2Z6G6a9DkYDbXJEc%3D",
> oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
> oauth_nonce="jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE",
> oauth_consumer_key="QetEw0FtIfvaNyBfgxRYmw",
> oauth_timestamp="1277230019", oauth_token="18911703-
> HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU"
> No post body.
>
> Tom
>

[twitter-dev] Re: Which IETF standard has the year appearing after the time?

[Peter Cross]

Thanks for the explanation.  It's easy enough to parse, it just seemed
so bizarre (and I was having a bad oAuth day!).  -ZPC

On Jun 21, 4:37 pm, themattharris  wrote:
> The time format is a little weird and as far as I know, doesn't match
> any RFC. Instead it matches the ruby default and is represented in
> tokens by:
>   %a %b %d %H:%M:%S %Z %Y
>
> The format has been like this since the API was first released which
> means, for backwards compatibility with other applications, we can't
> easily change it with this version of the API.
>
> I hope that explains the why it is still in the format it is.
> Hopefully you can use the token string above to parse the date using
> the time parsing functions of your chosen language.
>
> Matt
>
> On Jun 21, 12:40 pm, Peter Cross  wrote:
>
>
>
> > This date is from a call 
> > tohttp://api.twitter.com/1/statuses/user_timeline.xml:
>
> > Mon Jun 21 19:06:21 + 2010
>
> > 
>
> > I've never seen the year come after the time... in any standard date
> > format.  It's as if someone thought "Hmmm... how can we make this date
> > format more difficult to work with?".  Why, why why?  Now I have to
> > write a special handler for this one exception.  It's sloppy.
>
> > 
>
> > This isn't an XML standard date format either.
>
> > -ZPC

[twitter-dev] How to compute the user list membership count

[Alfredo Artiles]

Hi,
Is there any way to count the user lists membership other than iterating
with the /:user/lists/memberships method?

All the best,
---
Alfredo
http://e24apps.com

fd1b63583b
fd1b63583b

[twitter-dev] Anywhere - over the trending topic ?

[Rahul]

Here is the scenario. I have list of trending topics on my page. I
want if user hovers over any of the trending topic a small popup
should slide below and list top 10 tweets for that trend. Is there any
javascript provided by twitter to do such thing or else i need to get
rolling and create something myself.

Thanks,
Rahul

[twitter-dev] Invalid signature - but it's fine

[Tom]

Hi all,

I'm trying to write a simple Twitter client but so far I'm not making
a lot of progress.

I already got as far as retrieving the timeline, but I seem to be
unable to sign the request. When I re-calculate the signature with a
different application, it's exactly the same. Yet Twitter reports that
it's wrong! ("Incorrect signature" with a 401 error)

Of course, I'm using a proper secret and not the one below, but that
one was used to calculate the signature for the request below.

Can anyone confirm that I'm using the proper signature? Information is
below.

Debug information :
URL: http://api.twitter.com/1/statuses/home_timeline.json
Token: 18911703-HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU
Customer key: QetEw0FtIfvaNyBfgxRYmw
Secret: this_has_been_used_as_the_secret
Nonce: jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
Time: 1277230019
Version: 1.0

Signature: aiUvshdfeRz2Z6G6a9DkYDbXJEc=
Str1: GET&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
%2Fhome_timeline.json&oauth_consumer_key%3DQetEw0FtIfvaNyBfgxRYmw
%26oauth_nonce%3DjOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE
%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp
%3D1277230019%26oauth_token%3D18911703-
HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU%26oauth_version%3D1.0
Str2: OAuth oauth_signature="aiUvshdfeRz2Z6G6a9DkYDbXJEc%3D",
oauth_version="1.0", oauth_signature_method="HMAC-SHA1",
oauth_nonce="jOzrZNZtsGFLftfjJpdiOfjYtgvNFzWPPXIOKHKE",
oauth_consumer_key="QetEw0FtIfvaNyBfgxRYmw",
oauth_timestamp="1277230019", oauth_token="18911703-
HjjtYklryN9C99pfTiXWs52PvEqrfabluLCdh5IJU"
No post body.

Tom

Re: [twitter-dev] Re: Streaming API OAuth explanation?

[John Kalucki]

OAuth should work fine on stream.twitter.com

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



On Tue, Jun 22, 2010 at 10:00 AM, Wil  wrote:
> I'm a bit dumbfounded here...
>
> I've been trying to login to stream.twitter.com using OAuth
> (particularly, I've been trying to access
> http://stream.twitter.com/1/statuses/filter.json?follow=). I used
> the access keys obtained from https://api.twitter.com/oauth/access_token
> however, I've been getting 401 errors. I've tried basic authentication
> and it works fine.
>
> Does that mean that stream:statuses/filter is still can only accept
> basic authentication?
>
> Regards,
> Wil
>
> On May 25, 5:51 am, John Kalucki  wrote:
>> We haven't announced our plans for streaming and oAuth, beyond stating that
>> User Streams will only be on oAuth.
>>
>>
>>
>> On Mon, May 24, 2010 at 1:57 PM, 140dev <140...@gmail.com> wrote:
>> > Does this mean that the streaming API will also make the switch from
>> > basic authentication to OAuth at the end of June?
>>
>> > On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
>> > wrote:
>> > > OAuth is now enabled on stream.twitter.com.  I'll also send a note out
>> > > to the announce list
>>
>> > >   ---Mark
>>
>> > >http://twitter.com/mccv
>>
>> > > On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin 
>> > wrote:
>> > >> Hi,
>>
>> > >> Is there an ETA for enabling oauth on stream.twitter.com?
>>
>> > >> Thanks,
>> > >> Aaron
>>
>> > >> On May 13, 1:11 pm, John Kalucki  wrote:
>> > >>> OAuthis not enabled on stream.twitter.com. You can try on
>> > >>> chirpstream.twitter.com.
>>
>> > >>> On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers <
>> > lucasvick...@gmail.com> wrote:
>> > >>> > I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
>> > >>> > but I like to do things myself to learn.
>>
>> > >>> > Anyhow I am trying to accesshttp://
>> > stream.twitter.com/1/statuses/sample.xml
>> > >>> > and I keep getting 401.
>>
>> > >>> > I have verified pretty much every parameter, and used the tool on
>>
>> >http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
>> > >>> > to verify my signature is correct. I used twurl to obtain the user
>> > >>> > access tokens to my account.
>>
>> > >>> > After doing some reading I'm no longer convinced that thestreaming
>> > >>> > server even supportsoauth.
>>
>> > >>> > can you fill me in on the current status of stream.twitter.com and
>> > >>> >oauth?
>>
>> > >>> > thanks!
>> > >>> > Lucas
>>
>> > >>> > On Apr 20, 11:02 pm, Jonathon Hill  wrote:
>> > >>> >> Thanks Taylor for the very detailed and helpful response!
>>
>> > >>> >> Jonathon
>>
>> > >>> >> On Apr 20, 1:17 pm, Taylor Singletary >
>> > >>> >> wrote:
>>
>> > >>> >> > Hi Jonathon,
>>
>> > >>> >> > ForStreamingAPI access that isn't from the perspective of a user's
>> > >>> >> > account, you would use two-leggedOAuthto establish authentication
>> > instead
>> > >>> >> > of basic auth.
>>
>> > >>> >> > A two-leggedOAuthrequest is very similar to otherOAuthrequests:
>> > you have
>> > >>> >> > a specific resource you are trying to access, you have some
>> > parameters you
>> > >>> >> > want to pass to that resource, and you have anOAuthconsumer key
>> > andOAuth
>> > >>> >> > consumer secret. Which is unlike three-leggedOAuthwhere you also
>> > have
>> > >>> >> > oauth_tokens representing either a user/access_token or a request
>> > token in
>> > >>> >> > addition to the rest.
>>
>> > >>> >> > But the rules remain the same. You take all theOAuthparameters and
>> > the
>> > >>> >> > parameters you are sending to the resource, organize them, build a
>> > signature
>> > >>> >> > base string, then sign that with your consumer secret and send the
>> > request
>> > >>> >> > on to Twitter properly signed. The only difference is that there
>> > is no
>> > >>> >> > oauth_token and oauth_token_secret getting involved in the mix.
>>
>> > >>> >> > This is essentially what a two-legged request to thestreamingAPI
>> > would
>> > >>> >> > look like:
>>
>> > >>> >> > Signature Base String
>> > >>> >> > GET&http%3A%2F%2Fstream.twitter.com
>>
>> > %2F1%2Fstatuses%2Fsample.json&oauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2
>> >  
>> > ­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu
>> >  
>> > r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0
>>
>> > >>> >> > Signature
>> > >>> >> > Xi5jfuw2XqtU5KpNX9ZCtTptJS0=
>>
>> > >>> >> > Authorization Header
>> > >>> >> >OAuthoauth_nonce="SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8",
>> > >>> >> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1271783743",
>> > >>> >> > oauth_consumer_key="ri8JxYK2zzwSV5xIUfNNvQ",
>> > >>> >> > oauth_signature="Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D",
>> > oauth_version="1.0"
>>
>> > >>> >> > Taylor Singletary
>> > >>> >> > Developer Advocate, Twitterhttp://twitter.com/episod
>>
>> > >>> >> > On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill <
>> > jhill9...@gmail.com> wrote:
>> > >>> >> > >

[twitter-dev] Hashtags in prepopulated status's when the user was not logged in

[maestrojed]

You can pre-populate a tweet by doing something like: http://twitter.com/home?status=I am asking a question on
stackoverflow">http://twitter.com/home?status=I am asking a question
on stackoverflow

If you want to use a hashtag you have to urlencode it http://twitter.com/home?status=I am asking a
question on %23stackoverflow

If the user is not already logged into twitter, once they do log in,
they are redirected to a 404 because of these hashtags. I am sure its
because twitter has to save/pass through this status query string
while you log in.

Any one have suggestions? A hashtag is important to me in this
situation.

[twitter-dev] Whats wrong? Cant update profile image

[man]

Its small class for twitter

/**
 * Twitter API abstract class
 * @package twitterlibphp
 */
abstract class TwitterBase {

/**
 * the last HTTP status code returned
 * @access private
 * @var integer
 */
private $http_status;

/**
 * the whole URL of the last API call
 * @access private
 * @var string
 */
private $last_api_call;

/**
 * the application calling the API
 * @access private
 * @var string
 */
private $application_source;

function updateImg($options = array(), $format = 'json') {
$options = array('image' => $image,
 'type' => $type);

return $this->apiCall('account/update_profile_image', 'post',
$format, $options);
}
}


/**
 * Access to the Twitter API through HTTP auth
 * @package twitterlibphp
 */
class Twitter extends TwitterBase {

/**
 * the Twitter credentials in HTTP format, username:password
 * @access private
 * @var string
 */
var $credentials;

/**
 * Fills in the credentials {...@link $credentials} and the application
source {...@link $application_source}.
 * @param string $username Twitter username
 * @param string $password Twitter password
 * @param $source string Optional. Name of the application using the
API
 */
function __construct($username, $password, $source = null) {
$this->credentials = sprintf("%s:%s", $username, $password);
$this->application_source = $source;
}

/**
 * Executes an API call
 * @param string $twitter_method The Twitter method to call
   * @param string $http_method The HTTP method to use
   * @param string $format Return format
   * @param array $options Options to pass to the Twitter method
 * @param boolean $require_credentials Whether or not credentials are
required
 * @return string
 */
protected function apiCall($twitter_method, $http_method, $format,
$options, $require_credentials = true) {
$curl_handle = curl_init();
$api_url = sprintf('http://twitter.com/%s.%s', $twitter_method,
$format);
if (($http_method == 'get') && (count($options) > 0)) {
  $api_url .= '?' . http_build_query($options);
}
//echo $api_url . "\n";
curl_setopt($curl_handle, CURLOPT_URL, $api_url);
if ($require_credentials) {
curl_setopt($curl_handle, CURLOPT_USERPWD, 
$this->credentials);
}
if ($http_method == 'post') {
curl_setopt($curl_handle, CURLOPT_POST, true);
  curl_setopt($curl_handle, CURLOPT_POSTFIELDS,
http_build_query($options));
}
curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, TRUE);
curl_setopt($curl_handle, CURLOPT_HTTPHEADER, array('Expect:'));
$twitter_data = curl_exec($curl_handle);
$this->http_status = curl_getinfo($curl_handle, 
CURLINFO_HTTP_CODE);
$this->last_api_call = $api_url;
curl_close($curl_handle);
return $twitter_data;
}

}





And little function

if (isset($_POST['save_download'])) {
$upload_file = $_FILES['twimg']['name'];
$upload_dir = 'up/';
$tmp_path = $_FILES['twimg']['tmp_name'];
$full_path_copy = $upload_dir.$upload_file;
$img = $_SERVER['DOCUMENT_ROOT']."/t/$full_path_copy";
$type = $_FILES['twimg']['type'];
if (move_uploaded_file($tmp_path,$full_path_copy)) {
$twitter = new Twitter("login", "password");
$options = array('image' => $img, 'type' => $type);
$twitter->updateImg($options);
}
}





But it is dont work Where my wrong?


ps: sorry for my bad english

[twitter-dev] Re: Streaming API OAuth explanation?

[Wil]

I'm a bit dumbfounded here...

I've been trying to login to stream.twitter.com using OAuth
(particularly, I've been trying to access
http://stream.twitter.com/1/statuses/filter.json?follow=). I used
the access keys obtained from https://api.twitter.com/oauth/access_token
however, I've been getting 401 errors. I've tried basic authentication
and it works fine.

Does that mean that stream:statuses/filter is still can only accept
basic authentication?

Regards,
Wil

On May 25, 5:51 am, John Kalucki  wrote:
> We haven't announced our plans for streaming and oAuth, beyond stating that
> User Streams will only be on oAuth.
>
>
>
> On Mon, May 24, 2010 at 1:57 PM, 140dev <140...@gmail.com> wrote:
> > Does this mean that the streaming API will also make the switch from
> > basic authentication to OAuth at the end of June?
>
> > On Mon, May 24, 2010 at 4:50 PM, Mark McBride 
> > wrote:
> > > OAuth is now enabled on stream.twitter.com.  I'll also send a note out
> > > to the announce list
>
> > >   ---Mark
>
> > >http://twitter.com/mccv
>
> > > On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin 
> > wrote:
> > >> Hi,
>
> > >> Is there an ETA for enabling oauth on stream.twitter.com?
>
> > >> Thanks,
> > >> Aaron
>
> > >> On May 13, 1:11 pm, John Kalucki  wrote:
> > >>> OAuthis not enabled on stream.twitter.com. You can try on
> > >>> chirpstream.twitter.com.
>
> > >>> On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers <
> > lucasvick...@gmail.com> wrote:
> > >>> > I am writing my own c++ basedOAuthlibrary.  I know there is liboauth
> > >>> > but I like to do things myself to learn.
>
> > >>> > Anyhow I am trying to accesshttp://
> > stream.twitter.com/1/statuses/sample.xml
> > >>> > and I keep getting 401.
>
> > >>> > I have verified pretty much every parameter, and used the tool on
>
> >http://hueniverse.com/2008/10/beginners-guide-to-oauth-part-iv-signin...
> > >>> > to verify my signature is correct. I used twurl to obtain the user
> > >>> > access tokens to my account.
>
> > >>> > After doing some reading I'm no longer convinced that thestreaming
> > >>> > server even supportsoauth.
>
> > >>> > can you fill me in on the current status of stream.twitter.com and
> > >>> >oauth?
>
> > >>> > thanks!
> > >>> > Lucas
>
> > >>> > On Apr 20, 11:02 pm, Jonathon Hill  wrote:
> > >>> >> Thanks Taylor for the very detailed and helpful response!
>
> > >>> >> Jonathon
>
> > >>> >> On Apr 20, 1:17 pm, Taylor Singletary 
> > >>> >> wrote:
>
> > >>> >> > Hi Jonathon,
>
> > >>> >> > ForStreamingAPI access that isn't from the perspective of a user's
> > >>> >> > account, you would use two-leggedOAuthto establish authentication
> > instead
> > >>> >> > of basic auth.
>
> > >>> >> > A two-leggedOAuthrequest is very similar to otherOAuthrequests:
> > you have
> > >>> >> > a specific resource you are trying to access, you have some
> > parameters you
> > >>> >> > want to pass to that resource, and you have anOAuthconsumer key
> > andOAuth
> > >>> >> > consumer secret. Which is unlike three-leggedOAuthwhere you also
> > have
> > >>> >> > oauth_tokens representing either a user/access_token or a request
> > token in
> > >>> >> > addition to the rest.
>
> > >>> >> > But the rules remain the same. You take all theOAuthparameters and
> > the
> > >>> >> > parameters you are sending to the resource, organize them, build a
> > signature
> > >>> >> > base string, then sign that with your consumer secret and send the
> > request
> > >>> >> > on to Twitter properly signed. The only difference is that there
> > is no
> > >>> >> > oauth_token and oauth_token_secret getting involved in the mix.
>
> > >>> >> > This is essentially what a two-legged request to thestreamingAPI
> > would
> > >>> >> > look like:
>
> > >>> >> > Signature Base String
> > >>> >> > GET&http%3A%2F%2Fstream.twitter.com
>
> > %2F1%2Fstatuses%2Fsample.json&oauth_consumer_key%3Dri8JxYK2zzwSV5xIUfNNvQ%2 
> > ­6oauth_nonce%3DSJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8%26oauth_signatu 
> > r­e_method%3DHMAC-SHA1%26oauth_timestamp%3D1271783743%26oauth_version%3D1.0
>
> > >>> >> > Signature
> > >>> >> > Xi5jfuw2XqtU5KpNX9ZCtTptJS0=
>
> > >>> >> > Authorization Header
> > >>> >> >OAuthoauth_nonce="SJJqJPdaZrYuIogToapS6ueJRyWB4Rs2ox4HEbu4nW8",
> > >>> >> > oauth_signature_method="HMAC-SHA1", oauth_timestamp="1271783743",
> > >>> >> > oauth_consumer_key="ri8JxYK2zzwSV5xIUfNNvQ",
> > >>> >> > oauth_signature="Xi5jfuw2XqtU5KpNX9ZCtTptJS0%3D",
> > oauth_version="1.0"
>
> > >>> >> > Taylor Singletary
> > >>> >> > Developer Advocate, Twitterhttp://twitter.com/episod
>
> > >>> >> > On Tue, Apr 20, 2010 at 10:05 AM, Jonathon Hill <
> > jhill9...@gmail.com> wrote:
> > >>> >> > > One thing I meant to find out @chirp last week--what
> > willoauthlook
> > >>> >> > > like for theStreamingAPI? I'm having a hard time visualizing how
> > >>> >> > > that will work.
>
> > >>> >> > > Thanks,
>
> > >>> >> > > Jonathon Hill
> > >>> >> > > @compwright
> > >>> >> > > Company52
> > >>> >> > >http://company52.com

[twitter-dev] @anywhere error checking

[Drezden]

Looking through the docs I'm struggling to find a way to detect errors
and handle them correctly.  For instance, I sometimes get a "bad
gateway" error when Twitter is over capacity or I get an "update.json"
error when there is a duplicate post.  But I can only see these using
developer tools, the twttr object is silent.

Is there any way to check for these?  There is no mention in the docs
or online about onError functions or callbacks.

Thanks for any help you can provide.

[twitter-dev] Twitter Places Follow Up

[ELB]

The "statuses/update" API  linked to (http://dev.twitter.com/doc/post/
statuses/update or 
http://apiwiki.twitter.com/Twitter-REST-API-Method%3A-statuses%C2%A0update)
is the method that is used for an authenticated Twitter user to add
his/her own new Tweet.  (It's not a method of returning Tweets already
created by other users.)

We don't want to create Tweets from a given place - instead we want to
use the Twitter API to publish Tweets from a given place.

So, here is our page about the Staples Center in Los Angeles.
http://sency.com/los-angeles/STAPLES-Center-4165

our goal is to publish the most recent Tweets, made from the Staples
Center - on this page...

would this be possible based on the current Twitter API?

Re: [twitter-dev] Re: Twitter Oauth Integration

[John Sullivan]

Anyone know about tweetstream buddypress not follwoing through to it's call
back url all of asudden ? Thanks goes to a white page on the site

On Tue, Jun 22, 2010 at 7:31 AM, luisg  wrote:

> web or desktop?
>
> On Jun 22, 3:35 pm, "Anil kumar M.S"  wrote:
> > Hi All,
> > Can you please help me in integrating Oauth to our app  ,
> >
> > thanks
> > Anilkumar
>



-- 
HOME of the KING
http://POTPOLITICS.COM
you know you want it;)
New Awesome Blogger Community
http://bloggerluv.com
All Bloggers welcome it has mad cool features to Promote YOU :) Thanks

Re: [twitter-dev] Search API returns only 15 results, even if rpp=100?

[Jonathan Reichhold]

There are plenty of results for this, but your url is encoded incorrectly

http://search.twitter.com/search.atom?q=microsoft+OR+%23ms+OR+lnk.ms+OR+msft+OR+%23surface&rpp=100

# is %23 in url-encoded form

As the query exists it is "microsoft OR " with a page reference.

Jonathan

On Tue, Jun 22, 2010 at 6:34 AM, John Kalucki  wrote:

> Try a less complex query, and you should get more results.
>
>
> On Mon, Jun 21, 2010 at 8:39 PM, Josh Santangelo 
> wrote:
> > For example, this query:
> >
> https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surface&page=1&rpp=100&result_type=recent
> >
> > Is there any way to get a larger number of results per page?
> >
> > thanks,
> > -josh
> >
>

Re: [twitter-dev] Incredibly slow graph processing

[Jesse Stay]

I've noticed slowness since weeks before the World Cup.  Is that all part of
the same issues you're fixing?  I'm not complaining - just wanted to make
sure this was logged as well so it got fixed as you guys try to revamp. (and
good luck on all the fixes)  I'm also trying to figure out what to tell
customers, and see what workarounds I can figure out in the meantime.

Thanks,

Jesse

On Tue, Jun 22, 2010 at 7:58 AM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> Hi Jesse,
>
> As has been mentioned on the Twitter blog (
> http://blog.twitter.com/2010/06/whats-happening-with-twitter.html ) and
> the status blog ( http://status.twitter.com/ ) we've been having some ups
> and downs lately, both with the World Cup and general networking issues with
> our servers. We're at a time where we're tuning things day-to-day, so I'm
> not surprised that you'll be seeing some sluggishness, increased error
> rates, and other symptoms of our current system state.
>
> Taylor
>
>
> On Tue, Jun 22, 2010 at 6:41 AM, Jesse Stay  wrote:
>
>> Right now it's taking forever to get through an entire followers list of
>> someone with over 50,000 followers.  It used to be much faster.  Did I miss
>> an announcement somewhere about API issues or response times?
>>
>> Thanks,
>>
>> Jesse
>>
>
>

[twitter-dev] Re: elliot haughin oAuth lib

[luisg]

Hello,

I'm using that library with CI too, but I did test that option...
what kind of issue?
BTW, you can retweet or edit user profile using haughin oAuth lib?

Thanks

On Jun 15, 7:41 pm, Peter Denton  wrote:
> Hello,
> Is anyone using elliot haughin oAuth lib for codeigniter? If so, Im having
> an issue with $this->twitter->call('friendships/exists' and would love to
> know if you have had experienced issues with that as well.
>
> Cheers

[twitter-dev] Re: Twitter Oauth Integration

[luisg]

web or desktop?

On Jun 22, 3:35 pm, "Anil kumar M.S"  wrote:
> Hi All,
> Can you please help me in integrating Oauth to our app  ,
>
> thanks
> Anilkumar

Re: [twitter-dev] availability of API

[Taylor Singletary]

Hi Mrinmoy,

By "add user as my friend" are you meaning that you want to the user to be
following your account?

This is all possible with both the API and @Anywhere (
http://dev.twitter.com/anywhere ).

If you went with an API-based integration, you'll need to implement OAuth
for the authentication leg of your integration (
http://dev.twitter.com/auth) and, provided that you've made it
abundantly clear to the user that the
act of approving the integration will result in them following a user, you'd
use the friendships/create API method
http://dev.twitter.com/doc/post/friendships/create/:id -- I'd recommend
asking the user to take a direct action to perform the follow operation
though, rather than automatically doing it.

Taylor


On Tue, Jun 22, 2010 at 7:08 AM, mrinmoy  wrote:

> Hi,
>
> We need to perform following works from our site.
>
> 1. Authenticate User using API
> 2. Add user as my friend
>
> Is there APIs available for these? Please reply. Thanking in advance
>
> We are thinking like bellow.
>
> 1. User will click a link on my website.
> 2. A popup will open asking login id and password of that user
> 3. User will give login credential and click join
> 4. That member will be added as my friend
>
> Regards,
> Mrinmoy Kundu
>

[twitter-dev] availability of API

[mrinmoy]

Hi,

We need to perform following works from our site.

1. Authenticate User using API
2. Add user as my friend

Is there APIs available for these? Please reply. Thanking in advance

We are thinking like bellow.

1. User will click a link on my website.
2. A popup will open asking login id and password of that user
3. User will give login credential and click join
4. That member will be added as my friend

Regards,
Mrinmoy Kundu

[twitter-dev] Re: trivial doubt

[themattharris]

Hi André,

Looking at your code it looks like you have added the line:
  id : 'twitterdiv'
but forgotten to put the comma after it.
If you add the comma the widget will work.

Matt

You don't need the  as the widget will
automatically create that for you.

On Jun 22, 6:25 am, André Lima  wrote:
> any suggestion of what I'm doing wrong here??
>
> On 21 jun, 22:00, André Luís Moura Lima  wrote:
>
>
>
> > Hello everybody,
> > I'm doing some tests with twitter widget profile...i do everything right on
> > the site,copy the resulting code to my html,but the twitter widget is not
> > shown,it isn't rendering.What can be wrong?for those who can help me,I will
> > post the code here.I guess I'm doing some confusion with some html tags like
> > body,head,html,etc...are they necessary to the code work right?anyway,i hope
> > so,cause this code that I'm posting is,obviously,an example...the real html
> > have head,body,html tags.anyway,here is the code:
> > 
> > http://widgets.twimg.com/j/2/widget.js";>
> > 
> > new TWTR.Widget({
> >   id : 'twitterdiv'
> >   version: 2,
> >   type: 'profile',
> >   rpp: 4,
> >   interval: 6000,
> >   width: 250,
> >   height: 300,
> >   theme: {
> >     shell: {
> >       background: '#33',
> >       color: '#ff'
> >     },
> >     tweets: {
> >       background: '#00',
> >       color: '#ff',
> >       links: '#4aed05'
> >     }
> >   },
> >   features: {
> >     scrollbar: true,
> >     loop: false,
> >     live: false,
> >     hashtags: true,
> >     timestamp: true,
> >     avatars: false,
> >     behavior: 'all'
> >   }}).render().setUser('andre').start();
>
> > 

Re: [twitter-dev] Incredibly slow graph processing

[Taylor Singletary]

Hi Jesse,

As has been mentioned on the Twitter blog (
http://blog.twitter.com/2010/06/whats-happening-with-twitter.html ) and the
status blog ( http://status.twitter.com/ ) we've been having some ups and
downs lately, both with the World Cup and general networking issues with our
servers. We're at a time where we're tuning things day-to-day, so I'm not
surprised that you'll be seeing some sluggishness, increased error rates,
and other symptoms of our current system state.

Taylor

On Tue, Jun 22, 2010 at 6:41 AM, Jesse Stay  wrote:

> Right now it's taking forever to get through an entire followers list of
> someone with over 50,000 followers.  It used to be much faster.  Did I miss
> an announcement somewhere about API issues or response times?
>
> Thanks,
>
> Jesse
>

Re: [twitter-dev] how to get original profile image url via API?

[Taylor Singletary]

Hi John,

There's no way to get the absolute original image url using the Twitter
API.

Thanks,
Taylor

On Mon, Jun 21, 2010 at 10:27 PM, John  wrote:

> Is there a way to get the original image url using the twitter API?
>
> Heres an example image:
>
> http://a3.twimg.com/profile_images/66869845/AJIMMY2.jpg
>

[twitter-dev] Twitter Oauth Integration

[Anil kumar M.S]

Hi All,
Can you please help me in integrating Oauth to our app  ,


thanks
Anilkumar

[twitter-dev] Incredibly slow graph processing

[Jesse Stay]

Right now it's taking forever to get through an entire followers list of
someone with over 50,000 followers.  It used to be much faster.  Did I miss
an announcement somewhere about API issues or response times?

Thanks,

Jesse

Re: [twitter-dev] Search API returns only 15 results, even if rpp=100?

[John Kalucki]

Try a less complex query, and you should get more results.


On Mon, Jun 21, 2010 at 8:39 PM, Josh Santangelo  wrote:
> For example, this query:
> https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surface&page=1&rpp=100&result_type=recent
>
> Is there any way to get a larger number of results per page?
>
> thanks,
> -josh
>

[twitter-dev] Re: trivial doubt

[André Lima]

any suggestion of what I'm doing wrong here??

On 21 jun, 22:00, André Luís Moura Lima  wrote:
> Hello everybody,
> I'm doing some tests with twitter widget profile...i do everything right on
> the site,copy the resulting code to my html,but the twitter widget is not
> shown,it isn't rendering.What can be wrong?for those who can help me,I will
> post the code here.I guess I'm doing some confusion with some html tags like
> body,head,html,etc...are they necessary to the code work right?anyway,i hope
> so,cause this code that I'm posting is,obviously,an example...the real html
> have head,body,html tags.anyway,here is the code:
> 
> http://widgets.twimg.com/j/2/widget.js";>
> 
> new TWTR.Widget({
>   id : 'twitterdiv'
>   version: 2,
>   type: 'profile',
>   rpp: 4,
>   interval: 6000,
>   width: 250,
>   height: 300,
>   theme: {
>     shell: {
>       background: '#33',
>       color: '#ff'
>     },
>     tweets: {
>       background: '#00',
>       color: '#ff',
>       links: '#4aed05'
>     }
>   },
>   features: {
>     scrollbar: true,
>     loop: false,
>     live: false,
>     hashtags: true,
>     timestamp: true,
>     avatars: false,
>     behavior: 'all'
>   }}).render().setUser('andre').start();
>
> 

[twitter-dev] Search API returns only 15 results, even if rpp=100?

[Josh Santangelo]

For example, this query:
https://search.twitter.com/search.atom?q=microsoft+OR+#ms+OR+lnk.ms+OR+msft+OR+#surface&page=1&rpp=100&result_type=recent

Is there any way to get a larger number of results per page?

thanks,
-josh

[twitter-dev] Display most recent post, load previous on click

[Andy Joe]

At a prototype wordpress site I'm building, I've got a twitter bird,
and when you hover over that bird, a speech bubble pops up (which has
some placement issues still in safari but looks fine in firefox).
Inside that speech bubble I want my most recent tweet to display. But
when I click on the bird, I want the previous tweet to display, and
each click thereafter just keeps going back to the previous and
previous tweet.

I'm a novice even at CSS, but I find that the forums out there support
my level of learning, unless they are forums regarding API's. I can
decode the meaning behind html, css, and maybe even php easier than
the english used on this site. So I'm just wondering if anyone here
could give me a hand. What would be the best way to implement what
I've mentioned above?

Re: [twitter-dev] Re: Recent Places-related API enhancements & more to come...

[znmeb]

Quoting David Helder :


The geo field is the user's (or tweet's) exact location.  The place
field, whether a POI, neighborhood, city, or admin, contains the
place's location.  Today POIs are always points, but in the future
there may be some polygons (e.g. stadiums, malls, amusement parks).
In this case the exact location would matter.

A place-annotated tweet will show up in the streaming API, even if
it doesn't have an exact location.

David
Twitter Geo Team


The POI data I've collected show that they are coded as four-sided  
polygons even if they are points, with all four "corners" of the  
polygon being equal to the "point". And sometimes the "geo" field is  
present and sometimes it isn't. And sometimes the "coordinates" field  
is present and sometimes it isn't. IIRC the geo and coordinates field  
have latitude first and longitude second, but it's the other way  
around for the "corners" of polygons!


Can we get this stuff documented so I'm not writing code that matches  
things that will change? And so I can file bugs when something doesn't  
work, like searching for places? Conversely, is there value in an open  
source library that monitors the "sample" streaming API and announces  
to the world when Twitter starts sending something new or starts  
sending stuff in a new format? ;-)


I've been in the "industry" a long time - normally Twitter's pretty  
good about announcing major changes, but "little stuff" like geo data  
formats tends to just get changed without documentation and sometimes  
without even warnings. In the case of User Streams, we *know* it's a  
developer preview and subject to change. But something like places is  
a *released* feature, and I think that kind of thing should happen  
*with* documentation on or preferably *before* release.