Re: [twitter-dev] Method /version/statuses/user_timeline.json not functioning properly

[kamesh SmartDude]

The Requrl u Supplied
http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?page=1?
include_rts=true
is wrong. and in the headers u can remove the parameters

correct one is

http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***&page=1&;
include_rts=true

And the headers

OAuth oauth_consumer_key="**",
  oauth_nonce="PaIdH40QrMznwDjGbD75a_hRDuE7Ys",
  oauth_signature_method="HMAC-SHA1",
  oauth_timestamp="1308206637",
  oauth_token="**",
  oauth_version="1.0",
  oauth_signature="YJ8LsrrXd13v0YLtnKSRdHScjaQ%3D"

Here in Headers removed the screen_name, include_rts, and page parameters

//kamesh



On Thu, Jun 16, 2011 at 12:19 PM, Georgooty varghese wrote:

> Dear Twitter,
>
> I have found some mismatching in header value.
>
>
> Rquest url is given below,
>
> http://api.twitter.com/1/statuses/user_timeline.json?include_rts=true&oauth_consumer_key=&oauth_nonce=15d_Hx5zHE_9ntMQZR30RbGI6UAeZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1308205453&oauth_token**&oauth_version=1.0&page=1
> &screen_name=MayuriModa9&oauth_signature=e2eZoO42zO%2B95IRf6QHhvxfnRP0%3D
>
> In response I got json response.
> But in header values ,I have found,
>
> Status Value :200 OK
> :X-Warning Value :Invalid OAuth credentials detected
>
> Its working fine. But I have a doubt, In future any problem?
>
> So I have changed the http request to authentication mechanism to rquest
> url to auth header.
>
> request url
>
> http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?page=1?include_rts=true
>
> header is given below,
> OAuth include_rts="true",oauth_consumer_key="**",
> oauth_nonce="PaIdH40QrMznwDjGbD75a_hRDuE7Ys",
> oauth_signatu re_method="HMAC-SHA1",
> oauth_timestamp="1308206637",oauth_token="**",
> oauth_version="1.0",page="1",screen_name="",
> oauth_signature="YJ8LsrrXd13v0YLtnKSRdHScjaQ%3D"
>
>
> But I didnt got the result
> ,
>
> got 404 Not Found error.
>
> Please  help me to solve this issue.
>
> Regards,
> Geoirge
>
>  --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Method /version/statuses/user_timeline.json not functioning properly

[Georgooty varghese]

Dear Twitter,

I have found some mismatching in header value.


Rquest url is given below,

http://api.twitter.com/1/statuses/user_timeline.json?include_rts=true&oauth_consumer_key=&oauth_nonce=15d_Hx5zHE_9ntMQZR30RbGI6UAeZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1308205453&oauth_token**&oauth_version=1.0&page=1
&screen_name=MayuriModa9&oauth_signature=e2eZoO42zO%2B95IRf6QHhvxfnRP0%3D

In response I got json response.
But in header values ,I have found,

Status Value :200 OK
:X-Warning Value :Invalid OAuth credentials detected

Its working fine. But I have a doubt, In future any problem?

So I have changed the http request to authentication mechanism to rquest url
to auth header.

request url

http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?page=1?include_rts=true

header is given below,
OAuth include_rts="true",oauth_consumer_key="**",
oauth_nonce="PaIdH40QrMznwDjGbD75a_hRDuE7Ys",
oauth_signatu re_method="HMAC-SHA1",
oauth_timestamp="1308206637",oauth_token="**",
oauth_version="1.0",page="1",screen_name="",
oauth_signature="YJ8LsrrXd13v0YLtnKSRdHScjaQ%3D"


But I didnt got the result
,

got 404 Not Found error.

Please  help me to solve this issue.

Regards,
Geoirge

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Centralizar background - center background

[Jota Oliveira]

Porque o background do perfil não é centralizado?
isso resolveria o problema de diferentes resoluções.

Why profile background is not centered?
This should resolve the diferent resolution problems.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Error with Web Intents Javascript Events

[Matt Harris]

Thanks for the update Mike,
Is this hosted on a webpage we can access, or can you put a test page up
that we can hit?

Best,
@themattharris 
Developer Advocate, Twitter



On Wed, Jun 15, 2011 at 6:47 PM, MManalo  wrote:

> Hi Matt,
>
> Thanks for your help with this. No JS errors or warnings. The button
> just does not fire any sort of event when we call it.
>
> Again it works just fine in IE8 and Firefox, sending data to Omniture.
> But unfortunately, nothing happens when clicked in IE7.
>
> On Jun 14, 9:27 pm, Matt Harris  wrote:
> > Hey,
> >
> > Does IE7 report any javascript errors or warnings?
> > Other than the events, does the button render and perform correctly?
> >
> > Best
> > @themattharris <
> https://twitter.com/intent/follow?screen_name=themattharris>
> > Developer Advocate, Twitter
> >
> > On Tue, Jun 14, 2011 at 10:56 AM, MManalo 
> wrote:
> > > Hey everyone,
> >
> > > We have been trying to implement tracking on the tweet buttons that
> > > are featured on our sites. We used the method recommended to us on
> > > this page:
> >
> > >https://dev.twitter.com/pages/intents-events
> >
> > > Upon testing, we found that the button sends data to Omniture, our web
> > > analytics provider, when we use IE8 and Firefox to access the site,
> > > but it does not happen when using IE7.
> >
> > > I was wondering if there may be any specific reason as to why, or what
> > > might we be doing wrong? Thanks!
> >
> > > --
> > > Twitter developer documentation and resources:
> https://dev.twitter.com/doc
> > > API updates via Twitter:https://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >https://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >https://groups.google.com/forum/#!forum/twitter-development-talk
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Error with Web Intents Javascript Events

[MManalo]

Hi Matt,

Thanks for your help with this. No JS errors or warnings. The button
just does not fire any sort of event when we call it.

Again it works just fine in IE8 and Firefox, sending data to Omniture.
But unfortunately, nothing happens when clicked in IE7.

On Jun 14, 9:27 pm, Matt Harris  wrote:
> Hey,
>
> Does IE7 report any javascript errors or warnings?
> Other than the events, does the button render and perform correctly?
>
> Best
> @themattharris 
> Developer Advocate, Twitter
>
> On Tue, Jun 14, 2011 at 10:56 AM, MManalo  wrote:
> > Hey everyone,
>
> > We have been trying to implement tracking on the tweet buttons that
> > are featured on our sites. We used the method recommended to us on
> > this page:
>
> >https://dev.twitter.com/pages/intents-events
>
> > Upon testing, we found that the button sends data to Omniture, our web
> > analytics provider, when we use IE8 and Firefox to access the site,
> > but it does not happen when using IE7.
>
> > I was wondering if there may be any specific reason as to why, or what
> > might we be doing wrong? Thanks!
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Twitter JSON feed falls out with php

[Patrick Kennedy]

You are accessing API in an unauthentic way and without oAuth, and you
are running out of API calls.  You can add a service method to track
remaining  API calls that you have left to confirm this, e.g,
http://api.twitter.com/1/account/rate_limit_status.{xml | json}.  You
can research from thousands of PHP tutorials and examples out their
and improve your code base to use oAuth.

Check out http://dev.twitter.com/pages/oauth_single_token to start
into oAuth for your single user feed application.

~Patrick

On Jun 13, 9:47 am, Andreas Voss  wrote:
> Hey Twitter Developers.
>
> I've had a bit om a problem with my "home made" twitter feed plugin
> for my website, sometimes it just wont load the feed for like 30
> minutes and then it starts working again. Is there any of you familiar
> with this kind of error?
>  $user = "andreasvoss";
> $url = "http://twitter.com/statuses/user_timeline/".$user.".json";;
> $json = file_get_contents($url);
> $data = json_decode($json);
>
> foreach($data as $val){
>         $screen_name = $val->user->screen_name;
>         $tweet = $val->text;
>         $date = strtotime($val->created_at);
> ?>
>               @ span>
>               
>               for  span>
> 
> ?>
>
> Kind regards Andreas Voss

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: New Status Using A Query String

[Arnaud Meunier]

Hey there,

This has just been deployed. The old "status" endpoints are
now seamlessly redirected (HTTP 301) to the share intent. Please note that
we still encourage you to replace these old URLs (i.e.
http://twitter.com/?status=hello and http://twitter.com/home/?status=hello)
for the Share Intent (i.e. http://twitter.com/intent/tweet?text=hello)

Arnaud / @rno 



On Fri, Jun 3, 2011 at 3:05 PM, Arnaud Meunier  wrote:

> Bumping this thread to give you guys the last update on this bug.
>
> As you know, the "status" parameter is an old hack belonging to the
> classic web version of twitter.com. On the other hand, Web Intents
> were developed specifically for this purpose, they are optimized to
> load quickly, they are mobile friendly, and we fully support them on
> the API side.
>
> We've heard your feedback: We know there are still many
> implementations of the old "status" hack out there, and we understand
> that it's painful to change all these URLs.
>
> That's why we're going to seamlessly redirect these old endpoints to
> the share intent. That will fix the issue with legacy integrations,
> without requiring any changes on your side. Please note that we
> encourage you to replace these old URLs for the Share Intent (that
> will save an unnecessary 301 hit).
>
> While we don't yet have an ETA for this change, we are getting closer
> to rolling this out and wanted to give you as much advance notice as
> we could.
>
> Arnaud / @rno
>
>
> On May 17, 10:49 pm, DustyReagan  wrote:
> > Right on. Thanks for the update Arnaud! :)
> >
> > On May 17, 7:55 pm, omegdadi  wrote:
> >
> >
> >
> >
> >
> >
> >
> > > +1. Thanks for the update Arnaud. This is affecting all of our
> customers at
> > > the moment.
> >
> > > Cheers,
> > > Omar
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] oauth_bridge_code Disabled?

[DustyReagan]

Was oauth_bridge_code disabled? If so how are we suppost to bridge
@anywhere OAuth logins to the REST API?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Sharing a Twitter with Twitter intent in Windows Phone 7

[Luis Guerrero]

Hi all!

I'm trying to share a text and an Url on the Twitter intent from Windows 
Phome 7, the final url is:

http://twitter.com/share?text=Acampada+Sol+condena+la+violencia+en+Madrid+y+Barcelona&url=http%3a%2f%2fpolitica.elpais.com%2fpolitica%2f2011%2f06%2f15%2factualidad%2f1308146157_022121.html

This url is working on the desktop browser, but not in the Windows Phone 7 
IE Browser, anyone experienced this issue before, Am I missing something?

It's only appears the text, an image is attached to this post.

Thanks.


-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk
<>

Re: [twitter-dev] What changed in the OAuth signature process last few weeks?

[Taylor Singletary]

Hi there,

We're now a bit stricter with how we evaluate the validity of requests.

Few things to look into for starters -- hopefully will help you discover the
subtle issue:

  - Are you setting your Content-Type:  x-www-form-urlencoded when POSTing
any kind of POST data?
  - Make sure that your signature basestring is properly sorting your
parameters and that any param values requiring percent-encoding are properly
encoded. If your POST body contains any characters that need to be
%-encoded, they'll need to be %-encoded again for your signature base string
  - Double verify that your consumer key and secret are correct and being
used at the right steps.
  - Double verify that you're specifying an oauth_token for resource
requests and that you've signed the request with the composite signing key
made up of your consumer secret and the access token secret, joined by a "&"
character.
  - If you're using header based auth, make sure that you aren't sending
oauth_* parameters in multiple locations like the query string in addition
to the header

Thanks,
@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 1:20 PM, @giberti  wrote:

> A few months ago I wrote an application that interfaced with two API
> calls: statuses/user/timeline and statuses/update. It has been working
> fine until about seven days ago when I started receiving 401 status
> codes when reading the user timeline.
>
> I'm using a hand rolled OAuth / Twitter library that I built using the
> examples provided on the developer docs. I'm not sure where to go from
> here.
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Couldn't resolve host 'stream.twitter.com

[Tom van der Woerdt]

Toms-MacBook-Pro:~ tom$ host stream.twitter.com
stream.twitter.com has address 199.59.148.138

You should probably check your server's DNS settings.

Tom


On 6/15/11 10:47 PM, Perez2, Rocio (GE, Corporate, consultant) wrote:


Hi!!

I was using the Search API but now I want to change to Sream API. I 
have this  doubt,  I hope you can help me:


First I try this: 
curlhttp://stream.twitter.com/1/statuses/sample.json?delimited=length  
-uAnyTwitterUser:Password

Since prompt, but it return this:

Couldn't resolve host 'stream.twitter.com

Is there something wrong with my instruction? Or I'm missing something?

I'd appreciated your help.

Thank you J

--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: 
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk 



--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Couldn't resolve host 'stream.twitter.com

[Scott Wilcox]

Being unable to resolve the host is a network condition between you and the 
Twitter API. I'd check your DNS settings on your machine/server.

stream.twitter.com is up and working fine for me.

On 15 Jun 2011, at 21:47, Perez2, Rocio (GE, Corporate, consultant) wrote:

> Hi!!
> I was using the Search API but now I want to change to Sream API. I have this 
>  doubt,  I hope you can help me:
>  
> First I try this: curl 
> http://stream.twitter.com/1/statuses/sample.json?delimited=length 
> -uAnyTwitterUser:Password
> Since prompt, but it return this:
> Couldn't resolve host 'stream.twitter.com
>  
> Is there something wrong with my instruction? Or I’m missing something?
>  
> I’d appreciated your help.
>  
> Thank you J
>  
> 
> -- 
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> https://groups.google.com/forum/#!forum/twitter-development-talk

--
Scott Wilcox

@dordotky | sc...@dor.ky | http://dor.ky
+44 (0) 7538 842418 | +1 (646) 827-0580



-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Couldn't resolve host 'stream.twitter.com

[Perez2, Rocio (GE, Corporate, consultant)]

Hi!! 

I was using the Search API but now I want to change to Sream API. I have
this  doubt,  I hope you can help me:

 

First I try this: curl
http://stream.twitter.com/1/statuses/sample.json?delimited=length
-uAnyTwitterUser:Password

Since prompt, but it return this:

Couldn't resolve host 'stream.twitter.com

 

Is there something wrong with my instruction? Or I'm missing something?

 

I'd appreciated your help.

 

Thank you J

 

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] What changed in the OAuth signature process last few weeks?

[@giberti]

A few months ago I wrote an application that interfaced with two API
calls: statuses/user/timeline and statuses/update. It has been working
fine until about seven days ago when I started receiving 401 status
codes when reading the user timeline.

I'm using a hand rolled OAuth / Twitter library that I built using the
examples provided on the developer docs. I'm not sure where to go from
here.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Direct message change and the authentication URL

[James Estes]

I think this was addressed in the "A new permission level thread.

"> You said you were restricting this permission to the OAuth
/authorize web flow only. Will /oauth/authenticate  (Sign in with
Twitter) support the new permission?
The R/W/DM permission can only be granted through the /oauth/authorize
route. Sign in with Twitter cannot be used to grant R/W/DM.

We understand applications may use other methods of authentication
like Sign in with Twitter as well. For this reason, if a user has
authorised your application for R/W/DM and you direct them through
Sign in with Twitter, we will respect the existing access token
permission. This means you can use Sign in with Twitter after a user
has authorized your application for R/W/DM."

On Wed, Jun 15, 2011 at 2:20 PM, Craig Walls  wrote:
>
> I've updated my app settings to be "Read, Write, and Direct Messages",
> but when I go through the authentication page (not the normal OAuth
> authorization page), it still tells me that the app won't be able to
> access DMs after June 30th. Am I missing something or should that
> message no longer appear now that I've changed the settings?
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Direct message change and the authentication URL

[Craig Walls]

I've updated my app settings to be "Read, Write, and Direct Messages",
but when I go through the authentication page (not the normal OAuth
authorization page), it still tells me that the app won't be able to
access DMs after June 30th. Am I missing something or should that
message no longer appear now that I've changed the settings?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Create your own trends from only people you follow

[Scott Wilcox]

You'll need to use the streaming API to collect the timeline and then process 
that data yourself to deduce the most frequently used terms.

Streaming API documentation can be found at http://dev.twitter.com/doc

On 15 Jun 2011, at 19:20, Hugh Hopkins wrote:

> Heya,
> 
> I'm a student who has just started a student news website called
> http://www.sonews.co.uk/ we also tweet a lot on 
> http://twitter.com/#!/sellyoaknews.
> I was hoping to create local trends from only the accounts that
> @sellyoaknews follows and was wondering how this would be done?
> 
> So for example, I will be able to put on the website the 5 or 10 most
> talked about items from people I only follow. This would have a huge
> number of benefits because it would directly relate to the students we
> follow plus it would mean it wouldn't be susecptible to spam.
> 
> If any of you could help point me in the right direction that would be
> great!!
> 
> thanks and all the best,
> 
> Hugh Hopkins
> 
> http://twitter.com/#!/hughhopkins

--
Scott Wilcox

@dordotky | sc...@dor.ky | http://dor.ky
+44 (0) 7538 842418 | +1 (646) 827-0580



-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Create your own trends from only people you follow

[Hugh Hopkins]

Heya,

I'm a student who has just started a student news website called
http://www.sonews.co.uk/ we also tweet a lot on 
http://twitter.com/#!/sellyoaknews.
I was hoping to create local trends from only the accounts that
@sellyoaknews follows and was wondering how this would be done?

So for example, I will be able to put on the website the 5 or 10 most
talked about items from people I only follow. This would have a huge
number of benefits because it would directly relate to the students we
follow plus it would mean it wouldn't be susecptible to spam.

If any of you could help point me in the right direction that would be
great!!

thanks and all the best,

Hugh Hopkins

http://twitter.com/#!/hughhopkins

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] API Introspection

[joao aires]

Hi,

I don't know if this questions was already answered or not but I was
wondering if there's any way of programmatically get all the methods
supported by the twitter API. Just like, for instance, flickr has.

I'm creating a plugin based application and I intend to provide a
wrapper for the twitter api. Therefore, such feature would be
wonderful in order to not get my wrapper deprecated really soon.

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Introducing the Follow Button

[David Huang]

Hi all,

I was testing the new Follow button on my webpage and noticed that
"one-click" only works when the user have signed in to Twitter during
the same browsing session. If I relaunched the browser, even though
I'm still logged in to Twitter, clicking the Follow button would open
a popup. Am I missing anything, or is this the expected behavior?

Thanks,
David

On May 31, 1:07 pm, Arnaud Meunier  wrote:
> Hey developers,
>
> Today we're launching theFollowButton!  Similar to the Tweet Button,
> it's a new widget that lets users easilyfollowa Twitter account from
> any web page. TheFollowButton has a single clickfollowexperience,
> simple implementation model, and is configurable to fit the needs of
> your website.
>
> Read our announcement on the Twitter blog, and use the resources below
> to set up your ownFollowButton:
>
> - Create aFollowButton here:http://twitter.com/about/resources/followbutton
> - Detailed documentation:http://dev.twitter.com/pages/follow_button
>
> We’ve also added a Javascript layer to our Buttons and Web Intents
> that makes it possible for you to detect how users are interacting
> with these tools, and to hook them up to your own web analytics. More
> details on:http://dev.twitter.com/pages/intents-events
>
> We're excited to see how you guys will implement theFollowButton.
> Let us know what you think, or if you have any questions.
>
> Arnaud / @rno

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] New YouTube @twitterapi Channel and the Devnest Videos

[Jason Costa]

Hi everyone,

We're excited to have a new YouTube Twitter API channel available:

http://youtube.com/twitterapi

In addition to putting out this new channel, we've uploaded our first
set of videos there - the recordings of our Devnest event. This
includes talks from @dickc, @rsarver, @quora, @klout, @dataminr,
@guardian, plus the Q&A session.

Going forward, we'd like to add a lot more content, and want to ask
you: what would you like to see on this channel? Interviews with
engineers on how and why they built something? An overview of how to
consume the Streaming API? An OAuth debugging tutorial? We'd love to
know what you'd like to see.

Additionally, if you'd like to submit a video tutorial yourself,
please send me the file (jasonco...@twitter.com). We'll review it and
potentially post it to the channel.

Thanks,

@jasoncosta

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] error 401 from oauth, starting a few days ago

[arlomedia]

Last July I installed oauth-php to display items from my user timeline
on my website home page. I then copied the setup to another website
with another Twitter account and both have been working fine.

Then a few days ago both websites started returning error code 401,
"This method requires authentication." I can successfully run the
request_token command, but when I run the statuses/user_timeline
command I receive this error.

After experimenting with my own code for a while, I went back to
oauth's Twitter example code here:
http://code.google.com/p/oauth-php/source/browse/trunk/example/client/twoleggedtwitter.php.
This worked fine when accessing the public timeline, but when I
changed it to access the user timeline, I received the same
authentication error.

I've updated to the latest version of oauth, but that made no
difference. I also reset my consumer key and consumer secret key and
that made no difference, either.

Can someone tell me what might have changed in the last few days, or
how I should proceed with troubleshooting this?

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] error 401 from oauth, starting a few days ago

[Taylor Singletary]

Hi Arlo,

Happy to help.

First, Twitter doesn't support any two-legged OAuth aside from the mandatory
two-leggedness of the request token step of OAuth and the variant xAuth
flow. Two-legged OAuth is where you sign requests and present your API key
but you have no "user context" (the access/oauth_token). If you're signing
an API request with OAuth, you must include an oauth_token to provide
context on the user who is making the request.

We're more strictly enforcing correctness in OAuth signatures and requests
now. Is the account that you're trying to retrieve the user_timeline for a
protected account? Are you using API urls in the style of
http://api.twitter.com/1/statuses/home_timeline.json ?

If you want to access a resource without a user context, you should simply
directly request the resource without attaching any kind of authorization to
the request at all.

Thanks,
@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 10:09 AM, arlomedia  wrote:

> Last July I installed oauth-php to display items from my user timeline
> on my website home page. I then copied the setup to another website
> with another Twitter account and both have been working fine.
>
> Then a few days ago both websites started returning error code 401,
> "This method requires authentication." I can successfully run the
> request_token command, but when I run the statuses/user_timeline
> command I receive this error.
>
> After experimenting with my own code for a while, I went back to
> oauth's Twitter example code here:
>
> http://code.google.com/p/oauth-php/source/browse/trunk/example/client/twoleggedtwitter.php
> .
> This worked fine when accessing the public timeline, but when I
> changed it to access the user timeline, I received the same
> authentication error.
>
> I've updated to the latest version of oauth, but that made no
> difference. I also reset my consumer key and consumer secret key and
> that made no difference, either.
>
> Can someone tell me what might have changed in the last few days, or
> how I should proceed with troubleshooting this?
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] How do I register a non-existent app?

[Taylor Singletary]

Hi Tamara,

Just use placeholder data on dev.twitter.com/apps while registering your
application. You can use your @username as the name for your application or
something similar. For the callback URL -- this value is really just a
placeholder for all intents and purposes anyway, and so as long as you can
provide a valid URL there, you should be fine. With OAuth, you must specify
your callback URL explicitly on the request token step anyway.

After creating your application record, you can then use your API key and
secret to negotiate OAuth tokens and make calls from there. API methods that
don't require authentication also don't require that you use an API key to
access the resource, instead you could just simply explore the API using
curl or a simple HTTP library and move on from there.

Many beginners with OAuth find the tips on this page useful as well:
http://dev.twitter.com/pages/oauth_single_token

@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 9:58 AM, t.williams wrote:

> Hello Developers:
>
> I have always heard of Twitter but just recently created a Twitter
> account. I want to develop an app which will use the Twitter API and
> more specifically the REST API to collect public Tweets and then
> perform some processing. I have been reading the documentation but
> still have a long way to go. Therefore, my concern is that my
> application is still in the design phase of the software lifecyle
> which means that I have not yet decided on a name and there is no
> website or callback URL. How then would I be able to perform a
> registration? I wanted the flexibility to code in functions or classes
> and test by making calls to the API instead of waiting until the full
> application was complete. However, in order to get developer access to
> the Twitter API I need to register the app and also according to the
> Authentication pages, registration is needed in order to use OAuth. I
> also looked at Twitter4J which also requires the use of OAuth. I am
> grateful for any advise that you can give. Thank you.
>
> Cheers,
> T Williams
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Twitter search question

[Casey Wilson]

Hi Brian, Thanks for the quick response.

Here's something strange regarding the issue. When I go in and update the email
address (when it prompts me that the mail server had issues) the
tweets pop back
up within results in less than an hour. Is that working as it should?

Also, sometimes when I log back in it tells me again to update my
email. If I don't,
my tweets stop showing in the results until I do.

I don't know if I found a bug or what. I'll open a ticket to see if
any of them have been
flagged for anything.

Let me know if you need any further info from me.

Thanks,

-Casey


On Tue, Jun 14, 2011 at 4:16 PM, Brian Sutorius  wrote:
> Hey Casey,
> Not all Tweets make it into our search index. For more information,
> check out this article on our help center: 
> https://support.twitter.com/articles/42646.
> If you think your account has been affected, please fill out the form
> linked from the bottom of that page while logged in as the account,
> and we'll get back to you.
>
> Brian Sutorius
> Twitter API Policy
>
> On Jun 14, 9:06 am, Casey Wilson  wrote:
>> Hey all, I understand this is probably the wrong forum for this, but
>> if you could point me in the right direction I'd be appreciative.
>>
>> We have a question for the search side of things. We've had some niche
>> related sites using twitter for a long time now.
>>
>> Here within the last month or two we've noticed some of our accounts
>> getting flagged as not being able to be emailed (Mail server went
>> down) and since then
>> accounts have been going completely missing from search.
>>
>> We were wondering who to talk to about this, as I've gotten a few
>> emails on the issue and I don't know what to tell our users.
>>
>> Thanks!
>>
>> -Casey
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group: 
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] How do I register a non-existent app?

[t.williams]

Hello Developers:

I have always heard of Twitter but just recently created a Twitter
account. I want to develop an app which will use the Twitter API and
more specifically the REST API to collect public Tweets and then
perform some processing. I have been reading the documentation but
still have a long way to go. Therefore, my concern is that my
application is still in the design phase of the software lifecyle
which means that I have not yet decided on a name and there is no
website or callback URL. How then would I be able to perform a
registration? I wanted the flexibility to code in functions or classes
and test by making calls to the API instead of waiting until the full
application was complete. However, in order to get developer access to
the Twitter API I need to register the app and also according to the
Authentication pages, registration is needed in order to use OAuth. I
also looked at Twitter4J which also requires the use of OAuth. I am
grateful for any advise that you can give. Thank you.

Cheers,
T Williams

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Jeff]

Taylor,

Thanks so much for you help on this! I moved the arguments from the
url to an array so they can be sorted with the others and that fixed
the problem. It works now as before.

Jeff



On Jun 15, 10:54 am, Taylor Singletary 
wrote:
> Thanks Jeff -- I can see the problem instantaneously -- your query
> parameters are attached to the end of the escaped URL rather than be sorted
> and ordered with the rest of the "parameters" (including the OAuth ones).
>
> You correct signature base string would be:
> GET&http://api.twitter.com/1/followers/ids.json&cursor%3D-1%26oauth_consu...
>
> Notice how the base URL contains no query parameters here, cursor is the
> first parameter after the separator ("&") as c comes before o, and user_id
> is the final parameter in the sequence as u comes after o.
>
> @episod  - Taylor
> Singletary
>
>
>
>
>
>
>
> On Wed, Jun 15, 2011 at 8:43 AM, Jeff  wrote:
> > Here is a dump of $signatureBaseString
>
> > GET&http%3A%2F%2Fapi.twitter.com%2F1%2Ffollowers%2Fids.json%3Fcursor
> > %3D-1%26user_id%3D130232354&oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q
> > %26oauth_nonce
> > %3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-
> > SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-
> > gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0
>
> > On Jun 15, 10:34 am, Taylor Singletary 
> > wrote:
> > > Hi Jeff,
>
> > > This is close to what I'm looking for -- it has the authorization header
> > > which is important to see -- but what will really help us debug with you
> > is
> > > the signature base string -- it's a string that contains many of the same
> > > values from the authorization header but presented in a specific format
> > --
> > > this is the string that is signed to create your oauth_signature. This
> > > signature base string is usually the key to all OAuth problems, as the
> > order
> > > of parameters and particular encoding of them in relation to the
> > parameters
> > > on your query string or POST body are extremely important and somewhat
> > > fragile.
>
> > > I'm not sure which version of EpiOAuth you're using, but there's likely a
> > > method similar to this one. The value you want to debug/capture here is
> > > $signatureBaseString.
>
> > >  protected function generateSignature($method = null, $url = null,
> > > $params = null)
> > >   {
> > >     if(empty($method) || empty($url))
> > >       return false;
>
> > >     // concatenating and encode
> > >     $concatenatedParams =
> > > $this->encode_rfc3986($this->buildHttpQueryRaw($params));
>
> > >     // normalize url
> > >     $normalizedUrl = $this->encode_rfc3986($this->normalizeUrl($url));
> > >     $method = $this->encode_rfc3986($method); // don't need this but why
> > not?
>
> > >     $signatureBaseString =
> > "{$method}&{$normalizedUrl}&{$concatenatedParams}";
> > >     return $this->signString($signatureBaseString);
> > >   }
>
> > > @episod  - Taylor
> > > Singletary
>
> > > On Wed, Jun 15, 2011 at 8:22 AM, Jeff  wrote:
> > > > Taylor,
>
> > > > Thanks for the response. Hopefully, this is what you need. I dumped it
> > > > right before the request.
>
> > > > [
> > > >   "Expect:",
> > > >   "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
> > > > \/ids.json\",
> > > >                   oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
> > > >                   oauth_token=\"130232354-
> > > > gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
> > > >                   oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
> > > >                   oauth_timestamp=\"1308151065\",
> > > >                   oauth_signature_method=\"HMAC-SHA1\",
> > > >                   oauth_version=\"1.0\",
> > > >                   oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
> > > > \"",
> > > >   "User-Agent: "
> > > > ]
>
> > > > On Jun 15, 10:05 am, Taylor Singletary 
> > > > wrote:
> > > > > This means that your signing is slightly wrong (and likely has been
> > > > slightly
> > > > > wrong for some time) when you're using parameters in your request.
> > Can
> > > > you
> > > > > detail the signature base string and authorization header you are
> > using
> > > > when
> > > > > building this request?
>
> > > > > @episod  - Taylor
> > > > > Singletary
>
> > > > > On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
>
> > > > > > Tuesday morning around 10am CDT I noticed a change in the API
> > > > > > endpoint /version/followers/ids in how it operates.
>
> > > > > > If you provide the cursor parameter, such as:
>
> > > > > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns
> > data
> > > > > > correctly, however it also return the error warning "Invalid OAuth
> > > > > > credentials detected". Here is the response from the API.
>
> > > > > >   "data":{
>
> >  "responseText":"{\"previous_cursor\":0,\"next_cu

Re: [twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Taylor Singletary]

Thanks Jeff -- I can see the problem instantaneously -- your query
parameters are attached to the end of the escaped URL rather than be sorted
and ordered with the rest of the "parameters" (including the OAuth ones).

You correct signature base string would be:
GET&
http://api.twitter.com/1/followers/ids.json&cursor%3D-1%26oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q%26oauth_nonce%3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0%26user_id%3D130232354

Notice how the base URL contains no query parameters here, cursor is the
first parameter after the separator ("&") as c comes before o, and user_id
is the final parameter in the sequence as u comes after o.

@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:43 AM, Jeff  wrote:

> Here is a dump of $signatureBaseString
>
> GET&http%3A%2F%2Fapi.twitter.com%2F1%2Ffollowers%2Fids.json%3Fcursor
> %3D-1%26user_id%3D130232354&oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q
> %26oauth_nonce
> %3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-
> SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-
> gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0
>
>
>
> On Jun 15, 10:34 am, Taylor Singletary 
> wrote:
> > Hi Jeff,
> >
> > This is close to what I'm looking for -- it has the authorization header
> > which is important to see -- but what will really help us debug with you
> is
> > the signature base string -- it's a string that contains many of the same
> > values from the authorization header but presented in a specific format
> --
> > this is the string that is signed to create your oauth_signature. This
> > signature base string is usually the key to all OAuth problems, as the
> order
> > of parameters and particular encoding of them in relation to the
> parameters
> > on your query string or POST body are extremely important and somewhat
> > fragile.
> >
> > I'm not sure which version of EpiOAuth you're using, but there's likely a
> > method similar to this one. The value you want to debug/capture here is
> > $signatureBaseString.
> >
> >  protected function generateSignature($method = null, $url = null,
> > $params = null)
> >   {
> > if(empty($method) || empty($url))
> >   return false;
> >
> > // concatenating and encode
> > $concatenatedParams =
> > $this->encode_rfc3986($this->buildHttpQueryRaw($params));
> >
> > // normalize url
> > $normalizedUrl = $this->encode_rfc3986($this->normalizeUrl($url));
> > $method = $this->encode_rfc3986($method); // don't need this but why
> not?
> >
> > $signatureBaseString =
> "{$method}&{$normalizedUrl}&{$concatenatedParams}";
> > return $this->signString($signatureBaseString);
> >   }
> >
> > @episod  - Taylor
> > Singletary
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Jun 15, 2011 at 8:22 AM, Jeff  wrote:
> > > Taylor,
> >
> > > Thanks for the response. Hopefully, this is what you need. I dumped it
> > > right before the request.
> >
> > > [
> > >   "Expect:",
> > >   "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
> > > \/ids.json\",
> > >   oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
> > >   oauth_token=\"130232354-
> > > gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
> > >   oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
> > >   oauth_timestamp=\"1308151065\",
> > >   oauth_signature_method=\"HMAC-SHA1\",
> > >   oauth_version=\"1.0\",
> > >   oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
> > > \"",
> > >   "User-Agent: "
> > > ]
> >
> > > On Jun 15, 10:05 am, Taylor Singletary 
> > > wrote:
> > > > This means that your signing is slightly wrong (and likely has been
> > > slightly
> > > > wrong for some time) when you're using parameters in your request.
> Can
> > > you
> > > > detail the signature base string and authorization header you are
> using
> > > when
> > > > building this request?
> >
> > > > @episod  - Taylor
> > > > Singletary
> >
> > > > On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
> >
> > > > > Tuesday morning around 10am CDT I noticed a change in the API
> > > > > endpoint /version/followers/ids in how it operates.
> >
> > > > > If you provide the cursor parameter, such as:
> >
> > > > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns
> data
> > > > > correctly, however it also return the error warning "Invalid OAuth
> > > > > credentials detected". Here is the response from the API.
> >
> > > > >   "data":{
> > > > >
>  "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> > > > > \"previous_cursor_str\":\"0\",\"ids\":
> > > > > [222126862,95945240,169607024,148845934,954

[twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Jeff]

Here is a dump of $signatureBaseString

GET&http%3A%2F%2Fapi.twitter.com%2F1%2Ffollowers%2Fids.json%3Fcursor
%3D-1%26user_id%3D130232354&oauth_consumer_key%3DOlPht6d2h3N1XYwCpCyx5Q
%26oauth_nonce
%3D7997664e2131b5c8f95fc3400b27c647%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1308152495%26oauth_token%3D130232354-
gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY%26oauth_version%3D1.0



On Jun 15, 10:34 am, Taylor Singletary 
wrote:
> Hi Jeff,
>
> This is close to what I'm looking for -- it has the authorization header
> which is important to see -- but what will really help us debug with you is
> the signature base string -- it's a string that contains many of the same
> values from the authorization header but presented in a specific format --
> this is the string that is signed to create your oauth_signature. This
> signature base string is usually the key to all OAuth problems, as the order
> of parameters and particular encoding of them in relation to the parameters
> on your query string or POST body are extremely important and somewhat
> fragile.
>
> I'm not sure which version of EpiOAuth you're using, but there's likely a
> method similar to this one. The value you want to debug/capture here is
> $signatureBaseString.
>
>  protected function generateSignature($method = null, $url = null,
> $params = null)
>   {
>     if(empty($method) || empty($url))
>       return false;
>
>     // concatenating and encode
>     $concatenatedParams =
> $this->encode_rfc3986($this->buildHttpQueryRaw($params));
>
>     // normalize url
>     $normalizedUrl = $this->encode_rfc3986($this->normalizeUrl($url));
>     $method = $this->encode_rfc3986($method); // don't need this but why not?
>
>     $signatureBaseString = "{$method}&{$normalizedUrl}&{$concatenatedParams}";
>     return $this->signString($signatureBaseString);
>   }
>
> @episod  - Taylor
> Singletary
>
>
>
>
>
>
>
> On Wed, Jun 15, 2011 at 8:22 AM, Jeff  wrote:
> > Taylor,
>
> > Thanks for the response. Hopefully, this is what you need. I dumped it
> > right before the request.
>
> > [
> >   "Expect:",
> >   "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
> > \/ids.json\",
> >                   oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
> >                   oauth_token=\"130232354-
> > gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
> >                   oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
> >                   oauth_timestamp=\"1308151065\",
> >                   oauth_signature_method=\"HMAC-SHA1\",
> >                   oauth_version=\"1.0\",
> >                   oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
> > \"",
> >   "User-Agent: "
> > ]
>
> > On Jun 15, 10:05 am, Taylor Singletary 
> > wrote:
> > > This means that your signing is slightly wrong (and likely has been
> > slightly
> > > wrong for some time) when you're using parameters in your request. Can
> > you
> > > detail the signature base string and authorization header you are using
> > when
> > > building this request?
>
> > > @episod  - Taylor
> > > Singletary
>
> > > On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
>
> > > > Tuesday morning around 10am CDT I noticed a change in the API
> > > > endpoint /version/followers/ids in how it operates.
>
> > > > If you provide the cursor parameter, such as:
>
> > > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
> > > > correctly, however it also return the error warning "Invalid OAuth
> > > > credentials detected". Here is the response from the API.
>
> > > >   "data":{
> > > >      "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> > > > \"previous_cursor_str\":\"0\",\"ids\":
> > > > [222126862,95945240,169607024,148845934,95447204,94401716],
> > > > \"next_cursor\":0}",
> > > >      "headers":{
> > > >         "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
> > > >         "Server":"hi",
> > > >         "Status":"200 OK",
> > > >         "X-Warning":"Invalid OAuth credentials detected",
> > > >         "X-Transaction":"1308148794-15054-58845",
> > > >         "X-RateLimit-Limit":"150",
> > > >         "X-Frame-Options":"SAMEORIGIN",
> > > >         "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
> > > >         "X-RateLimit-Remaining":"66",
> > > >         "X-Runtime":"0.02003",
> > > >         "Content-Type":"application\/json; charset=utf-8",
> > > >         "Content-Length":"150",
> > > >         "Pragma":"no-cache",
> > > >         "X-RateLimit-Class":"api",
> > > >         "X-Revision":"DEV",
> > > >         "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
> > > >         "Cache-Control":"no-cache, no-store, must-revalidate, pre-
> > > > check=0, post-check=0",
> > > >         "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
> > > >         "X-RateLimit-Reset":"1308150383",
> > > >         "Vary":"Accept-Encoding",
> > > >         "Connection":"close"
> > > >      }

Re: [twitter-dev] Re: illegal character in json feed

[michael hazzard]

Much better!

I let http://jsfiddle.net/NBCGf/34/ run 1000 tries successfully before
taking mercy on your servers and shutting it off.

Good job and thanks,

//mh


On Tue, Jun 14, 2011 at 11:28 PM, themattharris
wrote:

> Hey everyone,
>
> Thanks for all the information you provided. We were able to reproduce
> the problem and the engineers have now released a fix.
> You shouldn't receive any garbled API responses anymore, if you do
> please let us know.
>
> Best,
> @themattharris
>
> On Jun 14, 7:59 pm, michael hazzard  wrote:
> > Marc,
> > Nice theory but I'm not so sure since I'm reloading the same exact tweet
> (I
> > think)over and over again and its getting corrupted.
> > Although I've heard of type of thing before where an application
> (notepad)
> > tries to do charset encoding detection but fails and outputs a corrupted
> > file upon reopening.
> > On Jun 14, 2011 9:24 PM, "marc fawzi"  wrote:
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > > Re: error handling the jsonp "script error"
> >
> > > I started using the previously mentioned "window.onerror" mechanism
> > > wherein I reload the iframe from which I'm initiating the jsonp call,
> > > up to 10 times, 3 seconds apart (the average delay in getting the
> > > script back from twitter, which triggers the error which in turn
> > > starts another jsonp request and so on, up to 10 times)
> >
> > > I'm using this approach in addition to my pre-existing "5 retries on
> > > general error, 10 seconds apart" non-blocking error handler which was
> > > able to survive the "illegal character" error on its own and recover
> > > from it, but sometimes it ended up with "Sorry, try again
> > > later" (twitter recovers after a while on its own and my app continues
> > > from there but sometimes the error persists with twitter.) The pre-
> > > existing handler was using more time on average (about 20-50 seconds)
> > > and the newly added window.onerror mechanism, which runs before the
> > > self-terminating, non-blocking handler loop, is taking less time on
> > > average (6-15 seconds) to go thru the same process for the jsonp
> > > "script error" reported by the browser. However, sometimes, this error
> > > persists for too many retries and falls out of the window.onerror but
> > > 99% of the time so far it's getting caught by my pre-existing general
> > > error handler (now, the second layer of defense)
> >
> > > I never thought I had to double up! :)
> >
> > > Re: illegal character
> >
> > > Wow. Really? you can have the unicode character for "delete" \u0008 in
> > > the response? I have a full dump of the jsonp response in firebug and
> > > that's the character that firebug terminates at when reporting the
> > > error so I assume that's the culprit, but could be others as well. On
> > > a more relevant note, I don't think the illegal character coming back
> > > in jsonp have anything to do with the tweet's content. It looks as if
> > > some tweets contain some combination of characters that cause twitter
> > > to return a binary dump of some sort (in casual terms, it causes it to
> > > hallucinate.)
> >
> > > Anyway intriguing. :)
> >
> > > Marc
> > > On Jun 14, 6:53 pm, Romica  wrote:
> > > > I have the same problem (bad JSON most of the times). The weird thing
> > > > is that if I access the URL direct from the browser it works (good
> > > > JSON every time). I'm using jQuery.getJSON and I think that this (or
> > > > something connected to this) might be the problem.
> >
> > > > Unfortunately I cannot use window.onerror (as Michael suggested)
> > > > because I have multiple asynchronous requests at the same time (it
> > > > would be tricky and expensive to find out which one is bad - at least
> > > > I suppose so).
> >
> > > > Good luck in solving this
> >
> > > --
> > > Twitter developer documentation and resources:
> https://dev.twitter.com/doc
> > > API updates via Twitter:https://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> >
> > https://code.google.com/p/twitter-api/issues/list> Change your
> membership to this group:
> >
> > https://groups.google.com/forum/#!forum/twitter-development-talk
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>



-- 
Thank You,

Michael Hazzard
(954) 247-4461 

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Taylor Singletary]

Hi Jeff,

This is close to what I'm looking for -- it has the authorization header
which is important to see -- but what will really help us debug with you is
the signature base string -- it's a string that contains many of the same
values from the authorization header but presented in a specific format --
this is the string that is signed to create your oauth_signature. This
signature base string is usually the key to all OAuth problems, as the order
of parameters and particular encoding of them in relation to the parameters
on your query string or POST body are extremely important and somewhat
fragile.

I'm not sure which version of EpiOAuth you're using, but there's likely a
method similar to this one. The value you want to debug/capture here is
$signatureBaseString.

 protected function generateSignature($method = null, $url = null,
$params = null)
  {
if(empty($method) || empty($url))
  return false;

// concatenating and encode
$concatenatedParams =
$this->encode_rfc3986($this->buildHttpQueryRaw($params));

// normalize url
$normalizedUrl = $this->encode_rfc3986($this->normalizeUrl($url));
$method = $this->encode_rfc3986($method); // don't need this but why not?

$signatureBaseString = "{$method}&{$normalizedUrl}&{$concatenatedParams}";
return $this->signString($signatureBaseString);
  }


@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:22 AM, Jeff  wrote:

> Taylor,
>
> Thanks for the response. Hopefully, this is what you need. I dumped it
> right before the request.
>
> [
>   "Expect:",
>   "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
> \/ids.json\",
>   oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
>   oauth_token=\"130232354-
> gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
>   oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
>   oauth_timestamp=\"1308151065\",
>   oauth_signature_method=\"HMAC-SHA1\",
>   oauth_version=\"1.0\",
>   oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
> \"",
>   "User-Agent: "
> ]
>
> On Jun 15, 10:05 am, Taylor Singletary 
> wrote:
> > This means that your signing is slightly wrong (and likely has been
> slightly
> > wrong for some time) when you're using parameters in your request. Can
> you
> > detail the signature base string and authorization header you are using
> when
> > building this request?
> >
> > @episod  - Taylor
> > Singletary
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
> >
> > > Tuesday morning around 10am CDT I noticed a change in the API
> > > endpoint /version/followers/ids in how it operates.
> >
> > > If you provide the cursor parameter, such as:
> >
> > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
> > > correctly, however it also return the error warning "Invalid OAuth
> > > credentials detected". Here is the response from the API.
> >
> > >   "data":{
> > >  "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> > > \"previous_cursor_str\":\"0\",\"ids\":
> > > [222126862,95945240,169607024,148845934,95447204,94401716],
> > > \"next_cursor\":0}",
> > >  "headers":{
> > > "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
> > > "Server":"hi",
> > > "Status":"200 OK",
> > > "X-Warning":"Invalid OAuth credentials detected",
> > > "X-Transaction":"1308148794-15054-58845",
> > > "X-RateLimit-Limit":"150",
> > > "X-Frame-Options":"SAMEORIGIN",
> > > "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
> > > "X-RateLimit-Remaining":"66",
> > > "X-Runtime":"0.02003",
> > > "Content-Type":"application\/json; charset=utf-8",
> > > "Content-Length":"150",
> > > "Pragma":"no-cache",
> > > "X-RateLimit-Class":"api",
> > > "X-Revision":"DEV",
> > > "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
> > > "Cache-Control":"no-cache, no-store, must-revalidate, pre-
> > > check=0, post-check=0",
> > > "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
> > > "X-RateLimit-Reset":"1308150383",
> > > "Vary":"Accept-Encoding",
> > > "Connection":"close"
> > >  },
> >
> > > The problem here is that because it thinks the OAuth credentials are
> > > "Invalid" it gives me a rate limit of 150.
> >
> > > If I remove the parameters "?cursor=-1&user_id=12345" and simply use
> > > the endpoint /1/followers/ids.json it accepts my OAuth credentials as
> > > valid and and returns the appropriate rate limit of 350. Although this
> > > works, I need pagination as there are a lot of ids I need to retrieve.
> >
> > > This had been working correctly and I noticed the change yesterday
> > > morning.
> >
> > > Any help on resolving this or letting me know if something has changed

[twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Jeff]

Taylor,

I forgot to mention that I'm using the class epi as the client API for
PHP and I have several other endpoint being called with parameters and
so far, this is the only endpoint experiencing the issue.

Thanks,
Jeff

On Jun 15, 10:22 am, Jeff  wrote:
> Taylor,
>
> Thanks for the response. Hopefully, this is what you need. I dumped it
> right before the request.
>
> [
>    "Expect:",
>    "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
> \/ids.json\",
>                    oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
>                    oauth_token=\"130232354-
> gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
>                    oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
>                    oauth_timestamp=\"1308151065\",
>                    oauth_signature_method=\"HMAC-SHA1\",
>                    oauth_version=\"1.0\",
>                    oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
> \"",
>    "User-Agent: "
> ]
>
> On Jun 15, 10:05 am, Taylor Singletary 
> wrote:
>
>
>
>
>
>
>
> > This means that your signing is slightly wrong (and likely has been slightly
> > wrong for some time) when you're using parameters in your request. Can you
> > detail the signature base string and authorization header you are using when
> > building this request?
>
> > @episod  - Taylor
> > Singletary
>
> > On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
>
> > > Tuesday morning around 10am CDT I noticed a change in the API
> > > endpoint /version/followers/ids in how it operates.
>
> > > If you provide the cursor parameter, such as:
>
> > > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
> > > correctly, however it also return the error warning "Invalid OAuth
> > > credentials detected". Here is the response from the API.
>
> > >   "data":{
> > >      "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> > > \"previous_cursor_str\":\"0\",\"ids\":
> > > [222126862,95945240,169607024,148845934,95447204,94401716],
> > > \"next_cursor\":0}",
> > >      "headers":{
> > >         "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
> > >         "Server":"hi",
> > >         "Status":"200 OK",
> > >         "X-Warning":"Invalid OAuth credentials detected",
> > >         "X-Transaction":"1308148794-15054-58845",
> > >         "X-RateLimit-Limit":"150",
> > >         "X-Frame-Options":"SAMEORIGIN",
> > >         "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
> > >         "X-RateLimit-Remaining":"66",
> > >         "X-Runtime":"0.02003",
> > >         "Content-Type":"application\/json; charset=utf-8",
> > >         "Content-Length":"150",
> > >         "Pragma":"no-cache",
> > >         "X-RateLimit-Class":"api",
> > >         "X-Revision":"DEV",
> > >         "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
> > >         "Cache-Control":"no-cache, no-store, must-revalidate, pre-
> > > check=0, post-check=0",
> > >         "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
> > >         "X-RateLimit-Reset":"1308150383",
> > >         "Vary":"Accept-Encoding",
> > >         "Connection":"close"
> > >      },
>
> > > The problem here is that because it thinks the OAuth credentials are
> > > "Invalid" it gives me a rate limit of 150.
>
> > > If I remove the parameters "?cursor=-1&user_id=12345" and simply use
> > > the endpoint /1/followers/ids.json it accepts my OAuth credentials as
> > > valid and and returns the appropriate rate limit of 350. Although this
> > > works, I need pagination as there are a lot of ids I need to retrieve.
>
> > > This had been working correctly and I noticed the change yesterday
> > > morning.
>
> > > Any help on resolving this or letting me know if something has changed
> > > when parameters are used with this endpoint would be greatly
> > > appreciated.
>
> > > Thanks,
> > > Jeff
>
> > > --
> > > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > > API updates via Twitter:https://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >https://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Jeff]

Taylor,

Thanks for the response. Hopefully, this is what you need. I dumped it
right before the request.

[
   "Expect:",
   "Authorization: OAuth realm=\"http:\/\/api.twitter.com\/1\/followers
\/ids.json\",
   oauth_consumer_key=\"OlPht6d2h3N1XYwCpCyx5Q\",
   oauth_token=\"130232354-
gI42iFYrX1Mtn72N5y1yr3WYSeQ6hfpposibfxY\",
   oauth_nonce=\"71cc67f647043054dbd640b9b1f3d8fc\",
   oauth_timestamp=\"1308151065\",
   oauth_signature_method=\"HMAC-SHA1\",
   oauth_version=\"1.0\",
   oauth_signature=\"lYen9ON%2B5bVah%2BBHVGnPCMqBXQ8%3D
\"",
   "User-Agent: "
]

On Jun 15, 10:05 am, Taylor Singletary 
wrote:
> This means that your signing is slightly wrong (and likely has been slightly
> wrong for some time) when you're using parameters in your request. Can you
> detail the signature base string and authorization header you are using when
> building this request?
>
> @episod  - Taylor
> Singletary
>
>
>
>
>
>
>
> On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:
>
> > Tuesday morning around 10am CDT I noticed a change in the API
> > endpoint /version/followers/ids in how it operates.
>
> > If you provide the cursor parameter, such as:
>
> > /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
> > correctly, however it also return the error warning "Invalid OAuth
> > credentials detected". Here is the response from the API.
>
> >   "data":{
> >      "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> > \"previous_cursor_str\":\"0\",\"ids\":
> > [222126862,95945240,169607024,148845934,95447204,94401716],
> > \"next_cursor\":0}",
> >      "headers":{
> >         "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
> >         "Server":"hi",
> >         "Status":"200 OK",
> >         "X-Warning":"Invalid OAuth credentials detected",
> >         "X-Transaction":"1308148794-15054-58845",
> >         "X-RateLimit-Limit":"150",
> >         "X-Frame-Options":"SAMEORIGIN",
> >         "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
> >         "X-RateLimit-Remaining":"66",
> >         "X-Runtime":"0.02003",
> >         "Content-Type":"application\/json; charset=utf-8",
> >         "Content-Length":"150",
> >         "Pragma":"no-cache",
> >         "X-RateLimit-Class":"api",
> >         "X-Revision":"DEV",
> >         "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
> >         "Cache-Control":"no-cache, no-store, must-revalidate, pre-
> > check=0, post-check=0",
> >         "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
> >         "X-RateLimit-Reset":"1308150383",
> >         "Vary":"Accept-Encoding",
> >         "Connection":"close"
> >      },
>
> > The problem here is that because it thinks the OAuth credentials are
> > "Invalid" it gives me a rate limit of 150.
>
> > If I remove the parameters "?cursor=-1&user_id=12345" and simply use
> > the endpoint /1/followers/ids.json it accepts my OAuth credentials as
> > valid and and returns the appropriate rate limit of 350. Although this
> > works, I need pagination as there are a lot of ids I need to retrieve.
>
> > This had been working correctly and I noticed the change yesterday
> > morning.
>
> > Any help on resolving this or letting me know if something has changed
> > when parameters are used with this endpoint would be greatly
> > appreciated.
>
> > Thanks,
> > Jeff
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Taylor Singletary]

This means that your signing is slightly wrong (and likely has been slightly
wrong for some time) when you're using parameters in your request. Can you
detail the signature base string and authorization header you are using when
building this request?

@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 8:00 AM, Jeff  wrote:

>
> Tuesday morning around 10am CDT I noticed a change in the API
> endpoint /version/followers/ids in how it operates.
>
> If you provide the cursor parameter, such as:
>
> /1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
> correctly, however it also return the error warning "Invalid OAuth
> credentials detected". Here is the response from the API.
>
>   "data":{
>  "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
> \"previous_cursor_str\":\"0\",\"ids\":
> [222126862,95945240,169607024,148845934,95447204,94401716],
> \"next_cursor\":0}",
>  "headers":{
> "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
> "Server":"hi",
> "Status":"200 OK",
> "X-Warning":"Invalid OAuth credentials detected",
> "X-Transaction":"1308148794-15054-58845",
> "X-RateLimit-Limit":"150",
> "X-Frame-Options":"SAMEORIGIN",
> "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
> "X-RateLimit-Remaining":"66",
> "X-Runtime":"0.02003",
> "Content-Type":"application\/json; charset=utf-8",
> "Content-Length":"150",
> "Pragma":"no-cache",
> "X-RateLimit-Class":"api",
> "X-Revision":"DEV",
> "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
> "Cache-Control":"no-cache, no-store, must-revalidate, pre-
> check=0, post-check=0",
> "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
> "X-RateLimit-Reset":"1308150383",
> "Vary":"Accept-Encoding",
> "Connection":"close"
>  },
>
> The problem here is that because it thinks the OAuth credentials are
> "Invalid" it gives me a rate limit of 150.
>
> If I remove the parameters "?cursor=-1&user_id=12345" and simply use
> the endpoint /1/followers/ids.json it accepts my OAuth credentials as
> valid and and returns the appropriate rate limit of 350. Although this
> works, I need pagination as there are a lot of ids I need to retrieve.
>
> This had been working correctly and I noticed the change yesterday
> morning.
>
> Any help on resolving this or letting me know if something has changed
> when parameters are used with this endpoint would be greatly
> appreciated.
>
> Thanks,
> Jeff
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Method /version/followers/ids.json not functioning properly when cursor parameter is provided

[Jeff]

Tuesday morning around 10am CDT I noticed a change in the API
endpoint /version/followers/ids in how it operates.

If you provide the cursor parameter, such as:

/1/followers/ids.json?cursor=-1&user_id=12345 the method returns data
correctly, however it also return the error warning "Invalid OAuth
credentials detected". Here is the response from the API.

   "data":{
  "responseText":"{\"previous_cursor\":0,\"next_cursor_str\":\"0\",
\"previous_cursor_str\":\"0\",\"ids\":
[222126862,95945240,169607024,148845934,95447204,94401716],
\"next_cursor\":0}",
  "headers":{
 "Date":"Wed, 15 Jun 2011 14:39:54 GMT",
 "Server":"hi",
 "Status":"200 OK",
 "X-Warning":"Invalid OAuth credentials detected",
 "X-Transaction":"1308148794-15054-58845",
 "X-RateLimit-Limit":"150",
 "X-Frame-Options":"SAMEORIGIN",
 "Last-Modified":"Wed, 15 Jun 2011 14:39:54 GMT",
 "X-RateLimit-Remaining":"66",
 "X-Runtime":"0.02003",
 "Content-Type":"application\/json; charset=utf-8",
 "Content-Length":"150",
 "Pragma":"no-cache",
 "X-RateLimit-Class":"api",
 "X-Revision":"DEV",
 "Expires":"Tue, 31 Mar 1981 05:00:00 GMT",
 "Cache-Control":"no-cache, no-store, must-revalidate, pre-
check=0, post-check=0",
 "X-MID":"c7827d770b9045b049f3967663b08dce7704a9fb",
 "X-RateLimit-Reset":"1308150383",
 "Vary":"Accept-Encoding",
 "Connection":"close"
  },

The problem here is that because it thinks the OAuth credentials are
"Invalid" it gives me a rate limit of 150.

If I remove the parameters "?cursor=-1&user_id=12345" and simply use
the endpoint /1/followers/ids.json it accepts my OAuth credentials as
valid and and returns the appropriate rate limit of 350. Although this
works, I need pagination as there are a lot of ids I need to retrieve.

This had been working correctly and I noticed the change yesterday
morning.

Any help on resolving this or letting me know if something has changed
when parameters are used with this endpoint would be greatly
appreciated.

Thanks,
Jeff

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] [Wanted] Weekly Twitter Tools Article Author

[robscott]

Hi,

We're looking for people who are able to help contribute a weekly (or
less frequent) digest of new Twitter tools and enhancements to the
tech section of The Global Herald (http://theglobalherald.com/).

If this sounds like something you'd be interested in getting involved
with, please email robin.sc...@theglobalherald.com with a few details
about yourself, and what you'd be able to contribute to our
publication.

Thanks.

Robin Scott
Publisher
TheGlobalHerald.com

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Randomly failing OAuth procedure

[Felix Oldenburg]

Hi Taylor,

after doing some more detailed logging, i managed to figure out the
problem.

First I do the encoding of the post body, then the signature is being
build and attached to the post body.
I just forgot to encode the signature string, too, after attaching it
to the post body.
So everytime when the signature strings contained a slash or an equal
sign, like base64 tends to produce, the oauth failed.

Besides the encoding of the status texts was wrong. Just as I saw in
Abraham's Twitter PHP library I decoded %7E back to ~ in the final
string and oauth is happy. Otherwise, if the string contains a plain ~
it fails, still wondering why...

Thanks again for the support and sunny greetings from Hamburg Germany,
Felix.


On 14 Jun., 18:03, Felix Oldenburg 
wrote:
> Hi Taylor,
>
> thanks for many hints on tracking down the problem.
> I don't use any libraries, neither for Twitter, nor for oauth. I'm
> doing all by my self, thus printing out some debugging messages is
> fairly easy.
> As I'm able to do a status update some times successfully, I was sure
> to do everything correctly.
> Of cource, I inspected every detail, like the assembling of the base
> string and its signing.
> I followedhttp://dev.twitter.com/pages/authand I get the same
> results for the base string and the final signature string, when I use
> the same input as in the example.
> Even using special characters(space, exclamation mark, and so on..) in
> the text of the tweet is possible, as I already tweeted some cryptic
> posts - containing different special chars - to my wall.
> So I pressume my url encoding and signing process should be correct.
>
> https://api.twitter.com/oauth/request_tokenandhttps://api.twitter.com/oauth/access_token
> are the paths I use for acquiring the request and access token.
>
> The system clock of my Macbook is fine, I think, but I'll check that
> out on detail.
> Maybe I should recheck my timestamp and oauth_nonce generation code,
> because I don't check if a timestamp, or oauth_nonce is being used
> twice. Though I can't imagine what could go wrong, when simply using a
> unix timestamp.
> (Oh.. is it seconds or miliseconds ruby returns when using
> Time.now.to_i, I'd better check that out oO!!!)
>
> I'll check the timestamp thing and if that's not the problem, I'll
> post some detailed debug report tomorrow.
>
> Many thanks for your inspiring reply, Felix!
>
> On 14 Jun., 17:10, Taylor Singletary 
> wrote:
>
>
>
>
>
>
>
> > Hi Felix,
>
> > Are you using a specific OAuth library for the OAuth portion?
>
> > I would recommend adding a bit of logging around the OAuth token negotiation
> > process.. find out the signature base string, the exact URL you're
> > executing, and the Authorization header you're sending. Log the response
> > code and body of the response when it fails. With the main OAuth ruby gem
> > that's out there, some of these details are hard to come by because the
> > values are hidden in private methods (PSA to OAuth library developers: don't
> > do this), so you may need to monkey patch the OAuth gem here and there to
> > debug the values.
>
> > What you're mainly looking for is a specific pattern to your failed requests
> > for a request token -- is some value not being sent correctly? Do you have
> > some kind of problem where in certain conditions a variable you've set like
> > your consumer key gets unset somehow? Is your system clock reliable? Is the
> > library you're using to generate HMAC-SHA1 signatures doing the right thing?
> > Are you using the right kind of URL encoding? Are you accidentally sending
> > double parameters for something?
>
> > Verify that you're usinghttps://api.twitter.com/oauth/asthe base path for
> > the OAuth negotiation steps.
>
> > While there have been failures in the past in exchanging a request token for
> > an access token due to some lag, we're not aware of
> > anything specifically wrong with the process for fetching the request token.
>
> > @episod  - Taylor
> > Singletary
>
> > On Tue, Jun 14, 2011 at 7:25 AM, Felix Oldenburg <
>
> > oldenburg.fe...@googlemail.com> wrote:
> > > Hi twitter developing community,
> > > I'm using ruby( on rails) to do the oauth dance manually and finally
> > > call /1/statuses/update.json to update the status of an authorized
> > > user.
>
> > > Every single step during the oauth procedure is confirmed to be
> > > working.
> > > Actually I already tweeted some messages successfully. But for no
> > > obvious reason(to me), oauth sometimes fails at the very beginning
> > > while acquiring a request token. Then it just sais: "Failed to
> > > validate oauth signature and token".
>
> > > Then I retry it several times until it (suddenly) works.
> > > The next step, i.e. exchanging the request token for an access token,
> > > works perfectly every time.
> > > But when it comes to the actual status update(i.e. calling the /1/
> > > statuses/update.json endpoint) it sometimes fail

Re: [twitter-dev] Re: Problem With Fetching Followers and Following Id's

[kamesh SmartDude]

Thank You episod.

//kamesh

On Wed, Jun 15, 2011 at 7:22 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> When using cursors, you cannot specify a count parameter. If you want to
> limit the results that you get back, simply truncate the response to the
> number of ids that suits you. You can pre-prepare paginated results by first
> building the complete set and then building a UI that will navigate between
> the already fetched data.
>
> @episod  - Taylor
> Singletary
>
>
> On Wed, Jun 15, 2011 at 2:26 AM, kamesh SmartDude <
> kamesh.smartd...@gmail.com> wrote:
>
>> to whom should we write for this particular issue
>>
>> //kamesh
>>
>> On Jun 14, 12:26 pm, Georgooty varghese  wrote:
>> > I am facing the same issue..
>> >
>> > On Tue, Jun 14, 2011 at 11:56 AM, kamesh SmartDude <
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > kamesh.smartd...@gmail.com> wrote:
>> > > Is Anybody have IDEA about the solution of above problem
>> >
>> > > //kamesh
>> >
>> > > On Jun 13, 12:49 pm, kamesh SmartDude 
>> > > wrote:
>> > > > Dear All,
>> >
>> > > > I am developing a twitter mobile application, and i have a problem
>> in
>> > > > fetching the followers and following list.
>> >
>> > > > earlier i used
>> >
>> > >http://api.twitter.com/version/statuses/friends.formathttp://api.twit.
>> ..
>> >
>> > > > API's to fecth the Followers and following people list. But now they
>> > > > are depricated.
>> >
>> > > > Now i want to use the API's
>> >
>> > >http://api.twitter.com/version/friends/ids.formathttp://api.twitter.c.
>> ..
>> >
>> > > > to fetch the ID's of the follower and following people Id's and
>> >
>> > > >http://api.twitter.com/version/users/lookup.formatAPI to get the
>> > > > user List.
>> >
>> > > > Now My problem is that i want to fetch the Specific number (as per
>> my
>> > > > requirement it is 16) of follower and following id's using the above
>> > > > two API's (friends/ids.format and followers/ids.format).
>> >
>> > > > But these two API's ignoring the "count" Parameter (suppose if i
>> sent
>> > > > a request to fetch the followers of the user = sachin_rt
>> >
>> > > >
>> http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rt&cur...
>> >
>> > > > it is ignoring the count parameterand returning an amount "5000"
>> > > > followers ID's.
>> > > > )
>> >
>> > > > and returning a huge number of Id's. As i am developing a mobile app
>> i
>> > > > don't want to store this amount of data in my database until user go
>> > > > for "showmore"/ or scroll to the bottom of the list.
>> >
>> > > > please let me know is there any solution to fetch the specific
>> number
>> > > > of ID's of the followers/follwing.
>> >
>> > > > Thanks in AdvanceKamesh
>> >
>> > > --
>> > > Twitter developer documentation and resources:
>> https://dev.twitter.com/doc
>> > > API updates via Twitter:https://twitter.com/twitterapi
>> > > Issues/Enhancements Tracker:
>> > >https://code.google.com/p/twitter-api/issues/list
>> > > Change your membership to this group:
>> > >https://groups.google.com/forum/#!forum/twitter-development-talk
>>
>> --
>> Twitter developer documentation and resources:
>> https://dev.twitter.com/doc
>> API updates via Twitter: https://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> https://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

[kamesh SmartDude]

Dear episod,

sry for the spell mistakeand sorry for not checking the reply u already
gave for the thread i started.

thanks for the reply to that post.

//kamesh

On Wed, Jun 15, 2011 at 7:33 PM, kamesh SmartDude <
kamesh.smartd...@gmail.com> wrote:

> Hai wpisod,
>
> how can i get only a specific number(Suppose 20 IDs only) of IDS using the
> API (http://dev.twitter.com/doc/get/followers/ids).
>
> I tested this API using "count" parameter in API...but it is ignoring this
> parameter and returning nearly 5000 ID's At a time if the the user has
> followers more than 5000
>
> Please guide me ASAP.
>
> //Kamesh
>
>
> On Wed, Jun 15, 2011 at 7:26 PM, Taylor Singletary <
> taylorsinglet...@twitter.com> wrote:
>
>> If you want to retrieve all of a user's followers, you first get their ids
>> by cursoring through
>> http://api.twitter.com/1/followers/ids.json?cursor=-1 [1] -- after
>> retrieving that data, you'll want to expand them for user ids into
>> "hydrated" user objects. To do this, pass 50 to 80 (maximum 100, but I
>> recommend lower maximums for best performance) of the ids at a time to the
>> bulk users lookup [2] API method. For some users this may take only two API
>> requests: one for the followers' ids, and another for the users/lookup.
>>
>> [1] http://dev.twitter.com/doc/get/followers/ids
>> [2] http://dev.twitter.com/doc/get/users/lookup
>>
>> @episod  - Taylor
>> Singletary
>>
>>
>>
>> On Wed, Jun 15, 2011 at 4:34 AM, Amit Battan Ror wrote:
>>
>>> one more issue /... as I want to get the list of my all follower
>>> But I seen in some discussion as this API not return all the friends.
>>> It only return the recently updated friends with there status.
>>> Is it?
>>> and what is the API which I want?
>>>
>>>
>>>
>>> On Jun 14, 5:04 pm, Bill Jacobson  wrote:
>>> > Amit,
>>> >
>>> > Your endpoint is obsolete and no longer supported by Twitter. That's
>>> why
>>> > you got the 403. Statuses/followers will succeed if you change it
>>> tohttp://api.twitter.com/1/statuses/followers.xml
>>> > 
>>> >
>>> > BUT this API is deprecated. Read all about it here:
>>> http://dev.twitter.com/doc/get/statuses/followers
>>> >
>>> > Bill
>>> >
>>> > On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > > Bill
>>> >
>>> > > Working fine :https://twitter.com/statuses/friends_timeline.xml
>>> >
>>> > > Not Working Giving 403 Error :
>>> https://twitter.com/statuses/followers.xml
>>> >
>>> > > On Jun 14, 10:14 am, Amit Battan Ror  wrote:
>>> > >> Thanks Bill
>>> >
>>> > >> I will check and try to track URL ..
>>> >
>>> > >> On Jun 13, 9:07 pm, Bill Jacobson  wrote:
>>> >
>>> > >>> Amit, also seehttp://
>>> www.mailinglistarchive.com/html/twitter-development-talk@googl
>>> > >>> That's what helped me.
>>> > >>> -Bill
>>> > >>> On 06/13/2011 10:44 AM, Bill Jacobson wrote:
>>> >  I'm suggesting that you find out what endpoint (Twitter URL) your
>>> app
>>> >  is targeting, and make sure that it matches what is currently
>>> >  documented. If it doesn't match, correct it. That's what worked
>>> for me.
>>> >  On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
>>> > > I am not getting the solution.
>>> > > and my API was working fine beofre 2 3 days..
>>> > > but not now..
>>> > > all other API except getFollowersIncludingCurrentStatus working
>>> ok and
>>> > > return proper output
>>> > > On Jun 13, 5:53 pm, Bill Jacobsonwrote:
>>> > >> Amit,
>>> > >> I don't know your library, but in my case the 403 was
>>> accompanied by
>>> > >> the
>>> > >> message "Not authorized to use this endpoint" and the solution
>>> was to
>>> > >> update to "http://api.twitter.com/1[etc.]";.
>>> > >> Bill Jacobson
>>> > >> On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
>>> > >>> any idea guys
>>> > >>> On Jun 10, 4:33 pm, Amit Battan Ror
>>>  wrote:
>>> >  Hi All
>>> >  I am using
>>> >  Twitter-OAuth-iPhonehttps://
>>> github.com/bengottlieb/Twitter-OAuth-iPhone
>>> >  I am calling [twitterObj
>>> getFollowersIncludingCurrentStatus:NO] for
>>> >  getting my friend list which was working fine. But from last
>>> two days
>>> >  its giving me the 403 error.
>>> >  -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed
>>> with
>>> >  error: Error Domain=HTTP Code=403 "The operation couldn t be
>>> >  completed. (HTTP error 403.)"
>>> >  As twitter api wiki 403 is due to crossing the limit of
>>> updates
>>> >  and DM
>>> >  but here in getFollowersIncludingCurrentStatus Why this error
>>> >  occurring and even list is not comes next day giving same 403
>>> error.
>>> >  Thanks
>>> >  Amit Battan
>>>
>>> --
>>> Twitter developer documentation and resources:
>>> https://dev.twitter.com/doc
>>> API upd

Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

[kamesh SmartDude]

Hai wpisod,

how can i get only a specific number(Suppose 20 IDs only) of IDS using the
API (http://dev.twitter.com/doc/get/followers/ids).

I tested this API using "count" parameter in API...but it is ignoring this
parameter and returning nearly 5000 ID's At a time if the the user has
followers more than 5000

Please guide me ASAP.

//Kamesh

On Wed, Jun 15, 2011 at 7:26 PM, Taylor Singletary <
taylorsinglet...@twitter.com> wrote:

> If you want to retrieve all of a user's followers, you first get their ids
> by cursoring through http://api.twitter.com/1/followers/ids.json?cursor=-1[1] 
> -- after retrieving that data, you'll want to expand them for user ids
> into "hydrated" user objects. To do this, pass 50 to 80 (maximum 100, but I
> recommend lower maximums for best performance) of the ids at a time to the
> bulk users lookup [2] API method. For some users this may take only two API
> requests: one for the followers' ids, and another for the users/lookup.
>
> [1] http://dev.twitter.com/doc/get/followers/ids
> [2] http://dev.twitter.com/doc/get/users/lookup
>
> @episod  - Taylor
> Singletary
>
>
>
> On Wed, Jun 15, 2011 at 4:34 AM, Amit Battan Ror wrote:
>
>> one more issue /... as I want to get the list of my all follower
>> But I seen in some discussion as this API not return all the friends.
>> It only return the recently updated friends with there status.
>> Is it?
>> and what is the API which I want?
>>
>>
>>
>> On Jun 14, 5:04 pm, Bill Jacobson  wrote:
>> > Amit,
>> >
>> > Your endpoint is obsolete and no longer supported by Twitter. That's why
>> > you got the 403. Statuses/followers will succeed if you change it
>> tohttp://api.twitter.com/1/statuses/followers.xml
>> > 
>> >
>> > BUT this API is deprecated. Read all about it here:
>> http://dev.twitter.com/doc/get/statuses/followers
>> >
>> > Bill
>> >
>> > On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > > Bill
>> >
>> > > Working fine :https://twitter.com/statuses/friends_timeline.xml
>> >
>> > > Not Working Giving 403 Error :
>> https://twitter.com/statuses/followers.xml
>> >
>> > > On Jun 14, 10:14 am, Amit Battan Ror  wrote:
>> > >> Thanks Bill
>> >
>> > >> I will check and try to track URL ..
>> >
>> > >> On Jun 13, 9:07 pm, Bill Jacobson  wrote:
>> >
>> > >>> Amit, also seehttp://
>> www.mailinglistarchive.com/html/twitter-development-talk@googl
>> > >>> That's what helped me.
>> > >>> -Bill
>> > >>> On 06/13/2011 10:44 AM, Bill Jacobson wrote:
>> >  I'm suggesting that you find out what endpoint (Twitter URL) your
>> app
>> >  is targeting, and make sure that it matches what is currently
>> >  documented. If it doesn't match, correct it. That's what worked for
>> me.
>> >  On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
>> > > I am not getting the solution.
>> > > and my API was working fine beofre 2 3 days..
>> > > but not now..
>> > > all other API except getFollowersIncludingCurrentStatus working ok
>> and
>> > > return proper output
>> > > On Jun 13, 5:53 pm, Bill Jacobsonwrote:
>> > >> Amit,
>> > >> I don't know your library, but in my case the 403 was accompanied
>> by
>> > >> the
>> > >> message "Not authorized to use this endpoint" and the solution
>> was to
>> > >> update to "http://api.twitter.com/1[etc.]";.
>> > >> Bill Jacobson
>> > >> On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
>> > >>> any idea guys
>> > >>> On Jun 10, 4:33 pm, Amit Battan Ror
>>  wrote:
>> >  Hi All
>> >  I am using
>> >  Twitter-OAuth-iPhonehttps://
>> github.com/bengottlieb/Twitter-OAuth-iPhone
>> >  I am calling [twitterObj getFollowersIncludingCurrentStatus:NO]
>> for
>> >  getting my friend list which was working fine. But from last
>> two days
>> >  its giving me the 403 error.
>> >  -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed
>> with
>> >  error: Error Domain=HTTP Code=403 "The operation couldn t be
>> >  completed. (HTTP error 403.)"
>> >  As twitter api wiki 403 is due to crossing the limit of updates
>> >  and DM
>> >  but here in getFollowersIncludingCurrentStatus Why this error
>> >  occurring and even list is not comes next day giving same 403
>> error.
>> >  Thanks
>> >  Amit Battan
>>
>> --
>> Twitter developer documentation and resources:
>> https://dev.twitter.com/doc
>> API updates via Twitter: https://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> https://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements 

Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

[Taylor Singletary]

If you want to retrieve all of a user's followers, you first get their ids
by cursoring through
http://api.twitter.com/1/followers/ids.json?cursor=-1[1] -- after
retrieving that data, you'll want to expand them for user ids
into "hydrated" user objects. To do this, pass 50 to 80 (maximum 100, but I
recommend lower maximums for best performance) of the ids at a time to the
bulk users lookup [2] API method. For some users this may take only two API
requests: one for the followers' ids, and another for the users/lookup.

[1] http://dev.twitter.com/doc/get/followers/ids
[2] http://dev.twitter.com/doc/get/users/lookup

@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 4:34 AM, Amit Battan Ror  wrote:

> one more issue /... as I want to get the list of my all follower
> But I seen in some discussion as this API not return all the friends.
> It only return the recently updated friends with there status.
> Is it?
> and what is the API which I want?
>
>
>
> On Jun 14, 5:04 pm, Bill Jacobson  wrote:
> > Amit,
> >
> > Your endpoint is obsolete and no longer supported by Twitter. That's why
> > you got the 403. Statuses/followers will succeed if you change it
> tohttp://api.twitter.com/1/statuses/followers.xml
> > 
> >
> > BUT this API is deprecated. Read all about it here:
> http://dev.twitter.com/doc/get/statuses/followers
> >
> > Bill
> >
> > On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Bill
> >
> > > Working fine :https://twitter.com/statuses/friends_timeline.xml
> >
> > > Not Working Giving 403 Error :
> https://twitter.com/statuses/followers.xml
> >
> > > On Jun 14, 10:14 am, Amit Battan Ror  wrote:
> > >> Thanks Bill
> >
> > >> I will check and try to track URL ..
> >
> > >> On Jun 13, 9:07 pm, Bill Jacobson  wrote:
> >
> > >>> Amit, also seehttp://
> www.mailinglistarchive.com/html/twitter-development-talk@googl
> > >>> That's what helped me.
> > >>> -Bill
> > >>> On 06/13/2011 10:44 AM, Bill Jacobson wrote:
> >  I'm suggesting that you find out what endpoint (Twitter URL) your
> app
> >  is targeting, and make sure that it matches what is currently
> >  documented. If it doesn't match, correct it. That's what worked for
> me.
> >  On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
> > > I am not getting the solution.
> > > and my API was working fine beofre 2 3 days..
> > > but not now..
> > > all other API except getFollowersIncludingCurrentStatus working ok
> and
> > > return proper output
> > > On Jun 13, 5:53 pm, Bill Jacobsonwrote:
> > >> Amit,
> > >> I don't know your library, but in my case the 403 was accompanied
> by
> > >> the
> > >> message "Not authorized to use this endpoint" and the solution was
> to
> > >> update to "http://api.twitter.com/1[etc.]";.
> > >> Bill Jacobson
> > >> On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
> > >>> any idea guys
> > >>> On Jun 10, 4:33 pm, Amit Battan Ror
>  wrote:
> >  Hi All
> >  I am using
> >  Twitter-OAuth-iPhonehttps://
> github.com/bengottlieb/Twitter-OAuth-iPhone
> >  I am calling [twitterObj getFollowersIncludingCurrentStatus:NO]
> for
> >  getting my friend list which was working fine. But from last two
> days
> >  its giving me the 403 error.
> >  -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed
> with
> >  error: Error Domain=HTTP Code=403 "The operation couldn t be
> >  completed. (HTTP error 403.)"
> >  As twitter api wiki 403 is due to crossing the limit of updates
> >  and DM
> >  but here in getFollowersIncludingCurrentStatus Why this error
> >  occurring and even list is not comes next day giving same 403
> error.
> >  Thanks
> >  Amit Battan
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Re: Problem With Fetching Followers and Following Id's

[Taylor Singletary]

When using cursors, you cannot specify a count parameter. If you want to
limit the results that you get back, simply truncate the response to the
number of ids that suits you. You can pre-prepare paginated results by first
building the complete set and then building a UI that will navigate between
the already fetched data.

@episod  - Taylor
Singletary


On Wed, Jun 15, 2011 at 2:26 AM, kamesh SmartDude <
kamesh.smartd...@gmail.com> wrote:

> to whom should we write for this particular issue
>
> //kamesh
>
> On Jun 14, 12:26 pm, Georgooty varghese  wrote:
> > I am facing the same issue..
> >
> > On Tue, Jun 14, 2011 at 11:56 AM, kamesh SmartDude <
> >
> >
> >
> >
> >
> >
> >
> > kamesh.smartd...@gmail.com> wrote:
> > > Is Anybody have IDEA about the solution of above problem
> >
> > > //kamesh
> >
> > > On Jun 13, 12:49 pm, kamesh SmartDude 
> > > wrote:
> > > > Dear All,
> >
> > > > I am developing a twitter mobile application, and i have a problem in
> > > > fetching the followers and following list.
> >
> > > > earlier i used
> >
> > >http://api.twitter.com/version/statuses/friends.formathttp://api.twit.
> ..
> >
> > > > API's to fecth the Followers and following people list. But now they
> > > > are depricated.
> >
> > > > Now i want to use the API's
> >
> > >http://api.twitter.com/version/friends/ids.formathttp://api.twitter.c.
> ..
> >
> > > > to fetch the ID's of the follower and following people Id's and
> >
> > > >http://api.twitter.com/version/users/lookup.formatAPI to get the
> > > > user List.
> >
> > > > Now My problem is that i want to fetch the Specific number (as per my
> > > > requirement it is 16) of follower and following id's using the above
> > > > two API's (friends/ids.format and followers/ids.format).
> >
> > > > But these two API's ignoring the "count" Parameter (suppose if i sent
> > > > a request to fetch the followers of the user = sachin_rt
> >
> > > >
> http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rt&cur...
> >
> > > > it is ignoring the count parameterand returning an amount "5000"
> > > > followers ID's.
> > > > )
> >
> > > > and returning a huge number of Id's. As i am developing a mobile app
> i
> > > > don't want to store this amount of data in my database until user go
> > > > for "showmore"/ or scroll to the bottom of the list.
> >
> > > > please let me know is there any solution to fetch the specific number
> > > > of ID's of the followers/follwing.
> >
> > > > Thanks in AdvanceKamesh
> >
> > > --
> > > Twitter developer documentation and resources:
> https://dev.twitter.com/doc
> > > API updates via Twitter:https://twitter.com/twitterapi
> > > Issues/Enhancements Tracker:
> > >https://code.google.com/p/twitter-api/issues/list
> > > Change your membership to this group:
> > >https://groups.google.com/forum/#!forum/twitter-development-talk
>
> --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Re: [twitter-dev] Hey...Hows Everyone Doing...Im John :)

[Scott Wilcox]

http://dev.twitter.com/doc has the API documentation.

If you state the platform you'll be developing on then people will provide you 
with libraries to use and more information.

On 15 Jun 2011, at 00:46, vpurplehaze4...@hotmail.co.uk wrote:

> Ok boys now i've introduced myself i am looking for some help if
> possiblei haven't done coding in years but i have thought of a
> project i would like to do...if anyone could point me in the right
> direction for material so i can do a quick refresh it would be
> appreciated :)
> 
> Thanks
> 
> vPurpleHaze420v

--
Scott Wilcox

@dordotky | sc...@dor.ky | http://dor.ky
+44 (0) 7538 842418 | +1 (646) 827-0580



-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Hey...Hows Everyone Doing...Im John :)

[vpurplehaze4...@hotmail.co.uk]

Ok boys now i've introduced myself i am looking for some help if
possiblei haven't done coding in years but i have thought of a
project i would like to do...if anyone could point me in the right
direction for material so i can do a quick refresh it would be
appreciated :)

Thanks

vPurpleHaze420v

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

[Amit Battan Ror]

one more issue /... as I want to get the list of my all follower
But I seen in some discussion as this API not return all the friends.
It only return the recently updated friends with there status.
Is it?
and what is the API which I want?



On Jun 14, 5:04 pm, Bill Jacobson  wrote:
> Amit,
>
> Your endpoint is obsolete and no longer supported by Twitter. That's why
> you got the 403. Statuses/followers will succeed if you change it 
> tohttp://api.twitter.com/1/statuses/followers.xml
> 
>
> BUT this API is deprecated. Read all about it 
> here:http://dev.twitter.com/doc/get/statuses/followers
>
> Bill
>
> On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
>
>
>
>
>
>
>
> > Bill
>
> > Working fine :https://twitter.com/statuses/friends_timeline.xml
>
> > Not Working Giving 403 Error :https://twitter.com/statuses/followers.xml
>
> > On Jun 14, 10:14 am, Amit Battan Ror  wrote:
> >> Thanks Bill
>
> >> I will check and try to track URL ..
>
> >> On Jun 13, 9:07 pm, Bill Jacobson  wrote:
>
> >>> Amit, also 
> >>> seehttp://www.mailinglistarchive.com/html/twitter-development-talk@googl
> >>> That's what helped me.
> >>> -Bill
> >>> On 06/13/2011 10:44 AM, Bill Jacobson wrote:
>  I'm suggesting that you find out what endpoint (Twitter URL) your app
>  is targeting, and make sure that it matches what is currently
>  documented. If it doesn't match, correct it. That's what worked for me.
>  On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
> > I am not getting the solution.
> > and my API was working fine beofre 2 3 days..
> > but not now..
> > all other API except getFollowersIncludingCurrentStatus working ok and
> > return proper output
> > On Jun 13, 5:53 pm, Bill Jacobson    wrote:
> >> Amit,
> >> I don't know your library, but in my case the 403 was accompanied by
> >> the
> >> message "Not authorized to use this endpoint" and the solution was to
> >> update to "http://api.twitter.com/1[etc.]";.
> >> Bill Jacobson
> >> On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
> >>> any idea guys
> >>> On Jun 10, 4:33 pm, Amit Battan Ror      wrote:
>  Hi All
>  I am using
>  Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone
>  I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for
>  getting my friend list which was working fine. But from last two days
>  its giving me the 403 error.
>  -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with
>  error: Error Domain=HTTP Code=403 "The operation couldn t be
>  completed. (HTTP error 403.)"
>  As twitter api wiki 403 is due to crossing the limit of updates
>  and DM
>  but here in getFollowersIncludingCurrentStatus Why this error
>  occurring and even list is not comes next day giving same 403 error.
>  Thanks
>  Amit Battan

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine

[Amit Battan Ror]

thanks Bill

it is solved now
I change
#define TWITTER_DOMAIN @"twitter.com"
to
#define TWITTER_DOMAIN @"api.twitter.com/1"
in MGTwitterEngine.m


Amit Battan

On Jun 14, 5:04 pm, Bill Jacobson  wrote:
> Amit,
>
> Your endpoint is obsolete and no longer supported by Twitter. That's why
> you got the 403. Statuses/followers will succeed if you change it 
> tohttp://api.twitter.com/1/statuses/followers.xml
> 
>
> BUT this API is deprecated. Read all about it 
> here:http://dev.twitter.com/doc/get/statuses/followers
>
> Bill
>
> On 06/14/2011 12:38 AM, Amit Battan Ror wrote:
>
>
>
>
>
>
>
> > Bill
>
> > Working fine :https://twitter.com/statuses/friends_timeline.xml
>
> > Not Working Giving 403 Error :https://twitter.com/statuses/followers.xml
>
> > On Jun 14, 10:14 am, Amit Battan Ror  wrote:
> >> Thanks Bill
>
> >> I will check and try to track URL ..
>
> >> On Jun 13, 9:07 pm, Bill Jacobson  wrote:
>
> >>> Amit, also 
> >>> seehttp://www.mailinglistarchive.com/html/twitter-development-talk@googl
> >>> That's what helped me.
> >>> -Bill
> >>> On 06/13/2011 10:44 AM, Bill Jacobson wrote:
>  I'm suggesting that you find out what endpoint (Twitter URL) your app
>  is targeting, and make sure that it matches what is currently
>  documented. If it doesn't match, correct it. That's what worked for me.
>  On 06/13/2011 08:05 AM, Amit Battan Ror wrote:
> > I am not getting the solution.
> > and my API was working fine beofre 2 3 days..
> > but not now..
> > all other API except getFollowersIncludingCurrentStatus working ok and
> > return proper output
> > On Jun 13, 5:53 pm, Bill Jacobson    wrote:
> >> Amit,
> >> I don't know your library, but in my case the 403 was accompanied by
> >> the
> >> message "Not authorized to use this endpoint" and the solution was to
> >> update to "http://api.twitter.com/1[etc.]";.
> >> Bill Jacobson
> >> On 06/13/2011 05:39 AM, Amit Battan Ror wrote:
> >>> any idea guys
> >>> On Jun 10, 4:33 pm, Amit Battan Ror      wrote:
>  Hi All
>  I am using
>  Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone
>  I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for
>  getting my friend list which was working fine. But from last two days
>  its giving me the 403 error.
>  -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with
>  error: Error Domain=HTTP Code=403 "The operation couldn t be
>  completed. (HTTP error 403.)"
>  As twitter api wiki 403 is due to crossing the limit of updates
>  and DM
>  but here in getFollowersIncludingCurrentStatus Why this error
>  occurring and even list is not comes next day giving same 403 error.
>  Thanks
>  Amit Battan

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] request with json format are not up to date

[boblefrag]

It seeems that twitter experience problems with json format :

When I try to request for exemple
http://api.twitter.com/1/users/show.json?screen_name=tremarthuro, it says
that I have 2 followers (this is untrue)
but if I request
http://api.twitter.com/1/users/show.xml?screen_name=tremarthuro it display
the right infos

Is this a bug ? Is there a bugfix ?

Thanks for your answers

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

[twitter-dev] Re: Problem With Fetching Followers and Following Id's

[kamesh SmartDude]

to whom should we write for this particular issue

//kamesh

On Jun 14, 12:26 pm, Georgooty varghese  wrote:
> I am facing the same issue..
>
> On Tue, Jun 14, 2011 at 11:56 AM, kamesh SmartDude <
>
>
>
>
>
>
>
> kamesh.smartd...@gmail.com> wrote:
> > Is Anybody have IDEA about the solution of above problem
>
> > //kamesh
>
> > On Jun 13, 12:49 pm, kamesh SmartDude 
> > wrote:
> > > Dear All,
>
> > > I am developing a twitter mobile application, and i have a problem in
> > > fetching the followers and following list.
>
> > > earlier i used
>
> >http://api.twitter.com/version/statuses/friends.formathttp://api.twit...
>
> > > API's to fecth the Followers and following people list. But now they
> > > are depricated.
>
> > > Now i want to use the API's
>
> >http://api.twitter.com/version/friends/ids.formathttp://api.twitter.c...
>
> > > to fetch the ID's of the follower and following people Id's and
>
> > >http://api.twitter.com/version/users/lookup.formatAPI to get the
> > > user List.
>
> > > Now My problem is that i want to fetch the Specific number (as per my
> > > requirement it is 16) of follower and following id's using the above
> > > two API's (friends/ids.format and followers/ids.format).
>
> > > But these two API's ignoring the "count" Parameter (suppose if i sent
> > > a request to fetch the followers of the user = sachin_rt
>
> > >http://api.twitter.com/1/followers/ids.json/screen_name=sachin_rt&cur...
>
> > > it is ignoring the count parameterand returning an amount "5000"
> > > followers ID's.
> > > )
>
> > > and returning a huge number of Id's. As i am developing a mobile app i
> > > don't want to store this amount of data in my database until user go
> > > for "showmore"/ or scroll to the bottom of the list.
>
> > > please let me know is there any solution to fetch the specific number
> > > of ID's of the followers/follwing.
>
> > > Thanks in AdvanceKamesh
>
> > --
> > Twitter developer documentation and resources:https://dev.twitter.com/doc
> > API updates via Twitter:https://twitter.com/twitterapi
> > Issues/Enhancements Tracker:
> >https://code.google.com/p/twitter-api/issues/list
> > Change your membership to this group:
> >https://groups.google.com/forum/#!forum/twitter-development-talk

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk